Posts by chewitt

LE has a single hardcoded default user (root) and default but changeable password (libreelec) with SSH disabled by default. In LE settings you can enable SSH, and enable/disable SSH passwords (disabling allows you to stop password login and use pre-installed SSH private keys instead) and change the root user password. If all you want to do is login remotely .. re-enable SSH passwords and use any SSH client to access.

Once you have SSH access sorted, run "pastekodi" after booting and share the URL so we can see the Kodi log.

Quote from Watdaph

On the Libre config I have enabled SSH and disabled SSH password on the Services page

Raspcontroller (which I have never seen or used, so guessing) is probably written for RaspiOS not LibreELEC so may not work. Did you install SSH private keys first before disabling passwords? .. If no, disabling SSH password auth (to use key-only auth) prevents password logon.

LE/Kodi depends on working EDID data from the HDMI connection to the TV/Monitor to understand what output options can be used. You can force HDMI output to a specific resolution using kernel boot params, but if EDID does not provide any audio options you'll have video and no audio.

Update to LE12 beta2, the Chrome add-on there was updated in the last week and "beta" is no less "stable" than 11.0.6.

Addon updates for LE12 by heitbaum · Pull Request #8804 · LibreELEC/LibreELEC.tv

Addon updates for LE12 flirc_util: update to githash 653f706 and addon (1) audiodecoder.openmpt: update addon (8) mpd: update addon (1) libopenmpt: update to…

github.com

NB: LE runs in well under 1GB RAM so swapfiles are not required (hence not created by default). All you achieved was increase the box boot time.

Quote from tokul

rsync -av -e ssh

^ that requires rsync to be installed via the System Tools add-on, whereas boring old scp achieves the same without needing that.

Quote from ehoitinga

No, I never built an LE image but I can try.

Have a read: https://wiki.libreelec.tv/development/build-basics

First step is to build the current LE master branch (LE12). Once that results in a working image that you can boot, we can describe how to bisect the changes.

Everything you want to keep/reuse is in the Kodi userdata folder. Everything else has references to specific hosts or hardware that you don't want to duplicate or retain. So stop Kodi and restore only /storage/.kodi/userdata from backup (or recursive scp it from old x86 host to clean-installed RPi4's over the network to avoid the hassle of remembeing tar commands) then restart Kodi and reinstall add-ons from repos and the existing add-on configs will be reused. You will need to revisit some Kodi system settings as info on audio devices etc. will be incorrect after the hardware change, and change the device name in LE settings so they're all unique.

DRM Memory Management — The Linux Kernel documentation

In short, the hardware decoder writes decoded video frames to DRMPRIME memory buffers in a format that allows the same buffer to be (re)used by multiple processes within the display pipeline until the frame is transmitted/output via HDMI. This more efficient than non DRMPRIME decoding where each process in the display pipeline must read (copy) the buffer from memory, do something, then writes data back to memory. DRMPRIME is "zero-copy" decoding. TL/DR: leave it turned on unless you want your RPi5 to work less efficiently. And if you have a problem with something .. this is unlikely to be the cause.

Adding "ssh" to boot params in uEnv.ini forces SSH to start on boot. Then stop Kodi and use nano to edit guisettings.xml to change any instances of 1080p resolutions in the file to the 720p equivalent (search for 1080) then restart Kodi. NB: If Ethernet is not working you're probably using an incompatible device-tree: although there aren't many to choose from.

The error messages explain the lack of video output though; no HDMI controller = no HDMI.

I never heard of p291 devices before. Can you share the android dtb file?

NB: that boot log shows the box is using some homebrew dtb, nothing we/me created. EDIT: anything from "ophub" is 100% not supported. I'm not surprised HDMI and audio aren't working. Armbian != LE and that developer creates half-baked device trees (and last time I looked, doesn't provide sources for them). Not my problem to solve.

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.