FYI: the builds have just finished and the 20240215 nightly with the fix is available:
https://test.libreelec.tv/12.0/RPi/RPi5/LibreELEC-RPi5.aarch64-12.0-nightly-20240215-540999d.img.gz
so long,
Hias
FYI: the builds have just finished and the 20240215 nightly with the fix is available:
https://test.libreelec.tv/12.0/RPi/RPi5/LibreELEC-RPi5.aarch64-12.0-nightly-20240215-540999d.img.gz
so long,
Hias
Wait about 20h before you try the latest LE12 nightly from here https://test.libreelec.tv/12.0/RPi/RPi5/
New images are currently being built and they include a fix for the "no display" issue on a KDL-46Z5500 - see bug report here https://forums.raspberrypi.com/viewtopic.php?p=2190093#p2190093
so long,
Hias
The Raspberry Pi DAC+ and DAC Pro (formerly IQaudio DAC+/Pro) come with a 3.5mm jack and cost about 20-25 bucks.
so long,
Hias
Very likely it's the well known USB3 / 2.4GHz interference issue
https://www.usb.org/sites/default/files/327216.pdf
Simple solution is to use an extension lead for the wireless dongle so you can put it 0.5-1m away from the USB3 leads/devices
so long,
Hias
No, that's all we've got. I recommend asking on the RPi forum https://forums.raspberrypi.com/
so long,
Hias
According to the log you are hitting the rather common UAS issue with your USB drive (lots of cheap drives have broken UAS implementations and Intenso doesn't have the best reputation).
Feb 06 12:22:13.841587 LibreELEC kernel: sd 0:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
Feb 06 12:22:13.842112 LibreELEC kernel: sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x28 28 00 77 3b c7 88 00 00 68 00
Feb 06 12:22:13.871559 LibreELEC kernel: scsi host0: uas_eh_device_reset_handler start
Add usb_storage.quirks=152d:0578:u to the end of /flash/cmdline.txt (on the same line!) to disable UAS for the SSD.
so long,
Hias
Should I expect deinterlacing to be working with a RPi5 with DRM Prime? Working as expected on a 12 nightly but not with 11.0.6.
Deinterlace on RPi5 only works in LE12 - kodi in LE11 doesn't support software (BWDIF) deinterlacing which is needed on RPi5.
so long,
Hias
Use an external (USB) HDMI grabber, this is still supported by current Hyperion. There don't exist any working software grabbers for RPi yet.
so long,
Hias
Do as the same as systemd-shutdown, ignore the message(s) (they are harmless and perfectly normal).
so long,
Hias
It depends on what you want.
By default the RPi uses the (better) ttyAMA0 for bluetooth and you can enable the (less capable) ttyS0 for use in your script with enable_uart=1 in config.txt.
With the miniuart-bt overlay bluetooth uses ttyS0 and you can use ttyAMA0 in your script.
so long,
Hias
Just use /dev/ttyS0 or /dev/ttyAMA0 in your script.
The (downstream RPi) script and udev rule to create the alias symlinks have been removed a while ago when the RPi kernel finally switched to upstream kernel BT configuration.
so long,
Hias
i mostly use san disk usb 3 drive
This doesn't say much, Sandisk has a ton of different models.
I can't test on RPi5 right now but on my PC eg my Sandisk Ultrafit 32GB USB3 stick does about 140MB read / 50 MB write whereas my Sandisk Extreme Pro 64GB microsd card achieves 170MB read / 90MB write speed (both tests were linear reading/writing 1GB of data).
so long,
Hias
It'll depend a lot on the exact model you use, most of the 32-128GB USB sticks I have are a lot slower than the 32/64GB SD cards I use (Sandisk Extreme Pro), especially when it comes to writes and random access.
As a rule of thumb: if the manufacturer didn's spec write speed it'll be slow. For SD cards also make sure you get one with A1 or A2 application class and, as always, stay away from no-name brands.
You'd need to look for USB SSDs (not USB sticks / thumb drives), they should be fast - but they are quite expensive.
so long,
Hias
The journal message already gave you the correct hint: use Option=nolock in your systemd mount unit.
so long,
Hias
Take your time, we're not in a rush.
I had planned to rework our noobs/pinn build a bit in the next weeks or so (as time permits) and it'd be nice to have that finished when we ship LE12.0.0. As we haven't started with LE12 betas yet I'd guess that won't be before March, so there's plenty of time (and it's also no huge deal if we do it some time later, then you/we can just do a manual os_list update).
so long,
Hias
Thanks for adding/updating the os list!
I think moving to sha checksums of the downloaded tarballs etc is a good idea, then we can drop the manual md5 sum creation and checks in partition_setup.sh.
Do you have some pointers how to use/add the pinn sha512 checksums?
In general I'm very open to all improvements and suggestions how to simplify stuff, just speak up
so long,
Hias