Posts by s3n0

    Hi.


    Could someone advise me, how to enable the serial port for Vu+ Zero 4K in Linux OS ?


    I learned on the OpenATV forum that this Zero 4K has its serial port "locked" (non-functional for Linux system) after successfully booting the set-top box. And this is really a problem. The serial port cannot then be used in any way under the Linux system, after the set-top box has been successfully booted. This serial port is only "service port" and is active only during the booting of the set-top box. After that, this serial service port is supposed to shut down.


    It is an RJ12 connector on the back panel of the Vu+ Zero 4K. And... of course, the pinouts of the RJ12 connector are connected correctly.


    I made the RJ12 <-> RS232 adapter myself and it also works without problems on my other set-top box: Vu+ Solo SE V2 (in this set-top box, the serial port works even after booting and while the set-top box is running, as a full-fledged serial port in the system).


    I am using the build:


    OpenATV 7.3

    Linux kernel 4.1.20

    ARM chipset


    Does anyone know a trick or an unofficial third-party driver that can enable the serial port on the RJ12 connector in the Linux system on the Zero 4K set-top box, even after it boots ?


    Thank you in advance for any advice.

    Hi.


    This depends on the firmware (which particular Enigma2 distribution) you use in your set-top box.


    It basically depends on the version of the system kernel (Linux).


    And then it depends on which WiFi dongle drivers are available in the specific firmware - according to the specific chipset and system kernel (linux kernel version).


    Also, these WiFi dongle drivers must be properly debugged and thus functional. Common practice is often to move drivers without testing them to other set-top boxes with similar hardware and with the same Linux kernel, and this is not good.


    Another common problem is the fact that many WiFi dongles release a new HW revision over time. This means that even if the WiFi USB dongle appears to be the same, it may not be the same inside. This is the case, for example, with the Tenda U2 device. For example, a built-in USB HUB can be added to which a USB Flash Memory Stick with an installer is connected and at the same time the network WiFi card itself, ... and a problem can arise with the initialization of the WiFi USB dongle in Linux, which does not recognize the new HW revision and this revision the driver does not assume (expect). Then it doesn't work even if the driver is correct.


    But there are many similar cases in different HW revisions.


    For example, some WiFi USB dongles, such as the TP-LINK TL-WN725N-V3 device, add a function where when searching for available WiFi networks, they change the MAC address to a random one - while searching for available WiFi networks. This is for higher security. However, if the current WiFi driver in the used firmware of your set-top box does not support this, again there is a problem with finding available WiFi networks and possibly other problems. The driver for this TP-LINK device then requires an update, also to support HW revision number 3.


    So... under normal circumstances, even if you google the chipset included in the selected WiFi USB dongle that you are going to buy, this driver in your firmware (you can find it simply through a terminal connection to your set-bop box, e.g. with commands: opkg update; opkg list | grep "chipset-name" ), may not work correctly if it is a new HW revision of the WiFi USB dongle. It is best if they are old HW revisions. They should be supported and therefore functional.

    Yup... picons are kept in CACHE... also when SKIN is loaded / starting, available directories with picons are searched. And subsequently, the picon CACHE is used to store some picons - in RAM. That's why a quick restart of the Enigma2-GUI is always convenient, after updating picons.

    Hi.


    Alternative tools like YouTube-DL and YT-DLP work perfectly, so maybe this could be used for playback as well... somehow it might work. Or am I wrong ?


    I know it's a big difference to stream directly from a YouTube server and download parts of videos and then play them back... but it could work.

    Hi Smafia.


    If you have to ask how to do it, don't do it. It is more complicated even for people from the IT profession.


    One option is to use DD-WRT firmware and then Entware or Optware and install Oscam.


    Or even some other firmwares in routers, it is possible to use Entware and Optware. But it is a "long-distance run" to get Oscam there.


    Alternatively, you can make a server instead of a WiFi router. You buy a Raspberry or another mini-PC, connected with a LAN-switch, also with a high-quality WiFi antenna + install and set everything... and it's done :). You have a full-fledged Linux where you can do what you need... and at the same time it will serve as a WiFi router.

    I am well aware that my question is a difficult one. But, I thought the answer could list all the scenarios. :rasta: I'll tell you more as soon as I can. And I will give you the log file if you want. Thanks for your help.

    Not. You have to describe... as I mentioned... what you are trying to do. What, where, how, with whom, why, how much, etc. . Based on this, it can only then be assumed where the error could probably be.


    You could also include your configuration files (ideally in the CODE TAG). However, you will overwrite all private passwords and IP addresses (also all host-names) with some censorship (for example, "X" characters), for your safety.

    Hi.


    Sorry, but this is a stupid question.


    You provided very little information. You could have at least stated what you were trying to do, how you did it or what you did before before it still worked correctly for you.


    In addition, this error message can represent many different errors in Oscam.

    Hi.


    Simply use the unofficial online shell-script from the creators of OpenATV. It installs the necessary feed according to the detection of which Enigma2 core you use in ATV and according to the detected architecture.


    Page 16 / Post #312:

    I don't know this Qviart Dual 4K either, but according to the specification, it also only has HDMI 2.0a version.


    So far there is OpenPLi and also OpenATV for this set-top box:

    OpenPLi: https://openpli.org/download/qviart/Dual+4K

    OpenATV: http://images.mynonpublic.com/…rrent/index.php?open=dual


    Of course Qviart, as I already wrote, gives bad support to the creators of Enigma2. So it can happen, for example, in 1-3 more years that a new version of OpenPLi or OpenATV will no longer be available for this set-top box. However, this does not mean that the set-top box will not continue to be used. Everything will work for at least 5 years :).

    However, Qviart Lunix has very poor software support for Enigma2 development. This manufacturer ignores the development teams of various Enigma2 distributions (firmware) and does not supply / update new drivers that are necessary to run the new Linux kernel. And this means that there is a problem with updates to newer firmware (which, paradoxically, always contains a newer Linux OS kernel).


    Otherwise, these Qviart Lunix are very cheap and also good set-top boxes.


    https://satelity.ellano.sk/qviart-lunix-4k_38417.html - it can even be compared to Vu+ Zero 4K... although, of course, Vu+ uses better semiconductor components and a better type of DVB tuner

    Vu + Zero 4K


    Note, it can be bought with a DVB-C tuner but also with DVB-S2X --- so... choose the right one !

    However, this Vu+ only includes HDMI v2.0.

    Vu+ are more expensive, but after Dreambox, these Vu+ are the second best Linux set-top boxes.


    If you want something cheaper, choose from others listed above, such as Gigablue, Zgemma, Octagon, etc. .

    Has the OE "5.3" folder been added to the server ? How fast was that, uhm. In the case of Python3 test versions a year ago, it took a very long time to add another folder for the new OE :-).


    BTW, guys like Captain  SpaceRat  Space-Rat  Nicker etc. ... please ... who in the OpenATV team has access to the "feed" shell-script ? SpaceRat ?


    Earlier I suggested modifying the code in the "feed" shell script, specifically in the get_oever() function. This was a case of the POSIX syntax of the "sed" tool, which was not written correctly and did not work well in all cases of Linux-Shell interpreters... but in the meantime, I have an even better suggestion, to modify the code of the mentioned function to remove it redundant text, already directly in the Python code and not in the Linux-Shell:


    - from original:


    - to this new code:

    anestis1956


    Why don't you read what I write ?


    POST No. #325 - However, it is only a temporary solution !


    I also wrote that the NEWEST version does not mean a good version. This version 7.3 is a test version. Not officially released. Only version 7.2 is available for download on the official website of OpenATV. But not 7.3. This test version 7.3 can only be downloaded via the modified link.


    Many softcams do not have many dependencies on the Linux system (system libraries) used in set-top boxes. Of course... sometimes the dependencies (on system libraries such as SSL, CRYTPO, USB, etc.) also change... but not very often. So the softcams for OE 5.2 from the current OpenATV 7.2 should also work in the test version of OpenATV 7.3.

    Do it by commandline and it will get the correct one for your version of image.

    Code
    wget -O - -q http://updates.mynonpublic.com/oea/feed | bash

    Or just open OpenWebif and look at the information, in the left column click on info: "About device". And the "OE-Alliance ?.?" version will be also listed there.

    Your link is bad. It is intended for developers, beta-testers or experienced users who know that the standard softcam feed extension will not work yet ! They can also deal with problems, and even report these problems or propose their own correction (on Github).


    The official http link for downloading OpenATV is here:

    Downloads gesamt

    And there you will only find version 7.2 - as the last stable released version of OpenATV.


    If you edit the http link manually to download version 7.3, it does not mean that it is the official version !

    The last stable OpenATV version is 7.2 and not 7.3. Why are you downloading the test (beta/alpha) version 7.3?


    There is probably another OE version and that's why it doesn't work. You can try this as a temporary solution:

    Code
    wget -O /tmp/feed --no-check-certificate "http://updates.mynonpublic.com/oea/feed"
    chmod a+x /tmp/feed
    sed -i '133iOEVER="5.2"' /tmp/feed
    /tmp/feed


    That should help. The OE 5.2 feed will also be used in OpenATV 7.3. This means that the softcam feed intended for OpenATV 7.2 will be used in OpenATV 7.3.


    However, I warn you... that after the release of the official version 7.3, it would be a good idea to uninstall this softcam-feed again and install the original one again (it will then be modified so that it works for the 7.3 version as well).