Larsen most boxes will boot from a USB, but usually only one specific port on the box. All boxes should boot from an SD card though. It's unlikely that an S905W box has encrypted boot, so I wouldn't run down that rabbit-hole before trying an SD card.
Posts by chewitt
-
-
-
Can you rm -rf the connman service folder for the NIC under /storage/.cache/connman/<name of service> and reboot. Any change?
And/Or try to use connmanctl to create a connection:
connmanctl
agent on
scan wifi
services
connect <service>
-
ConnMan intentionally cannot see hidden networks, but you can SSH into the device (over Ethernet) and configure WiFi using iwctl.
-
The image compatibility check will fail during RPi2 to RPi3 update/crossgrade as the image name doesn't match the current one. The cheat for that is "touch /storage/.update/.nocompat" before rebooting.
-
Code
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" ?
-
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.