Posts by Da Flex

Quote from PinnacleRG

Not sure if this is related to what you saw in the log.

Code

BEDROOM-LibreELEC:~ # pastecrash
terminate called after throwing an instance of 'std::runtime_error'
 what():  No modesetting DRM card found
Aborted (core dumped)
https://paste.libreelec.tv/outgoing-shad.log

DRM seems to be disabled by systemd, but later in use by kernel:

Oct 15 14:11:12.863659 LibreELEC systemd[1]: [email protected]: Deactivated successfully.
Oct 15 14:11:12.863682 LibreELEC systemd[1]: Finished [email protected].
...
Oct 15 14:11:15.007318 BEDROOM-LibreELEC kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0
Oct 15 14:11:15.007348 BEDROOM-LibreELEC kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 PST 2019

Or does the first DRM mean "Digital Rights Management"?

The WLAN driver shows some errors in the crash log. So try with Ethernet, if you can (deactivate WiFi on the LE settings).

Quote from scaesare

Yeah, it's been working for several years, and was on 12.0.2. It was one of the devices listed on Mr. Chromebox's page and I used his script to flash the firmware & install LibreELEC.

Do you use the same BIOS settings in both boxes?

Quote from chewitt

How do you explain it working on 12.0 then ???

Maybe the GPU is not supported by newer kernels, and older kernels had an unofficial driver.

scaesare Can you compare the BIOS options of the working and non-working box? Maybe that's all it needs for booting LE.

I think your GPU is not supported on any Linux:

Quote from scaesare

It's an ASUS Chromebox CN 60 as described HERE.

Quote

Linux GPU Support : No

It's basically the same answer we already gave you in your other thread:

Post

RE: [x86-64] Wrong speed with "Sync Playback to Display"

Quote from chewitt , who explained it to me in the background:

[…]

Da Flex

September 26, 2025 at 6:17 PM

What did you installed exactly? LE x86-64 legacy? What are your hardware specs?

Quote from MichalDV

It’d be great if this info was highlighted a bit more in the docs, because most newcomers won’t even think to dig into cmdline.txt.

Most newcomers don't even know what composite is. So the conclusion is: If someone needs composite, then it's a nerd, who can deal with config files. Anyway, you can write into our Wiki, if you want.

Quote from chewitt , who explained it to me in the background:

Quote

feel free to mess with compile flags AND disabling hardware decoding

the latter is important, because when you enable hardware decoding (on most hardware) Kodi is trying to use a zero-copy path

zero-copy basically means no opportunity to mess with the stream (as that requires copying)

most hardware cannot CPU decode and process high-bitrate 4K UHD media

the example given of low-latency DJ tools being able to stretch audio is correct, but ignores the reality of 4K UHD video being 10x the data size of an mp3 file

all that data needs to be moved in/out of memory multiple times once you mess with it

and at that point all the whizzy ideas are dead in the water

Display More

Maybe time stretching helps to normalize playback speed. Seems like it's actually possible with FFmpeg:

Timestretch Audio and Video Using 'Rubberband' Filter - FFmpeg By Example

The following command will be a video that plays at half speed with audio that's both slowed down and pitched down by an octave. Note: To enable compilation…

ffmpegbyexample.com

chewitt Do we use the rubber band flag for FFmpeg compilation?

Quote from chewitt

The getedid script solves a single and specific problem; the TV not being powered on before the RPi starts.

That could have an impact for CEC connection, so I would give it a shot.

LE probably still uses the old CEC route for HDMI port 3. So run getedid create from SSH while being connected to HDMI port 2.

I don't think it's an LE problem. The easiest solution is to solder the LED off, and use an LED connected to GPIO.

Try without any HiFiBerry entries at config.txt. There is a chance that it's detected automatically in newer LE versions, and explicit activation leads to a setup mismatch.

Quote from hasta

I've been using Libreelec9.x on a Raspi3.

...

Now I've updated to Libreelec12.2 (complete reinstallation and also reconfiguration of the system).

Do you mean an installation from scratch? That's the officially suggested way to "update" from LE 9.x to LE 10+.

Background: If you're using an outdated settings file internally, then something like your audio issue can happen.

Double-post:

Audio Profiles (for Kodi 18 and later)

Closed, because the dev is at Kodi forum, not here.