ipw2200 - Wireless network disconnects randomly, won't reconnect

[Endolith]

My computer occasionally disconnects from my wireless router, and I can't get it to reconnect unless I reboot. It used to work completely fine. Something has been changed in the last month or two to make it stop working and I have no idea where to look.

Two times it has disconnected around the same time, 8:15 in the morning, which is suspicious. I don't know of any event at that time that would cause that.

Logs show things like:

    WPA: 4-Way Handshake failed - pre-shared key may be incorrect

though the key is correct. I also saw this:

   ipw2200: Firmware error detected. Restarting.

[Philip Wyett (philwyett)]

What release of Ubuntu are you using?

[Jonathan Schuster (jschuster)]

Are you running NetworkManager Applet, or some other network manager app like that, and if so, what version?

[Mike McCune (mjmccune-gmail)]

Also, which wifi car and drivers are you using? This can be found in the output of lsmod. Please post the entire output of lsmod if you don't know which wifi driver you are using.

[Endolith (endolith)]

Ubuntu 8.10
  Main, Universe, Restricted, Multiverse enabled
  Security, Updates, Proposed, Backports enabled
  FreeNX PPA, OpenOffice PPA, and Medibuntu repositories

Dell Inspiron 8600
  Intel® PRO/Wireless 2915ABG
  ipw2200
  WPA2 with DD-WRT on the other end

NetworkManager applet

It happened again around 8 am, so something stupid is going on.

[Endolith (endolith)]

I upgraded my router from DD-WRT to Tomato a few weeks ago and this hasn't happened since. I have no idea what caused it. I ran DD-WRT for about two years with this card without this problem, and I don't know what I would have changed to cause it.

[Endolith (endolith)]

More info:

* running sudo service networking restart doesn't help
* killing nm-applet and restarting doesn't help
* killing NetworkManager and restarting doesn't help
* punching the wall doesn't help

[Endolith (endolith)]

Plugging in a cable between the laptop and the router works fine. Wireless doesn't connect until I reboot.

[Endolith (endolith)]

(Oh wait, this is an older bug.) The symptoms are the same and it's on the same hardware, so I guess I'll keep it.

Since upgrading to Jaunty the problem has reappeared. Several other users experience the same thing:

http://ubuntuforums.org/showthread.php?t=1186754

I am in Jaunty with the same Inspiron / Intel hardware, same Tomato router (Version 1.25 in a Buffalo WHR-HP-G54).

It will work fine for hours, maybe even days, and then suddenly disconnect and refuse to reconnect. Logging out and logging in doesn't help, turning off wi-fi in hardware doesn't work.

nm-applet repeatedly tries to reconnect and nothing happens. The only thing I can figure out is to reboot.

[Endolith (endolith)]

Security is WPA2 Personal AES

[Tony Espy (awe)]

Sounds like a driver and/or hardware issue to me, *not* a NetworkManager bug.

If nm-applet is trying to re-connect, then that means Network Manager saw the disconnect and is trying to do the right thing...but since the driver / firmware on the card is in a bad state, all bets are off.

A few other questions... does the same problem occur if you use your router's default image? Does it occur with other access points? Do you always see the firmware error log message when it happens?

[Leaman Crews (leamanc)]

Dell Inspiron 1720 with Broadcom Wi-Fi b/g/n card. Access point is Apple AirPort Extreme 802.11b/g/n, WPA2 security. Worked fine on Ubuntu 8.04 and 8.10. Tested with neighbor's totally open Linksys 802.11b/g, problem also occurs.

As others have said, simple reboot does not work. You must shut down and then power on again. Disconnects are very random; it could go for four hours or four minutes before disconnects start.

Using the router's defaults make no difference. Yes, the firmware error is always in the log when the disconnect happens.

Very frustrating! I love 9.04 other than this. There are four other Mac laptops, one Dell XP laptop, and two iPhones in the house that maintain rock solid connections.

Hope this helps and that this bug can be addressed somehow. I would say it has to be a driver issue. Any way to revert to an older wl driver?

[Endolith (endolith)]

