From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Sodhi Date: Thu, 24 Feb 2011 12:21:07 +0100 Subject: [ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout In-Reply-To: <1298545686.25101.36.camel@jm-desktop> References: <20110223204641.GA19782@fly> <19813.55419.872426.269636@gargle.gargle.HOWL> <20110224040749.29275.qmail@stuge.se> <19814.2496.216607.495827@gargle.gargle.HOWL> <20110224074209.11758.qmail@stuge.se> <20110224090010.GB19782@fly> <20110224091823.32641.qmail@stuge.se> <20110224095848.GD24543@fly> <1298545686.25101.36.camel@jm-desktop> Message-ID: <20110224112107.GA11720@fly> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Thu, Feb 24, 2011 at 01:08:06PM +0200, Jouni Malinen wrote: > On Thu, 2011-02-24 at 01:58 -0800, Cedric Sodhi wrote: > > I hope I understood you correctly. If you want me to run "rfkill list" > > at the very moment between those two 132 errors, that could be difficult > > as they appear very quickly after eachother > > Yes, I think you understood correctly. However, it looks like this is > something specific to what Gentoo is doing in its network configuration > scripts. It looks like /etc/init.d/net.wlan? script ends up soft > blocking all wifi for some reason and that result in the 132 error. Why would it do that? To be frank I doubt your diagnosis at this point, how did you come to conclude that? > If this causes you any problems in getting wpa_supplicant running, I would > suggest targeting this question to whoever is maintaining the Gentoo > scripts. You can also try to manually unblock the soft block with > "rfkill unblock wifi" before starting wpa_supplicant. I might have misunderstood, but as I said the device is unlocked before and after the (attempted) start of wpa_supplicant: # rfkill list Soft lock: no Hard lock: no # /etc/init.d/net.wlan1 restart ... SIOCSIFFLAGS: Unknown error 132 SIOCSIFFLAGS: Unknown error 132 ... # rfkill list Soft lock: no Hard lock: no Trying to unlock wouldn't make any sense, correct? > I was able to reproduce the part of WLAN getting soft blocked, but the > script did manage to get wpa_supplicant running. Please make sure you > are running an up-to-date version of wpa_supplicant to get better > support for dynamically changing rfkill state. I'll try a bleeding-edge wpa_supplicant and will report back. Do you have any ideas left? I'm quite certain that Gentoo Devs will not be able to help me with that but rather point me at you, saying the driver has a problem. PS: Would it perhaps be possible that you configure your MUA so that it respects mailing lists? It appears to reply like to an ordinary message which coerces me (and others) to manually copy over the correct address when we want to reply to you.