Wireless LAN sometimes fails to connect

rohshall · 03-07-2010, 07:31 AM

Hi,

My laptop fails to connect to the access point (router) sometimes. Rebooting the router solves the problem. But, on windows machine, there is no such issue. So, I am assuming the problem must be with my Linux.

Here is my machine info:

Code:

salil@salil-laptop ~ $ uname -a
Linux salil-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Here is the log using dmesg. I have highlighted the hardware info.

Code:

[   15.967662] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[   15.967666] iwl3945: Copyright(c) 2003-2009 Intel Corporation
[   15.967764] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   15.967780] iwl3945 0000:03:00.0: setting latency timer to 64
[   16.049974] iwl3945 0000:03:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
[   16.049979] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
[   16.050097]   alloc irq_desc for 26 on node -1
[   16.050100]   alloc kstat_irqs on node -1
[   16.050135] iwl3945 0000:03:00.0: irq 26 for MSI/MSI-X
[   16.182422] tifm_7xx1 0000:05:06.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   16.191465] sdhci-pci 0000:05:06.3: SDHCI controller found [104c:803c] (rev 0)
[   16.191484] sdhci-pci 0000:05:06.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[   16.191558] Registered led device: mmc0::
[   16.191604] mmc0: SDHCI controller on PCI [0000:05:06.3] using DMA
[   16.305503] yenta_cardbus 0000:05:06.0: CardBus bridge found [1179:ff00]
[   16.305529] yenta_cardbus 0000:05:06.0: Enabling burst memory read transactions
[   16.305536] yenta_cardbus 0000:05:06.0: Using CSCINT to route CSC interrupts to PCI
[   16.305539] yenta_cardbus 0000:05:06.0: Routing CardBus interrupts to PCI
[   16.305547] yenta_cardbus 0000:05:06.0: TI: mfunc 0x10aa1b22, devctl 0x64
[   16.536801] yenta_cardbus 0000:05:06.0: ISA IRQ mask 0x0cf8, PCI irq 16
[   16.536807] yenta_cardbus 0000:05:06.0: Socket status: 30000006
[   16.536813] pci_bus 0000:05: Raising subordinate bus# of parent bus (#05) from #06 to #09
[   16.536823] yenta_cardbus 0000:05:06.0: pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
[   16.536828] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x2000-0x2fff: clean.
[   16.537101] yenta_cardbus 0000:05:06.0: pcmcia: parent PCI bridge Memory window: 0xd0000000 - 0xd00fffff
[   16.537105] yenta_cardbus 0000:05:06.0: pcmcia: parent PCI bridge Memory window: 0x40000000 - 0x43ffffff
[   16.777598] phy0: Selected rate control algorithm 'iwl-3945-rs'
[   16.850891] cfg80211: World regulatory domain updated:
[   16.850895] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   16.850900] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   16.850903] 	(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   16.850907] 	(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   16.850911] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   16.850914] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   17.483296] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
[   17.485353] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
[   17.486204] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
[   17.486906] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
[   17.487821] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
[   19.036041]   alloc irq_desc for 22 on node -1
[   19.036046]   alloc kstat_irqs on node -1
[   19.036055] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[   19.036060] hda_intel: probe_mask set to 0x3 for device 1179:ff00
[   19.036097] HDA Intel 0000:00:1b.0: setting latency timer to 64
[   19.444997] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
[   19.971383] iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
[   20.209702] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
[   20.282759] Registered led device: iwl-phy0::radio
[   20.282825] Registered led device: iwl-phy0::assoc
[   20.282850] Registered led device: iwl-phy0::RX
[   20.282872] Registered led device: iwl-phy0::TX
[   20.300930] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.318051] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.671520] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
[   23.274656] [drm] TV-14: set mode NTSC 480i 0
[   23.414828] [drm] TV-14: set mode NTSC 480i 0
[   23.713496] [drm] TV-14: set mode NTSC 480i 0
[   23.853766] [drm] TV-14: set mode NTSC 480i 0
[   29.409425] ppdev: user-space parallel port driver
[   31.695529] [drm] TV-14: set mode NTSC 480i 0
[   31.845594] [drm] TV-14: set mode NTSC 480i 0
[   32.127301] [drm] TV-14: set mode NTSC 480i 0
[   32.273514] [drm] TV-14: set mode NTSC 480i 0
[   32.567406] [drm] TV-14: set mode NTSC 480i 0
[   32.708110] [drm] TV-14: set mode NTSC 480i 0
[   43.649888] ACPI: EC: GPE storm detected, transactions will use polling mode
[   44.060101] [drm] TV-14: set mode NTSC 480i 0
[   44.201202] [drm] TV-14: set mode NTSC 480i 0
[   44.515965] [drm] TV-14: set mode NTSC 480i 0
[   44.656973] [drm] TV-14: set mode NTSC 480i 0
[   44.936224] [drm] TV-14: set mode NTSC 480i 0
[   45.078548] [drm] TV-14: set mode NTSC 480i 0
[   68.920227] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[   69.116116] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[   69.316111] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[   69.516108] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[   74.359324] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[   74.557053] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[   74.756827] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[   74.957064] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[   81.993506] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[   82.192108] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[   82.392050] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[   82.592044] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out <== This is where it times out trying to connect to the access point.
The following is when I switch off my wireless. I do that because sometimes it works after I switch off and then switch on wireless ==>
[   88.334010] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_ABORT_CMD: enqueue_hcmd failed: -5
[   88.334087] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5
[   88.334093] iwl3945 0000:03:00.0: Error setting new configuration (-5).
[   88.334101] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5
[   88.334106] iwl3945 0000:03:00.0: Error setting new configuration (-5).
[  208.876836] Registered led device: iwl-phy0::radio
[  208.876919] Registered led device: iwl-phy0::assoc
[  208.876957] Registered led device: iwl-phy0::RX
[  208.876992] Registered led device: iwl-phy0::TX
[  208.905642] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  221.600528] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[  221.801039] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[  222.000103] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[  222.200096] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[  229.276879] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[  229.477066] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[  229.677034] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[  229.876104] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[  240.228380] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[  240.428089] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[  240.628163] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[  240.828139] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[  247.975508] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[  248.172030] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[  248.376037] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[  248.576037] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out
[  270.851583] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 1
[  271.048139] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 2
[  271.248157] wlan0: direct probe to AP 00:1c:10:09:e4:a5 try 3
[  271.448118] wlan0: direct probe to AP 00:1c:10:09:e4:a5 timed out

