TP-Link TL-WN8200ND in 5.4

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

TP-Link TL-WN8200ND in 5.4

Bernd Schoeller-2
Hello,

I was hoping that my TP-Link TL-WN8200ND works in 5.4, but it looks like
it is only detected as an unsupported USB device.

ugen0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2

While the documentation from the provider is not verbose about the
chipset used, the following page claims that it is a Realtek RTL8192CU,
which seems to be supported by urtwn(4).

http://wikidevi.com/wiki/TP-LINK_TL-WN8200ND

Assuming that the firmware was missing, I tried fw_update, but that did
not download any firmware files.

I would be thankful for any kind of help to get this adapter running.

Bernd


# usbdevs -v



Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
RDC(0x17f3), rev 1.00
 port 1 powered
 port 2 addr 2: high speed, power 500 mA, config 1, 802.11n WLAN
Adapter(0x0100), Realtek(0x2357), rev 2.00, iSerialNumber 00e04c000001
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
RDC(0x17f3), rev 1.00
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
RDC(0x17f3), rev 1.00
 port 1 powered
 port 2 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
RDC(0x17f3), rev 1.00
 port 1 powered
 port 2 powered

# dmesg
OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Vortex86 SoC  (586-class) 934 MHz
cpu0: FPU,TSC,CX8,MMX
real mem  = 1039724544 (991MB)
avail mem = 1011290112 (964MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010
apm0 at bios0: Power Management spec V1.2
pcibios0 at bios0: rev 3.0 @ 0xf0000/0x10000
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries)
pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 vendor "RDC", unknown product 0x6022 rev 0x00
rl0 at pci0 dev 1 function 0 "Realtek 8139" rev 0x10: irq 11, address
44:4d:50:07:1b:19
rlphy0 at rl0 phy 0: RTL internal PHY
rl1 at pci0 dev 2 function 0 "Realtek 8139" rev 0x10: irq 11, address
44:4d:50:07:1b:1a
rlphy1 at rl1 phy 0: RTL internal PHY
pcib0 at pci0 dev 7 function 0 vendor "RDC", unknown product 0x6036 rev 0x00
vte0 at pci0 dev 8 function 0 "RDC R6040 Ethernet" rev 0x00: irq 6,
address 00:1b:eb:25:30:9e
rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1
ohci0 at pci0 dev 10 function 0 "RDC R6060 USB" rev 0x12: irq 7, version
1.0, legacy support
ehci0 at pci0 dev 10 function 1 "RDC R6061 USB" rev 0x03: irq 3
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "RDC EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 11 function 0 "RDC R6060 USB" rev 0x12: irq 5, version
1.0, legacy support
ehci1 at pci0 dev 11 function 1 "RDC R6061 USB" rev 0x03: irq 9
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "RDC EHCI root hub" rev 2.00/1.00 addr 1
pciide0 at pci0 dev 12 function 0 "RDC R1011 IDE" rev 0x01: DMA
(unsupported), channel 0 configured to compatibility, channel 1
configured to compatibility
pciide0: channel 0 ignored (not responding; disabled or no drives?)
wd0 at pciide0 channel 1 drive 0: <ST9320421AS>
wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
vga1 at pci0 dev 13 function 0 vendor "RDC", unknown product 0x2012 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
azalia0 at pci0 dev 14 function 0 vendor "RDC", unknown product 0x3010
rev 0x01: irq 10
azalia0: No codecs found
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: probed fifo depth: 0 bytes
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb2 at ohci0: USB revision 1.0
uhub2 at usb2 "RDC OHCI root hub" rev 1.00/1.00 addr 1
usb3 at ohci1: USB revision 1.0
uhub3 at usb3 "RDC OHCI root hub" rev 1.00/1.00 addr 1
ugen0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid0: 256 targets
root on wd0a (197b846eebaa6c90.a) swap on wd0b dump on wd0b

Reply | Threaded
Open this post in threaded view
|

Re: TP-Link TL-WN8200ND in 5.4

Jonathan Gray-11
On Thu, Jan 16, 2014 at 08:09:00PM +0000, Bernte wrote:

> Hello,
>
> I was hoping that my TP-Link TL-WN8200ND works in 5.4, but it looks like
> it is only detected as an unsupported USB device.
>
> ugen0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2
>
> While the documentation from the provider is not verbose about the
> chipset used, the following page claims that it is a Realtek RTL8192CU,
> which seems to be supported by urtwn(4).
>
> http://wikidevi.com/wiki/TP-LINK_TL-WN8200ND
>
> Assuming that the firmware was missing, I tried fw_update, but that did
> not download any firmware files.
>
> I would be thankful for any kind of help to get this adapter running.
>
> Bernd

A device attaching as ugen means no driver has claimed it.
Support for your device and many other urtwn devices was added
after 5.4.

Here is an untested patch against 5.4 that should work:

to apply:

