Posts by chewitt

Feb 16 19:11:01.959281 LibreELEC kernel: usb 1-1.5: r8712u: CustomerID = 0x000a
Feb 16 19:11:01.960477 LibreELEC kernel: usb 1-1.5: r8712u: MAC Address from efuse = 24:05:0f:6b:f2:ef
Feb 16 19:11:01.961390 LibreELEC kernel: usb 1-1.5: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Feb 16 19:11:01.962782 LibreELEC kernel: usbcore: registered new interface driver r8712u
...
Feb 16 19:11:02.386054 LibreELEC connmand[639]: wlan0 {create} index 3 type 1 <ETHER>
Feb 16 19:11:02.386091 LibreELEC connmand[639]: wlan0 {update} flags 4098 <DOWN>
Feb 16 19:11:02.386127 LibreELEC connmand[639]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Feb 16 19:11:02.386158 LibreELEC connmand[639]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Feb 16 19:11:02.387214 LibreELEC connmand[639]: Adding interface wlan0 [ wifi ]

^ The MAC address of the USB NIC matches what ConnMan sees as wlan0. The only thing I see that looks abnormal is the interface not being brought to an UP state. What happens if you manually do "ifconfig wlan0 up" ?

Quote from miebster

Does anyone know how to get 2 identical displays?

Use an HDMI cable that duplicates (mirrors) the output to two displays. There are lots of cheap $5-10 options on Amazon/eBay.

Use numerical numbering, e.g. 11.0.1 .. 11.0.1.1 .. 11.0.1.2 .. 11.0.2

If you are going to release/maintain images please set BUILDER_NAME="ardaoktay" in .libreelec/options so we can track the image in active-install stats. This means you can also ask occasionally to discover how many (or few) users you are entertaining

Please you run "pastekodi" and share the URL so we can see the full log. The snipped you've shared appears to show the device being probed and the driver loaded. The difference between LE10 and LE11 is we've dropped the vendor driver in favour of an in-kernel driver that's in the process of replacing it.

To be clear, Kodi does not support downgrading so while "updating" to the older .tar file will downgrade the core OS and embedded Kodi app itself without any issues; there is zero support for downgrading add-ons and this may cause issues. If you see problems, you will need to stop Kodi and rename the current add-on binary folders out of the way and then restart and reinstall the add-ons you need. If you are lucky the K20 and K19 add-on settings formats are compatible; and if not you'll need to stop and rename those out of the way too.

If videos are on the USB drive the speed of the SD card is rather irrelevant. Just use it.

Support for 23.976Hz modes is determined by the EDID data presented by the TV/Monitor on the HDMI connection. Most (but not all) TV's will have a 23.976 mode. Most better monitors support it too. Older TVs may not, and cheap monitors often support only 50/60Hz modes.

If the remote doesn't work please follow this: https://wiki.libreelec.tv/configuration/…ration-advanced to capture the keys so we can compare to what I've set in the preconfigured keymap.

Testing with no dtb name or dtb's for SoC types that don't match yours (S812 aka meson8m2) is pointless. I would not expect them to work so we can ignore those non-results. And if you're going to report an issue (on the correct SoC type) as a minimum you need to share the URL generated by "pastekodi" after accessing via SSH, or dump the systemd journal and pastebin it somewhere.

fab233 add "video=HDMI-A-1:1920x1080M@60" to boot params in syslinux.cfg; this should force Linux to 1080p@60 instead of the 4K modes which either driver or TV seems to dislike. Kodi GUI will run best @ 1080p with 4K modes only used for video playback via whitelist and adjust-refresh set to start/stop.

As documented in the release notes that nobody reads: Users with an nVidia GPU will need to use the Generic Legacy image as the GBM/V4L2 graphics stack that is now used in the Generic image does not support nVidia cards.

Pastebin a debug log somewhere please.

What's the actual CPU temp on the box? .. is it running at 85ºC or did the kernel evolve and finally gain support for reporting CPU thermals resulting in some overlooked placeholder value triggering warnings at 50ºC?

Post

RE: Rock 5B 3588

bosko1333 Initial support for the RK3588 SoC and core board peripherals are not merged into the upstream kernel and it will take time to work on u-boot support and media drivers etc. once those are finally merged. I'm sure we will have RK3588 images in the future, but right now it's way too early to think about creating anything. LE is not interested in images based on the vendor kernel (which is also incomplete but does exist). If the community wants to play with the vendor kernel it's…

chewitt

December 15, 2022 at 1:57 PM

^ Same SoC so same answer, there is only minor progress since December. Ask again in six months (or look for a different board).

Kodi has logic for handling fall-back to software decoding with DRMPRIME hardware decoding enabled. As no hardware supports 10-bit H264 hardware decoding it will always fall-back to software. This normally gives bad results because software decoding 10-bit H264 requires lots of CPU and few users are using high(er)-end Intel chips that are capable of the task.

Subtitles support selection preferences for default selection when there's a collection of subs to choose from, but there's currently no way to say "if english keep subs off, if french turn subs on" .. the on/off decision is always manual and user determined. If you want that to change you need to make a request in the Kodi forum feature-requests section. If you want to submit something to the Kodi main branch it needs to be code because Team Kodi doesn't accept requests via GitHub issues - it's a bug tracker so if you make one it will be closed.

https://wiki.libreelec.tv/configuration/edid has instructions on configuring an edid.bin file so Kodi sees the TV as always connected. The wiki needs updating to reflect that the Intel instructions apply to all devices using the kernel DRM architecture; including Amlogic (and Allwinner, Rockchip) boards.

https://chewitt.libreelec.tv/edid.bin was dumped from older (2012-ish?) Samsung 8-series TV, and contains 23.976/24/25/29.97/30/50/59.94/60 modes. You might not be able to use all (or any) of them, but it might work and you can disable the ones that don't in the whitelist.

https://wiki.libreelec.tv/configuration/…ration-advanced has instructions (also needing update) on capturing and creating a custom IR config. The bit that needs updating is that the config file format has changed to "toml" .. but if you look at the wiki instructions and compare to the toml files in /usr/lib/udev/rc_keymaps/ the new format is pretty simple to crib.

Kodi only reads mode data once at startup so swaping cables after boot will not change anything. And if the 4K 50/60 modes configured in the mode whitelist are not available (due to 1.4 cables) they will be silently dropped; requiring you to edit the list and reinstate them if you reboot with higher spec 2.0 cables attached again. NB: Lots of users think they have high-speed cables and will swear on their mothers life that their cables are not the issue; but issues often magically go away when a new certified cable is purchased