77 replies to this topic

[pedy]

Whaaaaaaaaaaaaaat ?

[pedy]

Unfortunately the corresponding image is not attached, ill try again later.

[s3n0]

You must be doing something wrong.

 

In addition to uploading the image from the disk, you also have to click on "insert into the discussion".

 

You can also upload the image to a storage server such as https://imgbb.com/ or https://imgur.com/ and then insert a link to this uploaded image here.

[neo]

You can not paste an image, it will show, but it isn't saved. You need to upload via the "more reply options" button.

[pedy]

Here its the picture. I attached that.

Attached Files

•  IMG_3549.JPG   157.42KB   2 downloads

[s3n0]

As you can see, it is:

• ID = 0BDA:8179
• https://linux-hardwa...d=usb:0bda-8179
• RTL8188EUS, 802.11n, Wireless Network Adapter

I found "kernel-module-rt8188eu" on the OpenPLi feed server, but I don't know if this ".....eu" will work as well as the ".....eus" version. Maybe yes. I have no idea. That must be answered by OpenPLi experts, that whether it will work or whether some patch and update is needed. Also in OpenPLi list of supported WiFi devices there is this one "xxxxEU" but not "xxxxEUS" - https://wiki.openpli..._Device_support

Edited by s3n0, 7 May 2023 - 19:10.

[pedy]

Thank you for your response, according to the kernel you found, what is your recommendation to continue working and what does this mean considering that the Device_support page is empty in front of the rt8188eu table, thank you

[s3n0]

I dont know. Sorry.

 

First, you need to find out what the final letter "S" in the product label means. Maybe it can be found on the Internet... I don't know, sorry. If the "S" doesn't represent any hardware change that would require a whole new Linux driver, then it will probably work. Maybe "S" is just a "Small" model of the device, for example. I really have no idea what it means. It could mean anything.

 

First, find out whether support is already installed in your OpenPLi. It should also be possible via terminal / linux shell:

opkg list-installed | grep "8188"

Then, if you had your set-top box connected to the internet, and if the system driver and system firmware 8188 were not installed, then install them:

opkg update
opkg install firmware-rtl8188eu
opkg install kernel-module-r8188eu

Alternatively, other dependencies (modules / packages) will be installed automatically as needed, when you are connected to the Internet and if the compatibility of the system and OpenPLi (according to the version) is still maintained (I mean the current version of your OpenPLi).

Edited by s3n0, 9 May 2023 - 10:24.

[neo]

According to the source, that USB ID is supported: https://github.com/l.../usb_intf.c#L50

[pedy]

Hello, I executed the first command, opkg list-installed... and sent the result in the screenshot for review, please give your opinion, thank you.

please look attachment.

Attached Files

•  IMG_3554.JPG   60.46KB   1 downloads

[s3n0]

The firmware package is already installed, you still need the second one (kernel package), mentioned above, so install it. Then try to reboot the device and try to connect your WiFi USB dongle. I'm not sure if it will work since your USB is ".....EUS" and not ".....EU" model. Try it .

 

However... when you have a set-top box connected to the Internet, it should also be possible to install it through the GUI (Enigma2) - in the Plugin MENU - with the help of RCU.

Edited by s3n0, 11 May 2023 - 17:28.

[neo]

@s3n0:

 

According to the source, that USB ID is supported: https://github.com/l.../usb_intf.c#L50

 

[s3n0]

@neo:

Have you already found the difference between the chipset designation Realtek 8188 EU and Realtek 8188 EUS ? Because I don't . And I'm too lazy to google it . So I'm not sure if it will definitely work. Although as I wrote before, the hardware ID matches this one "......EUS" device.

[neo]

I looked in the source: https://github.com/l.../usb_intf.c#L47

 

It supports both EU and EUS, and defines the USB ID of the device in question: https://github.com/l.../usb_intf.c#L50

[s3n0]

OMG... yes... basically, one driver is used for multiple USB WiFi from one group of Realtek chipsets.

 

