Posts by dtech

Quote from gthebest

Code

fb_addr=0x07900000

I know you have already sent this. This seems it is the standard address on MXIII-G/Plus, so I accept it.

However, I think it would be worth replacing your SD card because the it boots very slowly in your video, but that's not the device's fault.

Quote from viachy

Hello guys,

I have an Amlogic M8s+ tv box (S812) and I``` am running LE 9.2.8.2 and it`s been great.

I am interested if I can upgrade to LE 10 (Matrix) ? I` have been browsing through the different sections but cant figure it out.

Can someone advise please if that will be possible (in the near future if not now)..?

Thanks

This is a recurring question...

Post

RE: Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

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.

dtech

November 29, 2021 at 1:54 PM

Quote from loki7777

fb_addr=0x07900000

On my box it takes like ~22sec from kodi reboot menu to land back in Kodi again. Boot from Nand.

Do you also have a black screen between the vendor and the LE logos?

Mine only started a little slower because the "wait for network" (aprox. +10 seconds) option is also enabled due to loading the IPTV channel list and EPG (XMLTV). This is important because if Kodi can't load them at startup, it won't try again later. Without that, it would take me about the same amount of time.

Mine also runs from the internal eMMC, but it is not much slower when starting it from a U1 class card (a.k.a. Class 10). BTW, the sd card of gthebest seems terribly slow.

gthebest

Okay, it's really "almost" perfect. It already looks quite tolerable, but your SD card seems a bit slow.

However, the black screen between the Tronsmart and the LibreELEC logos is probably due to an incorrect framebuffer address.

I know it, because I tried the reverse (0x15100000 -> 0x07900000) on my M8S and experienced the same black screen.

However, I have no idea how this got into your device, because this is the standard value of fb_addr for S805 SoCs, not S812.

Coincidentally, isn't (or wasn't earlier) an unofficial "cooked" Android ROM installed on your internal NAND?

loki7777

Can I request an fw_printenv output from you too? I'm just wondering what fb_addr is set to on your device.

Quote from gthebest

Its working almost perfect. I can see the Libreelec logo again for 4-5 seconds!

"almost perfect" -> What does it mean exactly? For example, what is the difference on your box compared to one of my boxes?

gthebest  loki7777

Maybe I managed to fix the issue, please check the new image here:

http://libreelec.dtech.hu/3rdParty/S8X2/ (Updated: 2021-12-01)

Quote from V77V77

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:

Post

RE: Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

[…]

From branch 9.2, along with the end of official amlogic support, aml-specific patches for docker support was also dropped.

The docker compatibility was not a priority in my builds, so I wasn’t really concerned with re-implementing background support.

dtech

September 12, 2021 at 4:28 PM

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.

gthebest

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:

fb_addr=0x15100000

• Your device (MXIII-G):

fb_addr=0x07900000

However, I saw the same framebuffer address (0x07900000) on my S805 devices only. Strange...

Quote from loki7777

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?

Quote from gthebest

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.

gthebest

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.

Quote from chewitt

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.

Quote from gthebest

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?

Quote from Wild Penguin

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/linux

Linux kernel source tree. Contribute to Leverex/linux development by creating an account on GitHub.

github.com

Quote from Wild Penguin

Any 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.

-=guybrush=-

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:

Post

RE: Tvheadend nightly builds for LE

[…]

The previous link is no longer live because it was added to the repository in the meantime. If you use my build, you should find it here:

Add-ons -> Install from repository -> LibreELEC Add-ons -> Services -> Tvheadend Server 4.3 (Alpha)

dtech

October 23, 2022 at 7:45 AM

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?

Quote from tiku

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.

1. 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.
2. Yes, you can, but since your DTB is from an older build, it is not 100% sure it will work.