Posts by loki7777

Yes, I do have the black screen between google tv and LE logo for around 2sec(at the end of it some linux things).

fb_addr=0x07900000

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

All is correct now. Goggle TV- "Linux" for split second- LE logo and Kodi.

Quote from dtech

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)

Will check it within 2h:)

2 hours later - it's perfect now:)

Quote from dtech

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.

Yes. I have google tv logo(around)5sec, glitches(around 5sec too) after that Kodi logo. But i'm ok with that;)

Disconnect hdmi cable. Power off all devices by unpluging power cord from the wall for a minut. Connect all again(including hdmi cable) - it helped when i had a problem with my Panasonic 4k TV and rest of the team.

Quote from dtech

Your boxes are quite different. For example, your box was equipped with Gigabit Ethernet (Realtek RTL8211F), not 10/100 Mbps.

On the other hand, your box has an S812 SoC and ochentay4 's box has an S802 only.

But nonetheless, I am happy to accept the result from both.

Yes, it is working fine on my box.

Quote from ochentay4

Ok, image seems to work nicely on Netxeon M82_V4.0_20141106 device (Tronsmart MXIII 2G/8GB Wifi 6330). Wifi worked correctly, funny enough, ethernet did not, cant get ip from DHCP (triple checked connections). Ethernet chip is H1601NL (1502-XG). Any fix you can think of?

Start reading from this post or few posts above as well RE: LE-9.2.8 builds for some Amlogic S905x, S802/S812 and S805 devices

I didn't try ethernet but will try it today as we are using the same image on similar box.

Quote from dtech

The problem is, I don’t even know if it worked with earlier versions under 3.10/3.14 kernel or not.

Unfortunately, the addon problems are in the same hat as the docker. I have neither the time nor the opportunity to investigate very much.

In the background, I'm also trying to bring back amcodec support to the Kodi Matrix version so that older devices can be used with the older kernel for at least some time. But I can't really move forward with that either.

Apparently, I was left alone for this, because the previous developers had already got out of this "suffering" since LE version 8.2 or 9.0 (kszaq, Demetris, datrh, etc.). Unfortunately, I’m starting to realize that the Amlogic v3.10/3.14 kernels are slowly no longer compatible with anything new.

Display More

Honestly if that would be slowly the end of does devices i would be still more then happy by what you achieved and what i have now installed on my box. While i was running kodi 15 for last few years i might as well run kodi 18.9 for another 3 years(as only using it for playing 1080p files and now maybe even x256 (maybe even in 4k). S

o i'm good with that. And then i will buy a newer box or something else to use LE.

THANK YOU.

Quote from dtech

Unfortunately, if a storage device is connected to an external USB (external HDD, flash drive, etc.), it would try to boot from there first.

If you need to ignore startfromext, you need to set this:

Code

fw_setenv bootcmd run storeboot

And then reboot. If all goes well, it will no longer try to boot from an exernal device (not even an SD card).

I can try it but first how to go back to boot from external?

Ok, tried first and it is working perfect - i assume the only downside would be to try to flash it from SD card or will it work?

Quote from dtech

Well, the easiest way to really do this is to type the ID at the top of the chip into a search engine.

This really matters if you run from there. (E.g. if it is installed to the internal memory with installtointernal script.)

This is my M8S (n200C), LE runs from the internal NAND:

Code: df -h

Filesystem                Size      Used Available Use% Mounted on
devtmpfs                766.4M      4.0K    766.4M   0% /dev
/dev/system             975.9M    124.1M    835.8M  13% /flash
/dev/loop0              122.0M    122.0M         0 100% /
/dev/data                 5.3G      1.3G      3.9G  25% /storage
tmpfs                   768.4M         0    768.4M   0% /dev/shm
tmpfs                   768.4M      9.1M    759.2M   1% /run
tmpfs                   768.4M         0    768.4M   0% /sys/fs/cgroup
tmpfs                   768.4M      2.2M    766.2M   0% /var
tmpfs                   768.4M         0    768.4M   0% /tmp

I used Android to check it and A1 SD benchmark - 4887mb - now benchamrking it(READ:19.22MB/s WRITE:15.00MB/s but thts's internal memory but i have another 2 SD card(same size as internal) and write is ~5MB/s) .

I don't know why i was always thinking it's 16gb(went to check the box and it is 8gb);)

From nand

LibreELEC:~ # df -h

Filesystem Size Used Available Use% Mounted on

devtmpfs 786.4M 4.0K 786.4M 0% /dev

/dev/system 1.4G 130.4M 1.3G 9% /flash

/dev/loop0 126.0M 126.0M 0 100% /

/dev/data 4.8G 313.7M 4.5G 6% /storage

tmpfs 788.4M 0 788.4M 0% /dev/shm

tmpfs 788.4M 8.5M 779.8M 1% /run

tmpfs 788.4M 0 788.4M 0% /sys/fs/cgroup

tmpfs 788.4M 2.6M 785.8M 0% /var

tmpfs 788.4M 0 788.4M 0% /tmp

To my surprise this time it booted instantly from flash:)

