From: "Justin P. Mattock" <justinmattock@gmail.com>
To: piotr@hosowicz.com
Cc: Randy Dunlap <rdunlap@xenotime.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: What's up with wireless drivers?
Date: Sat, 22 May 2010 06:44:58 -0700 [thread overview]
Message-ID: <4BF7DFDA.3000604@gmail.com> (raw)
In-Reply-To: <4BF7DEE7.9010801@example.com>
On 05/22/2010 06:40 AM, Piotr Hosowicz wrote:
> On 22.05.2010 15:35, Justin P. Mattock wrote:
>> On 05/22/2010 06:13 AM, Piotr Hosowicz wrote:
>>> On 22.05.2010 14:43, Piotr Hosowicz wrote:
>>>> On 22.05.2010 10:40, Piotr Hosowicz wrote:
>>>>> On 22.05.2010 00:20, Piotr Hosowicz wrote:
>>>>>> On 22.05.2010 00:12, Randy Dunlap wrote:
>>>>>>> On Fri, 21 May 2010 23:31:28 +0200 Piotr Hosowicz wrote:
>>>>>>>
>>>>>>>> On 21.05.2010 23:21, Piotr Hosowicz wrote:
>>>>>>>>> On 21.05.2010 23:07, John W. Linville wrote:
>>>>>>>>>> On Fri, May 21, 2010 at 10:53:56PM +0200, Piotr Hosowicz wrote:
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I try to build kernel from git source. Now n-th build try is
>>>>>>>>>>> performing, each time it failed on wireless drivers - Atheros,
>>>>>>>>>>> Marvel etc. Did I miss something?
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Piotr Hosowicz
>>>>>>>>>>
>>>>>>>>>> Perhaps you should post your actual output from the build
>>>>>>>>>> failure?
>>>>>>>>>
>>>>>>>>> I dont have it right now, I disabled wireless at all and started
>>>>>>>>> build.
>>>>>>>>> The output to the console was make-kpkg ordinary message - saying
>>>>>>>>> that
>>>>>>>>> sub build finished with error code 2 AFAIR, it stopped each
>>>>>>>>> time on
>>>>>>>>> wireless drivers.
>>>>>>>>
>>>>>>>> Zonk! It seems that the problem is not only with wireless, now it
>>>>>>>> broke
>>>>>>>> here:
>>>>>>>>
>>>>>>>> (snip)
>>>>>>>> CC [M] drivers/net/usb/int51x1.o
>>>>>>>> CC [M] drivers/net/usb/cdc-phonet.o
>>>>>>>> CC [M] drivers/net/wan/lmc/lmc_media.o
>>>>>>>> CC [M] drivers/net/wan/lmc/lmc_main.o
>>>>>>>> CC [M] drivers/net/wan/wanxl.o
>>>>>>>> CC [M] drivers/net/usb/ipheth.o
>>>>>>>> LD [M] drivers/net/wan/cyclomx.o
>>>>>>>> CC [M] drivers/net/usb/sierra_net.o
>>>>>>>> CC [M] drivers/net/wan/lmc/lmc_proto.o
>>>>>>>> LD [M] drivers/net/wan/lmc/lmc.o
>>>>>>>> make[1]: Opuszczenie katalogu
>>>>>>>> `/usr/src/linus/linux-2.6-20100521-2044'
>>>>>>>> make: *** [debian/stamp/build/kernel] Błąd 2
>>>>>>>>
>>>>>>>> Opuszczenie katalogu `/usr/src/linus/linux-2.6-20100521-2044' is
>>>>>>>> "leaving directory", Błąd is error.
>>>>>>>
>>>>>>> That still doesn't show the actual error/problem message...
>>>>>>
>>>>>> Because there was no other messages, maybe Debian make-kpkg mutes
>>>>>> them
>>>>>> some way. I can try tommorrow the classic linux way and test it. I
>>>>>> attach botching config.
>>>>>
>>>>> I git-pulled and have run build with make-kpkg --verbose, again
>>>>> failed.
>>>>> This is the tail of the output:
>>>>>
>>>>
>>>> (snip)
>>>>
>>>> I tried git8 from kernel.org and the make-kpkg build fails on iwlwifi.
>>>> I'll give up for today I think.
>>>
>>> I gave it one more try and it failed again like in my first post
>>> yesterday:
>>>
>>> CC [M] drivers/net/wireless/rtl818x/rtl8187_rtl8225.o
>>> CC [M] drivers/net/wireless/zd1211rw/zd_usb.o
>>> CC [M] drivers/net/wireless/rtl818x/rtl8187_leds.o
>>> CC [M] drivers/net/wireless/rtl818x/rtl8187_rfkill.o
>>> LD [M] drivers/net/wireless/rtl818x/rtl8180.o
>>> LD [M] drivers/net/wireless/rtl818x/rtl8187.o
>>> LD [M] drivers/net/wireless/ath/ath9k/ath9k_hw.o
>>> LD [M] drivers/net/wireless/ath/ath9k/ath9k_common.o
>>> LD [M] drivers/net/wireless/ath/ath9k/ath9k_htc.o
>>> LD [M] drivers/net/wireless/ath/ath.o
>>> LD [M] drivers/net/wireless/zd1211rw/zd1211rw.o
>>> make[1]: Opuszczenie katalogu `/usr/src/linux-2.6.34-git8'
>>> make: *** [debian/stamp/build/kernel] Błąd 2
>>>
>>> zd1211rw is in wireless Zydas device driver, behaves like yesterday
>>>
>>> I am giving up for a time being or may be someone will help me here.
>>>
>>> Regards,
>>>
>>> Piotr Hosowicz
>>>
>>
>>
>> not sure whats happening and/or how debian is
>> building the kernel, but can you try
>> make V=1 so there is more of a verbose message
>> on the screen of whats breaking.
>
> This is the same what --verbose make-kpkg switch is doing and I've tried
> that and posted result here.
>
> Regards,
>
> Piotr Hosowicz
>
what about strace make
(maybe will give you info)
Justin P. Mattock
next prev parent reply other threads:[~2010-05-22 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 20:53 What's up with wireless drivers? Piotr Hosowicz
2010-05-21 21:07 ` John W. Linville
2010-05-21 21:21 ` Piotr Hosowicz
2010-05-21 21:31 ` Piotr Hosowicz
2010-05-21 22:12 ` Randy Dunlap
2010-05-21 22:20 ` Piotr Hosowicz
2010-05-22 8:40 ` Piotr Hosowicz
2010-05-22 12:43 ` Piotr Hosowicz
2010-05-22 13:13 ` Piotr Hosowicz
2010-05-22 13:35 ` Justin P. Mattock
2010-05-22 13:40 ` Piotr Hosowicz
2010-05-22 13:44 ` Justin P. Mattock [this message]
2010-05-22 14:04 ` Piotr Hosowicz
2010-05-22 14:17 ` Justin P. Mattock
2010-05-22 14:21 ` Piotr Hosowicz
2010-05-23 13:54 ` Piotr Hosowicz
2010-05-23 17:50 ` Jiri Slaby
2010-05-23 18:28 ` Piotr Hosowicz
2010-05-23 21:53 ` Randy Dunlap
2010-05-24 2:54 ` Piotr Hosowicz
2010-05-23 17:53 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF7DFDA.3000604@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=piotr@hosowicz.com \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).