I'm fuzzy on the reasons why, but I don't think it's currently possible. It would be nice to have though. NB: We build an OVA image for vmware Workstation/Fusion (or ESXi) or Oracle VirtualBox to support GUI dev work without the need for real hardware.
Posts by chewitt
-
-
"dtname" will tell you the "compatible" string used by your board.
-
11.0.6 has switched ix.io to our own paste server since ix.io was down, so just cat/pipe files to "paste" and you'll get a URL.
Uploading files sounds like you're copying the file over SMB? Has it been created in Notepad.exe? If yes this is likely a Windows line endings issue and will be solved by creating files with Linux line endings using Notepad++ or accessing the box via SSH and using nano (copy/paste the content to the screen) to create the file.
-
Share the full "pastekodi" debug log not the snippet YOU think is relevant that lacks all the other info WE know is relevant.
-
No comment on the hardware, configuration, or media type so nothing to investigate.
-
I'm going to break some rules and push a kernel bump to Linux 6.8.y for LE12 b2 .. so there are 11.95.2 images in my test share.
dmladenov the S905L content is now p271 (all mention of p261 is gone) so you will need to update then edit uEnv.ini to change the dtb name. If you confirm it all still works (at least the essentials) I will send the device-tree upstream.
WP2 fixes are in the process of being upstreamed. I found some other minor things and am figuring out how best to do thing before sending a revised patchset.
I've added an Amlogic version of the "getedid" script to support devices turn on before TV's, for those who need it.
I've abandoned interest in supporting overlays. I'm not sure they're really needed and it complicates things.
U-Boot 2024.04 removes all Amlogic device-tree files (so we only maintain the kernel ones, which is great) but the change assumes that all dtb files live in an /amlogic folder in the root of boot media so I've changed the layout in our .img files. This drops a couple of patches and aligns us with Allwinner and Rockchip (also good). Updates work the same as always; the update script will check for dtb files in existing locations in addition to the new one and update them accordingly. No need for new installs or panic.
I've added support for the Vero 4K (again). It now has S/PDIF audio support and whoever it was who needed a p212 device with S/PDIF audio should be able to us it to get their no-name box working (can't find the thread.. never mind).
-
Install the web filemanager add-on (available in LE11/LE12) to put the file in the right place, then reboot.
This is a lost cause
-
Code
Display MoreFound resolution 1920x1080 with 3840x2160 @ 60.000000 Hz Found resolution 1920x1080 with 3840x2160 @ 50.000000 Hz Found resolution 1920x1080 with 3840x2160 @ 30.000000 Hz Found resolution 1920x1080 with 3840x2160 @ 25.000000 Hz Found resolution 1920x1080 with 3840x2160 @ 24.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz Found resolution 1920x1080 with 1920x1080i @ 60.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 50.000000 Hz Found resolution 1920x1080 with 1920x1080i @ 50.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 30.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 25.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 24.000000 Hz
The Kodi log shows the TV doesn't offer 1080p/2160p @ 23.976 through EDID which is why that mode doesn't work correctly. The usual routine with EDID proglems is to check the cables and the ports on the TV (and software options on the TV) as different ports often have different capabilities (resulting in different EDID).
The upstream kernel hardware decoder does not support 4K/H264; the original developer comment was "Amlogic had to go through various lengthy hacks to get it implemented so I've skipped it for now" .. and that was 2019 and nothing changed since. The box will play 1080p H264 and 4K HEVC so the main suggestion would be to re-rip/encode 4K H264 media files to 4K HEVC. There is no HDR to SDR conversion for UHD media in the upstream kernel.
The vega-s95 device-tree in my test share has been tweaked to allow non-broadcom SDIO modules (e.g. Realtek) and the image has some RTL8189ES/FS drivers: https://chewitt.libreelec.tv/testing/ which might allow WiFi to work. The remote can be (re)configured using the instructions in the wiki: https://wiki.libreelec.tv/configuration/ir-remotes - You can (re)use the "rc-videostrong-kii-pro" keymap which is already present in the image if that works.
NB: The AMLGX image does not have feature parity with older LE releases and will not suit everyone's media collection. If it does that's great. If it doesn't .. it doesn't.
-
-
If the USB drive mount point under /var/media/<disklabel> changes the database files contain incorrect paths to the media and need to be updated else you will see "file not found" errors when trying to play something.
Code<advancedsettings> <pathsubstitution> <substitute> <from>/var/media/OLDNAME/SOURCE/</from> <to>/var/media/NEWNAME/SOURCE/</to> </substitute> </pathsubstitution> </advancedsettings>
Path substitution ^ should work. Or you need to process the contents of the database files.
-
This is normally a failure of u-boot to read a factory programmed MAC from efuse; which is then populated to device-tree and used by Linux once it's booted. In some cases the MAC wasn't programmed. In others it's been programmed to a different efuse location on your board-type to the location that u-boot expects. I'd hazard a guess that u-boot needs tweaking with a custom board file so that u-boot knows how to read it from a Rock Pi 4 SE vs a generic RK board and that change probably exists in Radxa's downstream u-boot fork but hasn't been upstreamed to the mainline u-boot source that LE is using. Ask Radxa..
-
If you did clean reinstall (option e in a list - not a keyboard press/hotkey) there is no need to do a hard reset. Everything else would benefit from one. You need to change the "Update channel" to see older releases.
-
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>kodiuser</user> <pass>kodipass</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>192.168.1.100</host> <port>3306</port> <user>kodiuser</user> <pass>kodipass</pass> </musicdatabase> <videolibrary> <importwatchedstate>true</importwatchedstate> <importresumepoint>true</importresumepoint> </videolibrary> </advancedsettings>
That's my advancedsettings.xml file ^ and I've never had to do more than that to have things work. MariaDB is running on a NAS box in the network. Try telnet'ing to the IP/port for the database to ensure it connects. Networking issues are not uncommon once VMs and containers are being used. Also have a look in logs for any issues; enable debugging and issues are normally quite clear.
-
I have not used the term ‘Wizard’ for a long time.
In the Kodi ecosystem "Wizards" are mostly associated with piracy add-ons/builds so avoiding that term is a good move
-
The primary reason people want a dummy /opt link is to install entware, and the primary reason people want entware is to add a package manager to install piracy tools. There are other uses for entware, but observation of distros in our surrounding media-oriented ecosystem where it's been added shows clearly what the majority are trying to do.
Our source code is on GitHub. You are welcome to take it, modify it to your needs, and use as you like, but we have no interest in supporting or encouraging entware so it's not going to happen in our default image.
-
I'm hoping there's an interface within KODI I can use to just attach a second external storage, copy/move the newer content, then remove once I'm finished.
Kodi Settings > File Manager .. it's a little clunky to use but does exactly that ^
Or copy things over the network (SMB or SFTP)
Or realise that 14TB should really be a NAS device on the Network somewhere
-
Five options:
a) Copy the file old release file (.img.gz, .img, or .tar) to the Update SMB share on the box and reboot
b) Use an SFTP client to copy it to /storage/.update, then reboot
c) SSH in, change directory (cd) to /storage/.update and then wget the file, then reboot
d) Use the manual update function to change to an older release series and select an older version, then reboot.
e) Create new install media using the older .img.gz file and clean-install using that.
Unless you did 'E' once you're on the old release, do a hard reset in LE settings to remove all traces of newer versions.
All of the above are documented in the wiki .. and I'm done with the spoon feeding.
-
Kodi determines audio/video capabilities based on EDID content on the HDMI connection so if the EDID output is bad or broken it will cause features to be not-detected. It's unusual for a modern TV to have bad EDID data, but it does happen.
I'd suggest experimenting with other HDMI cables and different ports on the TV, as different ports often have different capabilities and sometimes you need to enable e.g. "Deep Colour" modes in port settings to have HDR or 4K60 support (there are no standard terms; vendors make up different names).