Posts by chewitt

mainline-status.md · main · hardware-enablement / Rockchip RK3588 upstream enablement efforts / Notes for Rockchip 3588 · GitLab

Collabora GitLab

gitlab.collabora.com

AFAIK the HDMI code has either been submitted or is close to being submitted, and panthor GPU support is now merged, but hardware video decode codecs are still missing. It'll be usable at 1080p with software decoding. I'm not sure about 4K media.

At this point someone who cares about RK3588 support should probably submit changes to create an LE13 image. I think we'd have no problem with including backports and patches that are iterating on mailing lists, but we wouldn't accept drivers from the vendor codebase uless backed with a commitment from a "known name" developer planning to rework them in the mid-term.

Read: https://wiki.libreelec.tv/configuration/…ration-advanced

You installed Armbian. You want to boot Android. What does this have to do with LibreELEC ???

Whatever the problem is, it's not our problem

Random suggestion: boot into Ubuntu and "dd" the LE image directly to the NVME drive, then see if it can boot?

Quote from Zuma

- is support DRM decoder and working for Generic build ?

- Support HLG DVB... ?

It supports libwidevine DRM (software decoded, not hardware) .. Generic is the same as all other LE images. Kodi supports HLG so as long as the hardware (and drivers) and TV support HDR it should work.

Quote from jonchance84

Generic on LibreELEC 12 Beta2, VPN in OPENVPN Manager fails

You need to share log files in a separate thread. It's mostly likely an issue with the manager add-on and not the core OS, in which case it will need to be addressed by the add-on creator not LE team.

Quote from suigenul

If you would like to help me, please tell me all which command to enter.

In your browser, type "http://forum.armbian.com" then ask for help there (as this is nothing to do with LibreELEC).

Quote from ludelafo

Would you be interested?

You have mail

#################################################################
# Installing syslinux to /tmp/installer/part1
#################################################################

/dev/nvme0n1p1: unsupported sectors size

(as before) the installer fails to install syslinux to the NVME drive and no bootloader = no boot.

If you have a standard non-fancy drive around you can see if that works (to isolate the issue to NVME vs SATA) but it's likely due to some oddity with NVME drive firmware. I'm unsure what the solution/workaround is with syslinux so install grub to the (otherwise fine) nvme drive instead of syslinux and see what happens.

Google reports there are 387,000 results for "install grub bootloader" so plenty of things to read.

The add-on base version is bumped occasionally during development; meaning over time there are multiple versions of the add-on repo and a specific LE nightly will pull add-ons only from it's hard-coded version-matched repo. We aim to keep current and one-previous nightly repo version around (although only the current one will receive updates) and we delete older repos to save disk space over time which means old nightlies will often have no add-ons available. It's not clear from your explanation whether this is an LE11 or LE12 nightly, but I'd guess LE12 and that's likely the problem. Unless you want to build your own add-ons, the sole solution is to update to a current release (with current repo).

NB: while it will boot, Zero 2W is no longer supported due to being 512MB RAM size. I'm also not aware of any issues with Samsung SD cards over 32GB, and anything with major boot impact like that would normally be a high priority firmware or kernel issue for the Pi developers to resolve.

Create an Ubuntu Live USB and see if that boots. If it does, grub works (where syslinux does not) and you can do a manual LE install to the NVME drive using grub as the bootloader. Create a GPT partition scheme on the drive with two partitions: BOOT (512MB/VFAT) and STORAGE (100% remaining space/EXT4) and setup the grub boot entry using the data in syslinux.cfg as a general guide for boot params.

Nope

jernej any ideas on the root cause here?

It's not possible to fully answer the Q without a Kodi debug log to look at, but I'd guess this is an interlaced resolution and since Kodi only outputs progressive, it (and other interlaced modes) is/are automatically excluded from the output options.

I've never seen/owned/booted a Chromebox so can't really advise. There's fairly extensive instructions on the mrchromebox site.

Share the install log from the installer USB?

I need a UART log to see what is (or isn't) happening when the board boots.

I think you're over-thinking what's involved. Just configure a different HDMI output to the one being used for video.