Ralink rt5370 adapter doesn't work

Feedback Hardware
1

Hello everybody.
After installing Haiku on my PC there doesn’t work Ralink rt5370 Wi-Fi adapter (Tenda W311Ma). After connecting the adapter I also tried to execute ifconfig -a in the Haiku Shell. But there are only ethernet and loopback devices, and no my adapter listed:
/dev/net/via_rhine/0
Hardware type: Ethernet, Address: 00:0e:a6:33:75:7e
Media type: 100 MBit, 100BASE-TX
inet addr: 192.168.0.100, Bcast: 192.168.0.255, Mask: 255.255.255.0
MTU: 1500, Metric: 0, up broadcast link auto-configured
Receive: 8159 packets, 0 errors, 8362934 bytes, 0 mcasts, 0 dropped
Transmit: 7858 packets, 0 errors, 1835763 bytes, 0 mcasts, 0 dropped
Collisions: 0

loop    Hardware type: Local Loopback, Address: none
        inet addr: 127.0.0.1, Mask: 255.0.0.0
        inet6 addr: ::1, Prefix Length: 128
        MTU: 16384, Metric: 0, up loopback link
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Collisions: 0

In listdev my adapter is not listed:

device Network controller (Ethernet controller) [2|0|0]
  vendor 1106: VIA Technologies, Inc.
  device 3065: VT6102/VT6103 [Rhine-II]

device Multimedia controller (Multimedia audio controller) [4|1|0]
  vendor 1106: VIA Technologies, Inc.
  device 3059: VT8233/A/8235/8237 AC97 Audio Controller

device Mass storage controller (IDE interface) [1|1|8a]
  vendor 1106: VIA Technologies, Inc.
  device 0571: VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE

device Bridge (ISA bridge) [6|1|0]
  vendor 1106: VIA Technologies, Inc.
  device 3177: VT8235 ISA Bridge

device Serial bus controller (USB controller, EHCI) [c|3|20]
  vendor 1106: VIA Technologies, Inc.
  device 3104: USB 2.0

device Serial bus controller (USB controller, UHCI) [c|3|0]
  vendor 1106: VIA Technologies, Inc.
  device 3038: VT82xx/62xx UHCI USB 1.1 Controller

device Serial bus controller (USB controller, UHCI) [c|3|0]
  vendor 1106: VIA Technologies, Inc.
  device 3038: VT82xx/62xx UHCI USB 1.1 Controller

device Serial bus controller (USB controller, UHCI) [c|3|0]
  vendor 1106: VIA Technologies, Inc.
  device 3038: VT82xx/62xx UHCI USB 1.1 Controller

device Communication controller [7|80|0]
  vendor 11c1: LSI Corporation
  device 044c: LT WinModem

device Display controller [3|80|0]
  vendor 1002: Advanced Micro Devices, Inc. [AMD/ATI]
  device 4e71: RV350/M10 [Mobility Radeon 9600] (Secondary)

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 1002: Advanced Micro Devices, Inc. [AMD/ATI]
  device 4e51: RV350 [Radeon 9550/9600/X1050 Series]

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 1106: VIA Technologies, Inc.
  device b198: VT8237/VX700 PCI Bridge

device Bridge (Host bridge) [6|0|0]
  vendor 1106: VIA Technologies, Inc.
  device 3189: VT8377 [KT400/KT600 AGP] Host Bridge

But in listusb it is listed correctly:

09da:000a /dev/bus/usb/0/0 "A4Tech Co., Ltd." "Optical Mouse Opto 510D / OP-620D" ver. 0623
1c4f:0002 /dev/bus/usb/0/1 "SiGma Micro" "Keyboard TRACER Gamma Ivory" ver. 0110
0000:0000 /dev/bus/usb/0/hub "HAIKU Inc." "UHCI RootHub" ver. 0110
0000:0000 /dev/bus/usb/1/hub "HAIKU Inc." "UHCI RootHub" ver. 0110
0000:0000 /dev/bus/usb/2/hub "HAIKU Inc." "UHCI RootHub" ver. 0110
148f:5370 /dev/bus/usb/3/2 "Ralink Technology, Corp." "RT5370 Wireless Adapter" ver. 0101
0951:1689 /dev/bus/usb/3/3 "Kingston Technology" "DataTraveler SE9" ver. 0100
0000:0000 /dev/bus/usb/3/hub "HAIKU Inc." "EHCI RootHub" ver. 0200

Probably this adapter uses rt2870 driver, because on the Drivers & Tools CD which comes with it, the Linux driver in the W311Ma folder is named “rt2870” and it works after installling in Linux. For Haiku I found this driver too, and downloaded it here (probably unofficial?): https://github.com/jackburton79/haiku_ralink_usb Then I compiled and installed it by make and make install commands, previously wroted needed paths and other optional parameters in makefile:
DRIVER_PATH = net/
and
INSTALL_DIR = /boot/system/non-packaged/add-ons/kernel/drivers/bin
But after executing
ifconfig /dev/net/ralink_usb/0 192.168.0.101 255.255.255.0 up
there is an error
ifconfig: Could not add interface: No such device
The same error appears if try to execute the same command for the driver named “ralinkwifi”.
I also maked a link on the “ralink_usb” driver in /dev/net.
If the driver “ralink_usb” is correct, is there a way to get working my device in Haiku? Thanks.

2

Usb wifi adapters are currently not supported in Haiku. So you will have to find some other way to get online.

3

Thanks for the reply. But if there is no usb wifi support in Haiku, why that driver is named “haiku_ralink_usb”?

4

Cause it supports Ralink based USB interfaces? I don’t know, i just assumes it from the _usb part.

HaikuFan, please, try to understand, if one says Haiku support this and that, and not support something else, we are meaning: the Haiku base install, without any 3rdparty driver.

This is a 3rdparty driver.
You should ask the developer, what’s the state of this driver.
You can create an issue at github too.
You got the hardware, you can help to the developer to debug it.

We can’t do anything else here.

5

Thanks a lot. I fully understood you. So I need to contact to the developer of this driver.

6

You need to make a bug report with this data, because developers does not watching this forum so much.

http://besly.de/menu/search/archiv/dev/haiku-trac_eng.html
http://besly.de/menu/search/archiv/misc/beslysat_eng.html
http://besly.de/menu/search/archiv/misc/haiku-hardware_compatibility_list.html

7

This driver doesn’t support your hardware. Your device has product ID 5370, the driver you’re talking about checks for product ID 3070, presumably because that’s what the author had. These are similar, but there’s no guarantee that “just” swapping out the ID would get it working even if the driver was otherwise serviceable.

However the driver has been abandoned unfinished, a big part of the source code you downloaded is the unmodified FreeBSD driver, and then that’s been cut-and-pasted to try to make a Haiku driver.

The author started out assuming that Haiku has a complete native WiFi stack, and they just needed to plug the FreeBSD driver into Haiku’s USB stack and WiFi stack, keeping only the hardware-specific bits. What they realised after a few days was that nope, Haiku doesn’t have a native WiFi stack. So, they would need to not only translate the FreeBSD driver to use Haiku’s semi-working USB stack, but they’d also need to hook it back into the compatibility layer in Haiku for FreeBSD network drivers. Some point along that road they came to their senses and just plugged in a Cat5 cable or switched to a different laptop.

Your resourcefulness in searching Github is commendable, but in this case it seems unlikely to result in a working system.

8

The bugreport is created: https://dev.haiku-os.org/ticket/13977