Re: Atheros driver.
On Sun, Sep 30, 2012 at 10:42:55PM +0930, David Walker wrote: Hi. I'm trying to find a PCI wireless card and bought one of these: http://www.tp-link.com/en/products/details/?categoryid=246model=TL-WN350GD dmesg shows: vendor Atheros, unknown product 0x001d (class network subclass ethernet, rev 0x01) at pci1 dev 1 function 0 not configured Does this mean point blank this is an un-supported chipset or are there things to check, etcetera? That means it is unclaimed by all drivers in the kernel. In this case it seems to be an AR2417, which would be covered by ath(4) if ath was updated to support it. So it is unsupported for now.
Re: Atheros driver.
It looks like you're probably out of luck, see http://madwifi-project.org/wiki/Compatibility/TP-Link TL-WN350GD is AR2417 / AR5007G, neither of which are listed either in athn(4) or ath(4), or the CVS commits if openbsd src is searched. I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Which relates to http://www.tp-link.com/en/products/details/?categoryid=240model=TL-WN951N http://www.wikidevi.com/wiki/TP-LINK_TL-WN951N_v1 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. On 30 September 2012 14:12, David Walker davidianwal...@gmail.com wrote: Hi. I'm trying to find a PCI wireless card and bought one of these: http://www.tp-link.com/en/products/details/?categoryid=246model=TL-WN350GD dmesg shows: vendor Atheros, unknown product 0x001d (class network subclass ethernet, rev 0x01) at pci1 dev 1 function 0 not configured Does this mean point blank this is an un-supported chipset or are there things to check, etcetera? Best wishes.
Re: Atheros driver.
On Sun, Sep 30, 2012 at 04:39:16PM +0100, Peter Kay wrote: I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. Android might require power management support which was recently added to athn(4) in -current. So try -current on the AP, it might fix problems with the Android device.
Re: Atheros driver.
This is post the -current fix with athn(4) power saving. Without it Android devices don't really work at all, with it they work for a bit and then stop working claiming the access point isn't within range. It's a problem that's not specific to OpenBSD - some access points suffer the same issue, but I've not seen a definite solution so far. On 30 September 2012 17:38, Stefan Sperling s...@openbsd.org wrote: On Sun, Sep 30, 2012 at 04:39:16PM +0100, Peter Kay wrote: I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. Android might require power management support which was recently added to athn(4) in -current. So try -current on the AP, it might fix problems with the Android device.
