Posts by chewitt

Clean install the current nightly from Index of / with no 4K60 configuration and prove things work normally and the RPi4 can see 4K (up to 30) modes - right now it is only seeing 1080p. That suggests bad or inadequate/uncertified HDMI cables (or broken EDID from the TV) or using the wrong HDMI port on the TV. Note that LE defaults to 1080@60 GUI even if the TV supports 4K playback. Rendering the GUI is about CPU performance, it is not hardware accelerated like 4K video, so the GUI will be noticeably slower if you force it to run at 4K. You can still whitelist 4K modes for playback and Kodi will switch to 4K when required. Also note that practically all 4K media is [email protected]/25/30 so in most cases, users do not require 4K60 to be forced.

If vendor boot firmware is present on emmc the box will always boot from it, so to freely experiment with other boot firmware(s) from an SD card or USB stick you will need to completely erase emmc. If the goal is to run the dtech image you should focus on finding a replcement "vendor" u-boot. NB: the u-boot.bin.sd.bin files in my share (in case that's what you found) are mainline u-boot variants and might boot the box but will not greatly help in any mission involving 3.14 vendor kernels. Start by sharing the "strange characters and letters/numbers" seen via UART via pastebin so people can understand what the current boot-state of the device is.

I'm not sure what the issue is (no logs are provided which might give clues) but using autostart.sh should never be preferred over system.d, as the later provides better control over when things are executed.

If you set min SMBv1 and max SMBv3 in Kodi it will default to SMBv2 and you won't connect. Forcing requires min/max SMBv1 to be set.

GitHub shows no commit activity from Thoradia since Jan this year. We have zero contact with him/her/they outside of this forum so we have no way to enquire about future plans. at this point people should assume that this thread (and the repo) is dead.

Quote from dtech

Okay, so far only three people do not understand sarcasm.

Your audience is multinational

For the record .. on LE 9.2.6 on Intel HW we are still rendering via Xorg which means GL not GLES surface (GLES will be in the future once we dump Xorg) but crap add-ons are still crap add-ons

Quote from jimjack12

Now I ask you: is it possible to somehow install LE directly on the nand via aml usb burning, or via usb / sd

Amlogic Burning Tool = No (our .img is not the format used by that tool). USB/SD = You can boot from SD/USB but we provide no tools for internal install (the box has emmc btw, not nand but that doesn't change anything) and you will need working vendor u-boot on the box to boot into LE (or CE, which is probably a better option for clone box). Currently there are no LE releases for this kind of box.

Martin Blumenstingl and I both have Core boxes now (Martin having one is vastly more important - esp. since I have littl time for Amlogic fiddling at the moment). Meson8 devices now have working HDMI (1080p) and initial audio support is on the mailing list so platform support has progressed. You can forget LE10 support, LE11 might be more realistic for alpha support; although Meson8 devices will soon be stuck at the same incomplete vdec support as all the newer Amlogic hardware versions. Most of the current activity originates from Lakka/Batocera devs as the S812 chip has a reputation for great performance .. and gaming doesn't need fancy stuff like vdec/4K etc.

If you flashed a ROM built from boot FIPs with the wrong acs.bin for the RAM in the box (acs.bin has the RAM timing data) the early boot stage will not be able to reach the point where u-boot loads; so it errors and cycles to try again (ad infinitum). To get past this you need to prevent the eMMC being detected, because if it's detected, it's used. The "nice" ways to override the boot logic are an Amlogic SDIO debug board (almost nobody has one) or custom HDMI dongle (almost nobody has one) or you need the "less nice" shorting pins on the eMMC chip method. It's ugly but it temporarily disables eMMC and the boot logic then looks for u-boot on an SD Card or USB stick.

The next steps involve experiments with shorting the correct pins and different u-boot(s) on SD cards so basically you need to UART hooked up to see what works and what doesn't work. It's fiddly but not actually that complicated once you mentally get over the idea of stuffing a screwdriver into your expensive cicruit board

I wouldn't "rm .kodi" as that prevents you from easily copying back all the bits that don't cause issues. Simple "mv .kodi .kodi-old" and then reboot to update is fine. You can keep DB files, sources.xml, thumbnail caches and add-on settings without problems.

Quote from sugatam

Hi, I cannot find any amlogic images on test.libreelec.tv anymore (nor on Index of /testing/). Please help, thanks

I pulled them because real-life is rather busy and I won't have time for kernel fiddling anytime soon. All the sources are in my github repo.

I see mention of MMAL so this must be LE 9.2. Go test LE10. Kodi 19 includes lots of feature/bug fixes, and RPi has an entirely different kernel driver stack. From our side of the fence there is no point (and thus not much interest) in investigating issues on LE 9.2 .. it's an effectively dead codebase now.

Auto-update works when someone on staff remembers to update the server side of things to do it .. which is not often.

Requests to modify how the Kodi SSH/FTP client performs/behaves should be done via the Kodi forums. LE simply consumes whatever code the respective Kodi devs publish or bundle with Kodi.

This has a high probability of failure because autostart.sh is executed right at the start of userspace boot before the network stack is up. If you run the script in the background (as you are) you need to add sleep values to allow the network to come up, and you probably need to delay Kodi start to allow for the mount to happen first.

This is why systemd mounts exist. Systemd allows you to apply dependencies, e.g. so the mount "wants" the network target to be up, and "before" the Kodi service is started. Look at the examples in /storage/.config/system.d/

3D support in RPi4B is not broken, it is not implemented (in both LE 9.2.x and LE10 codebases). Last time I asked about future support in the LE10 codebase I was told it's not impossible to support, but there's a long list of much higher-prioority things in the To-Do list. If you need 3D support, it's best to keep an RPi3 around (which does suppport it under LE 9.2.x, but not LE10).

Real-life is rather busy right now .. I'll get around to it eventually