You are not logged in.
I just built a needed wireless driver (ath9k_htc) from AUR. I thought that installing it from pacman would place it in the correct location for loading, but after reboot, 'lspci -k' showed the module hadn't been loaded, even though I'd set up a config in /etc/modules-load.d/ to do so. Here's some output from the build http://bpaste.net/show/N2Yl4UPewiLOupTfuYS1/
I'd appreciate any advice to move the needed file to the correct location (if necessary) and what I may have overlooked to get this module loaded at boot.
Reference: backports-patched 3.11_rc3_1-6
Last edited by bpont (2013-11-20 04:47:32)
Offline
First, this driver is in the kernel already, so no need to compile form AUR, especially when what you compiled is older than the current kernel. Second, ath9k_htc is an USB driver, so of course it won't show up in lspci.
Which wireless card do you have? Once you know that (using lspci if it's an internal card, or lsusb if it's an external adapter), you can research which driver you need. Most are in the kernel already and require no special setup.
Last edited by Gusar (2013-11-19 20:59:26)
Offline
First, this driver is in the kernel already, so no need to compile form AUR, especially when what you compiled is older than the current kernel. Second, ath9k_htc is an USB driver, so of course it won't show up in lspci.
Which wireless card do you have? Once you know that (using lspci if it's an internal card, or lsusb if it's an external adapter), you can research which driver you need. Most are in the kernel already and require no special setup.
Yes, it's a Netgear N150 Wireless USB Adapter WNA1100 which requires the ath9k_htc driver and the htc_9271.fw firmware (which I have installed). My understanding is that there's an ath9k driver already built-in as you say, but that the ath9k_htc driver is different and is meant to support my particular USB device and has to be installed via backports-patched (though, I could be mistaken about that). I have very limited experience with networking issues (wireless, in particular), so it's easy for me to overlook something. However, the reason I made the distinction is because that particular module (ath9k_htc) is mentioned on the wiki as needing to be built via the backports-patched package in AUR.
Right now, the module lives at /usr/lib/modules/extramodules-3.12-ARCH/drivers/net/wireless/ath/ath9k/ath9k_htc.ko.gz
...and I tried loading it in /etc/modules-load.d/netgear_wna1100.conf both with the line "ath9k_htc.ko.gz" and "ath9k_htc" but it didn't seem to work, though as you pointed out, I checked with 'lspci -k' and not 'lsusb -v' which I'll do now after a reboot (I'm on an XP partition at the moment, which has net access) and then I'll update this post with the results.
Edit
Here is the output of lsusb -v:
Bus 001 Device 003: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0846 NetGear, Inc.
idProduct 0x9030 WNA1100 Wireless-N 150 [Atheros AR9271]
bcdDevice 1.08
iManufacturer 16
iProduct 32
iSerial 48
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 60
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0There doesn't seem to be any driver information, but I guess it might be safe to assume the correct one has been loaded by virtue of the fact that lsusb showed this info?
Last edited by bpont (2013-11-19 23:07:48)
Offline
Both atk9k and ath9k_htc are in the kernel. I see how that wiki page is misleading, there's no mention of ath9k_htc anywhere but the backports section.
You don't need any modules-load.d file, udev loads device drivers automatically. Your device works out-of-the-box. I don't think lsusb shows modules like lspci -k does, check with lsmod.
Last edited by Gusar (2013-11-19 21:54:48)
Offline
Both atk9k and ath9k_htc are in the kernel. I see how that wiki page is misleading, there's no mention of ath9k_htc anywhere but the backports section.
You don't need any modules-load.d file, udev loads device drivers automatically. Your device works out-of-the-box. I don't think lsusb shows modules like lspci -k does, check with lsmod.
Thanks, this info has been helpful. So lsmod shows (I edited out anything non-relevant):
ath9k_htc 50891 0
ath9k_common 1670 1 ath9k_htc
ath9k_hw 378838 2 ath9k_common,ath9k_htc
ath 12833 3 ath9k_common,ath9k_htc,ath9k_hw
mac80211 396461 1 ath9k_htc
cfg80211 340580 3 ath,mac80211,ath9k_htc
compat 953 5 cfg80211,ath9k_common,mac80211,ath9k_htc,ath9k_hwI don't know how much of this output comes from the standard kernel and how much might be from the backports package. I also don't know how I'd be able to know if my device is actually using the ath9k_htc module. Any ideas?
Offline
OK, I'm adding some more info...what might be most relevant is at the end of this post, but I'm going to add some other output just in case it is relevant:
$ dmesg | grep usbcore
[ 0.958264] usbcore: registered new interface driver usbfs
[ 0.958285] usbcore: registered new interface driver hub
[ 0.960881] usbcore: registered new device driver usb
[ 4.802947] usbcore: registered new interface driver ath9k_htc
[ 6.824110] usbcore: registered new interface driver uvcvideo
[ 7.536458] usbcore: registered new interface driver snd-usb-audio
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s29f7u4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
link/ether e0:91:f5:56:82:89 brd ff:ff:ff:ff:ff:ff
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
DOWN mode DEFAULT group default qlen 1000
link/ether 00:0d:56:16:47:fd brd ff:ff:ff:ff:ff:ff
# ip link set wlp0s29f7u4 up
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s29f7u4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
link/ether e0:91:f5:56:82:89 brd ff:ff:ff:ff:ff:ff
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
DOWN mode DEFAULT group default qlen 1000
link/ether 00:0d:56:16:47:fd brd ff:ff:ff:ff:ff:ff
# dmesg | grep htc_9271.fw
[ 4.506629] usb 1-4: ath9k_htc: Firmware htc_9271.fw requested
[ 4.925309] usb 1-4: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
# iw dev wlp0s29f7u4 link
Not connected.
# iw dev wlp0s29f7u4 scan
/* I won't post all that output here (unless requested), but there *were* scan results of
/* available networks. My network was not found because my router is configured not to
/* broadcast the ESSID.
# iw dev
phy#0
Interface wlp0s29f7u4
ifindex 2
wdev 0x1
addr e0:91:f5:56:82:89
type managedOK, here's what's probably the most significant information:
# wpa_supplicant -i wlp0s29f7u4 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Line 13: invalid key_mgmt 'WPA-PSK-SHA256'
Line 13: failed to parse key_mgmt 'WPA-PSK WPA-PSK-SHA256'.
Line 14: unknown network field 'ieee80211w'.
Line 19: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.Here is my /etc/wpa.supplicant.conf:
# cat /etc/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
country=US
device_name=Netgear WNA1100
device_type=1-0050F204-1
filter_ssids=1
network={
ssid="my_essid"
scan_ssid=1
key_mgmt=WPA-PSK WPA-PSK-SHA256
ieee80211w=1
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk=<password>
}I have the network configured for wpa2-psk encryption, so I'm guessing I botched my configuration somewhere.
Offline
Both atk9k and ath9k_htc are in the kernel. I see how that wiki page is misleading, there's no mention of ath9k_htc anywhere but the backports section.
You don't need any modules-load.d file, udev loads device drivers automatically. Your device works out-of-the-box. I don't think lsusb shows modules like lspci -k does, check with lsmod.
I tweaked my config a bit:
# cat /etc/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
country=US
device_name=Netgear WNA1100
device_type=1-0050F204-1
network={
ssid="my_essid"
scan_ssid=0
key_mgmt=WPA-PSK
auth_alg=OPEN
psk=<password>
} Now I get a message that wpa_supplicant is successfully initialized, but there are subsequent error messages, and it also doesn't connect to my network:
# wpa_supplicant -i wlp0s29f7u4 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
# iw dev wlp0s29f7u4 link
Not connected. Offline
All the errors went away and everything is now working normally. The problem seemed to be that I had configured my router not to broadcast my SSID. It must have caused some scanning issues. When I turned broadcasting back on, my wireless configuration worked.
I also got rid of my /etc/modules.d/*.conf file and uninstalled backports-patched...both of which I didn't need.
Marking as solved.
Offline