Wireless for iwl3945 still broken

[saniac]

I have upgraded from gutsy to hardy. Have installed linux-backports-modules. However, NetworkManager shows no wireless networks.

stephen@lung:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[saniac (stephen-vital)]

PS, iwl3945 appears to be the latest version:

stephen@lung:~$ modinfo iwl3945
filename: /lib/modules/2.6.24-16-generic/updates/wireless/iwlwifi/iwlwifi/compatible/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2007 Intel Corporation
version: 1.2.25
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
srcversion: FDE2E62843DE3ED112A50C3
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
depends: led-class,iwlwifi_mac80211
vermagic: 2.6.24-16-generic SMP mod_unload 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: hwcrypto:using hardware crypto engine (default 0 [software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

[UdZq3tDn (udzq3tdn-deactivatedaccount)]

I'm having the same problem with my "Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)" wireless card as well.

[satet (order-regis)]

I have the same problem with iwl3945 on a Tecra A8. The result from "modinfo iwl3945" is identical to saniac except I have:
vermagic: 2.6.24-17-generic SMP mod_unload 586.
This is on a clean install of Hardy with linux-backport-modules installed. The results from iwconfig for saniac and me are identical.

[Rami Al-Rfou' (rmyeid)]

I think it was fixed by an informal hack
try to look @
http://linuxexpert.wordpress.com/2008/04/28/fix-intel-wireless-driver-on-hardy/

On Sun, May 4, 2008 at 8:16 PM, satet <email address hidden> wrote:

> I have the same problem with iwl3945 on a Tecra A8. The result from
> "modinfo iwl3945" is identical to saniac except I have:
> vermagic: 2.6.24-17-generic SMP mod_unload 586.
> This is on a clean install of Hardy with linux-backport-modules installed.
> The results from iwconfig for saniac and me are identical.
>
> --
> Wireless for iwl3945 still broken
> https://bugs.launchpad.net/bugs/220734
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Ramy Eid
Mobile: [phone]
rmyeid.blogspot.com
/'_|/

[saniac (stephen-vital)]

Ramy's suggestion does not work for me, I'm afraid.

[Rami Al-Rfou' (rmyeid)]

please, can you attach the output of
lspci -vvnn
lsmod
dmesg | tail
iwlist scanning

On Sun, May 4, 2008 at 10:44 PM, saniac <email address hidden> wrote:

> Ramy's suggestion does not work for me, I'm afraid.
>
> --
> Wireless for iwl3945 still broken
> https://bugs.launchpad.net/bugs/220734
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Ramy Eid
Mobile: [phone]
rmyeid.blogspot.com
/'_|/

[saniac (stephen-vital)]

$ iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

[saniac (stephen-vital)]

Stuff from dmesg:

[128922.119721] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
[129356.278416] ACPI: PCI interrupt for device 0000:03:00.0 disabled
[129416.606056] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.25
[129416.606065] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[129416.607863] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[129416.607891] PCI: Setting latency timer of device 0000:03:00.0 to 64
[129416.607930] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[129416.651463] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[129416.865710] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[129417.005887] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[129417.011236] Registered led device: iwl-phy0:RX
[129417.011276] Registered led device: iwl-phy0:TX
[129417.015689] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[129506.678987] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[129506.725776] Registered led device: iwl-phy0:RX
[129506.725812] Registered led device: iwl-phy0:TX
[129506.732208] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[175667.463829] usb 5-5: new high speed USB device using ehci_hcd and address 12
[175667.847111] usb 5-5: configuration #1 chosen from 1 choice

[UdZq3tDn (udzq3tdn-deactivatedaccount)]

Attached are the outputs of the four commands.

[Andy (andy-xillean)]

Same problem here on an HP NX6310
 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

I installed the linux-backports-modules. Wireless networks don't show up in network manager
until about 10-20 minutes after a reboot. Sometimes wireless networks don't show up at all.
Once they show up and a connection is made then the connection is quite solid.

[UdZq3tDn (udzq3tdn-deactivatedaccount)]

Ok I have a feeling I misunderstood the original bug. My wireless doesn't show up as wireless, it shows up as wired but otherwise works fine.

Is this the same problem you are having, or is yours not working at all?

I have filed another bug for my specific problem. So you may have to disregard all my previous comments as irrelevant! D'oh!

[saniac (stephen-vital)]

I am sorry to report that this problem has gone away for me, but I'm not sure what I did to fix it.

I did two things which might have made a difference:
- changed my router's configuration to use WPA and TKIP rather than WPA2 and AES
- took the interface out of "roaming mode" using nmapplet's "manual configuration" option

My hypothesis is that immediately after Hardy upgrade, there was a problem with iwl3945. In trying to resolve it I used nmapplet's "manual configuration" option to take the interface out of roaming mode and explicitly specify what options to use. In a subsequent upgrade, I got the new backports package, but because I was still using manual configuration, it didn't work?

If I can think of a way to replicate this issue properly, I'll post it here.

[Leann Ogasawara (leannogasawara)]

Hi Saniac,

Thanks for the updates. Since you are the original bug reporter I'm going to close this report for now since you are no longer experiencing this issue. If you are able to narrow down how to reproduce this issue, please let us know by reopening this report (ie change the Status back to New). Thanks.

[Leann Ogasawara (leannogasawara)]

Hi .bg - I'm not sure why you opened the linux-ubuntu-modules-2.6.24 task for this bug. You didn't leave any comment. I'm going to close it for now. If you or anyone else is still experiencing issues, please open a new report.

Additionally, it would be best to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10. You should be able to test via a LiveCD - http://www.ubuntu.com/testing. If the issue still exists, per the kernel team's bug policy, please attach the following information in your new report. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies .

And finally, also note that beginning with the Intrepid Ibex 8.10 development cycle the linux-ubuntu-modules package was actually merged with the linux kernel package. Going forward, bugs that would have been reported against linux-ubuntu-modules should now just be reported against linux. So please be sure to file your bug against the 'linux' package. Thanks.

[Leann Ogasawara (leannogasawara)]

I'm not sure why the status of this bug was set back to "New"? If someone reopened this, please post a comment why and also provide up to date debugging information. Thanks.