You are not logged in.
I'm installing Arch on a desktop PC which has a TP-Link WN822N USB wireless adaptor (2.4Ghz only), which is correctly detected and uses the ath kernel module. Before I formatted the computer I had Ubuntu 14.04 on it for over 18 months, which worked perfectly with the wifi.
When I boot into the Arch installer from a USB stick I can use wifi-menu to successfully connect to my wireless network, which happens to be on channel 13. The problem is that once I reboot into the installed Arch system (during the install I installed the following: base dialog wpa_supplicant networkmanager iw) I can only see networks on the 2.4GHz channels 1-11, no matter if I use wifi-menu or NetworkManager.
I've tried connecting directly to my wireless network by putting in the name and password with nmcli, but it just comes back with 'No network with that SSID' or something.
I've confirmed that both the Arch installer and the installed system use the same kernel - 4.2.5-1 - and that in the dmesg output the 'ath' module is automatically choosing the domain 'CN'. I've tried changing the regdomain with 'iw set reg' to various different things (00, US, EU, AU etc.) but it doesn't seem to help.
I don't understand what the difference between the installer environment and my installed system could be? Any ideas?
(BTW I don't want to change the wifi channel because a) the router chose that automatically, and b) there are around 23 wifi networks visible (incl. the channel 13 ones) so choosing a channel manually is a pain; plus I want to find out what's gone wrong here)
Last edited by tk83 (2015-12-16 10:46:59)
Offline
Can you show the output of 'dmesg | grep cfg80211' please?
1000
Offline
Thanks, but I worked out what I was missing: installing the 'base' package (following the Installation Guide in the wiki) doesn't actually install the crda package. It's also not installed when installing NetworkManager.
So the solution is:
pacman -Sy crda
vim /etc/conf.d/wireless-regdom # uncomment the line for the right country/region
reboot
Last edited by tk83 (2015-12-16 10:49:17)
Offline
Great that you found a solution for your problem. Just a note: Use of "pacman -Sy <package-name>" is discouraged. Better to use "pacman -Syu <package-name>" for reasons explained here.
Last edited by cjazz (2015-12-16 12:02:17)
Offline