Code
mkdir -p /storage/.config/firmware/brcm^ create and download correctly named files in that folder and reboot - no need to hack the SYSTEM file
Posts by chewitt
-
-
I'm running my own image with some minor tweaks, but only cosmetic things. Do you have any funny characters in passwords?
-
I'd guess the drives are EXT4 formatted? EXT2/3/4 reserve 5% space for root to ensure (when the disk is a system drive) that core processes have available space to operate. So the drives showing 0% available have < 5% free. You can use tune2fs to reduce the percentage that's reserved. This can have a negative impact on fragmentation, but with media drives that contain large (should be contiguous) files this is probably a lesser concern than for system drives. You can run e.g. "tune2fs -m 1 /dev/sde1" to set the percentage at 1%.
-
Your description implies that build completed but the devicee does not boot. It would be informative to know at what point in the boot sequence the device fails to boot, hence the request for UART output. However it looks like you're one of those users who is fixated on a specific thing and knows better than us how debug a boot problem. So
and good luck. NB: LE 9.2 is a dead codebase so I would restart with LE10 anyway. -
SMB configs are simple but there are many variables to guess from. So unless you describe what you're trying to connect to in detail, we can't help.
-
Note that RPi4 using LE 9.2.6 does not support 4K@50/60 modes (anything above 4K@30) without additional options set in config.txt, and there is currently no equivalent support in the LE10b1 release (4K60 is still being worked on).
-
XML
Display More<?xml version="1.0" encoding="utf-8" ?> <advancedsettings version="1.0"> <!-- enable debug logging --> <loglevel hide="false">1</loglevel> <videodatabase> <type>mysql</type> <host>192.168.1.100</host> <port>3306</port> <user>username</user> <pass>password</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>192.168.1.100</host> <port>3306</port> <user>username</user> <pass>password</pass> </musicdatabase> <videolibrary> <importwatchedstate>true</importwatchedstate> <importresumepoint>true</importresumepoint> </videolibrary> </advancedsettings>^ FYI, this is mine, with minor edits to change credentials
-
There is no issue with using the </advancedsettings> tag (works fine here with a range of devices I test with). I'd guess there is an XML formatting problem somewhere else in the file.
-
Yeah, but it's the same answer.
-
Very sad to hear.
The GBM/V4L2 pipeline has probably been actively used on about 10% of the overall range of x86_64 hardware that users probably have. Some of that percentage will be low-risk, but we're expecting a fair number of quirks to surface. So you might be in a rush to use an "official" image instead an otherwise working fine "community" image, but LE10 already impacts 85% of our userbase (RPi) so Generic is in the queue and will have its day (along with the likely end of nVidia support) but some more elapsed time is a good thing. We're not in a rush.
-
No logs, no accurate description of before/after changes to SMB settings, and not enough technical detail to do anything beyond guess at the issue:
a) Your hardware might have NICs that need odd drivers to work
b) Your SMB server needs different settings, or Kodi client isn't configured correctly
I'd guess it's the later .. but .. it's just a guess
btw, LE *never* auto updates between Kodi major versions, so it was your decision to manually upgrade.
-
Switching between LE10 nightlies and LE10 beta images doesn't require reinstallation. Just 'update' as needed.
-
-
If we want to use official
Until we switch from X11 there are no official images with HDR support. The earliest we might do something is LE10.2, but more likely LE11/K20.
-
Why won't it make it to the LE10 builds?
because LE10 still uses ye olde Xorg for the Generic image and all these patches are aimed at the GBM/V4L2 pipeline we are not (yet) using. Until we make the switch, community created images are the well-proven approach to testing things.
-
No, for the simple technical reason there is zero upstream kernel support for the hardware. An RPi Zero will outclass it by a mile.
-
Does post that I just found help?
Nope. The entire video rendering and hardware decoding pipeline has changed. All previous articles are null and void.
-
Kodi assumes that you will define "sources" and then "Set content" for the source to e.g. "Movies" and then scan (scrape) the source, i.e. when it finds a movie it will lookup the movie in TVDB.com and download metadata and fanart etc. to create a rich library view. This fails since you are offline.
To prevent this and still use Libraries you will need to change the scraper for each source to "Use local content only" and provide the metadata via .info or .xml files and locally stored images (in the same folder as the movie normally). The Kodi wiki has lots of info on files/formats and how to arrange the media in folders etc. to do this.
To prevent this and not use Libraries at all .. define sources and browse them via the "Videos" menu item which is a non-Library raw view of the files in the source. Kodi will create thumbnails from the local media, but there's no online lookups.
It sounds like you're missing the step to change the scraper - for each source you've defined.
