Section "Device"
Identifier "Nvidia card"
Driver "nouveau"
EndSectionIn the Xorg image, create /storage/.config/xorg.conf with ^
XORG_DEBUG="-logverbose 6 -verbose 6"Also create /run/libreelec/debug/xorg.conf with this ^ and then systemctl restart xorg.service to get debug output.
Also run journalctl -xe windowmanager.service to perhaps see more about what the failing dependency is?
Official:Forum rules/Banned add-ons - Official Kodi Wiki
If you want support, come back with a full clean Kodi debug log showing no pirate crapware installed.
Probably this https://github.com/LibreELEC/LibreELEC.tv/pull/9671
in which case grab the latest nightly from https://test.libreelec.tv/ .. both LE12 and LE13 nightlies have the fix.
Fresh image using OpenGL/Xorg: https://chewitt.libreelec.tv/testing/LibreE…-12.80.1.img.gz
If OpenGL ES vs. OpenGL wasn't the issue, I'm out of ideas.
What happens if you run umount /etc/issue ??
It's a 2.4GHz wireless (but not WiFi) device that pretends to be a keyboard then. It's most unusual to see issues with them as they are simply a keyboard device to the OS. Share the output of "lsusb -tv" and the URL from "pastekodi" please.
RPi5:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4085920 16 4085904 0% /dev
tmpfs 1648976 17904 1631072 1% /run
/dev/nvme0n1p1 524008 154160 369848 29% /flash
/dev/loop0 139264 139264 0 100% /
/dev/nvme0n1p2 228336223 3052383 225279744 1% /storage
tmpfs 4122400 0 4122400 0% /dev/shm
tmpfs 4122400 16 4122384 0% /var
tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs 4122416 0 4122416 0% /tmpIt's not like that here (on this RPi, or any other device I'm using). Post evidence to support and explain what you're seeing.
Please add "ssh" to boot params so the daemon is forced to start on boot and you can access the console without using textmode, which also disables a bunch of stuff in the OS and probably prevents Kodi from running. Then "pastekodi" to get the system boot and current Kodi log or Kodi crash log, if any?
NB: I suspect OpenGL ES support for nv40 cards might be rather lacking, so I'll tweak the image to use OpenGL instead.
How is the remote working? .. IR sensor added to RPi board, CEC, BT, USB widget that pretends to be a keyboard?
Boot with the TV on, then SSH in and run getedid create to capture the EDID data from the HDMI connection to file and configure boot to use this so it thinks the TV is always on.
What have you set (or not set) in config.txt ??
See if this works: https://chewitt.libreelec.tv/testing/LibreE…-12.80.1.img.gz
If yes, these were the buildsystem changes: https://github.com/chewitt/LibreELEC.tv/commits/nouveau
The only tweaks I made from the original PR were updating the libdrm change to use enabled/disabled not true/false, and I bumped the xf86-video-nouveau version to latest. The image was built with PROJECT=Generic DEVICE=Nouveau ARCH=x86_64 make image
I think most of your issues stemp from not declaring GRAPHICS_DRIVERS correctly. You've modified config/graphic to force one part of the overal buildsystem config but that variable is used in many places so "nouveau" must be set in the device options file.
The TLS cert issue in older images is simply that the embedded ca chain is now outdated and thus websites and services don't work as certs are seen to be invalid. Current images support /storage/.config/cacert.pem as a boot time override, but I forget when that was added or whether LE 9.0/9.2 works with it. You can also try the image that dtech is still shipping for some boards (not sure if he has something for C2 or not). Crib https://github.com/LibreELEC/LibreELEC.tv/pull/9533 for the most recent cacert.pem update we merged if you're looking to build something in yourself - there are general self-build instructions in the wiki.
The original RPi boards needed hardware decoding to handle media and codecs could be licensed to keep costs down. It's never been an option on any other vendors board and these days modern RPi boards abandonded licensing as the boards have enough CPU performance to decode older codecs with ease (RPi5 even does this for H264).
LE13 nightlies track Kodi master, so yes.
Hmm, is there maybe a typo in the wiki as I only see two "move-after" and not one "move-before" commands in the example from the above mentioned wiki page:
Stop blindly copying things from the wiki. It shows general hints not verbatim instructions. Your existing service file results in a connection. You can add move-after or move-before commands to adjust the routing config. You can also run the move-after/before commands from the SSH console to experiment in-situ and see the impact on the routes on your box. Go experiment, figure out what combination you need, then add the same sequence to the file. If you don't need static routes, don't add static routes.
The error message is quite clear, no?
