Posts by chewitt

Installation to spare disk space (needing two partitions not one) is possible, but not using our installer, and we do not provide instructions or support on dual-boot setups. If you know what you're doing (and depending on which other OS's are involved) it's not particularly hard to configure. If you don't know what you're doing (and most users don't) then it's a fiddly multi-step process with lots of confusing terminology and a high risk of trashing the other OS installs. We're not interested in the support work of guiding someone through recovery, which is why we don't have the feature or support dual-boot setups.

2023-10-09 19:45:27.267 T:1229    ERROR <general>: CFileCache::Open - <http://USERNAME:[email protected]:9981/imagecache/151> failed to open
2023-10-09 19:45:27.268 T:1229    ERROR <general>: CCurlFile::Open failed with code 404 for http://127.0.0.1:9981/imagecache/85:

It's not a debug log (so of limited use for diagnosing media issues) .. the only thing that stands out is ^ this sort of thing which is probably missing channel picons or thumbs of some kind in TVHeadend which is causing delays when doing DVB things. I don't see any attempts to play offline media though .. which is presumably what a delay when "navigating to a folder" is about. Debug log needed for that.

As noted by johnny depp the installer app should be able to see the USB drive under Windows to write the LE image directly to the SSD. RPi images do not boot into an installer where you pick the install target (as in the Generic image).

Does the SSD have it's own PSU or are you trying to power the SSD from the board? .. and what PSU is being used?. Note that USB booting has a much higher current draw on the board than SD card and will need something like the official Raspberry Pi PSU that's rated for (and will actually give) 5V/3A to avoid power brown-out issues; which from the description of boot failures and reboots is my guess/hunch on the problem. You might also need config.txt changes to boost power on the USB ports and some USB drives still suck enough current to need their own independent PSU. For kicks, you can also boot an LE12 nightly from SD card and ensure any available firmware updates have been applied (via updates in LE settings).

If this all sounds fiddly, please remember the board was designed to boot easily from SD card (and that bit works easily and as advertised). If you want to go off-piste with more exotic boot scenarios it's not quite as straightforward.

cp /storage/.config/samba.conf.sample /storage/.config/samba.conf
nano /storage/.config/samba.conf
<make changes, save, exit, etc.>
reboot

In LE the /etc/ path is inside a read-only file so cannot be edited, but renaming the samba.conf.sample file and editing does the same thing.

Did you interrupt syslinux and type the command? (correct) .. or boot into the installer and type the command? (wrong)

No idea on the boot/reset issue. You need to force recovery boot if the device has been running CE else the u-boot bootscripts are looking for the wrong files; but your description says you've seen the Kodi home screen which would mean you've gotten beyond that issue and first-booted the box into LE.

You can use the same video= line but chage the resolution to 720p. Kodi can only handle progressive output so will ignore 1080i resolutions.

Otherwise it's pretty much impossible to "guess the issue" without UART logs from the box.

Upstream u-boot has no support for Amlogic proprietary restore image formats and sequences.

No idea what the issue is, but if the nightly works, use it, you'll find it's quite stable (Kodi is overdue a move to Beta).

Removing "quiet" and adding "ssh" to the APPEND line in uEnv.ini will result in console output on-screen (although it tends to dump text to screen faster than most eyeballs can track anything) and forces SSH to start so if boot has reached userspace (maybe) you might be able to connect to the box and poke around to look for issues. Something else to try is adding "video=HDMI-A-1:1920x1080M@60" (all on the same line) to force DRM output to 1080p; in case it's trying to use a 4K mode and disagreeing with the TV panel in some way.

Kodi displays a percentage indicator on-screen when playback stalls and the 'stream' needs to be buffered again. There's a multitude of reasons for a stream to stall and never recover, but the main candidates are a bug or something in the hardware decoder, or something in the media that ffmpeg doesn't handle right.

Things to try:

a) Disable DRMPRIME and hardware decoding. If the media now plays (software decoded) the issue is in the hardware decoder.

b) If not 'A' the enable things again and update to a current LE12 nightly since this has newer everything

c) If not resolved with 'B' share a reasonable snippet of media so that Pi engineers can have a look.

And if posting again, share a debug log that demonstrates the issue.

You cannot write (dd) anything from the u-boot console. Even if you could, you would fail writing to emmc since that's what the device has booted u-boot from (at some point you overwrite the code you're running). The board should boot from USB in addition to SD though; although you might need to manually start USB from the usb console before manually running bootscript commands.

Specs claim that it's an S905 (GXBB) so the AMLGX "box" image should work from SD card. You'll need to experiment with different "gxbb" device-tree files to see what works best. Read: https://wiki.libreelec.tv/hardware/amlogic#box-images

Quote from AiRLAC

You happen to have a dd backup of the Wetek Hub factory image?

backup-hub.tar.gz

Shared with Dropbox

www.dropbox.com

Quote from WarpLover

I am about to use emmctool and want to verify that the Play2 chip I am about to flash is a qualcomm?

Nope. Amlogic S905.

Library databases are in /storage/.kodi/userdata/Databases (from memory) as versioned sqlite .db files, e.g. MyVideos121.db; the databases are not .xml files.

Quote from JohnWayne111

What do you think about a LE 11 support for PI 5 ? Is it possible?

If yes, must we have to wait for a Kodi Nexus 20.3 release?

Kodi still has the intent to make a 20.3 release but there are complications with shipping another K20 Android release via the Google Play store as Google now requires a minimum API version that's higher than K20 implements (and each API bump typically requires some finessing in Kodi code). The route forwards hasn't been agreed yet.

If/when/once https://github.com/LibreELEC/LibreELEC.tv/pull/8181 is merged support will be in nightlies; although personally I'd still prefer the team to focus on an LE12 release; while LE11 compiles fine I'm not sure anyone put some testing miles on it and users expect "stable" releases to be, well, stable.