raju.mopidevi · 03-07-2010, 08:24 AM

install this library b43-fwcutter

rohshall · 03-07-2010, 11:11 PM

Thank you very much! I will try that when I get home.

reed9 · 03-08-2010, 10:16 AM

Quote:

Originally Posted by raju.mopidevi

install this library b43-fwcutter

This is the second post I've seen where this person has posted this exact same advice. It has absolutely nothing to do with your wireless card. b43-fwcutter is a tool for extracting the firmware for some broadcom cards using the b43 driver.

To the poster, your card is this

Code:

Intel(R) PRO/Wireless 3945ABG/BG

It uses the iwl3945 driver. I have the same card on a laptop and have had some similar trouble with it under Arch. Strangely, the difficulty connecting only happens when using arch's network scripts. When I use WICD, I have no troubles. Go figure.

I don't really have a solution for you, but you might try updating your drivers. Either build the latest compat-wireless. Or in Ubuntu you should be able to get more recent drivers by installing linux-backports-modules-karmic.

Code:

sudo apt-get install linux-backports-modules-karmic

raju.mopidevi · 03-08-2010, 10:19 AM

Actually I got this advice from another forum. After installing this I was able to scan ! that's the reason I was given that !

raju.mopidevi · 03-08-2010, 10:27 AM

The b43 drivers (bcm43xx in mainline kernels, b43 and b43legacy in wireless-2.6 and 2.6.24 and later) are drivers for the 802.11 B/G family of wireless chips Broadcom produces. The choice of which driver your card uses depends on the revision level of the 802.11 core. This number is read by driver ssb, and the correct choice for your device is made at that point. Note: If your card is a BCM4306 Rev 2, or only has 802.11b capability, it uses b43legacy. All other models use b43.

reed9 · 03-08-2010, 10:29 AM

Quote:

Originally Posted by raju.mopidevi

Actually I got this advice from another forum. After installing this I was able to scan ! that's the reason I was given that !

If installing b43-fwcutter helped you, then you have a Broadcom card. But please don't give advice if you don't know what it means. At the very least, google your advice and see if it looks pertinent to the problem at hand.

As you can see, the first hit takes you to the b43 wireless site, which tells you exactly which wireless cards this applies to.

reed9 · 03-08-2010, 10:32 AM

Quote:

Originally Posted by raju.mopidevi

The b43 drivers (bcm43xx in mainline kernels, b43 and b43legacy in wireless-2.6 and 2.6.24 and later) are drivers for the 802.11 B/G family of wireless chips Broadcom produces. The choice of which driver your card uses depends on the revision level of the 802.11 core. This number is read by driver ssb, and the correct choice for your device is made at that point. Note: If your card is a BCM4306 Rev 2, or only has 802.11b capability, it uses b43legacy. All other models use b43.

All true, but again, it has nothing to do with the posters problem. Their dmesg output clearly shows that they have an Intel Pro 3945, and use the iwl3945 driver.

rohshall · 03-09-2010, 02:51 AM

Quote:

Originally Posted by reed9

It uses the iwl3945 driver. I have the same card on a laptop and have had some similar trouble with it under Arch. Strangely, the difficulty connecting only happens when using arch's network scripts. When I use WICD, I have no troubles. Go figure.

I don't really have a solution for you, but you might try updating your drivers. Either build the latest compat-wireless. Or in Ubuntu you should be able to get more recent drivers by installing linux-backports-modules-karmic.

Code:

sudo apt-get install linux-backports-modules-karmic

Thanks very much. I will check out whether installing latest wireless drivers from backports-modules package helps.