[arch-general] Wifi not working after kernel upgrade to 2.6.29
Hi, I've just upgraded kernel to 2.6.29.1-3 and since then I can't connect to my wireless network. netcfg times out and says "Wireless association failed". The driver is iwl3945, here is the profile's content: CONNECTION="wireless" INTERFACE=wlan0 SCAN="no" SECURITY="wpa" ESSID="foo" KEY="foobar" IP="dhcp" TIMEOUT=20 QUIRKS=(preessid wpaessid) If I correctly understand how it all works, wpa_supplicant is run and then "wpa_cli status" is saying "wpa_state=SCANNING" for the whole 20 seconds until netcfg gives up. Does anybody have similar problems or knows a solution? Perhaps also relevant lines from /var/log/everything.log: Apr 10 00:00:33 hermione kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:radio Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:assoc Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:RX Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:TX Apr 10 00:00:33 hermione kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 10 00:00:55 hermione kernel: iwl3945 0000:03:00.0: PCI INT A disabled Ondřej -- Cheers, Ondřej Kučera
Ondřej Kučera schrieb:
Hi,
I've just upgraded kernel to 2.6.29.1-3 and since then I can't connect to my wireless network. netcfg times out and says "Wireless association failed". The driver is iwl3945, here is the profile's content: CONNECTION="wireless" INTERFACE=wlan0 SCAN="no" SECURITY="wpa" ESSID="foo" KEY="foobar" IP="dhcp" TIMEOUT=20 QUIRKS=(preessid wpaessid)
If I correctly understand how it all works, wpa_supplicant is run and then "wpa_cli status" is saying "wpa_state=SCANNING" for the whole 20 seconds until netcfg gives up.
Does anybody have similar problems or knows a solution?
Perhaps also relevant lines from /var/log/everything.log: Apr 10 00:00:33 hermione kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:radio Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:assoc Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:RX Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:TX Apr 10 00:00:33 hermione kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 10 00:00:55 hermione kernel: iwl3945 0000:03:00.0: PCI INT A disabled
All fine here (no netcfg, but iwl3945). Out of curiosity, which channel do you use and which country are you in?
Hi, Thomas Bächler wrote:
All fine here (no netcfg, but iwl3945). Out of curiosity, which channel do you use and which country are you in?
No idea about the channel, how do I find out? The country is Czech Republic. Ondřej -- Cheers, Ondřej Kučera
Ondřej Kučera schrieb:
Thomas Bächler wrote:
All fine here (no netcfg, but iwl3945). Out of curiosity, which channel do you use and which country are you in?
No idea about the channel, how do I find out? The country is Czech Republic.
It's in the settings of your AP for example. Or iwconfig shows it as "frequency". Talking to other people with this problem makes me think that this is not the problem though.
Ondřej Kučera 写道:
Hi,
I've just upgraded kernel to 2.6.29.1-3 and since then I can't connect to my wireless network. netcfg times out and says "Wireless association failed". The driver is iwl3945, here is the profile's content: CONNECTION="wireless" INTERFACE=wlan0 SCAN="no" SECURITY="wpa" ESSID="foo" KEY="foobar" IP="dhcp" TIMEOUT=20 QUIRKS=(preessid wpaessid)
If I correctly understand how it all works, wpa_supplicant is run and then "wpa_cli status" is saying "wpa_state=SCANNING" for the whole 20 seconds until netcfg gives up.
Does anybody have similar problems or knows a solution? I've got the same issue and have been looking for the reason. AFAIK, the earliest report is from Pierre Schmitz in "[arch-general] [signoff] kernel-2.6.29.1-3" thread:
It allways worked for me as user and not only when I had scanned as root before. Maybe the previous driver scanned on its own from time to time?
Anyway the result is reproducable: start with .28 -> iwlist wlan scan as user shows all networks start with .29 -> iwlist wlan scan as user shows no networks
I am not sure what driver Pierre is using (ipw2200?), I am using an Atheros AR5008 (ath9k) and here's an example of rt2570: http://bbs.archlinux.org/viewtopic.php?id=69498
Perhaps also relevant lines from /var/log/everything.log: Apr 10 00:00:33 hermione kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:radio Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:assoc Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:RX Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:TX Apr 10 00:00:33 hermione kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 10 00:00:55 hermione kernel: iwl3945 0000:03:00.0: PCI INT A disabled
Ondřej
Ondřej Kučera schrieb:
Hi,
I've just upgraded kernel to 2.6.29.1-3 and since then I can't connect to my wireless network. netcfg times out and says "Wireless association failed". The driver is iwl3945, here is the profile's content: CONNECTION="wireless" INTERFACE=wlan0 SCAN="no" SECURITY="wpa" ESSID="foo" KEY="foobar" IP="dhcp" TIMEOUT=20 QUIRKS=(preessid wpaessid)
If I correctly understand how it all works, wpa_supplicant is run and then "wpa_cli status" is saying "wpa_state=SCANNING" for the whole 20 seconds until netcfg gives up.
Does anybody have similar problems or knows a solution?
Perhaps also relevant lines from /var/log/everything.log: Apr 10 00:00:33 hermione kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:radio Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:assoc Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:RX Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:TX Apr 10 00:00:33 hermione kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 10 00:00:55 hermione kernel: iwl3945 0000:03:00.0: PCI INT A disabled
Is wpa_supplicant even running? I looked into the issue with someone on IRC and in his case, wpa_supplicant wouldn't start! wpa_supplicant -dd would say: Using existing control interface directory. ctrl_interface_group=10 (from group name 'wheel') ctrl_iface bind(PF_UNIX) failed: Address already in use ctrl_iface exists and seems to be in use - cannot override it Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=wheel'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again. He said that /var/run/wpa_supplicant didn't exist at the time. I don't understand it, but it might be the same thing that is happening to you. It might also explain why this is only happening to WPA networks for some people.
Thomas Bächler wrote:
Ondřej Kučera schrieb:
Hi,
I've just upgraded kernel to 2.6.29.1-3 and since then I can't connect to my wireless network. netcfg times out and says "Wireless association failed". The driver is iwl3945, here is the profile's content: CONNECTION="wireless" INTERFACE=wlan0 SCAN="no" SECURITY="wpa" ESSID="foo" KEY="foobar" IP="dhcp" TIMEOUT=20 QUIRKS=(preessid wpaessid)
If I correctly understand how it all works, wpa_supplicant is run and then "wpa_cli status" is saying "wpa_state=SCANNING" for the whole 20 seconds until netcfg gives up.
Does anybody have similar problems or knows a solution?
Perhaps also relevant lines from /var/log/everything.log: Apr 10 00:00:33 hermione kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:radio Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:assoc Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:RX Apr 10 00:00:33 hermione kernel: Registered led device: iwl-phy0:TX Apr 10 00:00:33 hermione kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 10 00:00:55 hermione kernel: iwl3945 0000:03:00.0: PCI INT A disabled
Is wpa_supplicant even running? I looked into the issue with someone on IRC and in his case, wpa_supplicant wouldn't start! wpa_supplicant -dd would say:
Using existing control interface directory. ctrl_interface_group=10 (from group name 'wheel') ctrl_iface bind(PF_UNIX) failed: Address already in use ctrl_iface exists and seems to be in use - cannot override it Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=wheel'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
He said that /var/run/wpa_supplicant didn't exist at the time. I don't understand it, but it might be the same thing that is happening to you. It might also explain why this is only happening to WPA networks for some people.
I may look into that again in the evening but I'm quite sure that wpa_supplicant was running. I was able to run wpa_cli status without any weird errors or warnings. The only problem was that the status was "SCANNING" all the time (as I mentioned) which means that netcfg gives up after 20 seconds. Ondřej -- Cheers, Ondřej Kučera -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Ondřej Kučera schrieb:
I may look into that again in the evening but I'm quite sure that wpa_supplicant was running. I was able to run wpa_cli status without any weird errors or warnings. The only problem was that the status was "SCANNING" all the time (as I mentioned) which means that netcfg gives up after 20 seconds.
So this means we have at least 2 different problems. Can you increase netcfg's timeout? Does "iwlist scan" (as root) show anything? Also, active scanning is disabled by default due to regulatory restrictions. If you install the crda package and set your country code in /etc/conf.d/wireless-regdom (then reboot or run /etc/rc.d/wireless-regdom start) you should be able to do active scans again, maybe that helps, maybe not.
Thomas Bächler wrote:
Ondřej Kučera schrieb:
I may look into that again in the evening but I'm quite sure that wpa_supplicant was running. I was able to run wpa_cli status without any weird errors or warnings. The only problem was that the status was "SCANNING" all the time (as I mentioned) which means that netcfg gives up after 20 seconds.
So this means we have at least 2 different problems. Can you increase netcfg's timeout? Does "iwlist scan" (as root) show anything?
I think I tried increasing the timeout (although I don't remember to which value, I'll try again). I did try iwlist wlan0 scan and it worked without problems (I didn't see my AP but that's because it doesn't broadcast essid).
Also, active scanning is disabled by default due to regulatory restrictions. If you install the crda package and set your country code in /etc/conf.d/wireless-regdom (then reboot or run /etc/rc.d/wireless-regdom start) you should be able to do active scans again, maybe that helps, maybe not.
OK I can try that as well and see what happens. Ondřej -- Cheers, Ondřej Kučera -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Am Freitag 10 April 2009 schrieb Ondřej Kučera:
Thomas Bächler wrote:
Ondřej Kučera schrieb:
I may look into that again in the evening but I'm quite sure that wpa_supplicant was running. I was able to run wpa_cli status without any weird errors or warnings. The only problem was that the status was "SCANNING" all the time (as I mentioned) which means that netcfg gives up after 20 seconds.
So this means we have at least 2 different problems. Can you increase netcfg's timeout? Does "iwlist scan" (as root) show anything?
I think I tried increasing the timeout (although I don't remember to which value, I'll try again). I did try iwlist wlan0 scan and it worked without problems (I didn't see my AP but that's because it doesn't broadcast essid).
Also, active scanning is disabled by default due to regulatory restrictions. If you install the crda package and set your country code in /etc/conf.d/wireless-regdom (then reboot or run /etc/rc.d/wireless-regdom start) you should be able to do active scans again, maybe that helps, maybe not.
OK I can try that as well and see what happens.
Ondřej
-- Cheers, Ondřej Kučera Does that mean you hide your AP? Hiding the AP never worked for me. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Does that mean you hide your AP? Hiding the AP never worked for me. greetings tpowa
Yes I do that and it has worked for me since I bought the router (at least a year), first problem came now with 2.6.29. But when I'm back home I can also try to unhide it and see what happens. Ondřej -- Cheers, Ondřej Kučera -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Ondřej Kučera schrieb:
So this means we have at least 2 different problems. Can you increase netcfg's timeout? Does "iwlist scan" (as root) show anything?
I think I tried increasing the timeout (although I don't remember to which value, I'll try again). I did try iwlist wlan0 scan and it worked without problems (I didn't see my AP but that's because it doesn't broadcast essid).
Ah, then I was right and you need active scans to find it, and those are disabled if you don't have crda and the right regulations set, see the output of "iw list".
Thomas Bächler wrote:
Ondřej Kučera schrieb:
So this means we have at least 2 different problems. Can you increase netcfg's timeout? Does "iwlist scan" (as root) show anything?
I think I tried increasing the timeout (although I don't remember to which value, I'll try again). I did try iwlist wlan0 scan and it worked without problems (I didn't see my AP but that's because it doesn't broadcast essid).
Ah, then I was right and you need active scans to find it, and those are disabled if you don't have crda and the right regulations set, see the output of "iw list".
And this is new with 2.6.29? Because I know that the optional dependency of kernel26 on crda has been there for some time and I haven't needed crda yet. When I'm running 2.6.28 not having crda installed and having AP hidden, everything works without problems. Ondřej -- Cheers, Ondřej Kučera -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Ondřej Kučera schrieb:
And this is new with 2.6.29? Because I know that the optional dependency of kernel26 on crda has been there for some time and I haven't needed crda yet. When I'm running 2.6.28 not having crda installed and having AP hidden, everything works without problems.
2.6.28 had static regulatory settings for "US", "EU" and "JP" built-in, and "US" was enabled by default. Active scans were allowed there on channels 1-11, but now the default changed to "World" and that is VERY restrictive. If you don't have crda installed, you cannot use any 802.11a channels, only channels 1-11 are enabled with passive scanning only and no adhoc.
Thomas Bächler wrote:
Ondřej Kučera schrieb:
And this is new with 2.6.29? Because I know that the optional dependency of kernel26 on crda has been there for some time and I haven't needed crda yet. When I'm running 2.6.28 not having crda installed and having AP hidden, everything works without problems.
2.6.28 had static regulatory settings for "US", "EU" and "JP" built-in, and "US" was enabled by default. Active scans were allowed there on channels 1-11, but now the default changed to "World" and that is VERY restrictive. If you don't have crda installed, you cannot use any 802.11a channels, only channels 1-11 are enabled with passive scanning only and no adhoc.
I've been away for the Easter holidays but anyway it seems that really all I needed to do was install crda and uncomment WIRELESS_REGDOM="CZ" in /etc/conf.d/wireless-regdom and it all seems to work again. Thanks a lot! Ondřej -- Cheers, Ondřej Kučera
participants (4)
-
Lyman
-
Ondřej Kučera
-
Thomas Bächler
-
Tobias Powalowski