Hi, > First note that dfly switched to a new usb stack recently. This is now the > default and wiggly in places. Unless you configured your kernel to use oldusb, > you'll be using the new usb stack.
I saw that DragonFly switched the USB stack and I did not change the configuration. So I should have installed the new USB stack. > If you are using the new usb stack, something does not add up here. > The usb ath driver is called if_uath and creates a device uathX. One should > then create a wlan device using > > ifconfig wlan0 wlandev uath0 > > etc. The WLAN card is a TPLink PCI card, so I expect not to run any USB driver here to get this card working. The ath driver seems to be loaded. Some details are shown in the dmesg output. These lines are added below > But even then, uath is not ported yet afaict, the module does ot build for me. > > Markus Thanks for your ideas. Sven dmesg snippets related to ath wlan: <802.11 Link Layer> ath_dfs: WTF module ath_rate: <SampleRate bit-rate selection algorithm> ath0.pci3.pcib3.pci0.pcib0.acpi0.nexus0.root0 ath0: <Atheros 2413> [tentative] mem 0xfebf0000-0xfebfffff irq 20 at device 5.0 on pci3 ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfebf0000 ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: AR2413 mac 7.8 RF2413 phy 4.5 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0056 ath0: Use hw queue 1 for WME_AC_BE traffic ath0: Use hw queue 0 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic ath0: Use hw queue 8 for CAB traffic ath0: Use hw queue 9 for beacons ath0: using multicast key search ath0: <Atheros 2413> [attached!] mem 0xfebf0000-0xfebfffff irq 20 at device 5.0 on pci3 pci3: <ACPI PCI bus> [attached!] on pcib3 pcib3: <ACPI PCI-PCI bridge> [attached!] at device 20.4 on pci0