I am getting errors with iwlagn kernel 2.6.31-gentoo-r6. When I switch to vanilla 2.6.31.6 with the same config, it works. tdanotebook ~ # /etc/init.d/net.wlan0 restart * Stopping wlan0 * Bringing down wlan0 * Shutting down wlan0 ... [ ok ] * Stopping wpa_cli on wlan0 ... [ ok ] * Stopping wpa_supplicant on wlan0 ... [ ok ] * Starting wlan0 RTNETLINK answers: Unknown error 132 RTNETLINK answers: Unknown error 132 * Starting wpa_supplicant on wlan0 ... [ ok ] * Starting wpa_cli on wlan0 ... [ ok ] * Backgrounding ... /var/log/messages Dec 20 15:20:04 tdanotebook kernel: wlan0: direct probe to AP 00:1f:f3:c3:88:b4 try 1 Dec 20 15:20:04 tdanotebook kernel: wlan0 direct probe responded Dec 20 15:20:04 tdanotebook kernel: wlan0: authenticate with AP 00:1f:f3:c3:88:b4 Dec 20 15:20:04 tdanotebook kernel: wlan0: authenticated Dec 20 15:20:04 tdanotebook kernel: wlan0: associate with AP 00:1f:f3:c3:88:b4 Dec 20 15:20:05 tdanotebook kernel: wlan0: associate with AP 00:1f:f3:c3:88:b4 Dec 20 15:20:05 tdanotebook kernel: wlan0: deauthenticated (Reason: 9) Dec 20 15:20:05 tdanotebook kernel: wlan0: deauthenticating by local choice (reason=3) Reproducible: Always
Oh, also, I have the Intel 5300 adapter. tdanotebook ~ # lspci | grep 5300 04:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection
The 132 error code basically means "Operation not possible due to RF-kill". Emerge net-wireless/rfkill and attach the output of "rfkill list": a) With vanilla kernel 2.6.31.6. b) With 2.6.31-gentoo-r6 and the rfkill button (you are on a laptop right?) pressed. c)With 2.6.31-gentoo-r6 and the rfkill button pressed again.
I'm going to be busy doing accounting for a few days here. I'll get back to you on this. yes, it's a notebook, but there is no button, just a switch. Oops, I'm wrong, there is a button, I have never saw it or used it before.
Haven't forgotten about this. I wasn't able to reproduce it completely again. I'll try again soon.
I have the same story. uname -r 2.6.31-gentoo-r6 When WiFi router is up and /etc/conf.d/net configured correctly it works all right just after loading iwlagn. But if WiFi router is e.g. switched off, I load iwlagn and rc scripts fail to configure network. That's not a problem, problem is that I'm not able even manually configure wireless network, because command ip link set up dev wlan0 give me: RTNETLINK answers: Unknown error 132 Thanks for the link to rfkill tool ( I found more info in kernel sources Documentation/rfkill.txt) rfkill list showed me: 1: phy1: Wireless LAN Soft blocked: yes Hard blocked: no Then I executed rfkill unblock all And now I'm able to configure wireless as I wish. Regarding to original bug - may be rc scripts should check "soft blocked" status and unblock if needed?
With my notebook the same error appears. It seams to be depending on the transfer rate. With a loaded network it stops working after approximated 1h. Trying to restart it (/etc/init.d/net.wlan0 restart) the above mentioned line (RTNETLINK answers: Unknown error 132) appears and no access point will be found. lspci: Network controller: Intel Corporation Wireless WiFi Link 5100
It seems to be intermittent for me. This seems like a linux kernel issue, not a gentoo specific issue, because I have it happen on my vanilla kernel now and then as well. (In reply to comment #6) > With my notebook the same error appears. It seams to be depending on the > transfer rate. With a loaded network it stops working after approximated 1h. > Trying to restart it (/etc/init.d/net.wlan0 restart) the above mentioned line > (RTNETLINK answers: Unknown error 132) appears and no access point will be > found. > > lspci: > Network controller: Intel Corporation Wireless WiFi Link 5100 > I have also noticed my machine having serious problems with my 5100 being up for some time (could be due to large data transfer, or small amounts over time causing it). After awhile, it completely locks up my machine. Even the Alt-SysReq RSEIUB does not work. I'm thinking maybe it's a 5100 driver issue causing this.
Can someone test with gentoo-sources-2.6.32-r3
whoops
I can confirm this on my Dell Studio 1555 (WiFi Link 5100) and various kernel packages: gentoo-sources 2.6.31-r6 and r9, tuxonice-sources up to 2.6.32-r1. They behave all the same, and I though it was my laptop that has severe troubles with the linux ACPI subsystem I had to patch (http://en.gentoo-wiki.com/wiki/Dell_Studio_1555#ACPI). Now I see that happens to others. Any time I restart the wifi interface I get the unknown error 132 message, even though rfkill reports all the switches are unblocked. Curiously enough if I start the wifi interface manually (I mean calling ifconfig + wpa_supplicant + dhcp directly) no problem arises: it just works. This is very painfull if you suspend/hibernate and resume since you're always stuck with your interface down. I remember with my previous centrino laptop (intel pro/wireless) the connection just restarted in a matter of 10-20 seconds by itself. Now I always must open a command line and sometimes it doesn't even work. As a matter of fact, iwconfig and dmesg often report that the interface is attached to the AP, but I don't get any ip address... What I don't understand is where the real problem resides: is it the kernel driver, the ACPI subsystem, the rfkill switch, wpa_supplicant...?
I forgot two things. First, I get a slightly different message from the original reported here: * Starting wlan0 SIOCSIFFLAGS: Unknown error 132 SIOCSIFFLAGS: Unknown error 132 * Starting wpa_supplicant on wlan0...[ ok ] * Starting wpa_cli on wlan0...[ ok ] * Backgrounding ... Second, I forgot to mention that, even though I get this message, sometimes everything works nonetheless. For instance, if I disable the RF switch in the BIOS I get the infamous error as expected since the system starts with the device turned off. If I issue /etc/init.d/net.wlan0 restart... well, it seems to work, but the message is still there. I'm switching from tuxonice-sources to gentoo-sources for a while now to see what happens.
I am seeing the same as comment #11 as well. Sometimes I get the message, and it still works, even though I did nothing but restart the net.wlan0 interface.
(In reply to comment #11) > I forgot two things. First, I get a slightly different message from the > original reported here: > * Starting wlan0 > SIOCSIFFLAGS: Unknown error 132 > SIOCSIFFLAGS: Unknown error 132 Switching from tuxonice-sources-2.6.31-r7 to 2.6.31-r9 or r10 the message slightly changes and becomes: RTNETLINK answers: Unknown error 132 RTNETLINK answers: Unknown error 132 when restarting the interface. It works correctly otherwise. Same thing tested with gentoo-sources-2.6.32-r4 and vanilla-sources-2.6.32.8.
Please submit this issue upstream at http://bugzilla.kernel.org
Once submitted upstream, please post the url back here.
any news about forwarding it to upstream?
I put in a bug report upstream. http://bugzilla.kernel.org/show_bug.cgi?id=15374
Oh, sorry, that was a different bug entirely, my bad.
from https://qa.mandriva.com/show_bug.cgi?id=61004 i am said the upstream bug is https://bugzilla.kernel.org/show_bug.cgi?id=18642 and as of TODAY, it seems to be still "open", aka not fixed.
