Date: Sat, 27 Oct 2018 17:50:31 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-stable@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: TP-LINK TL-WN321G Message-ID: <3D95450B-21E6-4587-B246-2345CB301834@lists.zabbadoz.net> In-Reply-To: <f9eb9b42-dc8f-02c8-9b48-99c83b3eceaf@zyxst.net> References: <f9eb9b42-dc8f-02c8-9b48-99c83b3eceaf@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Oct 2018, at 16:01, tech-lists wrote: Hi, > context: 12-stable amd64 > > When TP-LINK TL-WN321G usb dongle is inserted, this appears in dmesg: > > ugen1.3: <Ralink 802.11 n WLAN> at usbus1 .. > run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address > [REDACTED] .. > and run0 appears, and works, yet: > > rum(4) says it supports this: > TP-LINK TL-WN321G > > but no rum0 happens either on insertion (using standard GENERIC > kernel) or with rum loaded. The problem with these dongles is that sometimes there’s a rev A and a rev B which use entirely different chipsets and hence are entirely different drivers. That is rarely observable from online shopping sites or even product packaging. I haven’t checked this particular case but if you can send me a usbconfig dump_device_desc for it I can go an have a look. /bz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D95450B-21E6-4587-B246-2345CB301834>