Repository navigation
Closed
Labels
Description
Hi @catalinii and others,
I've now one unit of the cheap James Donkey HD DUO. And after a lot of testing over several weeks I can finally run minisatip on this device, albeit with fairly limited capabilities. So first of all I want to share the facts I have discovered:
- The unit can run minisatip if you install the last version of the OpenATV firmware version 6.4. One relevant aspect is to use the driver version: 20210607 (kernel 4.4.35).
- To run minisatip you need to use the option
-1 1because the stream can only be readed from the/dev/dvb/adapter0/demuxXand not the common/dev/dvb/adapter0/dvrX. - The "streaming" mode requires to be enabled using
echo 1 > /proc/stb/parameters/ts_tap(already set by the script/etc/init.d/dinobot-pvr.sh). - The firmware has some bug regarding the background splash image. Therefore you need to kill the
showiframeprocess that is consuming a lot of CPU resources. - Current minisatip ARM binaries can't be run because a mismatch with the GLIBC version. You need to recompile it with an older toolchain with
./configure --enable-static --host=arm-linux-gnueabihf --disable-dvbca --disable-dvbcsaandmake EXTRA_CFLAGS="-DNEEDS_SENDMMSG_SHIM". - The pid filtering implemented inside the dvb driver is very buggy. With the simple
dmesgcommand you can see a lot of errors. And now I discovered that the driver only supports up to 10 "service" pids plus another 10 "psi" pids. So you have to request the opening of the pids in this order: first you can request up to 10 pids from the range 32-8190, and then continue with another 10 pids from the range 0-31. This is very crazy. But if you request the opening of the pids not using this technique, then you can open only a small number of pids. If you request for example:100,0,101,1,102,16then you will recive only pids 100 and 0, and nothing else! So the golden strategy is to open (0-10)service_pids, (0-10)psi_pids. - But anything else seems to work very well. I can use the two tuners independently, and stream multiple pids with a bandwith of 30mbps from each tuner without troubles.
Therefore, I request if you can help to improve the support for this device:
- The first "simple" question is to provide a compatible binary. I suggest to add to the releases another ARM target compiled with an older toolchain, and with
EXTRA_CFLAGS="-DNEEDS_SENDMMSG_SHIM". I feel several low cost devices with ARM cores will agree. You accept this @catalinii ? - The second question is how to handle the "limited pid list". My first idea is to ordering the received pid list, split it in two groups, and send it in the correct way limiting to 10 pids per list. However, a lot of edges cases can appear. So any idea to almost improve the current behaviour with minimal changes?
Please, comment anything you want, and let me know if you want me to perform any concrete test.
Activity
catalinii commentedon May 22, 2023
Hey @lars18th,
IMHO we should not really support such devices.
There are few reasons for that:
I honestly feel disappointed by my gigablue (quad 4k) that takes 1s to set a pid filter, which makes tuning to a channel a 10s deal.
I understand that the device is cheaper than a regular one (50EUR vs 100-150EUR), but you will pay 10x that difference in time spent to make it work and keep supporting it.
IMHO I am ok if we do not support devices for which the company that creates them does not do the minimum of providing a device that can handle the DVBAPI.
Jalle19 commentedon May 22, 2023
I agree with @catalinii , some devices are just not worth the trouble. It's already somewhat of a pain tl support AXE devices, and those at least have some unique capabilities (cheap, fast quad tuner with internal switching matrix, custom OS). But an aliexpress dual tuner, meh 🤷
Providing a pre-built binary on the other hand could be done, especially if there are other old Enigma device that would benefit from that. Feel free to make the necessary changes to the GitHub workflow.
lars18th commentedon May 23, 2023
Hi,
Thank you for your comments. Regarding this:
OK, and I can do it.
However, before changing the
/workflows/binaries.yml, we need to update the containercatalinii/minisatip-build-image:latestto add the "legacy" toolchain for ARM. The one that I've used searching from the Internet is this: http://tropical.jungle-team.online/utilidades/toolchains.tar.gz.If @catalinii updates the container and he put the toolchain (this or anything else similar) in one alternative path (like
/opt/arm-legacy/), then I'll update the workflow to generate the new target: ARM-legacy.You agree?
catalinii commentedon May 23, 2023
The issue here is that the toolchain contains an old gcc version (4.8.3). I am trying to use newer C features and not really enjoying keeping old gcc supported.
Why not update openatv: http://images.mynonpublic.com/openatv/7.2/index.php?open=jdhdduo
lars18th commentedon May 24, 2023
Because this version has some troubles with this device. I've tested 7.x and 6.x, and the most reliable version (for running minisatip) is the 6.4 (LTS). I do the same with my other Enigma boxes (Edision and ZGemma). So please, continue supporting old compilers. With embedded devices is quite common to it have only ancient toolchains.
So, direct question: You agree to include inside a separate subdirectory (i.e.
/opt/legacy-toolchain/) the older toolchain in the docker container? If you agree then I'll prepare a PR for it.Regards.
Jalle19 commentedon May 24, 2023
What kind of troubles?
catalinii commentedon May 24, 2023
IMHO if we have to use a older version of glibc that could be ok, but we still need a new compiler. Was wondering how that would work with clang.
Which glibc version is openatv running?
lars18th commentedon May 24, 2023
$ strings /lib/libc.so.6 | grep LIBC-->GLIBC_2.30This is true on both ARM (JamesDonkey) and MIPS (Edision).
The errors running the current minisatip binaries in ARM are:
The same version in MIPS is not generating any error. Any idea @catalinii ?
I don't know how to link to an specific previous version of glibc with the toolchain.
lars18th commentedon May 24, 2023
Hi @Jalle19 ,
With OpenATV 7.x in the James Donkey HD DUO the system seems to run very slowly. For this reason I prefer to stay running 6.4, because I run only minisatip and nothing else (enigma2 is off). I the rest of boxes I continue with 6.4 because I don't need nothing more... minisatip just runs ok.
lars18th commentedon May 24, 2023
Hi @catalinii ,
FYI, the last "binary release" ARM compatible with GLIBC is v1.1.92 (Apr 28, 2022). And the first with errors is v1.2.1 (May 2, 2022). Checking the docker image seems that this is the change that has broked the compatiblity (Apr 29, 2022): catalinii/minisatip-build-image@6314dff
It could be that you compile the OpenSSL for ARM with a different toolchain?
Jalle19 commentedon May 24, 2023
@lars18th does it run so slow that minisatip can't be used? Seems odd.
catalinii commentedon May 24, 2023
The driver does not seem to have been updates in the last 5 years: https://github.com/oe-alliance/oe-alliance-core/blame/4.1/meta-brands/meta-dinobot/recipes-linux/linux-dinobot_4.4.35.bb
so to run minisatip just libc is probably changed between versions (6.4 -> 7.x)
lars18th commentedon May 26, 2023
Hi @catalinii ,
Regarding the Docker Container to generate the binaries:
Dockerfile: usingFROM ubuntu:20.04insted ofFROM ubuntu:lunar../configure --enable-static --host=arm-linux-gnueabihf --disable-dvbca --disable-dvbcsa && make.objdump -T minisatip | grep -Eo 'GLIBC_\S+' | sort -udisplays this:Therefore, I suggest these changes:
Futhermore, I see that for MIPS platform you are'nt using any Ubuntu package, but a custom "ancient" toolchain. Doing this you can't use new GCC versions, because you're limited to this ancient toolchain. Why not convert this in a "legacy" asset, and use the "mipsel-unknown-linux-musl" stock packages to compile using the Ubuntu toolchain?
Regards.
lars18th commentedon May 26, 2023
Hi @Jalle19 ,
The OpenATV firmware is not just the "driver" package and the "enigma2" process. Using the 6.4 firmware (remember LTS, so with all updates and the last driver version) the system seems to be more reliable. And this is true without running any enigma process and only minisatip driving the tuners. Any other daemons are still there. So, I don't know the root cause for the difference in the performance. But if the branch 6.4 is more robust than 7.x with some devices without updated drivers and kernels, then I prefer to continue to use this "legacy branch". Don't you think so?
Hi @catalinii ,
In OpenATV the drivers are updated based on the kernel, and not in the firmware version (6.x or 7.x). Therefore, nothing is erroneous if the device uses a 5 years old driver. This driver (
linux-dinobot_4.4.35version 20210607) is fine except for the limited pid filtering handle (and used on more devices). Futhermore comparing my "Edision OS nino+" with dual tuner (C/T + S2) with this dumb "James Donkey HD DUO", the ARM mono-core CPU of the last is three times faster than the dual core MIPS of the first. So, the box is good to drive two DVB-S2 tuners using minisatip. The problem is only the uggly driver.Anyway, at time the "official" minisatip binaries for MIPS are using an ancient toolchain. But this is not true for the ARM platform. And these binaries have sense only on systems without a compiler. Therefore IMHO it's preferable to offer binaries for a large "legacy" level of platforms. Don't you think so?
Regards.
catalinii commentedon May 28, 2023
Basically what I am trying to say brings back to @Jalle19's point about supporting axe. The short story is that it becomes a hassle. Maybe now is ok to support openatv 6.4, but I am not sure this is a long term solution.
Does the minisatip build with ubuntu:22.04 works ?
Will try to move off that old toolchain for MIPS.
39 remaining items
Use clang for arm/x86 with static binary and zig cc for mips #1107
Use clang for arm/x86 with static binary and zig cc for mips #1107
Use clang for arm/x86 with static binary and zig cc for mips #1107
Use clang for arm/x86 with static binary and zig cc for mips #1107
Use clang for arm/x86 with static binary and zig cc for mips #1107 (#…
Jalle19 commentedon Jun 24, 2024
Can this be closed?
lars18th commentedon Jun 25, 2024
Hi @Jalle19 ,
I prefer that you leave it open. This issue contains interesting information (for not buying this type of device).
Jalle19 commentedon Jun 25, 2024
The information can just as easily be found even though the issue is closed
lars18th commentedon Jun 25, 2024
Not really. I suggest to leave it open. Please.
catalinii commentedon Jun 25, 2024
We can add it to the README, maybe make a unsupported devices section