[SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

Julius2 · 2011-01-12 14:38:55

Although I had previously been running the ar9170 (with some problems like long connection times and frequent disconnections), I decided to try the carl9170 driver. I followed the instructions on the Wiki page, disabling conflicting drivers, downloading the carl9170 firmware package from the AUR, and then loading up the driver. Unfortunately, "iwconfig" and "ifconfig -a" showed nothing but eth0 and lo. My device is in the list of supported devices, so I was hoping that the problem was user error rather than incompatibility. Does anyone have experience with this driver? If so, what did you do to get it working?

Last edited by Julius2 (2011-01-13 14:41:49)

.:B:. · 2011-01-12 15:12:45

Check dmesg for output. If your device needs firmware and doesn't find it, or the driver encounters another error at load time, you'll see it there. If the driver recognises the device and activates it, you'll see it there.

Julius2 · 2011-01-12 15:23:29

I checked the dmesg output and didn't find anything obvious. here if you want to take a look at it yourself.

EDIT: It tells me the modules aren't loaded when I go to unload them with rmmod (ar9170usb, etc). Is it automatically loading carl9170 now? Maybe it only works if it starts itself and I was doing something wrong while manually loading it.

Last edited by Julius2 (2011-01-12 15:44:47)

.:B:. · 2011-01-12 16:32:12

You know what lsmod is for right?

And this would suggest the carl9170 module is being loaded, and the device is recognised:

ath: EEPROM regdomain: 0x807c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: CA
ath: Regpair used: 0x3a
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
cfg80211: Calling CRDA for country: CA
Registered led device: carl9170-phy0::tx
Registered led device: carl9170-phy0::assoc
usb 2-1.3: Atheros AR9170 is registered as 'phy0'
udev[3620]: renamed network interface wlan0 to wlanusb

Julius2 · 2011-01-13 14:41:31

Hmm, looks like whatever I was doing with loading it manually wasn't working properly. Now it works fine, I'm going to mark this as solved and attempt to bury this embarrassment.

Arch Linux

#1 2011-01-12 14:38:55

[SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

#2 2011-01-12 15:12:45

Re: [SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

#3 2011-01-12 15:23:29

Re: [SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

#4 2011-01-12 16:32:12

Re: [SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

#5 2011-01-13 14:41:31

Re: [SOLVED] D-Link DWA-160 A2 with carl9170 - No Interface

Board footer