Understood, I'll drop all those files from the build going forward. Cheers 👍
Posts by F1Fanb0y
-
-
HiassofT Amazing! its working perfectly now, thanks for looking at it.
I've been able to take a copy of the RPi4 device folder in the build system, add some options and quite easily turn it into a Slice4s device folder which has the dt-blob.bin, distroconfig.txt and dtoverlays all nicely baked into the image.
Just so I understand a little better, on the old 9.2.8 branch there’s a couple of linux patches for the mmc aliases and the cs4265 (power control?), I've recreated those patch files against the appropriate linux source and added them into my build, are they still needed? it seems to work but as far as I know they might also be doing nothing.
Also is the alsa config file only for handling the switching from analog to spdif in the cs4265?
Thank you!
-
adam.h. thanks for compiling this, it's given me plenty of things to to try. Cheers 👍
-
I'm trying to see if I can get the sound card working for my slice with a cm4s installed, I've managed to make some changes to the driver source code to make it compile with kernel V6 and make an aarch64 image.
I can hear sound from it but it's mostly distorted and there's a regular distorted sound that occurs every 4 seconds.
Just wondering if anyone has an idea about what it could be and can point me in the right direction, debug log file is at https://paste.libreelec.tv/elegant-marmot.log
My repos can be seen here...
GitHub - 4nvjgf39/slice-dt-overlays: Device Tree Overlay files collectionDevice Tree Overlay files collection. Contribute to 4nvjgf39/slice-dt-overlays development by creating an account on GitHub.github.comGitHub - 4nvjgf39/slice-drivers: linux kernel modules for the Slice boxlinux kernel modules for the Slice box. Contribute to 4nvjgf39/slice-drivers development by creating an account on GitHub.github.comCheers
-
in your edid - it reports left, right and LFE
Thanks for the explanation and guide to fix the issue. It's the same thing I was seeing while testing a custom build. Turns out it was just the weird TV I was testing on and not my build.
-
Thanks for this, I've copied some of the updates to my local repo and the build is successful now.
-
Sadly due to the UK online safety act repo.or.cz is now blocked for UK users and only displaying the following page https://repo.or.cz/uk-blocked.html, that means it is no longer possible to build LibreELEC as it fails when trying to get the (rtmpdump package) without the use of a VPN.
If you're in the UK don't forget to thank your MP.
-
That's actually pretty amazing, thanks for sharing the news.
Might just have to plan an upgrade at some point
-
What usb versions are the hdd and port on the pc? My dashcam will not have a stable connection to any of my usb3 ports on my laptop, the only way I can connect it is via a cheap usb2 hub.
-
I had this issue today too upgrading from Februarys firmware to Junes (rpi5). The instructions here and a spare SD card got me back up and running.
Not sure if I caused it, I clicked the update toggle on the LibreELEC menu and when nothing was seemingly happening I did a reboot which then had problems
-
Updated my RPi5 to 20240308 nightly and then updated the EEPROM via the Libreelec settings and this issue now seems to be resolved.
Thank you Libreelec team.
-
Hello,
Setting up my RPi5 I noticed that almost all of my 25i content is not causing a change to the display refresh rate from its default 60Hz to 50Hz.
25p seems to switch okay and so does 24p. 30i also seems to cause a change.
Debug log:- https://paste.libreelec.tv/major-condor.log
Log file seems to mention 12.5fps, though ffmpeg mentions 25fps.
If theres anything else i can do please let me know.
Thank you.
-
thanks noggin for sharing this, this is really interesting news.
I'd certainly look into this if its easier than getting an rpi4, HVEC decoding and HBR audio would be a great feature update for the Slice and would buy a few more years of use. Dare we hope of 4K output too?
chewitt out of interest can you tell from the stats if people are moving over to LE10? Mine might be counted as a rpi3 (not that it makes much difference from a 100).
-
Thanks for the quick reply HiassofT , I've followed your suggestions and its looking much more stable now. I cleared the thumbnail folder too, and while I started off with cma320 which was much better it did still suffer a kodi restart. I'm using cma384 now and its looking good so far.
Cheers

-
Hi,
Thought I'd give LE10 a try on my Slice as the RPI3 is now supported, unfortunatley it seems a little unstable. Scrolling though the movies section I can consistently crash Kodi.
Links for the crash logs http://ix.io/3SlL
I'm also seeing the following on the boot screen (after i reboot or shutdown), not sure if its all connected...
Code[TIME] Timed out waiting for device /dev/serial1. [DEPEND] Dependency failed for Broadcom sdio firmware update for BCM43430A1 [111.455310] [813]: Failed to unmount /flash: Device or resource busy [111.458831] systemd-shutdown[1]: Failed to finalise file systems, loop devices, ignoring.No worries if this is not a priority to look at right now I've got my 9.2.8 backup. Maybe it helps with RPI3, maybe it doesn't.
Cheers
-
The Slice look like it uses a GL830 USB > Sata interface
That makes sense, it certainly looks like a USB drive from the way Libreelec and Kodi present it.
Maybe i will try the RPi2 build
I dont think it will make any difference for you with this issue. it'll possibly be useful when LE10.2 is released.
Maybe it's just a power issue
that would be my guess too, my original drive is rated at 1amp. When you connected it via usb, did you use a seperate power supply? The plug is rated at 3amps so the slice is capable of drawing plenty of power, cant find any real power output details for that chip.
-
I'm still using the slice (CM3) with the original onboard 1TB drive, I switched over to the RPi2 build a couple of months ago as a test and it still works for me.
if I remember rightly the drive height is thin, 7mm maybe? does your drive fit in the case? thats the only reason thats stopped me putting in a newer disk. I think I'm using exFAT for the disk format.
-