Opened 7 years ago

Closed 6 years ago

Last modified 5 years ago

#13977 closed enhancement (duplicate)

Ralink RT5370 adapter driver doesn't work

Reported by: Haiker Owned by: nobody
Priority: normal Milestone:
Component: Drivers/Network Version: R1/Development
Keywords: Cc:
Blocked By: #12158 Blocking:
Platform: All

Description (last modified by diver)

Ralink RT5370 adapter (Tenda W311Ma) doesn't work for me in Haiku nightly hrev51774. After connecting the adapter to my PC it does not detect automatically. When I executing

ifconfig -a

from the terminal, there are only ethernet and loobback devices:

/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

This adapter also is supported in FreeBSD by the "run" driver: https://www.freebsd.org/cgi/man.cgi?query=run&apropos=0&sektion=4&manpath=FreeBSD+9.3-stable&arch=default&format=html and it was included in that since 8.1 release: https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers#FreeBSD And there is 3rdparty port probably of this driver for Haiku, which supports the same chipsets as that driver (rt2870 and rt3070, rt5370 is listed in FreeBSD list too): https://github.com/jackburton79/haiku_ralink_usb I tried to compile and install it from that sources by make and make install commands, previously worte to makefile

DRIVER_PATH = net/

and

INSTALL_DIR = /boot/system/non-packaged/add-ons/kernel/drivers/bin

Also I made a symlink on it in /dev/net. But after installing the driver and reboot there is the same situation. When I try to up /dev/net/ralink_usb/0 by ifconfig, there is an error "no such device". So is it possible to get working this driver in Haiku?

Change History (7)

comment:1 by diver, 7 years ago

Description: modified (diff)
Owner: changed from mmlr to jackburton
Status: newassigned

My guess is that haiku_ralink_usb is incomplete.

comment:2 by pulkomandy, 7 years ago

There is probably a good reason this driver wasn't integrated in Haiku. And indeed, it is currently not possible to write a wifi driver for an USB device on Haiku.

The reason is you either write a native-style driver, and can support USB. Or, you write a FreeBSD style driver, and can support Wifi.

There is a GSoC project idea about adding USB to the FreeBSD compatibility layer to make this possible.

comment:3 by jackburton, 7 years ago

I stopped developing that driver since I don't have the hardware anymore, and the work to fully integrate it with the Haiku wifi stack was too much for me, anyway.

in reply to:  3 comment:4 by Haiker, 7 years ago

I have needed hardware (adapter), so maybe I can help you or another developer to test the driver?

comment:5 by korli, 7 years ago

Component: Network & Internet/WirelessDrivers/Network
Keywords: Ralink RT5370 Wi-Fi Haiku. removed
Owner: changed from jackburton to nobody
Type: bugenhancement

comment:6 by waddlesplash, 6 years ago

Blocked By: 12158 added
Resolution: duplicate
Status: assignedclosed

comment:7 by nielx, 5 years ago

Milestone: Unscheduled

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.