Add "textmode" to boot options, and the system will start as console.
Posts by Da Flex
-
-
Known issue:
ThreadRaspberry Pi Legacy Tools Add-on
I would like to know the reasons why the RPi.GPIO library was dropped from the Raspberry Pi Tools add-on. In my opinion, this is a mistake. I'll explain. I am the author of the OLEDproc plugin. It depends on several libraries, including the luma.oled and luma.core libraries. And therein lies the trouble. The luma.core library needs the RPi.GPIO library to work. I am convinced that it is unthinkable and also pointless for me to create some clone of the luma.core library, which would use, for…
LuRuJuly 20, 2024 at 9:55 AM Pro tip: Always use the search function from the forums main page before posting anything.
-
Our devs will make it part of the LE image. Check nightly builds from time to time.
-
For the best experience in mid 2024, which hardware would you choose?
Wrong question. Describe what you need, and then WE make suggestions for YOU.
Learn to speak for yourself.
-
Have a look at Settings -> System -> Input -> Peripherals -> CEC Adapter.
As you can see, you can only use one HDMI device as CEC target, and that's probably your projector.
Other CEC devices only have an on/off/standby switch via CEC.
-
Wiki says:
QuoteThe second impact of the Kodi desktop resolution is how media is scaled. If "Adjust Refresh" is not enabled, Kodi will scale all media played up or down to the desktop resolution and refresh rate, which by default is 1080p @ 60 fps.
So enable "Adjust Refresh".
-
Thanks, probably my Firefox has a bug.
-
Please check your attachment. I can't download the file.
Does Balena Etcher verification work for the written image?
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
My power LED also doesn't work with standard RPi Tools. It's one of the coolest RPi features to program small displays.

-
Code
Feb 27 17:26:06.187729 LibreELEC kernel: [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader! ... Feb 27 17:26:09.555847 LibreELEC kernel: panfrost d00c0000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found ... Feb 27 17:26:09.826320 LibreELEC kernel: brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.clm_blob failed with error -2Please update all available firmware:
-
A dev was talking to me, and said it's very likely a network issue.

-
Could be a DRM Prime buffering issue:
Code2024-07-18 17:29:55.961 T:1120 debug <general>: CDVDVideoCodecDRMPRIME::Reset - flush buffers 2024-07-18 17:29:55.967 T:1121 debug <general>: CDVDAudio::Pause - pausing audio streamYou can try to disable DRM Prime, but that might disable HDR, too:
PostRE: Raspberry Pi 5: HDR not working
[…]
HDR probably doesn't work without DRMPRIME, which is why I keep trying to stop people disabling it.
chewittJune 9, 2024 at 2:19 PM -
Sorry, the dev still needs more info. This is what he wrote to me:
QuotePlease ask for the kodi.old.log immediately after the RPi has rebooted (with debug enabled, run pastebinit .kodi/temp/kodi.old.log immediately after reboot).
The last two crashlogs were empty and the one from the first post seems like some unrelated crash from a normal shutdown.
It doesn't look like some crash, more like an intentional reboot or shutdown+poweron - maybe from the gpio-shutdown overlay / button cabling- enable permanent log level 1 by creating an advancedsettings.xml file
- reboot
- replicate the issue
- run the above command, and post the resulting URL
-
updated Nuc13 firmware to the latest version...
Which firmware exactly? HDMI support is part of the graphics driver firmware. That's the important one.
-
The "inhibit lock taken" is normal, I have the same message in my own RPi3B+ log.
The dev had a look at the logs, and was talking to me. He would like to see a crash log right after a crash.
So when LE crashes, bring it back to a functional state, login by SSH, run pastecrash, and post the resulting URL.
-
-
Thanks. It's a problem with the initialization of the internal Bluetooth adapter.
CodeJul 12 17:54:41.968605 HTPC (uetoothd)[932]: bluetooth.service: Referenced but unset environment variable evaluates to an empty string: BLUEZ_ARGS, BLUEZ_DEBUGSo it's a Linux kernel issue (driver/firmware). Buying a Bluetooth dongle seems to be the easiest/quickest solution. Do some research first, and make sure the dongle is Linux compatible.