Posts by chewitt

Have you read the info in https://wiki.libreelec.tv/configuration/pulseaudio ?

Please update to a current LE13 nightly and share the URL from "dmesg | paste" again so we can see if there's any difference from newer kernel/drivers. If none, pastebin the system log and "lsmod" output from Manjaro so we can compare things.

The latest images in my testing share have some changes:

• FFmpeg bump to v7.1 - In brief testing I didn't see changes (no regressions, no improvements) but none were expected.
• Some patches from @sarbes that improve GUI performance - although we're firmly in the realm of marginal gains so don't expect performance changes to be overly noticeable.
• Ethernet performance on WP2 appears to have doubled (33MB/s is now 76MB/s) - although I am not sure why, but I suspect recent kernel changes suggested-by kszaq are responsible. It's nice to see as it's always bugged me why the WP2 NIC ran at half the speed of the (also 1Gb/sec) NIC on a N2+ or RPi4/5 board. I've no idea if this impacts other boxes .. but maybe. EDIT: An N2+ board also shows improvement from 75-80MB/s to ~110MB/s so this appears to be a general improvement.

Luni the subtitle issue is due to Kodi changes from @sarbes that impact Mali 400/450 GPUs. I've flagged the issues to him.

Quote from Tahurel

Mm ok, how often do the kodi repo update?

Whenever the addon author pushes an update to the Kodi repo

Both are from the same author and generated from the same codebase, but since the dontpanic repo is managed directly by the add-on author I wouldn't be suprised if there were newer versions in that repo, or more frequent updates to that repo.

Oleg (balbes150) was the original creator of the multiboot approach, hence LE/Armbian use it, but the scripts have been adapted over time for many varieties of hardware. From S905 onwards the vendor u-boot environment is quite consistent, but before that time things are more "open to interpretation" among clone-box vendors and you'll find more devices that don't work with our scripts. I'm not aware of any specific repo's that would be useful these days. There are likely forks of Oleg's repo in GitHub, but I would have no idea how to find/spot them among all the others.

You need to share the u-boot (early stage boot) serial uart output. This will either show what stage of boot something fails at, or nothing which indicates a more fundamental u-boot compile/packaging issue.

dtech I'm not well versed in Meson8 boot but it looks like the same "search for boot files" stuff used everywhere.

You can configure the RPi to not-wake the TV over HDMI-CEC when the board is turned on, but if the TV is off, the IR/BT receiver on the TV is also off, so the TV cannot send remote commands over HDMI-CEC to control the RPi board.

dtech It's basically the same "search for stuff on SD, USB, eMMC" sequence that AMLGX uses, only looking for older filenames.

Kodi generally aims to ship something before DevCon (so we can talk about it then) and in recent years this seems to be happening in March/April so the release is most likely to happen in Feb .. but no guarantees

The image in post #1 is 100% the mesa issue resolved in nightlies so unless you've mixed up SD cards and are still booting the 12.0.1 image and not the LE12 or LE13 nightly, there's no real explanation. The nightlies work for other users with boards using the newer chip stepping.

You can add "ssh" to boot params in the cmdline.txt file on the SD card and this will force the SSH daemon to start so you can login to poke around and generate logs. You can also access the "Logfiles" SMB share over the network to generate a zip file in the share with all the logs, but if you are still seeing the same image as shown in post #1 there probably won't be anything useful as systems are up/working okay - only the mesa version is missing support for the newer chip stepping and doesn't render things correctly.

I'd recommend (re)setting the desktop resolution to 1080@60. This is the max resolution for current skins and forcing things to 4K desktop just makes the UI run slower. Configure 4K modes in the mode whitelist for playback only.

"If it works, don't fix it" .. so if you're happy with the RPi4's, an RPi5 is the natural choice. Being a mean parent I'd bag the RPi5 for myself and pass down an RPi4 to the kid

Show the output of all the commands, in sequence, or copy/paste to pastebin.com or similar.

Yup, looks like the device is present but there are no paritions/filesystems - You need to create one. The commands I shared in the second code-block above should fix that.

RPi5:~ # ls -l /dev/nvme*
crw-------    1 root     root      243,   0 Dec  6 03:29 /dev/nvme0
brw-rw----    1 root     disk      259,   0 Dec  6 03:29 /dev/nvme0n1
brw-rw----    1 root     disk      259,   1 Dec  6 03:29 /dev/nvme0n1p1
brw-rw----    1 root     disk      259,   2 Dec  6 03:29 /dev/nvme0n1p2

If you do ^ that, do you see at least /dev/nvme0 listed? - I'm not really seeing any errors but there's no mention of any partitions being checked or mounted. The probable and logical explanation for that would simply be that none exist on the drive and you need to create one, e.g. (not 100% sure of the commands here, am working from memory):

parted -s /dev/nvme0n1 mklabel gpt
parted -s /dev/nvme0n1 mkpart primary ext4 40s 100%
parted -s /dev/nvme0n1 name 1 'MEDIA'
mkfs.ext4 -L "MEDIA" /dev/nvme0n1p1
fsck.ext4 -y /dev/nvme0n1p1

If that's not the issue I'm unsure what the actual issue is, so hard to advise.

Monitors with different display properties might require full-range, but normal TV's should be fine with limited range, so no need to fiddle with anything. Nothing to change for HDR content either.