Is there any way to completely restart networking without restarting the whole computer?

[jenku (jenku)]

I also suffer from random wifi disconnects under 9.04. I first thought it was USB related as I am normally using a DWL122 network adapter, but I tried a PCMCIA adapter instead and it disconnected as well.
Anyway after I lost connection I need to reboot in order to make it work again.

[Josta (grizzy7)]

Same thing... I have a D-Link WDA 2320 Desktop card.... Jaunty has been awesome, other than this issue - it only took me two tries to make my ATI card play nice! ^_^

[Endolith (endolith)]

Does anyone have any idea how to troubleshoot this? I'm just running an Ethernet cable from my computer to the router at this point.

[Josta (grizzy7)]

I haven't a clue! For whatever reason it only does it once a while for me
now - I think I did a clean install & it was better. When ever it does
happen, a restart seems to fix it.

On Thu, Jun 25, 2009 at 11:06 AM, Endolith <email address hidden> wrote:

> Does anyone have any idea how to troubleshoot this? I'm just running an
> Ethernet cable from my computer to the router at this point.
>
> --
> Wireless network disconnects randomly, won't reconnect
> https://bugs.launchpad.net/bugs/331103
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux-firmware” package in Ubuntu: New
> Status in “network-manager” package in Ubuntu: New
>
> Bug description:
> My computer occasionally disconnects from my wireless router, and I can't
> get it to reconnect unless I reboot. It used to work completely fine.
> Something has been changed in the last month or two to make it stop working
> and I have no idea where to look.
>
> Two times it has disconnected around the same time, 8:15 in the morning,
> which is suspicious. I don't know of any event at that time that would
> cause that.
>
> Logs show things like:
>
> WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>
> though the key is correct. I also saw this:
>
> ipw2200: Firmware error detected. Restarting.
>

[quickstep (rg-hx)]

Yes, I experience the same problem with nm-applet (Jaunty) on a Dell Mini 9. Wireless (WPA) will be randomly lost after a few minutes or hours. A cable connection to the router works. I can either reset this problem by rebooting the netbook or switching the router off and on again.

[pacaj2am (paci-paci)]

hello,

i've read a lot of forums, but found no solution. My network card randlomly disconnects.

I have intel wireless 5300 card:

root@paci-laptop:~# lspci -vv -s 02:00.0
02:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection
 Subsystem: Intel Corporation Device 1001
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 29
 Region 0: Memory at f6000000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: [c8] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
  Address: 00000000fee0300c Data: 41b1
 Capabilities: [e0] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <32us
   ClockPM+ Suprise- LLActRep- BwNot-
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Device Serial Number 4e-4e-36-ff-ff-ea-16-00
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

When it disconnects...i can just in Network manager click on the same wireless network and it goes on, or just running:

iwlist wlan0 scan

establishes the connection back.

I am streaming DVB-T video over network, i can reproduce bug in every 2-5 mins, when there is big network traffic. When just browsing web pages, it disconnects at about once per hour. No issues in windows or in 8.04.

Here is part of dmesg:

