Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
Updated drivers on newer Linux kernel.
PS:
2025-11-12 19:50:07.762 T:1129 info <general>: load skin from: /storage/.kodi/addons/skin.xperience1080/ (version: 10.0.0)
Use the default skin to rule out any complications with a custom skin.
Should I move all those - besides the newly added <power> - to remote.xml instead?
Yes, basically just to keep remote and major device separated in config files.
Check your microSD for errors. You can do that from any Linux PC. You can also copy & paste among microSD cards that way.
Thanks, but I actually want to get the shutdown dialog when pressing the power button on my remote control. I just want to power-off when pressing the power-button on the computer.
That's why remote.xml exists as a separate option.
I thought Legacy was for NVidia cards?
Generally yes, but the old X11 can sometimes fix issues like this.
Same with Generic-Legacy?
Is the SD card with the problems completely broken, or will formatting it be enough to get it working again?
Use GParted for scan and repair. This tool can leave bad blocks out during formatting.
Yep, if you find a current crash log, post that one, and use the same method as for kodi.old.log. ATM it's unclear whether it's a crash or a hanger.
To shutdown instantly, create this /storage/.kodi/userdata/keymaps/keyboard.xml:
<keymap>
<global>
<keyboard>
<power>shutdown</power>
</keyboard>
</global>
</keymap>But when the issue occurs, the system is unresponsive and I have to switch it off to get it to work again.
For such cases use cat /storage/.kodi/temp/kodi.old.log | pastebinit from SSH, and post the resulting URL. kodi.old.log contains the data from the last session with the crash.
Before you start logging, set the log level to 1 at advancedsettings.xml, and reboot.
Just log at log level 1...
Thanks for your prompt reply but I am not sure what you are saying.
Simple: No support until you've cleaned your LE add-ons and repos.
So the DAC doesn't exist at /dev folder after boot sequence, right? What's the /dev path after hot-plugging the DAC?
I guess you have to remove the driver(s) first. Also try to restart the audio server (ALSA).
chewitt Maybe reloading a driver from autostart can do the trick?
Maybe a problem with the USB hub. Connect the DAC without using the USB hub.
Thanks. Please post a complete log for the boot sequence (when the DAC isn't detected).
Is the DAC selected as your default audio device in the settings?
