Hi there,
I have a really strange issue with my Atheros WiFi card since re-installing Arch. It doesn't manage to connect to my wireless AP, except when I first boot windows and then reboot to Arch. So it looks like Arch doesn't manage to start the card properly. Output from dmesg is the same in both cases, and the card correctly shows up in lspci.
[sorcix@morpheus ~]$ dmesg | grep ath ath9k 0000:01:0b.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18 ath: EEPROM regdomain: 0x30 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: AM ath: Regpair used: 0x30 ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' Registered led device: ath9k-phy0
I tried netcfg, networkmanager and manually using wpa_supplicant. When I didn't boot windows first, the card seems to connect to the AP, and then disconnect again.
wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
It then starts looping trying to reconnect.
After first booting into windows, it simply connects and stays connected. Everything works fine then. Note that it always works fine in windows, so it isn't a hardware problem.
Does anyone else have this problem, or knows how to fix it?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
On Tue, Jul 26, 2011 at 10:19, Vic Demuzere vic@demuzere.be wrote:
<snip>
wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
It then starts looping trying to reconnect.
AFAIK Reason 3 means wrong secret. You don't have it right, or you have not set up the Connection Manager correctly.
On 26 July 2011 10:01, Filip Filipov pilif.pilif@googlemail.com wrote:
AFAIK Reason 3 means wrong secret. You don't have it right, or you have not set up the Connection Manager correctly.
According to the header file [1]: WLAN_REASON_DEAUTH_LEAVING.
It doesn't make any sense.
Also, the PSK is correct, as the same configuration works fine after first booting into windows.
[1] http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=blob;f...
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
On 26 July 2011 09:19, Vic Demuzere vic@demuzere.be wrote:
Hi there,
I have a really strange issue with my Atheros WiFi card since re-installing Arch. It doesn't manage to connect to my wireless AP, except when I first boot windows and then reboot to Arch. So it looks like Arch doesn't manage to start the card properly. Output from dmesg is the same in both cases, and the card correctly shows up in lspci.
[sorcix@morpheus ~]$ dmesg | grep ath ath9k 0000:01:0b.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18 ath: EEPROM regdomain: 0x30 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: AM ath: Regpair used: 0x30 ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' Registered led device: ath9k-phy0
I tried netcfg, networkmanager and manually using wpa_supplicant. When I didn't boot windows first, the card seems to connect to the AP, and then disconnect again.
wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
It then starts looping trying to reconnect.
After first booting into windows, it simply connects and stays connected. Everything works fine then. Note that it always works fine in windows, so it isn't a hardware problem.
Does anyone else have this problem, or knows how to fix it?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
You could try playing with rfkill a bit.
2011/7/26 Lukáš Jirkovský l.jirkovsky@gmail.com:
You could try playing with rfkill a bit.
Thanks, I didn't know about rfkill.
It doesn't seem to help though, it shows up as not blocked in rfkill, even when it doesn't work.
Is there anywhere I can look for differences between a cold boot and a reboot from windows? I tried "dmesg | grep ath" but the output is the same in both cases. There must be a difference in output somewhere, right?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
On 07/26/2011 12:30 PM, Vic Demuzere wrote:
2011/7/26 Lukáš Jirkovskýl.jirkovsky@gmail.com:
You could try playing with rfkill a bit.
Thanks, I didn't know about rfkill.
It doesn't seem to help though, it shows up as not blocked in rfkill, even when it doesn't work.
Is there anywhere I can look for differences between a cold boot and a reboot from windows? I tried "dmesg | grep ath" but the output is the same in both cases. There must be a difference in output somewhere, right?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
Vic,
On my Toshiba laptop, I created a profile in rc.conf based on the following note:
Install the netcfg package, create a profile under /etc/network.d (there are some examples, so you shouldn't have any problem), and edit /etc/rc.conf: add the name of your profile into "NETWORKS=(...)" and add 'net-profiles' to your DAEMONS.
I have had no problems with Atheros wifi since. It connects every time.
On 26 July 2011 23:13, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On my Toshiba laptop, I created a profile in rc.conf based on the following note:
Install the netcfg package, create a profile under /etc/network.d (there are some examples, so you shouldn't have any problem), and edit /etc/rc.conf: add the name of your profile into "NETWORKS=(...)" and add 'net-profiles' to your DAEMONS.
I have had no problems with Atheros wifi since. It connects every time.
I'm using net-auto-wireless instead of net-profiles, I could try to change that. But I don't think that will solve it, as it doesn't even work when connecting manually. I tried connecting to my network using networkmanager, netcfg and manual wpa_supplicant. Neither work, so I doubt it has something to do with the netcfg config.
It's worth the try though, thanks!
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
Hi,
I had a similar problem with a different WiFi card. Try "ifconfig wlan0 down" before starting the network.
-- Benedikt
On 27 July 2011 11:02, Benedikt Kraxner b.kraxner@gmail.com wrote:
Hi,
I had a similar problem with a different WiFi card. Try "ifconfig wlan0 down" before starting the network.
That sounds like a weird solution, never tried that! I've tried using "ip link set dev up" before starting the network.
I can't test it right now, I'm waiting for a hard disk replacement for my home partition. (Or I should figure out how to mount /home and /var in tmpfs). I'll try it out when I have my Arch back up & running.
Thanks for your help!
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
On 26/07/11 17:19, Vic Demuzere wrote:
After first booting into windows, it simply connects and stays connected. Everything works fine then. Note that it always works fine in windows, so it isn't a hardware problem.
Does anyone else have this problem, or knows how to fix it?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
One possibility is firmware, do you have the correct one installed for your card?
On 27 July 2011 13:47, JL Young johnlawrence.young@gmail.com wrote:
On 26/07/11 17:19, Vic Demuzere wrote:
After first booting into windows, it simply connects and stays connected. Everything works fine then. Note that it always works fine in windows, so it isn't a hardware problem.
Does anyone else have this problem, or knows how to fix it?
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
One possibility is firmware, do you have the correct one installed for your card?
ath5k and ath9k are part of the kernel now, so that should be a problem, right?
http://linuxwireless.org/en/users/Drivers/ath9k
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
I tried setting the netcfg profile as David C. Rankin suggested, also tried "ifconfig wlan0 down" before starting the network. Tried reloading the ath9k module, nothing helped.
It still only works when I have used the WiFi connection on windows first, then reboot to Arch.
I've found an ath9k mailing list, I'll try asking it there. Thanks for all your help!
-- vic@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features.
On 29-07-11 11:54, Vic Demuzere wrote: [...]
It still only works when I have used the WiFi connection on windows first, then reboot to Arch.
I've found an ath9k mailing list, I'll try asking it there. Thanks for all your help!
Please do report back here if you find a solution as there may be more users who get bitten by this bug.
mvg, Guus
On 08/01/2011 09:07 PM, Guus Snijders wrote:
Please do report back here if you find a solution as there may be more users who get bitten by this bug.
I didn't find a solution on that list. They asked me to enable debug messages, but that required recompiling the kernel. I have never done that before, and currently don't have time to look into that.
Setting the channel width to 20MHz on the access point fixed it though. It used to be set to "Auth 20/40 MHz". Looks like the ath9k is not compatible with that setting, but the windows driver is.
arch-general@lists.archlinux.org