Just tested an Edimax EW-7811Un N150 Wireless USB Adapter Nano, Version 1 which reports as a RealTek 8188CUS.
It works well which is great news because the laptop’s built in Atheros QCA6174 wifi isn’t supported
3 Likes
After long time pause of using Haiku, i test latest hrev55910(gcc2),
I have TP Link Wifi USB adapter TL-WN723N, is represent as
~> listusb | grep Realtek
2357:0109 /dev/bus/usb/1/0/1 "TP-Link" "TL-WN823N v2/v3 [Realtek RTL8192EU]" ver. 0200
is not working, but its nice that find it,
in Network manager i see “no link”
OK, just bought a $9.99 Tplink TL-WN725N (as linked above), and can confirm that it works perfectly in Haiku. Great work Augustin.
8 Likes
Wow. Cool. My Edimax EW-7811UN Super Mini WLAN USB-Stick (150MBit) does work out of the box. Its a random USB WIFI Dongle that I bought like 9 years ago. Yes. I double checked. 9 years.
1 Like
My USB dongle is labeled as “SURECOM EP-9001” it seems it has some Realtek chipset inside.
Booted with hrev55916, the green led is blinking but nothing happens, so the Network window reports “No link” (device appears as “rtl81xx/0”).
listusb reports:
0bda:b006 /dev/bus/usb/0/3 “Realtek Semiconductor Corp.” "Bluetooth Radio " ver. 0200
(this is my bluetooth adapter, no further realtek chipset detected, so I assume this dongle is totally unsupported ATM)
Under linux it appears as (sudo lsusb -v):
Bus 001 Device 008: ID 0769:31f3 Surecom Technology Corp. RT2573
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0769 Surecom Technology Corp.
idProduct 0x31f3 RT2573
bcdDevice 0.01
iManufacturer 1 Ralink
iProduct 2 802.11 bg WLAN
iSerial 3 (error)
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0035
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 (error)
bmAttributes 0x80
(Bus Powered)
MaxPower 300mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 5
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 (error)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
IIRC RT2573 is a Ralink chipset 
The company was bought by MediaTek so name changed.
Uh, so I was misleaded by the device identification “rtl” which is usually a short for realtek!
Sorry for the buzz!
Have start with the adapter inside or you plug in the adapter after system is started?
Anyone got an AC600 or better adapter to work? I am not sure what the support is like in FreeBSD, there is an RTL8812AU driver but it seems that it is not mainline https://github.com/s3erios/urtwm
Booted the OS with the dongle already plugged in, as waddlesplash suggested.
The driver does not support the “EU”-class devices (not sure what the differences are) unfortunately.
This is a Ralink device, those need a different driver. It’s on my TODO list to look into.
rtl81xx is a Realtek PCI ethernet device, not a WiFi device.
That driver is old. The mainline one in FreeBSD supports 8812AU/8821AU already. I tested with an 8812AU, works fine.
Hmm, actually I was mistaken; it does claim to support 8192EU. The ID for “WN823NV2” is already listed in the driver, so I guess if it is not working, there is some other problem.
My D-Link DWA-172 works. I’m told it has an RTL8811AU chip.
I have a RT2573 card in one of my x86 machines (32 bit) that is not detected. It reports as 0db0:6877 (Micro Star International RT2573). I think RT2573 is supported but perhaps this USB ID is not known?
In RT2573, RT stands for Ralink Technology. I will probably work with rum driver when ported.
Realtek chips names are starting by RTL.
2 Likes
@waddlesplash Thank you very much for all the work you are doing for Haiku and specifically for that one.
I bought a TP-Link with 10 euros and I have wireless for first time. A recent buy but looks like is working good enough. I have seen some disconnections-automatic reconnections sometimes but I have updated Haiku succesfully through it.
Please keep up the good work 
5 Likes
Is your adapter listed on our hardware list?
If not add it here to help collect running hardware:
1 Like
Just added
4 Likes
My device is similitar rtl8812AE(ASUS PCE-AC51) but it’s PCI and apparently is not supported yet. In the Next hours i try to figure out what are the device id’s if there is not device id added to the driver.
… Editing RTL8192EU does not work (ASUS PCE-N15).
The driver added is for USB only and adding the device ID wouldn’t be enough, I fear.