[ 9655.806014] wlan0: authenticate with AP 00:1f:1f:1c:c0:d0
[ 9655.807799] wlan0: authenticated
[ 9655.807806] wlan0: associate with AP 00:1f:1f:1c:c0:d0
[ 9656.004040] wlan0: associate with AP 00:1f:1f:1c:c0:d0
[ 9656.204273] wlan0: associate with AP 00:1f:1f:1c:c0:d0
[ 9656.404284] wlan0: association with AP 00:1f:1f:1c:c0:d0 timed out
[ 9662.811815] wlan0: authenticate with AP 00:1f:1f:1c:c0:d0
[ 9662.813781] wlan0: authenticated
[ 9662.813788] wlan0: associate with AP 00:1f:1f:1c:c0:d0
[ 9662.818953] wlan0: RX AssocResp from 00:1f:1f:1c:c0:d0 (capab=0x411 status=0 aid=1)
[ 9662.818962] wlan0: associated
[ 9676.671110] iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 00:1f:1f:1c:c0:d0 tid = 0
[ 9676.671162] iwlagn 0000:02:00.0: HW queue is empty
[ 9941.933850] wlan0: authenticate with AP 00:1f:1f:1c:c0:d0
[ 9941.935884] wlan0: authenticated
[ 9941.935891] wlan0: associate with AP 00:1f:1f:1c:c0:d0
[ 9941...

[pacaj2am (paci-paci)]

...oh one more thing... The problem wasn't solved using newer kernels. Now i am using

paci@paci-laptop:~$ uname -r
2.6.30-020630-generic

The same it was with:

2.6.28-11, 2.6.28-13

Jan

[Shiny (shinyshiny)]

I have 3 laptops - 2 fresh installs of 9.04 and one upgrade from interpid. Completely different hardware. Toshiba, Lenovo, eeepc.
All three have these symptoms. Happens on home wifi, work wifi, and cafe wifi. (when i boot the lenovo into Mint linux it behaves fine, no wifi problems.).

[11905.585049] wlan0: authentication with AP 00:1c:10:28:0f:25 timed out
[11920.747008] wlan0: authenticate with AP 00:1c:10:28:0f:25
[11920.748597] wlan0: authenticated
[11920.748606] wlan0: associate with AP 00:1c:10:28:0f:25
[11920.751215] wlan0: RX AssocResp from 00:1c:10:28:0f:25 (capab=0x411 status=0 aid=1)
[11920.751221] wlan0: associated
[11961.808168] wlan0: No ProbeResp from current AP 00:1c:10:28:0f:25 - assume out of range
[11965.141384] wlan0: authenticate with AP 00:1c:10:28:0f:25
[11965.142912] wlan0: authenticated
[11965.142918] wlan0: associate with AP 00:1c:10:28:0f:25
[11965.145437] wlan0: RX ReassocResp from 00:1c:10:28:0f:25 (capab=0x411 status=0 aid=1)
[11965.145447] wlan0: associated
[12021.768133] wlan0: No ProbeResp from current AP 00:1c:10:28:0f:25 - assume out of range
[12025.076151] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12025.080553] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12025.276047] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12025.476520] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12025.676212] wlan0: authentication with AP 00:1c:10:28:0f:25 timed out
[12040.891089] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12040.892653] wlan0: authenticated
[12040.892661] wlan0: associate with AP 00:1c:10:28:0f:25
[12040.895179] wlan0: RX AssocResp from 00:1c:10:28:0f:25 (capab=0x411 status=0 aid=1)
[12040.895185] wlan0: associated
[12228.008555] wlan0: deauthenticated
[12229.008169] wlan0: direct probe to AP 00:1c:10:28:0f:25 try 1
[12229.010493] wlan0 direct probe responded
[12229.010505] wlan0: authenticate with AP 00:1c:10:28:0f:25
[12229.013275] wlan0: authenticated
[12229.013284] wlan0: associate with AP 00:1c:10:28:0f:25

[pacaj2am (paci-paci)]

