On Fri, 09 Oct 2009 01:07:49 PDT, [email protected] said:
> The mm-of-the-moment snapshot 2009-10-09-01-07 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
Broke my iwl3945 wireless card:
Good (2.6.31-mmotm0917)
Oct 8 09:55:33 turing-police kernel: [ 0.809101] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
Oct 8 09:55:33 turing-police kernel: [ 0.809106] iwl3945: Copyright(c) 2003-2009 Intel Corporation
Oct 8 09:55:33 turing-police kernel: [ 0.809201] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Oct 8 09:55:33 turing-police kernel: [ 0.879463] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Oct 8 09:55:33 turing-police kernel: [ 0.879466] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
...
Oct 8 09:55:35 turing-police kernel: [ 31.599751] iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
Oct 8 09:55:35 turing-police kernel: [ 31.697046] iwl3945 0000:0c:00.0: loaded firmware version 15.28.2.8
Oct 8 09:55:35 turing-police kernel: [ 31.777214] Registered led device: iwl-phy0::radio
Oct 8 09:55:35 turing-police kernel: [ 31.777430] Registered led device: iwl-phy0::assoc
Oct 8 09:55:35 turing-police kernel: [ 31.777545] Registered led device: iwl-phy0::RX
Oct 8 09:55:35 turing-police kernel: [ 31.777676] Registered led device: iwl-phy0::TX
Oct 8 09:55:35 turing-police kernel: [ 31.789446] ADDRCONF(NETDEV_UP): wlan0: link is not ready
(and then wpa-supplicant is able to bring the card up when it finally gets launched by initscripts)
Bad 2.6.32-rc3-mmotm1009:
Oct 9 13:50:19 turing-police kernel: [ 0.931788] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
Oct 9 13:50:19 turing-police kernel: [ 0.944678] iwl3945: Copyright(c) 2003-2009 Intel Corporation
Oct 9 13:50:19 turing-police kernel: [ 0.957831] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Oct 9 13:50:19 turing-police kernel: [ 1.038946] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Oct 9 13:50:19 turing-police kernel: [ 1.038950] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
We never see the firmware load request, and of course everything goes
pear-shaped after that doesn't happen....
Kernel is built with:
% zgrep -i iwl /proc/config.gz
CONFIG_IWLWIFI=y
CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT=y
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLWIFI_DEVICE_TRACING=y
# CONFIG_IWLAGN is not set
CONFIG_IWL3945=y
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
On Sat, 2009-10-10 at 08:12 +0800, [email protected] wrote:
> On Fri, 09 Oct 2009 01:07:49 PDT, [email protected] said:
> > The mm-of-the-moment snapshot 2009-10-09-01-07 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
>
> Broke my iwl3945 wireless card:
>
> Good (2.6.31-mmotm0917)
> Oct 8 09:55:33 turing-police kernel: [ 0.809101] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
> Oct 8 09:55:33 turing-police kernel: [ 0.809106] iwl3945: Copyright(c) 2003-2009 Intel Corporation
> Oct 8 09:55:33 turing-police kernel: [ 0.809201] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> Oct 8 09:55:33 turing-police kernel: [ 0.879463] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
> Oct 8 09:55:33 turing-police kernel: [ 0.879466] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
> ...
> Oct 8 09:55:35 turing-police kernel: [ 31.599751] iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
> Oct 8 09:55:35 turing-police kernel: [ 31.697046] iwl3945 0000:0c:00.0: loaded firmware version 15.28.2.8
> Oct 8 09:55:35 turing-police kernel: [ 31.777214] Registered led device: iwl-phy0::radio
> Oct 8 09:55:35 turing-police kernel: [ 31.777430] Registered led device: iwl-phy0::assoc
> Oct 8 09:55:35 turing-police kernel: [ 31.777545] Registered led device: iwl-phy0::RX
> Oct 8 09:55:35 turing-police kernel: [ 31.777676] Registered led device: iwl-phy0::TX
> Oct 8 09:55:35 turing-police kernel: [ 31.789446] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> (and then wpa-supplicant is able to bring the card up when it finally gets launched by initscripts)
>
> Bad 2.6.32-rc3-mmotm1009:
>
> Oct 9 13:50:19 turing-police kernel: [ 0.931788] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
> Oct 9 13:50:19 turing-police kernel: [ 0.944678] iwl3945: Copyright(c) 2003-2009 Intel Corporation
> Oct 9 13:50:19 turing-police kernel: [ 0.957831] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> Oct 9 13:50:19 turing-police kernel: [ 1.038946] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
> Oct 9 13:50:19 turing-police kernel: [ 1.038950] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
>
> We never see the firmware load request, and of course everything goes
> pear-shaped after that doesn't happen....
The firmware loading happens when the user space brings the interface
up. Can you check NM is running for the bad case?
Thanks,
-yi
On Sat, 10 Oct 2009 08:42:35 +0800, Zhu Yi said:
> The firmware loading happens when the user space brings the interface
> up. Can you check NM is running for the bad case?
I'm not using NM, because I've never figured out how to get it to DTRT for
my network config, so I run wpa_supplicant directly. It's looking like
a bad update to dbus was the actual root cause.
(Did I mention how I loath dbus? Or at least the fact that if it breaks,
everything from wireless to pulseaudio immediately craps out too. That and
'hald' are my two favorite "only on this laptop because stuff refuses to
work without them"....)