Wireless stopped working - ipw3945: Detected geography ABG on kernel 2.6.20-16-generic

[Andy Leeman]

    Wireless on my Dell 1520 laptop with ipw3945 worked perfect for the first week, then became flakey for a day, then stopped altogether around the first week of August 2007. Driver is loaded, NM sees the ap's fine but will not connect to any, encrypted or otherwise. I get the message ' ADDRCONF(NETDEV_UP): eth1: link is not ready ' in syslog whenever I try and connect. As well, the syslog is fill of ' ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)' I have attached the dmesg.log from boot to when it tries to connect and fails. as well as dmesg1.log which is additional logging after I tried to pick an AP, then plugged in wired connection.
   One other odd thing is that the wireless on this machine worked with the PCLinuxOS live CD when I first got it. The 7.04 live CD doesn't work on these Dells, see http://ubuntuforums.org/showthread.php?t=501195 for more info. Anyway, when wireless stopped with Ubuntu, it stopped working with the PCLOS CD as well. The ipw3945 card itself is fine, I've tried it in an Acer with Vista and 7.04 and both were fine.

[Andy Leeman (andy-leeman)]

dmesg.log from boot to failure to connect

[Andy Leeman (andy-leeman)]

dmesg1.log from connection attempt and failure to plug in wired

[Andy Leeman (andy-leeman)]

lspci -vvnn

[Andy Leeman (andy-leeman)]

uname -a

[Andy Leeman (andy-leeman)]

version.log attached.

I should also mention that output from iwlist scan and iwconfig both seem normal, but I can attach them too, if requirered.

[Andy Leeman (andy-leeman)]

See ubuntu forums for more info. There's a lot of related bugs, but others seem to be able to get it working occassionally, so I didn't want to add to an existing bug if the symptoms were different.

http://ubuntuforums.org/showthread.php?t=530352
http://ubuntuforums.org/showthread.php?t=533331
http://ubuntuforums.org/showthread.php?t=525152

[Sergey V. Udaltsov (sergey-udaltsov)]

Same here, compaq nx7400. Very annoying. Extremely.

[Andy Leeman (andy-leeman)]

Unfortunately, I'm getting similar situation with Gutsy too

On 10/24/07, Sergey V. Udaltsov <email address hidden> wrote:
>
> Same here, compaq nx7400. Very annoying. Extremely.
>
> --
> Wireless stopped working - ipw3945: Detected geography ABG on kernel
> 2.6.20-16-generic
> https://bugs.launchpad.net/bugs/139642
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Andy Leeman
Londonderry, NS

[Eros Zanchetta (eros)]

Same problem here on a Toshiba A100-317, cannot rmmod ipw3945 or kill processes. The only solution is rebooting, and it doesn't always work.

Extremely annoying. This bug has been out there for a while and it's still marked as undecided, anything I can do to help identify the problem and get it fixed?

[Andy Leeman (andy-leeman)]

The bugis fixed in Gutsy with the new driver. At least on my dell. Are you
still using Feisty? You could upgrade.

On 12/11/07, eros <email address hidden> wrote:
>
> Same problem here on a Toshiba A100-317, cannot rmmod ipw3945 or kill
> processes. The only solution is rebooting, and it doesn't always work.
>
> Extremely annoying. This bug has been out there for a while and it's
> still marked as undecided, anything I can do to help identify the
> problem and get it fixed?
>
> --
> Wireless stopped working - ipw3945: Detected geography ABG on kernel
> 2.6.20-16-generic
> https://bugs.launchpad.net/bugs/139642
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Andy Leeman
Londonderry, NS

[Eros Zanchetta (eros)]

Nope, I'm using Gutsy (2.6.22-14-generic). I attach the relevant part of my dmesg

[Eros Zanchetta (eros)]

Also, the problem seems more evident on networks using encryption (I never experienced it when on an unprotected network, but I don't use unprotected networks very often so it may just be that the behaviour is completely random).

[Andy Leeman (andy-leeman)]

Mine did not immediately work in Gutsy. I blacklisted IPV6 and installed all
updates over a wired connection before mine worked. I'm not sure if the IPV6
had anything to do with it.

On 12/11/07, eros <email address hidden> wrote:
>
> Nope, I'm using Gutsy (2.6.22-14-generic). I attach the relevant part of
> my dmesg
>
> ** Attachment added: "dmesg"
> http://launchpadlibrarian.net/10841310/dmesg
>
> --
> Wireless stopped working - ipw3945: Detected geography ABG on kernel
> 2.6.20-16-generic
> https://bugs.launchpad.net/bugs/139642
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Andy Leeman
Londonderry, NS

[Eros Zanchetta (eros)]

Sounds promising: how did you blacklist IPV6? (my system is already up to date)

[Andy Leeman (andy-leeman)]

In a terminal;
sudo gedit /etc/modprobe.d/blacklist

Then add;
#still trying to fix the gd wireless (or some other comment so you remember
why it was done)
blacklist ipv6

to the end of the file and save. then i restarted.

On 12/11/07, eros <email address hidden> wrote:
>
> Sounds promising: how did you blacklist IPV6? (my system is already up
> to date)
>
> --
> Wireless stopped working - ipw3945: Detected geography ABG on kernel
> 2.6.20-16-generic
> https://bugs.launchpad.net/bugs/139642
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Andy Leeman
Londonderry, NS

[Eros Zanchetta (eros)]

Yep, that did the trick (at least I think it did since it started working immediately after restarting).

Thanks a lot, Andy!

[Andy Leeman (andy-leeman)]

No prob, man. I know how frustrating it is. I went from The end of July when
I got my laptop until gutsy was released in Oct with no wifi. Man, I tried
EVERYTHING!!! :)

On 12/11/07, eros <email address hidden> wrote:
>
> Yep, that did the trick (at least I think it did since it started
> working immediately after restarting).
>
> Thanks a lot, Andy!
>
> --
> Wireless stopped working - ipw3945: Detected geography ABG on kernel
> 2.6.20-16-generic
> https://bugs.launchpad.net/bugs/139642
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Andy Leeman
Londonderry, NS