Jump to content


Member Since 28 Dec 2016
Offline Last Active Yesterday, 20:43

Posts I've Made

In Topic: no named pil;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

26 May 2023 - 20:14



WanWizard is right. I think so.


According to the discussion from here:


You need to do this:

opkg update && opkg install python3-pillow

BTW, it is better to direct questions about plugins to the authors of these plugins, if they can be found on Google :-). If not, then write to the Enigma2 distribution support websites (PLi, ATV, HDF, BH, etc.) :-).

In Topic: Windows File explorer doesn't access Vu+ in a "short" network

20 May 2023 - 07:40



On Google you will find many instructions on how to diagnose these problems. It could be anything really. For example, Windows only requires or uses the SMB 2.0 protocol, while Enigma2 may only use the old 1.0 protocol. Although SMB1.0/CIFS is not famous because it can be a security risk, I have enabled it in Windows. Since then, Enigma2 has been working. In newer versions of Enigma2, of course, a newer version of the SMB protocol is used.


First, check the Linux system (set-top box). Windows is stubborn and prefers to manage everything by itself. There should be no error in Windows. Rather, there is probably an error in the Linux settings... as usual... Linux is a really great OS, but it requires careful configuration and diagnostics.


Unfortunately there is a dependency on the type of Linux. Set-top boxes contain only stripped-down (very small) Linux, so that means a fewer tools for diagnosing problems. But even so, the problem can be diagnosed. You just have to use some limited tools (not all that you can find on the internet).


You can also try accessing Total Commander via IP address instead of DNS name. Type in the command line in Total Comamnder below, this:

cd \\set-top-box-IP-address\shared-folder-name

If you share the entire root directory of your set-top box, then of course this is also sufficient:

cd \\set-top-box-IP-address

If you change the DNS name in the LAN... it is necessary to execute the flush DNS command (in Windows systems). Alternatively, if your WIFI router uses a local DNS cache... then restart your WIFI router afterwards. Or restart the WIFI router and also the set-top box and also the PC :-D.

In Topic: Bootlogo (splash_cfe_auto.bin / splash_cfe_auto.bmp)

12 May 2023 - 16:14

Vu+ Zero 4K looks for / requires / needs / the correct name and path for the splash logo image, as follows:



In Topic: OpenPLi supported WiFi chipsets

11 May 2023 - 19:21

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.

In Topic: OpenPLi supported WiFi chipsets

11 May 2023 - 18:05

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.