But... there is always but when external hdd not connected - otherwise is a long boot - it didn't boot after 10min so power off. Boots nice without hdd and i can connect it and it is mounted straight away but only after boot. Size does matter - small 32gb pendrive and it boots, larg 2tb hdd and it will not boot.

Quote from dtech

Code

/dev/mmcblk0p1 511.7M 134.2M 377.6M 26% /flash
/dev/mmcblk0p2 13.9G 288.0M 13.6G 2% /storage

This is not your SD card?

You are right. How to check flash size then?

Quote from dtech

Sorry, the link has been link fixed. There is no SSL certificate for this subdomain on my server, so the HTTPS is not valid in the URL.

But this stupid Crome found it funny to add that idiot s to http. No comment...

NCEFAT28-08G -> It is interesting because this is a 8GB eMMC on your PCB.

df -h

Filesystem Size Used Available Use% Mounted on

devtmpfs 786.4M 4.0K 786.4M 0% /dev

/dev/mmcblk0p1 511.7M 134.2M 377.6M 26% /flash

/dev/loop0 126.0M 126.0M 0 100% /

/dev/mmcblk0p2 13.9G 288.0M 13.6G 2% /storage

tmpfs 788.4M 0 788.4M 0% /dev/shm

tmpfs 788.4M 9.1M 779.3M 1% /run

tmpfs 788.4M 0 788.4M 0% /sys/fs/cgroup

tmpfs 788.4M 1.4M 787.0M 0% /var

tmpfs 788.4M 0 788.4M 0% /tmp

Quote from dtech

Okay, the manual workaround is here for the "repo bug after update":

(However, as a new installation, everything will work immediately, and there is no need for manual intervention.)

I also replaced the old repo, and the only package included is this:

After that you just need to update and point to the location of the new repo (S8X2):

Display More

Can't access this file (repository.libreelec.tv-9.2.1.zip) on your server.

BTW That's my box mainboard in attachment - it shows tronsmart on sticker and 8gb but it is 16gb.

Quote from dtech

Okay, I investigated and all new images in the S8X2 project are affected: M8S+, MXIII*, Uni-n200.

The cause of the error is probably not in my own build, but rather in Kodi or LE.

It is a fact: The repository link for the devices has changed.

Old: http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm

New: http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm

But that's still not the real reason, because both paths work and point to the same target (symlink).

Code

2021-09-14 06:37:34.376 T:3010805760 WARNING: Repository add-on repository.libreelec.tv uses plain HTTP for add-on downloads in path http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2021-09-14 06:38:04.143 T:2901406592 WARNING: Previous line repeats 32 times.
2021-09-14 06:38:04.143 T:2901406592   ERROR: Requested path http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm/virtual.dvb-tools/virtual.dvb-tools-9.2.0.105.zip not found in known repository directories

The repository link is good, the download link is working, it's just from the old index file.

Somehow the index would have to be updated to point to the new location, but I have no idea where LE stores this.

Update #1:

It doesn't work either: https://wiki.libreelec.tv/how-to/force-add-on-update

It can be updated, but it will still use the old URL when downloading add-ons. What a stupid bug is this?

Update #2: The Kodi backup/restore solution does not work either.

Display More

I wouldn't bother with that bug too much(tbh i downloaded only one add-on from repo and it is a skin;) - just add in first post that "users have to do a fresh install every time new build is released" and wait for LE to fix it.

Install failure. It looks like LE can't see files from this repo as it is not showing size. I did update from old snapshot(the one from 10th). Will check with new installation as well.

Yes - it is upgrade related as fresh installation is working ok.

Quote from dtech

Please check your device connection. I tried it a few minutes ago from a new SD card and I have no problem with LE addon downloads from my repo.

Not working for me as well(just checked) - there is no size beside them - installation failed. Kodi add-on repository is working without any problems. But i don't care about add-ons anyway.

MXIII-G 4K 2GB/16GB

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). Wifi no problem(connects with kodi repo straight away and is downloading skin without any issues), movie freeze gone. Manual update from previous snapshot is working as well - just tested to keep ale the settings intact. If there were no more changes from previous snapshot then i was testing it for hours and it is working flawless.

No volume/mute osd but i think it might be related to my avr/panasonic 4k tv but my older openelec build works without that glitch - will try to track it down with debug..

LibreELEC-MXIII-Plus.arm-9.2.8.2.img - no wifi for me so didn't test it more. Glitches at boot.