Posts by Albert

Quote from MatteN

Probably because you have banned stuff on your system.

https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons

Which ?

Quote from chewitt

Nope.

Why ?

Hi,

I had a crash after playing a video on YT, can you describe what happened ?

hastebin

Quote from popcornmix

I've never used one of these boards. So can't really advise. Maybe someone else uses something similar.

This is the sort of thing, but that one looks to be discontinued.

this maybe ?

Gravity: Digital IR Receiver Module

Infrared devices are widely used, and often for remote controlled devices. With the DFRobot digital IR receiver module, your Arduino project is now able to…

thepihut.com

Hi,

Is it possible to add just one IR module ?

Quote from chewitt

GPU memory is fixed at boot time and we already optimised consumption. Kernel caching has a simple rule: "if you understand the kernel documentation, do what you like, else leave alone" and since 99.99% of users will not understand kernel memory architecture it's best left alone. On the Kodi side users like to tweak cache/buffers settings thus undoing thousands of man-hours of effort to optimise the default settings with a ham-fisted bodge from a forum post where a user with a different use-case and no great clue about the underlying mechanisms said it made things better. As a broad rule cache settting changes will fix one thing and cause three more things. So feel free to go nuts .. do the reading (lots of kernel docs, RPi docs, Kodi docs are out there) but when it all makes no different or causes issues - revert back to the defaults and marvel at how things just work again.

Hi, I understand what you're saying, and you've convinced me.

Thank you for these explanations !

Quote from MatteN

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 😁.

Quote from MatteN

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

Quote from MatteN

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 !

chewitt  mglae  Da Flex

I installed the addon, plugged it in, unplugged it, restarted it. Everything seems to work now

Quote from HiassofT

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.

Quote from Da Flex

The initialization of the CEC adapter has a bug. On your working LE 12.0.1:

Code

2024-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

Display More

On your non-working LE 13 nightly (20241103-f662bea):

Code

2024-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

Quote from mglae

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

Quote from Da Flex

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

Quote from Da Flex

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

Quote from Da Flex

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 ?