Hi Stefan, Am Sonntag, Februar 10, 2019 11:06 CET, Stefan Sperling <[email protected]> schrieb:
> On Sat, Feb 09, 2019 at 06:56:45PM +0100, Sebastian Reitenbach wrote: > > Hi, > > > > got a cheap TP-Link TL-WN821N, which shows up as Atheros AR7015 under > > Windows 10. > > > > athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev > > 2.00/2.02 addr 5 > > athn0: failed loadfirmware of file athn-open-ar7010 (error 2) > > athn0: could not load firmware > > athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev > > 2.00/2.02 addr 5 > > athn0: bad ROM checksum 0x2c64 > > athn0: could not read ROM > > athn0: could not attach chip > > > > > usbdevs -v: > > addr 05: 0cf3:7015 ATHEROS, USB WLAN > > high speed, power 500 mA, config 1, rev 2.02, iSerial 12345 > > driver: athn0 > > > > Just wanted to make sure I don't miss anything, don't see that chpset > > somehow > > listed in athn(4) page, so guess this is just not supported yet? > > Please try this device on a another USB port and/or another machine. > There's a long-standing bug where these devices don't work on some > USB host controllers with our drivers, in particular ehci(4). > > Last I tried plugging an athn(4) behind a hub, it would not work at all. > I tried that device on my amd64 desktop, as well as on a i386, and mips64el notebook. It's the same bad ROM checksum error I get on all three of them. I've another athn stick which works well on all three: athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB2.0 WLAN" rev 2.00/1.08 addr 5 athn0: AR9271 rev 1 (1T1R), ROM rev 13, address e8:de:27:15:9e:5e The non-working one shows up as AR7015 in Windows, but I don't see a AR7015 chipset mentioned in athn(4), therefore I wanted to verify, if that particular chipset is actually supported by our athn(4) at all? cheers, Sebastian
