You are not logged in.

#1 2010-08-16 20:16:49

aneiser
Member
Registered: 2008-07-21
Posts: 59

iwlagn in 2.6.35 broken when using channel 12/13

Hi everybody,
i just wanted to play a bit with the kernel 2.6.35 in testing (by manually installing linux-firmware, nvidia, and kernel26, all other packages still core). I experience some strange behavior with the WLAN after reboot. See dmesg:

iwlagn 0000:03:00.0: PCI INT A disabled
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
iwlagn: Copyright(c) 2003-2010 Intel Corporation
iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:03:00.0: setting latency timer to 64
iwlagn 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:03:00.0: irq 48 for MSI/MSI-X
iwlagn 0000:03:00.0: loaded firmware version 9.193.4.1 build 19710
phy1: Selected rate control algorithm 'iwl-agn-rs'
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to 00:04:0e:6b:80:e6 (try 1)
wlan0: direct probe to 00:04:0e:6b:80:e6 (try 2)
wlan0: direct probe to 00:04:0e:6b:80:e6 (try 3)
wlan0: direct probe to 00:04:0e:6b:80:e6 timed out
...last lines repeat...

I'm using networkmanager under gnome. And it stays showing just one green dot (so no responses). The WLAN Led on my notebook is on. Do you know why this happens? Everything else seems to work fine.

Edit: I filed a bug report (and upstream here, use this one if contributing debug infos) and searched the internet, but only found http://www.spinics.net/lists/linux-wire … 53613.html which offers no solution and only 2.6.35-rc6 is concerned...

Last edited by aneiser (2010-08-20 08:07:28)

Offline

#2 2010-08-19 20:43:12

MadCat_X
Member
Registered: 2009-10-08
Posts: 189

Re: iwlagn in 2.6.35 broken when using channel 12/13

I've been experiencong similar issues ever since I updated to 2.6.35. I was actually was using rc6 for a while and now I think that this is where my problems started. I've been experiencing unexplicable packet losses and high latencies on my home wifi network and some other networks were not accessible at all. I could see them, but I couldn't connect to them. After a bit of experimentation I discovered that it is the 802.11g mode which has these serious problems. When I swithed my router to b mode only, wireless was working just fine. Switching it to g only (not b+g) caused the network to be completely unconnectable for me.

Are you able to try the same test to confirm that we're having identical problem?

Offline

#3 2010-08-19 20:54:07

Fackamato
Member
Registered: 2006-03-31
Posts: 579

Re: iwlagn in 2.6.35 broken when using channel 12/13

I just thought I'd mention that I've been using 2.6.35 since it's been out, with working iwlagn.

0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

Offline

#4 2010-08-20 08:03:25

aneiser
Member
Registered: 2008-07-21
Posts: 59

Re: iwlagn in 2.6.35 broken when using channel 12/13

MadCat_X wrote:

I've been experiencong similar issues ever since I updated to 2.6.35. I was actually was using rc6 for a while and now I think that this is where my problems started. I've been experiencing unexplicable packet losses and high latencies on my home wifi network and some other networks were not accessible at all. I could see them, but I couldn't connect to them. After a bit of experimentation I discovered that it is the 802.11g mode which has these serious problems. When I swithed my router to b mode only, wireless was working just fine. Switching it to g only (not b+g) caused the network to be completely unconnectable for me.

Are you able to try the same test to confirm that we're having identical problem?

Well, it does NOT depend on which 802.11 mode I use (I just tested it: in b-mode and channel 13/12, it still doesn't work), but it does depend on the channels: 12 and 13 are not working, all the others do. Maybe you can try changing the channels and keeping b+g mode? I'm participating in the upstream bug, which is the best place to discuss such problems: https://bugzilla.kernel.org/show_bug.cgi?id=16462

You can check your dmesg output and compare it to the reported stuff in the kernel bugzilla. Feel free to file another bug, if you think it's something different.

Edit: My Intel WLAN controller is: 03:00.0 Network controller: Intel Corporation WiFi Link 6000 Series (rev 35) but it happens with others, too!

Last edited by aneiser (2010-08-20 08:04:55)

Offline

Board footer

Powered by FluxBB