Maybe I managed to fix the issue, please check the new image here:
http://libreelec.dtech.hu/3rdParty/S8X2/ (Updated: 2021-12-01)
Posts by dtech
-
-
i installed corelec for my very old Enybox M8S, thank you very much.
But when I install docker, jellyfin doesn't seem to work. I can't conect my media server through port :8096 or 8080 (docker not run, i think so). Can you help me?? Sorry my English is not good.
Thank you.
You are welcome, and... wait a minute. Did you mean LibreELEC, right? I never created CE images.
About docker support:
-
I found something: Pandora's Box 3D 8000 Games Arcade Console Gameboard JAMMA Motherboard DIY PCB
The S912 is not a Cortex-A9, but the S802 and S812 are. Anyway, the heat sink is held in place by a spring-loaded strap, so why not take it off to check it out? The type is inscribed on the top of the SoC.
-
I honestly admit that at the moment I have no idea what might be causing it.
The same platform_init script works perfectly on M8S+ and WeTek Core (and in theory on Minix devices, though I haven't received any actual feedback on it).
However, it was noted that the MXIII-G uses a different memory area to load the logo, such as the two devices above:
- OTT M8S+/WeTek Core:
Code: fw_printenv | grep fb_addr=fb_addr=0x15100000- Your device (MXIII-G):
Code: fw_printenv | grep fb_addr=fb_addr=0x07900000However, I saw the same framebuffer address (0x07900000) on my S805 devices only. Strange...
-
LibreELEC-n200-AP6330_2G.arm-9.2.8.2 - some glitches at boot(when you see "linux things" - same with last snapshot but not important).
loki7777 Have you experienced this too?
I mean, did it show up for you instead of the logo?
However, if the onscreen log only appears for a moment and only flashes once before the logo loads, it's completely normal. It doesn't really show up on some TVs, it happens so quickly.
-
Which version did you update from?
-
The logo should hide the console output, but something is wrong with the resolution at boot time.
But I see the first lines of the LE logo at the bottom of the screen, and the image is also quite distorted.
I need a dmesg and an fw_printenv output shortly after the Kodi is loaded.
-
U-boot also allows the entire boot process to be encrypted/signed and protected; but this requires support for those things in Silicon which increases costs, so you almost never see it with cheap TV box devices.
It would have been more of a philosophical question, I personally don't like UEFI too much.
Altough on the boxes the /dev/system partition, which contains the squashfs file it is ext4, but on the sd card, flash drive (or removable eMMC) it is FAT. In principle, would u-boot be able to find and start the kernel if the first partition on the sd card is ext4?
I know I'm now speaking against myself as a Windows desktop user. Native ext4 support under Windows, that would be nice.
-
Thanks for your answer. And another question I have to do. After installing the 9.2.8.3 in my tv box when i reboot the box the libreelec logo at the beginning had disappear. Instead of the libreelec logo I see a very long incomprehensible list of a text for a while and after that the tv box is booting to Kodi. Is there anyway to fix it ?
Okay, this is a new issue... Can I get a photo of that?
-
I'm not sure where it pulls it Kernel sources from...
LiserTV uses the HardKernel's own kernel-branch with a few extra patches:
Commits · Leverex/linuxLinux kernel source tree. Contribute to Leverex/linux development by creating an account on GitHub.github.comAny OS can read FAT, and it will usually contain only a few files, written rarely - so efficiency etc. is not really an issue.
It is a little interesting that x86 has been forcing UEFI and secure boot (nightmares) for a long time, but for u-boot we still use a file system to load all boot files that doesn't even handle basic permissions. Okay, that's easy to store boot files on FAT... But is it secure at all?!
-
Since Matrix (Kodi v19) the legacy amlcodec is no longer supported. The old kernel (3.10) is already very outdated anyway, so the only solution is to switch to the mainline kernel. At the moment the state of the vdec is pretty much WiP. However, there is some progress in this area (Meson 8* Lives!), but it seems that Kodi v20 may be the first to run on Meson8* devices.
-
There is a little TvH 4.3 backport for my legacy Amlogic LE-9.2 images:
http://libreelec.dtech.hu/3rdParty/packa…E9.2_v4.3-1903/Source repository branch: https://github.com/dtechsrv/LibreELEC-AML/tree/tvheadend43
Update:
-
I’m really trying to adapt it, but I'd rather just say experimentation. Now I have a working image, but I wouldn't say it's 100% done.
http://libreelec.dtech.hu/snapshots/20211122/ (Source: https://github.com/dtechsrv/LibreELEC-AML/tree/odroid-c1)
It contains almost all Kodi patches I have used for the boxes, including the fix for the IPTV problem, and I also enabled the dvb-latest driver package. However, the kernel of wrxtasy I used for this build is unfortunately very outdated.
Although I only have this board for 2 weeks. Before that, I only had boxes.
For me, the u-boot is a whole new area, so unfortunately I can't answer your previous questions on the merits either, but all the experience comes in handy. If I understand correctly, you want a native ext2/ext4 partition instead of a squashfs + overlayfs for the system patrition, right?
-
Two Questions, is this MXQ-4K-Pro_2G.arm-9.2.8.3.img.gz will work in my box ?, as it says 2G ram where as my box is 1GB Ram, and another do i have to download this gxbb_p200_1G_mxq_pro_4k.dtb, and rename it to .dtb.? Can i extract & use the the .dtb file which is already there in my (LibreELEC-Amlogic.aarch64-MXSPlus-8.0.3-update) given by the supplier of the box.
- That 2GB in the name is only present because the image was created for this device: MXQ 4K Pro+ (S905X, 2G/16G).
The size of the memory is specified in the DTB, so if you replace it, the name is already irrelevant. - Yes, you can, but since your DTB is from an older build, it is not 100% sure it will work.
- That 2GB in the name is only present because the image was created for this device: MXQ 4K Pro+ (S905X, 2G/16G).
-
Now I see you are trying to update with an S805 (m8b) image, even though you have an S905 (gxbb) device. This is not going to be good.
If you update your S905 with the HD18Q image, it is guaranteed to never boot again after you restart your device.
And chewitt is also right, because in Leia versions (9.0/9.2) for Amlogic S905x the kernel is 64-bit, but Kodi is only 32-bit.
I think you need to look for another sd card and create a clean install with this image: LibreELEC-MXQ-4K-Pro_2G.arm-9.2.8.3.img.gz.
This is the correct dtb for your device: gxbb_p200_1G_mxq_pro_4k.dtb, it should be renamed to dtb.img and overwrite the original.
-
Everything looks good from the kernel side, I think the boot logo has been replaced by a custom ROM. If you can tolerate to see the OE logo appear on startup, you don’t have to deal with it because it doesn’t affect anything. However, if this bothers you, you will need to restore the factory Android ROM (this will restore the boot logo) and then install the LibreELEC image from the SD card to the NAND (with installtointernal script).
And to make CEC work, the fw_setenv cecconfig cec1f I wrote earlier must be run, because fw_printenv says it's still turned off:
Codececconfig=cec0 -
Thanks i copied .tar to .update folder, but it says this image is Uncompatible with my Hardware. I guess i have to use the previous version, can you recommend which is the last working version according to my specs.
The reason for the incompatibility is that the device name is different.
You need to create an empty .nocompat file next to .tar in the update directory, and try again.
-
All you need is the correct dtb.img (gxbb_p200_1G_mxq_pro_4k), it will need to be replaced in the new version. But if you install it as an update (*.tar), you don’t have to do that either. However, I don't really recommend updating from 8.0 to 9.2, before that do a backup under Kodi.