cd /usr/src/sys/dev/usb
patch -p0 < /tmp/path/to/patch
make

then build and install a kernel as normal

Index: usbdevs
===================================================================
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.601
diff -u -p -r1.601 usbdevs
--- usbdevs 21 Jul 2013 15:19:41 -0000 1.601
+++ usbdevs 17 Jan 2014 06:25:21 -0000
@@ -600,6 +600,7 @@ vendor TRENDNET 0x20f4 TRENDnet
 vendor RTSYSTEMS 0x2100 RT Systems
 vendor DLINK3 0x2101 D-Link
 vendor MOTOROLA2 0x22b8 Motorola
+vendor TPLINK 0x2357 TP-Link
 vendor TRIPPLITE 0x2478 Tripp-Lite
 vendor NHJ 0x2770  NHJ
 vendor ASUSTEK 0x2821 ASUSTeK Computer
@@ -3980,6 +3981,9 @@ product TORADEX ORIENT 0x0015 Toradex O
 /* Toshiba Corp products */
 product TOSHIBA RT3070 0x0a07 RT3070
 product TOSHIBA HSDPA 0x1302 HSDPA
+
+/* TP-Link products */
+product TPLINK RTL8192CU 0x0100 RTL8192CU
 
 /* Trek Technology products */
 product TREK THUMBDRIVE 0x1111 ThumbDrive
Index: if_urtwn.c
===================================================================
RCS file: /cvs/src/sys/dev/usb/if_urtwn.c,v
retrieving revision 1.27
diff -u -p -r1.27 if_urtwn.c
--- if_urtwn.c 21 Jul 2013 15:19:52 -0000 1.27
+++ if_urtwn.c 17 Jan 2014 06:24:35 -0000
@@ -130,6 +130,7 @@ static const struct usb_devno urtwn_devs
  { USB_VENDOR_SITECOMEU, USB_PRODUCT_SITECOMEU_RTL8188CU },
  { USB_VENDOR_SITECOMEU, USB_PRODUCT_SITECOMEU_RTL8188CU_2 },
  { USB_VENDOR_SITECOMEU, USB_PRODUCT_SITECOMEU_RTL8192CU },
+ { USB_VENDOR_TPLINK, USB_PRODUCT_TPLINK_RTL8192CU },
  { USB_VENDOR_TRENDNET, USB_PRODUCT_TRENDNET_RTL8188CU },
  { USB_VENDOR_TRENDNET, USB_PRODUCT_TRENDNET_RTL8192CU },
  { USB_VENDOR_ZYXEL, USB_PRODUCT_ZYXEL_RTL8192CU }

Reply | Threaded
Open this post in threaded view
|

Re: TP-Link TL-WN8200ND in 5.4

Bernd Schoeller-2
On 17/01/14 06:45, Jonathan Gray wrote:
> A device attaching as ugen means no driver has claimed it.
> Support for your device and many other urtwn devices was added
> after 5.4.
>
> Here is an untested patch against 5.4 that should work:

Hi Jonathan,

Thank you very much for the help, this was exactly what I was hoping
for, great support!

The only thing extra that I did (outside the FAQ) was calling 'make' in
/usr/src/sys/dev/usb to re-generate the header files. Not sure if that
was the right way to do it, normally I expected this to happen outside
the source tree as part of the regular 'make' call. But this way I
managed to compile the kernel and install it.

Again, thank you,
Bernd

Reply | Threaded
Open this post in threaded view
|

Re: TP-Link TL-WN8200ND in 5.4

Alexey Suslikov
Bernte <bernte <at> fams.de> writes:

> the source tree as part of the regular 'make' call. But this way I
> managed to compile the kernel and install it.

you didn't tell us is your urtwn(4) variant working or not after installing
new kernel. new dmesg wouldn't hurt.

Reply | Threaded
Open this post in threaded view
|

Re: TP-Link TL-WN8200ND in 5.4

Bernd Schoeller-2
On 18/01/14 13:40, Alexey E. Suslikov wrote:
>> the source tree as part of the regular 'make' call. But this way I
>> managed to compile the kernel and install it.
>
> you didn't tell us is your urtwn(4) variant working or not after installing
> new kernel. new dmesg wouldn't hurt.

Sorry for the late answer. The card seems to be recognized, see dmesg
below (a little censored with XX).

I still have problems getting it up to run; scanning works, but I cannot
seem to setup a stable WPA connection. It is probably me, so I will
continue to play around.

I am a little disappointed that the hostap is not supported, but that
was well documented.

Bernd

OpenBSD 5.4 (GENERIC) #0: Sat Jan 18 06:56:40 GMT 2014
     root@XXXXXXXX:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Vortex86 SoC  (586-class) 934 MHz
cpu0: FPU,TSC,CX8,MMX
real mem  = 1039724544 (991MB)
avail mem = 1011290112 (964MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010
apm0 at bios0: Power Management spec V1.2
pcibios0 at bios0: rev 3.0 @ 0xf0000/0x10000
 

pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries)
 

pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036
 

pcibios0: Warning, unable to fix up PCI interrupt routing
 

pcibios0: PCI bus #0 is the last bus
 

bios0: ROM list: 0xc0000/0x8000
 

cpu0 at mainbus0: (uniprocessor)
 

pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 

pchb0 at pci0 dev 0 function 0 vendor "RDC", unknown product 0x6022 rev
0x00

rl0 at pci0 dev 1 function 0 "Realtek 8139" rev 0x10: irq 11, address
44:4d:50:07:1b:19

rlphy0 at rl0 phy 0: RTL internal PHY
 

rl1 at pci0 dev 2 function 0 "Realtek 8139" rev 0x10: irq 11, address
44:4d:50:07:1b:1a

rlphy1 at rl1 phy 0: RTL internal PHY
 

pcib0 at pci0 dev 7 function 0 vendor "RDC", unknown product 0x6036 rev
0x00

vte0 at pci0 dev 8 function 0 "RDC R6040 Ethernet" rev 0x00: irq 6,
address 00:1b:eb:25:30:9e

rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1
 

ohci0 at pci0 dev 10 function 0 "RDC R6060 USB" rev 0x12: irq 7, version
1.0, legacy support

ehci0 at pci0 dev 10 function 1 "RDC R6061 USB" rev 0x03: irq 3
 

usb0 at ehci0: USB revision 2.0
 

uhub0 at usb0 "RDC EHCI root hub" rev 2.00/1.00 addr 1
 

ohci1 at pci0 dev 11 function 0 "RDC R6060 USB" rev 0x12: irq 5, version
1.0, legacy support
ehci1 at pci0 dev 11 function 1 "RDC R6061 USB" rev 0x03: irq 9
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "RDC EHCI root hub" rev 2.00/1.00 addr 1
pciide0 at pci0 dev 12 function 0 "RDC R1011 IDE" rev 0x01: DMA
(unsupported), channel 0 configured to compatibility, channel 1
configured to compatibility
pciide0: channel 0 ignored (not responding; disabled or no drives?)
wd0 at pciide0 channel 1 drive 0: <ST9320421AS>
wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
vga1 at pci0 dev 13 function 0 vendor "RDC", unknown product 0x2012 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
azalia0 at pci0 dev 14 function 0 vendor "RDC", unknown product 0x3010
rev 0x01: irq 10
azalia0: codecs: Realtek ALC262
audio0 at azalia0
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: probed fifo depth: 0 bytes
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb2 at ohci0: USB revision 1.0
uhub2 at usb2 "RDC OHCI root hub" rev 1.00/1.00 addr 1
usb3 at ohci1: USB revision 1.0
uhub3 at usb3 "RDC OHCI root hub" rev 1.00/1.00 addr 1
umass0 at uhub0 port 1 configuration 1 interface 0 "Generic Mass Storage
Device" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <Multi, Flash Reader, 1.00> SCSI0 0/direct
removable serial.058f6366058F0O1111B1
sd0: 248MB, 512 bytes/sector, 508928 sectors
uhidev0 at uhub2 port 2 configuration 1 interface 0 "Logitech USB
Receiver" rev 1.10/9.10 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 5 buttons, Z dir
wsmouse0 at ums0 mux 0
uhidev1 at uhub3 port 2 configuration 1 interface 0 "Cherry
Mikroschalter product 0x0011" rev 2.00/1.00 addr 2
uhidev1: iclass 3/1
ukbd0 at uhidev1: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (197b846eebaa6c90.a) swap on wd0b dump on wd0b
WARNING: / was not properly unmounted
sd0 detached
scsibus0 detached
umass0 detached
urtwn0 at uhub0 port 1 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2
urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R, address XX:XX:XX:XX:XX:XX

Reply | Threaded
Open this post in threaded view
|

Re: TP-Link TL-WN8200ND in 5.4

Jonathan Gray-11
On Wed, Jan 22, 2014 at 08:37:53PM +0000, Bernte wrote:

> On 18/01/14 13:40, Alexey E. Suslikov wrote:
> >>the source tree as part of the regular 'make' call. But this way I
> >>managed to compile the kernel and install it.
> >
> >you didn't tell us is your urtwn(4) variant working or not after installing
> >new kernel. new dmesg wouldn't hurt.
>
> Sorry for the late answer. The card seems to be recognized, see
> dmesg below (a little censored with XX).
>
> I still have problems getting it up to run; scanning works, but I
> cannot seem to setup a stable WPA connection. It is probably me, so
> I will continue to play around.
>
> I am a little disappointed that the hostap is not supported, but
> that was well documented.

For hostap Stefan has proposed the following diff against -current:
http://marc.info/?l=openbsd-tech&m=138983310300769&w=2