I dont think it affcet wireless drivers for particular network card. I saw a lot posts on iternet and this porblem is affecting all range of wireles cards (eg. http://ubuntuforums.org/showthread.php?t=1146367&page=11). I also dont thionk Network-manager or something else is the reason. I palied a little and found, that when the connection drops, the rate of wireless card is set just to 1Mbit and than conecction drops (ping fails...).

root@paci-laptop:~# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"pacihome"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1F:1F:1C:C0:D0
          Bit Rate=1 Mb/s Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr:off
          Encryption key:1575-9C1D-20BA-10B9-1C9C-E276-CD02-BDCD [2] Security mode:open
          Power Management:off
          Link Quality=38/70 Signal level=-72 dBm Noise level=-93 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@paci-laptop:~# iwconfig wlan0 rate 54M
root@paci-laptop:~# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"pacihome"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1F:1F:1C:C0:D0
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr:off
          Encryption key:1575-9C1D-20BA-10B9-1C9C-E276-CD02-BDCD [2] Security mode:open
          Power Management:off
          Link Quality=34/70 Signal level=-76 dBm Noise level=-95 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

it also seems that outgoing packets are sent and he accespoint accepts them, because when i reconnect quickly i can see very long returning icmp packets:

64 bytes from 192.168.2.1: icmp_seq=47 ttl=64 time=2.45 ms
64 bytes from 192.168.2.1: icmp_seq=48 ttl=64 time=2.40 ms
-----here occures the disconnection---
64 bytes from 192.168.2.1: icmp_seq=49 ttl=64 time=31079 ms
64 bytes from 192.168.2.1: icmp_seq=50 ttl=64 time=30071 ms
64 bytes from 192.168.2.1: icmp_seq=51 ttl=64 time=29063 ms
64 bytes from 192.168.2.1: icmp_seq=52 ttl=64 time=28055 ms
64 bytes from 192.168.2.1: icmp_seq=53 ttl=64 time=27047 ms
64 bytes from 192.168.2.1: icmp_seq=54 ttl=64 time=26039 ms
64 bytes from 192.168.2.1: icmp_seq=55 ttl=64 time=25031 ms
64 bytes from 192.168.2.1: icmp_seq=56 ttl=64 time=24023 ms
64 bytes from 192.168.2.1: icmp_seq=57 ttl=64 time=23015 ms
64 bytes from 192.168.2.1: icmp_seq=58 ttl=64 time=22001 ms
64 bytes from 192.168.2.1: icmp_seq=59 ttl=64 time=21001 ms
64 bytes from 192.168.2.1: icmp_seq=60 ttl=64 time=20001 ms
64 bytes from 192.168.2.1: icmp_seq=61 ttl=64 time=19001 ms
64 bytes from 192.168.2.1: icmp_seq=62 ttl=64 time=18001 ms
64 bytes from 192.168.2.1: icmp_seq=63 ttl=64 time=17001 ms
64 bytes from 192.168.2.1: icmp_seq=80 ttl=64 time=9.81 ms
64 bytes from 192.168.2.1: icmp_seq=81 ttl=64 time=2.43 ms
64 bytes from 192.168.2.1: icmp_seq=82 ttl=64 time=2.39 ms

It is really just question of Jaunty. 8.10 worked well.

Jan

[Leela (manoranjan-balanagu)]

I am facing the same problem with Jaunty. I had this problem with Ubuntu 7. My Wifi connection used to work fine with 8.10. I have read lot of links on net about this problem. Is there any fix or defect logged for this?

-Leela

[geert (geertdb)]

Hi there,

I have the same problem using Atheros wireless on my acer aspire one, using UBUNTU 9.03
It looks like the connection breaks because the beacon carrying the SSID sent by the AP does not reach my notebook.
I scanned for channels that are available, I was using the same channel as one of my neighbors.

Since this change, I had no disruptions anymore ...
to see channels in use: sudo iwlist wlan0 scan | pg

It is probably a bug in UBUNTU, but it's worth to find an available channel and reconfigure your AP for it, give it a try ...

regards,
Geert

[Endolith (endolith)]

This didn't start happening until Jaunty, but alright, I'll try changing the channel. I've just been using a cable. My router's site survey sees 6 people on channel 6, 1 on 11, and 1 on 1 (weakest). All are weak, and I had been using channel 1.

[geert (geertdb)]

Hi Endolith,

You are right, it is a bug for sure, and changing the channel will help ...
I still had some problems after that maybe once or twice a day, now
EVERYTHING is solved.

Here is what I did:

I upgraded to a new Kernel: 2.6.30.5

you can find this kernel here, just download and double click the file:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

I use WEP now, didnt try going back to WPA ...

I never had problems anymore ...

Give it a try ...
ps. I did not upgrade to 2.6.31 because that kernel does not work for my
build in webcam.

Cheers, good luck

Geert

On Thu, Aug 20, 2009 at 4:17 PM, Endolith <email address hidden> wrote:

> This didn't start happening until Jaunty, but alright, I'll try changing
> the channel. I've just been using a cable. My router's site survey
> sees 6 people on channel 6, 1 on 11, and 1 on 1 (weakest). All are
> weak, and I had been using channel 1.
>
> --
> Wireless network disconnects randomly, won't reconnect
> https://bugs.launchpad.net/bugs/331103
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux-firmware” package in Ubuntu: New
> Status in “network-manager” package in Ubuntu: New
>
> Bug description:
> My computer occasionally disconnects from my wireless router, and I can't
> get it to reconnect unless I reboot. It used to work completely fine.
> Something has been changed in the last month or two to make it stop working
> and I have no idea where to look.
>
> Two times it has disconnected around the same time, 8:15 in the morning,
> which is suspicious. I don't know of any event at that time that would
> cause that.
>
> Logs show things like:
>
> WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>
> though the key is correct. I also saw this:
>
> ipw2200: Firmware error detected. Restarting.
>

[Endolith (endolith)]

Switching to channel 3 seems to help

[ASDFASDF (user-487-deactivatedaccount)]

I am experiencing this bug as well in Karmic with the linux kernel 2.6.31-9.29 and network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2

The wireless network randomly disconnects and will not even try to reconnect to the same network, but it will try to connect to other wireless networks it finds.
The only way to make it work again is to reboot the system or do a suspend-resume cycle.

My wireless chipset is Intel PRO/Wireless 3945ABG.

[meanasspenguin (jason-meanasspenguin)]

I'm also seeing this issue in a fresh install (not an upgrade) of Jaunty (xubuntu). The same laptop and wireless router didn't have this issue with hardy.

Post 21 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/331103/comments/21 seems to be the most consistent with what I'm seeing as well. During times of heavy network traffic - **specifically over the internet** - the connection will stop working. Oddly enough I can still do things with other local machines (ssh, scp, etc) over wireless which is really strange and seems like a gateway routing issue (though my routing table is normal). The other machines have no trouble getting to the internet during that time.

The dmesg log will show:
iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 00:21:91:f7:5a:56 tid = 0
iwlagn 0000:02:00.0: HW queue is empty

If I wait a little while it will start working again. My NIC is an Intel PRO/Wireless 5100 AGN. I tried updating the kernel to 2.6.30 and while it runs great everywhere else, this issue still occurs. I feel like it's a nm-applet issue but not for certain.

[muzeex (gerard-grippi)]

Hi all,

See my post https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352150/comments/26 which explainend how I solved the problem (for now at least). Hope this help.

[Alexander Sack (asac)]

this is very unlikely a networkmanager issue. i am not sure this bug is still usable, lets try to use it for the initial reporter chipset: ipw 2200 ... if you have any other chip/driver, please open new buigs and do not comment here to avoid more noise - which would it make harder to debug/fix this.

[Alexander Sack (asac)]

Endolith, in this sense, can you (or anyone else having ipw2200) confirm that you still have this problem in all up-to-date karmic?

[muzeex (gerard-grippi)]

Well, the issue is still occuring...

BTW I noticed that when I get disconnected, the IPW2200 process takes 100% cpu.
The only way to connect again is using the following script:
# service wicd stop
# rmmod ipw2200
# modprobe ipw2200
# service wicd start

hope this helps

[muzeex (gerard-grippi)]

Ok,

I was bored being disconnected so I restinalled my laptop with ArchLinux and guess what my wifi using IPW2200 driver works very well.

[^_Pepe_^ (jose-angel-fernandez-freire)]

Endolith,

Please, can you confirm that this is still an issue with last Karmic version as Alexander said on comment #31?

Thanks in advance.

[Endolith (endolith)]

I haven't upgraded yet. It's on my to do list.

[Leaman Crews (leamanc)]

I have upgraded and the issue more or less persists. I have all the latest
patches for Karmic. It is better than before, but still prone to random
disconnects, and a full power cycle (not a restart) is the only way to get
reconnected to my WAP.

On Fri, Dec 18, 2009 at 9:21 AM, Endolith <email address hidden> wrote:

> I haven't upgraded yet. It's on my to do list.
>
> --
> ipw2200 - Wireless network disconnects randomly, won't reconnect
> https://bugs.launchpad.net/bugs/331103
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
> Status in “linux-firmware” package in Ubuntu: New
>
> Bug description:
> My computer occasionally disconnects from my wireless router, and I can't
> get it to reconnect unless I reboot. It used to work completely fine.
> Something has been changed in the last month or two to make it stop working
> and I have no idea where to look.
>
> Two times it has disconnected around the same time, 8:15 in the morning,
> which is suspicious. I don't know of any event at that time that would
> cause that.
>
> Logs show things like:
>
> WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>
> though the key is correct. I also saw this:
>
> ipw2200: Firmware error detected. Restarting.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/331103/+subscribe
>

[Leaman Crews (leamanc)]

A little more detail about "better than before." It is staying connected
for longer periods of time now. Before, I could stay on for 5 hours, or 5
minutes. Now it will generally be a longer duration before I get
disconnected.

Also, it seems when I run on battery, I don't get disconnected! That could
just be coincidental though. I usually am plugged into the wall, but I ran
last night for around 3 hours on battery and did not have a single
disconnect.

Cheers,
Leaman

On Fri, Dec 18, 2009 at 9:49 AM, Leaman Crews <email address hidden> wrote:

> I have upgraded and the issue more or less persists. I have all the latest
> patches for Karmic. It is better than before, but still prone to random
> disconnects, and a full power cycle (not a restart) is the only way to get
> reconnected to my WAP.
>
>
> On Fri, Dec 18, 2009 at 9:21 AM, Endolith <email address hidden> wrote:
>
>> I haven't upgraded yet. It's on my to do list.
>>
>> --
>> ipw2200 - Wireless network disconnects randomly, won't reconnect
>> https://bugs.launchpad.net/bugs/331103
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in “linux” package in Ubuntu: Incomplete
>> Status in “linux-firmware” package in Ubuntu: New
>>
>> Bug description:
>> My computer occasionally disconnects from my wireless router, and I can't
>> get it to reconnect unless I reboot. It used to work completely fine.
>> Something has been changed in the last month or two to make it stop working
>> and I have no idea where to look.
>>
>> Two times it has disconnected around the same time, 8:15 in the morning,
>> which is suspicious. I don't know of any event at that time that would
>> cause that.
>>
>> Logs show things like:
>>
>> WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>>
>> though the key is correct. I also saw this:
>>
>> ipw2200: Firmware error detected. Restarting.
>>
>> To unsubscribe from this bug, go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/331103/+subscribe
>>
>
>

[Endolith (endolith)]

I haven't experienced this in Karmic with Tomato.

[Adam Mikitzel (adam-mikitzel)]

I can verify the ipw2200 driver works without a glitch with tomato firmware on a Linksys router, but while connecting to a D-link router with the stock firmware, the disconnect happens frequently.

[Carey Underwood (cwillu)]

And I can confirm that it fails with Tomato firmware on a Linksys router, so it's probably not Linksys + Tomato secret sauce.

[Chase Douglas (chasedouglas)]

@Carey Underwood:

Do you see the same firmware message "ipw2200: Firmware error detected. Restarting." in your dmesg when this occurs?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[seakayone (seakayone)]

This bug affects me too. I am running Ubuntu 10.04 Lucid Lynx with recent updates on Thinkpad T43p with ipw2200 drivers on a PRO/Wireless 2915ABG chipset .

The connection to two different access point will get a disconnect under heavy usage, sometimes the connection will break just randomly. In often cases NetworkManager is able to reconnect and will not show the disconnect even though it is visible in syslog. If the connection breaks NM may not be able to reconnect. If I switch to another channel, deactive NM and reactivate it the connection can be brought up again.

See attached documents for details and feel free to ask for more information.

[seakayone (seakayone)]

Addendum: Running Ubuntu 8.04 Hardy Heron on the same machine I do not experience any of those issues.

[seakayone (seakayone)]

Maybe as well a duplicate to bug #374847 ?

[seakayone (seakayone)]

of bug #352150 ?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.