[VU+ Uno4KSE] Missing support for WiFi dongle [Archive] - Satellite Support Forum .: Home of OpenViX Team:.

View Full Version : [VU+ Uno4KSE] Missing support for WiFi dongle

stunt

31-07-20, 15:05

I have Vu+ Uno 4k SE, Vu+ Zero 4k, Vu+ Solo2 and Vu+ Duo 2
All of them are running OpenViX 5.3.037 or newer build until this date.

But only my Vu+ Uno 4kSE won't accept the wifi dongle.
The option for choosing Device, doesn't exist under Menu->Setup->Network->Device.
But it exist on my other boxoes.

Why? And how to solve this?
My ethernet dongle is as shown in picture60468

Andy_Hazza

31-07-20, 15:38

You installed the vu+ wifi drivers from the plugin feeds?

Sent from my iPhone using Tapatalk

Andy_Hazza

31-07-20, 15:39

Or maybe after inserting the vu+ wifi dongle do a reboot?

Sent from my iPhone using Tapatalk

stunt

31-07-20, 20:36

I tried both downloading all drivers as shown in screenshots, and rebooting after inserting the device.
Nothing helped.
The reason for multiple downloads of drivers, are cause I don't know the name of the wifi-dongle as shown above.
604706047160472

Andy_Hazza

01-08-20, 10:00

The Vu+ drivers for their Wifi dongle must already come pre-installed. Personally I would flash the latest ViX image (5.3.039) and start again.

Sent from my iPhone using Tapatalk

stunt

01-08-20, 12:52

For me, it seems like the driver doesn't exist in the builds for Vu+ Uno 4k SE and Vu+ Solo2.
Neither in the image or under plugin download menu.
Both are now running 5.3.039

I tried the older WiFi-dongle that was in the Solo2, and now the WiFi works in Uno 4k SE. but not the newer dongle in the Solo2.
This is the one that works on both Vu+ Solo2 and Vu+ Uno 4k SE:
6047360474

Update; I didn't notice the issue also included the Solo2, since it had the older WiFi-dongle.

ronand

01-08-20, 13:18

The RT5572 drivers should work with the new dongle if it is original. However there are a lot of fakes on the market. The original VU adapter has the RT8192CU chipset

stunt

01-08-20, 15:07

The RT5572 drivers should work with the new dongle if it is original. However there are a lot of fakes on the market. The original VU adapter has the RT8192CU chipset

But how come when the dongle (if it's fake) works well on Vu+zero 4k, but not on my uno 4k se?
Both are running latest build of the openvix image. 5.3.039
I have 2 of the latest dongle. Neither of them are working on uno 4k se, but does on zero 4k.
And I doubt it's fake since I got it when I ordered the uno 4k se and my zero 4k

ronand

01-08-20, 17:48

If it doesn't work its because the drivers are not installed - not because it is real or fake. As to what chipset is in it there are several ways to identify it. If there is an FCC ID on it then you can easily find out online (the old dongle is made by edimax). You could open it up and you will definitely see the chipset. Or you could ask your seller what drivers it requires. Have you tried the RT5572 drivers?

BrianTheTechieSnail

01-08-20, 20:31

Another way to identify it is to plug it in to a PC that's running Windows.
Then, using device manager, you will either be able to see what drivers get loaded for it or what it's hardware ID is. They look like this kind of thing: USB\VID_1D2E&PID_612E&REV_0100

Then you can search Google for it's hardware ID.

I bet if you SSH into your box there is also a way to get the Linux to tell you the hardware IDs.
I don't know how off hand though.

Joe_90

01-08-20, 23:38

Yes - if you ssh into your box and type lsusb you will get the IDs of all the USB devices attached. Thereafter you can do an internet search on the ID and it will give you details of the device and on-board chip etc. Here is a sample from my desktop:

joe@joe-desktop:~$ lsusb
Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 001 Device 003: ID 0c45:7603 Microdia
Bus 001 Device 005: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I've bolded the device id of the mouse

stunt

01-08-20, 23:56

Thank you for tips for finding model numbers

If it doesn't work its because the drivers are not installed - not because it is real or fake. As to what chipset is in it there are several ways to identify it. If there is an FCC ID on it then you can easily find out online (the old dongle is made by edimax). You could open it up and you will definitely see the chipset. Or you could ask your seller what drivers it requires. Have you tried the RT5572 drivers? .

Yes. I did install the RT5572

Another way to identify it is to plug it in to a PC that's running Windows.
Then, using device manager, you will either be able to see what drivers get loaded for it or what it's hardware ID is. They look like this kind of thing: USB\VID_1D2E&PID_612E&REV_0100

Then you can search Google for it's hardware ID.

I bet if you SSH into your box there is also a way to get the Linux to tell you the hardware IDs.
I don't know how off hand though.

The black new one that i'm struggling with:
USB\VID_148F&PID_5372\9&32ac2f53&0&1

The old one that works:
USB\VID_0BDA&PID_8178\00e04c000001

ronand

02-08-20, 00:46

Thats a Ralink 5372 - the RT3070 driver is the correct one

stunt

02-08-20, 11:43

Thats a Ralink 5372 - the RT3070 driver is the correct one

I installed it on both solo 2 and uno 4k se. Neither of them worked.

Joe_90

02-08-20, 11:49

stunt

02-08-20, 13:15

According to Debian the RT2800 driver should support that Ralink device -
https://wiki.debian.org/rt2800usb

Now, it may need some additional kernel driver. I use a no-name wireless dongle that supposedly is an RTL8812 which is in the image builds, but it needs the RTL8814 kernel driver which is not, so I end up having to manually install it each time I flash a new release.

I downloaded this stable release:
http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-misc-nonfree_20190114-2_all.deb
But how did you install in on the box?
Unzip and copy all files manually to respective folders, or only few of them like the /lib/firmware/rt3070.bin?

Joe_90

02-08-20, 15:23

I downloaded this stable release:
http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-misc-nonfree_20190114-2_all.deb
But how did you install in on the box?
Unzip and copy all files manually to respective folders, or only few of them like the /lib/firmware/rt3070.bin?

No - don't install anything from Debian! That was just the source where I got the info on Ralink drivers! Just download the RT2800 driver from the Openvix driver repository and install it.

spanner123

02-08-20, 16:55

https://www.world-of-satellite.com/showthread.php?37996-Network-drive-rt2800usb&p=500966#post500966 Post no. 3 Don't know if there is a newer one though.

Joe_90

02-08-20, 18:13

It's in the plugins list you screen grabbed earlier. Just download and install from there.

edit - my post was intended for the OP.

stunt

03-08-20, 13:40

It's in the plugins list you screen grabbed earlier. Just download and install from there.

edit - my post was intended for the OP.

Before starting this thread, I allready tried to install all of those. But still not working.

Joe_90

03-08-20, 13:52

stunt

03-08-20, 22:07

Just to be clear - you installed ALL of the drivers? If you did do that, then maybe uninstall all except RT2800. Or start with a clean image and just install RT2800. Otherwise contact VU+ and ask them to supply a driver suitable for your particular model.

I tried as you said.
Removed them all exept the RT2800
Fresh image with RT2800 as only extras via ipk-file
Then at the end also added the RT3070 as suggested earlier.

Now I will contact Vu+ or maby grab driver files from the Vu+ Zero 4k. Cause it works there.