LE builds are already optimized enough, the gain would be minimal.
I hear, it's just that I like to know how my device behaves 😁.
LE builds are already optimized enough, the gain would be minimal.
I hear, it's just that I like to know how my device behaves 😁.
Reducing the already low power consumption would probably be quite useless.
Right, how can we make the most of the rpi ?
I know that gpu memory, cache, buffer etc. can be added or managed. Or it's really useless ?
Hi,
I have a few more questions.
I would like to do a stress test to check the stability, i tried this command: journalctl -f | grep -i underv but it doesn't work.
And I also wanted to know if it's possible to optimize the rpi, I'm not looking for OC, but to disable or enable useful elements or not. to reduce consumption.
I'm thinking of the files config.xml and advancedsettings.xml
Just optimize the device
Having 2 ssd's connected through usb (without external power) on a Banana Pi M5 using CE21 havent caused any problems in close to a year, same ssd's on Pi 4 and LE f*cked up almost every week.
you'll have to wait for version 13 stable, otherwise do as I did, install nightly and the ntfs3g addon.
Thank you all !
Use the other HDMI port. CEC is only supported on the first HDMI port (HDMI-A-1, the one next to the power connector).
LE 12.0.1 contained a change to support CEC on both ports, but kodi didn't cope with this well so this had to be dropped again.
so long,
Hias
You had to think of it 😁. It actually works there.
The initialization of the CEC adapter has a bug. On your working LE 12.0.1:
Code Display More2024-02-27 18:26:18.011 T:916 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-02-27 18:26:18.012 T:899 info <general>: starting zeroconf publishing 2024-02-27 18:26:18.012 T:911 error <general>: CCurlFile::CReadState::FillBuffer - (0x7fff1401ca40) Failed: Couldn't resolve host name(6) 2024-02-27 18:26:18.012 T:927 debug <general>: Thread EventServer start, auto delete: false 2024-02-27 18:26:18.012 T:925 debug <general>: Thread CECAdapter start, auto delete: false 2024-02-27 18:26:18.012 T:925 debug <general>: OpenConnection - opening a connection to the CEC adapter: /dev/cec0 2024-02-27 18:26:18.012 T:912 error <general>: CCurlFile::CReadState::FillBuffer - (0x7fff080532d0) Failed: Couldn't resolve host name(6) 2024-02-27 18:26:18.012 T:912 error <general>: CCurlFile::Open - <https://mirrors.kodi.tv/addons/omega/addons.xml.gz?sha256> Failed with code 0: 2024-02-27 18:26:18.012 T:916 debug <general>: Initialise - initialised peripheral on '/dev/cec0' with 2 features and 0 sub devices 2024-02-27 18:26:18.012 T:916 info <general>: Register - new cec device registered on cec->/dev/cec0: CEC Adapter (0000:0000) 2024-02-27 18:26:18.012 T:916 debug <general>: GetMappingForDevice - device (0000:0000) mapped to CEC Adapter (type = cec) 2024-02-27 18:26:18.012 T:912 error <general>: CRepository: failed read 'https://mirrors.kodi.tv/addons/omega/addons.xml.gz?sha256' 2024-02-27 18:26:18.012 T:910 debug <general>: CAddonDatabase::GetAddons took 48 ms 2024-02-27 18:26:18.012 T:911 error <general>: CCurlFile::Open - <https://addons.libreelec.tv/12.0.0/ARMv8/aarch64/addons.xml.gz.sha256> Failed with code 0: 2024-02-27 18:26:18.012 T:911 error <general>: CRepository: failed read 'https://addons.libreelec.tv/12.0.0/ARMv8/aarch64/addons.xml.gz.sha256' 2024-02-27 18:26:18.012 T:916 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-02-27 18:26:18.013 T:930 debug <general>: Thread CECAdapter start, auto delete: false 2024-02-27 18:26:18.013 T:930 debug <general>: OpenConnection - opening a connection to the CEC adapter: /dev/cec1 2024-02-27 18:26:18.013 T:916 debug <general>: Initialise - initialised peripheral on '/dev/cec1' with 2 features and 0 sub devices 2024-02-27 18:26:18.013 T:916 info <general>: Register - new cec device registered on cec->/dev/cec1: CEC Adapter (0000:0000) 2024-02-27 18:26:18.013 T:916 debug <general>: Thread PeripBusCEC 140733637783296 terminating
On your non-working LE 13 nightly (20241103-f662bea):
Code2024-11-05 16:49:04.830 T:1046 debug <general>: InitialiseFeature - using libCEC v4.0.7 2024-11-05 16:49:04.830 T:1057 debug <general>: Thread CECAdapter start, auto delete: false 2024-11-05 16:49:04.830 T:1057 debug <general>: OpenConnection - opening a connection to the CEC adapter: Linux 2024-11-05 16:49:04.832 T:1046 debug <general>: Initialise - initialised peripheral on 'Linux' with 2 features and 0 sub devices 2024-11-05 16:49:04.832 T:1046 info <general>: Register - new cec device registered on cec->Linux: CEC Adapter (0000:0000) 2024-11-05 16:49:04.832 T:1046 debug <general>: Thread PeripBusCEC 140732832476800 terminating
In the working log, the CEC adapter is registered at /dev/cec1, in the non-working log at Linux.
I've already reported the bug to the devs. Stay tuned.
Ok, if I can't do anything on my side. I'll wait with my rpi3 again
You can build it yourself when having the environment (see Wiki). If not you have to wait.
I'm not sure I'll find it, it's here ?
https://wiki.libreelec.tv/development/build-commands/build-addons
Do you use IR (LIRC) or CEC for the remote?
CEC, but how can I really know. In any case it worked before the update to 13 nightly
I noticed that the version of cec adapter is 4.0.7. on my rpi3 (osmc) it is 6.0.2
You probably made a key mapping for the remote. This should be part of your LE 12 backup. Try to load it from LE 13.
Yes that's correct, the remote.xml file is still in the same location. So it should work.
EDIT:
Here last log: https://paste.libreelec.tv/frank-dragon.log
Our nightly builds are very stable, they are just not tested as much as the stable ones.
Make a backup from LE 12, and if something goes wrong with LE 13, you can go back by update folder method.
Hi,
I've upgraded, but my remote is no longer recognized, so I can't use it. do you know what could have happened ?
Hi, I'm just discovering LE, is it useful to do it every night? Is it a “stable” version ?
And if I make a backup of version 12, can I come back to it without worrying ?
The ntfs-3g addon is currently only available for LE13. For LE12 it still need to be merged.
Tell me if I can merge it or do I have to wait until it's official ?
- This is likely a power issue. Does your powered USB hub still work as expected?
No, when it's connected to my RPi 3 I have no problem. I've had this setup for years.
The NTFS-3G add-on should be in the LE repo (at least the LE13 repo, it might not be merged for LE12 yet) under Services. There's also an NTFS-PROGS add-on in the Tools section which has some of the utility binaries.
Drives that disconnect and reconnect on their own normally trace back to bad power supplies and/or bad USB cables.
Searching on github I found it. It is in .mk format. But on libreelec I don't see anything at all, in service, extension program....
My drive is powered by an independent power supply. I programmed the enclosure so that the drive stops spinning after 5 minutes when it is not working. But that is a question.
LE automounts local devices via udev and remote devices through systemd .mount units: /etc/fstab is nothing more than a stub file to stop some binaries complaining that it doesn't exist. It is not writeable since it's inside the read-only squashfs SYSTEM file.
If you haven't unmounted the NTFS filesystem cleanly from the current device it will probably be in a "dirty" state and that needs to be cleared on Windows using chkdsk.exe before you can attempting mounting under Linux again.
Have a look at the NTFS-3G add-on in the "Services" section of the LE repo. This (added in the last week) add-on overrides the in-kernel driver and uses the older NTFS-3G userspace driver approach used in older LE releases.
Yes, the clean disk is recognized, but if I modify it, add a file, it is no longer. Moreover I notice that it disconnects and reconnects it quite often, I don't know why it does that. For the ntfs-3g addon, I can't find it in the repo ??
Can I install it manually ?
Hi,
You have a solution to this problem.
I also tried to create a file fstab (UUID=5EAEFAE2FEFAB2FF/var/media/DDE ntfs defaults 0 0
and autostart.sh (mount -o uid=1000,gid=1000 UUID=5EAEFAE2FEFAB2FF/var/media/DDE)
but it doesn't work
Code Display MoreFeb 27 18:26:04.338050 LibreELEC kernel: usb 3-2.1: new high-speed USB device number 3 using xhci-hcd Feb 27 18:26:04.338150 LibreELEC kernel: usb 3-2.1: New USB device found, idVendor=2537, idProduct=1066, bcdDevice= 1.00 Feb 27 18:26:04.338251 LibreELEC kernel: usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 27 18:26:04.338333 LibreELEC kernel: usb 3-2.1: Product: NS1066 Feb 27 18:26:04.338429 LibreELEC kernel: usb 3-2.1: Manufacturer: Norelsys Feb 27 18:26:04.338522 LibreELEC kernel: usb 3-2.1: SerialNumber: 0123456789ABCDE Feb 27 18:26:04.338612 LibreELEC kernel: usb-storage 3-2.1:1.0: USB Mass Storage device detected Feb 27 18:26:04.338731 LibreELEC kernel: scsi host0: usb-storage 3-2.1:1.0 Feb 27 18:26:07.743322 LibreELEC kernel: scsi 0:0:0:0: Direct-Access Generic HDD 0 PQ: 0 ANSI: 0 Feb 27 18:26:07.744202 LibreELEC kernel: sd 0:0:0:0: [sda] Media removed, stopped polling Feb 27 18:26:07.744306 LibreELEC kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
The only mention of a USB drive device in the system log ^
The "Media removed, stopped polling" makes me suspect power issues. You can add "usb_max_current_enable=1" to config.txt and see if that makes a difference. Note that RPi5 needs a decent PSU (official one is recommended).
Hi,
My hard disk is powered by the HUB power supply, then I use a HUB to connect it to the RPi 5.
HD > HUB (PS) > RPi 5
only the microsd is powered by the RPi 5.
i've done some quick research and i see that there are problems with nfts disks.
because when I put my hard disk and microphones back on my RPi 3, they don't appear any more either. so the problem also occurs on my RPi 3, whose setup I've had for many years without a hitch.
when I run a check on my Windows it detects errors that it corrects, and then the disk goes up it goes up, but if I reboot and remove then put it back again.
So I don't know what's going on with libreELEC to make it do that.