Posts by chewitt

History shows that these changes are rarely permanent (where there's a will, there's a way) but since fixing depends on part-time developers giving time for free, things aren't always quick, esp. in early Jan when everyone heads back to their day jobs again. Keep a watch on the Kodi add-on support thread for more info.

Quote from gecko20016

I bought this tuner because it was recommended to work well with LE/Kodi. Can you suggest another model or manufacturer which works well in combination with a RPi4 ? I actually just want a setup that works reliably.

I've always recommended people run the server on a separate device to the player. This allows you to keep the server end on something that works; often a conventional distro where you can (re)compile the kernel with whatever set of shitty hacked-up drivers are needed to make the tuners work reliably, and then never change it while the no-longer-dependent-on-weird-kernels player device runs whatever latest LE/Kodi release you fancy. Linux DVB drivers suck

It looks like it got missed somewhere (we will investigate). You can always download 10.0.2 then do a manual update to 10.0.3 using the regular Generic .tar or .img.gz file (both contain KERNEL/SYSTEM which are the only things updated).

Textures13.db has become corrupted so a query to the DB fails; this is shown in the second and third errors. The DBus error is harmless.

Delete the Textures13.db file and the thumbnails folder. The DB will be recreated on Kodi restart, and thumbnails will be re-downloaded on access to GUI views that require artwork. If you don't remove the thumbs the cache references will be incorrect and you'll have blanks all over the GUI and you'll need to manually refresh everything to repopulate content.

The issue is probably add-on configuration not the content of the script or filesystem perms. You've probably configured a path to a folder not the script so it's trying to execute the folder (which isn't an executable object), hence the error.

To be clear: There is zero support for hyperion under GBM and that's unlikely to change. It's a fundamental "how GBM video pipeline's work" thing and not "development code is a bit rough" (there is no development code). Hence the previous suggestion to look at external grabbers if hyperion is a must-have for you.

I rebased my experimental AMLMX image (for Meson 8 devices) on LE master branch using Martin B's latest Linux 6.2-rc kernel yesterday. It's completely untested as I don't have a spare monitor to use at the moment, and prob. needs some manual fiddling to boot on some devices due to the prehistoric u-boot versions being used (UART cables may be required) but people are welcome to play:

https://chewitt.libreelec.tv/testing/LibreELEC-AMLMX.arm-10.88.0-box.img.gz

NB: I rebased the AMLMX image (for Meson 8 devices) on LE master branch using Martin B's latest Linux 6.2-rc kernel yesterday. It's untested as I don't have a spare monitor at the moment, and prob. needs some manual fiddling to boot on some devices due to the prehistoric u-boot versions being used, but people are welcome to play: https://chewitt.libreelec.tv/testing/LibreE…88.0-box.img.gz

Quote from jim_p

Thank you for all the clarifications. I want to try a le11 nightly image on s905 sometime (= when I will feel better and done with all the medical tests), so does it contain the device tree for my box (mxqpro4k 1gb)? Also, can it boot from a usb stick, because I have no sdcards handy?

There's no specific device tree but there are a number of other GXBB (S905) box devices present and one will probably be close enough to work. The upstream kernel doesn't require RAM specs to be coded in the device-tree which makes experiments a little easier. The box will always boot from emmc (hardcoded boot priorities) but you should be able to use the 'toothpick' method to trigger a recovery mode search for boot.scr and loading the upstream kernel from SD or USB.

If you have further Q's let's take them to a separate thread (or the AMLGX general thread) to keep this one on-topic.

Our settings add-on submits pastes anonymously, so there's no method to delete pastes. The site does purge pastes at some point, but there appears to be no formal policy on when (that we ever found). To ensure pastes are available for as long as possible (sounds like a reasonable goal) I'd expect purge to be FIFO and triggered on disk consumption not paste age.

_emanuel_ We inherit "keep-power-in-suspend;" from the w400 dtsi SDIO node so I'm not sure what's wrong or missing there. I do note that you've told me the sdio-pwrseq node is "GPIO_ACTIVE_LOW" whereas the vendor dts shows "GPIO_ACTIVE_HIGH" .. not sure if that's relevant.

Please also see if https://github.com/chewitt/linux/…e0c5cd69ba1c6f0 gives control over the red power LED, power button, and the Volume up/down/enter keys now?

Have a look at /storage/.kodi/temp/kodi.log for errors/issues. My thoughts would be a corrupted DB file or something add-on related. Worst case stop Kodi and rename /storage/.kodi to /storage/.kodi-old and restart; then start copying back config/content items from the old install until you either find the problem or end up with a working install again.

_emanuel_ I've rebased the branch with the SDIO change and this Fixup! patch https://github.com/chewitt/linux/…6757ed536b40b9d .. please see if that resolves the boot hang for you?

Quote from Omina

I have two 3.5" 4TB hard disks, plugged into an external drive dock ... and used the Storage Spaces utility to combine the two drives into an 8TB volume (setting up RAID 1)

To be pedantic: If you combine 2x 4TB drives into an 8TB volume you have RAID0 (striping) not RAID1 (mirroring) so data is "at risk" under any OS because RAID0 provides zero redundancy.

Quote from mdofperth

Any ideas on how I fix this and get my IVACY subscription running on LibreELEC?

LE10/LE11 images use Python 3.x, the last release to use Python 2.x was LE9.2. So options are:

a) Persuade <insert name of whatever VPN service> to provide a Python3 compatible version of their add-on

b) Find and extract the connection details and credentials/certs used from the add-on and use them with e.g. Zomboided's add-on.

Option A has no further action from us (the add-on, the service, and everything related to it is someone else's problem). If you go for Option B redirect future Q's to Zomboided's add-on support thread.

You probably need to test the specific (not Open) SUSE images provided for these devices as those are more likely to have some tweaked power management code. If not, you're needing to read up on ACPI debugging and/or sending emails to the Linux kernel mailing list asking for help on how to debug it. Understanding power states is one of those less-easily understood bit of the kernel .. I don't have any docs I can point you to.

The Kodi shows that there is no HDMI source detected. You can try appending "HDMI-A-1:1920x1080M@60" to boot params (same as the 'ssh') but this will only give you limited resolutions. You an also try an LE11 nightly: https://test.libreelec.tv/11.0/RPi/RPi4/