NB: If anyone has a second/spare U9-H box I'd be interested in acquiring it for testing. I've attempted to pick one up on eBay a few times, but I've either been outbid on the item (which is crazy) or sellers have refused to entertain shipping the device to the UAE.
Posts by chewitt
-
-
Adding "textmode" to kernel boot params in uEnv.ini will boot to a text console (no Kodi) allowing you to poke around. Kodi logs aren't going to be of any use/interest. The systemd journal/dmesg are where any clues might show up.
NB: I've no interest in LE11 codebase for a long time now, so please use the images from my test share instead.
-
How/where have you configured the keyboard?
-
Upower warnings are harmless and can be ignored. You probably need to stick with an older LE release that's more era-appropriate for 17-year old hardware.
-
The family daily-driver systems here are all configured for continuous debug logging .. all part of the joys of being a staff tester.
-
If the location of media changed the existing DB content is invalid and you will need to remove the NAS sources, add the USB drive as a new source, and rescrape; which will re-download all the thumbs and info off the internet again. Or you need to run a tool against the existing DB files to update/correct the invalid file paths (from NAS to USB) .. but if the USB only contains a subset of the content on the NAS device that isn't going to truly 'fix' anything either. TL/DR: In 99/100 cases cloning a current install "to save time and effort" causes confusion and results in more effort as you start out with a half-broken setup. Start out with a clean install, add the USB drive as a source, and let is scrape. Unless you're on dial-up 28.8k internet it'll be done fairly quickly and everything will be correctly referenced.
-
I never had problems .. don't go too extreme.
-
Update to 11.0.4 or a current 12 nightly and retest, an upstream bug was fixed that may have stopped things working.
-
I'd start over with a clean install and just use the Videos view to nagivate the USB stick. Keep it simple.
-
This forum is dedicated to LibreELEC which does not run on the nVidia shield. Ask for Android support in the Kodi forum.
-
The old image doesn't support the firmware and bits needed for newer "RPi4" hardware, and while that's not an impossible task to solve it's not going to help with providing a future path forwards; only the newer codebase offers that.
I'm not entirely sure where to direct attentions, but RPi4 and thus probably CM4S has different USB hardware compared to CM3 so there are probably some device-tree changes needed.
-
Do you have any advice or experineces whether a bigger passive heatsink (e.g. using the Flirc case) or other optimazations could help me to increase the max. playable bitrate?
Overclock?
-
In "textmode" boot a large number of services chained from systemd "user.target" aren't ever started hence audio and other things aren't preconfigured properly for Kodi use. It's interesting to note a possible correlation with Kodi being started, but the assumption that "the hdmi audio device driver falsely grabs the sd-card interface" is creative thinking, but not possible in code.
Have you previously reimaged the box with one of the custom legacy-kernel images? or is/was it still running a factory image? If the former, does the problem exhibit if you restore the box to factory spec first?
-
So, box image on USB---how to edit the uEnv.ini file?
Use Notepad++ on Windows (as unix line-endings are important). Use anything you like on macOS/Linux.
-
If you enable "show hidden files and directories" in Kodi Settings > Media you can use the Kodi filemanager to navigate to /storage and delete the folder.
-
This change was made in LE12: https://github.com/LibreELEC/LibreELEC.tv/pull/8161 and backported to LE11 in https://github.com/LibreELEC/LibreELEC.tv/pull/8180 before LE 11.0.4 was tagged/shipped.
According to the patch/change, using "Shutdown()" as the mapped button command should restore the previous behaviour.
-
Not possible. The traffic for an add-on is not 'contained' within Kodi, and Kodi itself does not run 'bound' to a specific interface on the host. So traffic is just traffic and the OS routes it off-host based on the default interface (default route) and static IP routes that send traffic for a specific destination through a specific interface. IP routing rules can achieve what you want to do, but the ruleset will be a non-trivial challenge to create and maintain over time.
-
Perhaps you should steal another version of the file that plays better then?