But I don't know what the added letter "S" at the end of the device marking means. If it's just some nonsense, like "S-mall" for example, then OK. But if it is, for example, a stronger antenna and the need for a stronger power supply from the USB port, then the driver also needs to be patched there. (I don't know - it's just a made-up example.)

 

I found the "aircrack" drivers on the internet... but that's another topic... I found them on Github - https://github.com/a...k-ng/rtl8188eus . And it also says that the current driver there works for rt8188eu + eus + etv, because apparently it's very similar hardware. However, I don't know what drivers are included on the feed server from OpenPLi. Are they also updated to current drivers ? Is it not necessary to update them somehow ? Will it work despite the unknown difference between EU and EUS ?

 

The link you sent me says nothing about the differences between EU and EUS. Again, only the same USB ID is listed there - for both EU and EUS devices, but there is nothing specific there.

If both EU and EUS are quite identical in hardware, then it's fine. But I have nowhere to find out.

Edited by s3n0, 11 May 2023 - 18:07.

[neo]

lwfinger is the authorative source of most of the realtek drivers, most others on github are forks.

 

We build from this repo: https://github.com/O...rt8188eu_1.0.bb

 

Which revision differs depending on the image:

8.3-release: https://github.com/O...orefs.conf#L291

develop: https://github.com/O...orefs.conf#L282 (i.e. HEAD)

Both support this particular USB ID.

 

Oh, and no clue what these letters mean, there is reference in the source to 8188EUS other then where the supported USB ID's are defined.

Edited by neo, 11 May 2023 - 18:27.

[s3n0]

I don't care about VID & PID from USB devices. I have already seen many devices whose PID & VID matched, but it was a completely different hardware. Specifically in USB WiFi from ASUS, the v1 and v2 models differ according to the HW revision, even though their PID & VID are quite the same... so the drivers didn't work... because you needed the right ones... for both v1 and v2 HW revision.

 

Therefore, the entire specification of the USB hardware is important (if the device provides it, it goes without saying what it should provide according to USB standards).

 

I won't argue with you about anything here. You're arguing with me again and about absolutely nothing.

 

If the driver works for both EU and EUS, then it's fine. But you didn't have to write 100 answers for practically nothing. And it's just a coincidence that EUS and EU are compatible with one driver. For many other devices, this may not apply.

 

That's why I drew attention to it right at the beginning.

 

In a few months, 100% someone will come to ask for help with USB WiFi from ASUS manufacturer... and you will again be firmly convinced of compatibility without trying the driver. But with this USB WiFi, the "universal" driver will no longer work.

[neo]

This happens a lot with "customer" implementation (the ones you see at the bottom of the USB ID list in the source. TP-Link is another vendor that just uses the first chip they can find.

 

But normally, a v1, v2, v3 all have different USB-ID's, I've never seen two different devices with the same ID, that would violate the USB consortium rules.

 

And I am not arguing, I am merely stating this driver supports these USB ID's. We're not talking about ASUS, we're not talking about other devices.

 

Only about this specific 8188EUS device, with the given USB ID. It is very normal for Realtek to have drivers that support a long list of devices with sometimes different identifications.

 

You speculate without any backing, based on "some" experience with something completely different, which is useless, both for the TS and for any other reader on this forum.

Edited by neo, 11 May 2023 - 20:05.

[pedy]

Dear s3n0 and neo friends, I think the continuation of this discussion between you gentlemen has become a bit specialized and it is a bit difficult and confusing for me to understand, I request you to please guide me in a simpler and easier way, what is the next step to overcome this challenge? Do I have to follow a new command in Telnet and if the answer is yes, what is that command? thank you

 

 

 

 

[neo]

@s3no already gave the relevant commands in this post: https://forums.openp...-3#entry1539144

 

Unplug the stick from the box if it is currently connected.

 

Then issue the three opkg commands from that post, one by one.

 

The reboot the box.

 

When it has started again, plug the stick in.

 

And finally issue the command "dmesg", and post the output here. Do this as direct as possible after you plugged in the stick.