Posts by chewitt

Please share the boot log (dmesg) from the box running LE (can you SSH over WiFi?) and after booting the original Android OS.

Download https://releases.libreelec.tv/LibreELEC-AMLG…droid-c2.img.gz and write it to an SD card (or the eMMC module) using another app like Etcher or Win32DiskImager. Not sure why it's not reaching 100% but the USB-SD app isn't doing anything special so it's fine to use something else.

phemmer Ignoring the obvious I/O errors, the one thing that stands out to me is this:

[ 1.557543] meson_uart c11084c0.serial: Failed to create device link (0x180) with wifi32k

Most of the errors are I/O and look like a dying SD card or perhaps bad PSU that causes instability issues for the (known to be problematically sensitive) MMC devices: SD/eMMC/SDIO. The failure of the wifi32k device to probe right means WiFi (SDIO) will not work, but oddly the other UART based device, BT, appears to proble. Most odd. Another possible cause is the MMC clock speed being too high, but it's only 100MHz (default in the upstream kernel is 50MHz) and it's been stable at that rate with other devices (stats show other U9-H users) so I don't think that's the reason. If the device has been booting CE or Android fine that would generally rule out PSU issues; they would likely show up in other OS too.

Please put this on a new/different SD card https://chewitt.libreelec.tv/testing/LibreE….0.2-box.img.gz and see if you can grab the boot log again. I'm not seriously expecting anything to be different but it has some additional patches and a newer kernel than the official release so you never know

I deleted the other post on the same topic. Keep to one thread and please stop formatting text with code tags (unless you really do want posts to be ignored)..

Stats show a bunch of active installs using the GT1 device-tree file. Read: https://wiki.libreelec.tv/hardware/amlogic

Create a clean LE11 image (to remove previous configuration attempts). Now edit "config.txt" and change "include distroconfig.txt" to "include distroconfig-composite.txt" and then boot the board. Working?

NB: Kodi only supports progressive output.

You might also want to check-out dtech LE 9.2.8 release for older WeTek boxes.

Nope. Still there.

2023-04-24 18:04:04.764 T:1428     info <general>: Found resolution 1280x720 with 1280x720 @ 60.000000 Hz
2023-04-24 18:04:04.765 T:1428     info <general>: Found resolution 1920x1080 with 1920x1080i @ 60.000000 Hz
2023-04-24 18:04:04.765 T:1428     info <general>: Found resolution 1920x1080 with 1920x1080i @ 59.940063 Hz
2023-04-24 18:04:04.765 T:1428     info <general>: Found resolution 1920x1080 with 1920x1080i @ 50.000000 Hz
2023-04-24 18:04:04.765 T:1428     info <general>: Found resolution 1280x720 with 1280x720 @ 59.940063 Hz
2023-04-24 18:04:04.765 T:1428     info <general>: Found resolution 1280x720 with 1280x720 @ 50.000000 Hz

The mode list ^ shows you haven an older "HD Ready" TV that does 720p max. Kodi only outputs progressive so we ignore the 1080 interlaced modes that are available.

2023-04-24 18:24:48.646 T:3321     info <general>: [WHITELIST] Searching the whitelist for: width: 1920, height: 1080, fps: 25.000, 3D: false
...
2023-04-24 18:24:48.646 T:3321    debug <general>: [WHITELIST] Matched a desktop resolution with double the refresh rate 1280x720 @ 50.000000 Hz (22)
2023-04-24 18:24:48.646 T:3321     info <general>: Display resolution ADJUST : 1280x720 @ 50.000000 Hz (22) (weight: -nan)
2023-04-24 18:24:48.651 T:3321  warning <general>: OpenStream - Unsupported stream 1001. Stream disabled.

The 2/3/4 plays in the log follow this format; note the unsupported stream warning. The first play doesn't show the warning .. not sure why but all are trying to play 1080@25 media at 720@50 which probably isn't going to work.

In most countries channels are broadcast in 540p (PAL) or 480p (NTSC) "SD" versions and 720p or 1080p "HD" versions. As you don't have a 1080p capable TV you will need to remove/ignore the 1080p HD channels in your channel list.

Quote from LucidEye

Really doesn't instill any confidence in your product if you can't even DL it.

We don't have a product and everything is hosted for free via third party mirrors. If you want to use something else .. we're fine with that.

The second one is harmless (appears on all hardware running LE) and can be ignored.

The first one is related to UPnP support .. no idea what the issue is though. In general your logs are so full of deprecated warning garbage that its hard to see what's really going on.

Quote from Grarea

Any pointers or advice would be appreciated, thank you.

Report add-on issues to the add-on maintainer via the add-on support thread in the Kodi forums .. it's not an LE issue.

Initiative test .. what happens when you type "LibreELEC debug log" into Google?

Enable debug loging .. clean boot .. demonstrate the problem .. run "pastekodi" and share the URL generated. From this we can see properties of the media being played and resolution changes etc.

Pithy comments normally inspire the forum staff to ignore posts. Just saying..

In the absence of a boot log ..

I have never seen anyone using Radarr/Sonarr outside of a Torrenting setup; which means piracy; which means I didn't read the original post beyond those words. And just because I have a high post count doesn't mean you can assume personal support.

Apr 23 15:12:13.064341 LEMC kernel: EXT4-fs (sdb1): error count since last fsck: 13
Apr 23 15:12:13.064824 LEMC kernel: EXT4-fs (sdb1): initial error at time 1598463659: ext4_validate_block_bitmap:384
Apr 23 15:12:13.065026 LEMC kernel: EXT4-fs (sdb1): last error at time 1599941347: ext4_free_blocks:4964

Both drives were fsck'd on boot due to dirty filesystems (not unmounted cleanly before shutdown) but it's impossible to see/say what causes the shutdowns. The ^ above errors suggest the drive has errors after being fsck'd so it might be dying. The largest cause of drive mounting issues and instability on RPi boards is an inadequate power supply. And power characteristics of the board under LE11 may also be different than LE9 due to major software changes and general evolution. If you're adding drives then the board is going to draw more current even if the drives are powered from a separate hub or via their own PSUs.