Posts by chewitt

boot=UUID=0602-0454 disk=UUID=a7ecf32f-d897-4f8e-b760-03d219e31c88 quiet ssh

^ cmdline.txt normally looks like this, with both "boot" and "disk" using UUID identifier. I'm not sure why yours is using =label for the "disk" but it can be changed. The UUID will be unique to each .img.gz file that we release so ^ above is NOT something you can use, as it's for an image I've created that you don't have. You can find the UUIDs for your image using "blkid" command. It will look something like:

/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="0602-0454" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a0ebf7ce-01"
/dev/mmcblk0p2: LABEL="STORAGE" UUID="a7ecf32f-d897-4f8e-b760-03d219e31c88" BLOCK_SIZE="1024" TYPE="ext4" PARTUUID="a0ebf7ce-02"

You can see that the /dev/mmcblk0p1 (partition 1) needs UUID=0602-0454 and /dev/mmcblk0p2 (partition 2) has a much longer UUID=

a7ecf32f-d897-4f8e-b760-03d219e31c88 .. and in cmdline.txt there is a space between the boot=UUID=<string> and disk=UUID=<string> sections.

Ahh, thanks for the correction

The HEVC decoder has poor memory and buffer management which impacts resource usage and seeking; the legacy of it never being finished by its original developer (and beyond making the unfinished code run, nobody really touched it since). My semi-educated guess is that HEVC doesn't release CMA memory correctly and then when you play media requring a different codec the new codec can't reserve enough CMA and things start to fall (and hence a clean boot works around the issue). It all buckets under "HEVC needs work" and I also confirm MPEG2 is not working right now (packets go into the driver, nothing comes out).

S912's have always run hot so a good heatsink is never a bad thing. I've a VIM2 + heatsink which runs around 60-65ºC so I'd be wondering what add-ons you're using that chew CPU in the background (some do) to keep cores busy.

RE: Zero see https://github.com/radxa/kernel/p…ment-1013592761 .. although I'm not sure whether A311D (more compute, but also more power needed, more heat given off, etc.) is a good fit of the small package size. A sample is in the post so I get to have a play someone soon in theory. I do like the S905Y2 version as I can power it off the UART pins and it runs well except for the state of playback on newer devices (there are some problems). There's a plan for fixing things but we need to be patient while developers work through other items on a long board bring-up list .. and eventually they reach the subset of media topics we care about.

4K and HDR works quite well on GXL/GXM devices although GXL internally processes at 10-bit but outputs only 8-bit (GXM can do 10-bit).

Latest attempt at the IRQ splat with suggestions from maintainers - see if it works:

WIP: arm64: dts: meson: add support for OSMC Vero 4K/4K+ · chewitt/linux@12d9c05

The OSMC Vero 4K device is based on the Amlogic S905X (P212) reference design with 10/100 Ethernet. The Vero4K+ is based on the S905D (P230) reference design…

github.com

+&usb2_phy0 {
+       /* HDMI_5V also supplies the USB VBUS */
+       phy-supply = <&hdmi_5v>;
+};

^ also see if that works for the USB error?

EDIT: I've pushed updated box/tar files with those changes.

[    2.037266] dwc2 c9100000.usb: dwc2_core_reset: HANG! Soft Reset timeout GRSTCTL_CSFTRST
[    2.039904] dwc2: probe of c9100000.usb failed with error -16

Hmm.. I will bug maintainers for ideas on the IRQ splat - I also see it on a Bananapi-M5 board. This ^ also needs looking into.

Put batteries in the remote, put it in "pair" mode. Go into LE settings add-on, bluetooth settings, see the device, select > pair

boot=UUID=3010-5350 disk=LABEL=STORAGE quiet

It's a text file. It's better to edit it in Notepad++ to avoid Windows line endings, but it can be done from Windows. Note that it should look like above, no spaces between "boot = UUID" etc.

fixup · chewitt/linux@2cc8c94

github.com

^ Can you try with that. If no change please drop the IRQ 29>30 change and try again.

Last I heard it was generally working well on RPi3 boards (1GB RAM) and we were thinking to release LE 10.0.2 with support. I'm less sure of the state that RPi2 is in .. lots of those boards have less RAM which will be more of an issue.

Utiliser une clavier USB pour navigation en Kodi et connection de la télécommande Logitech

Use a USB keyboard for Kodi navigation and to connect the Logitech remote.

NB: Langue de la forum est Anglais. Il n'y a pas beaucoup des person ici qui parle Français.

On a Raspberry Pi the error means it booted from the KERNEL file and executed the init script inside, but this cannot find disk=?? device that was specified in kernel boot params (from cmdline.txt on a Pi device).

If cmdline.txt has disk=UUID=xxxx then perhaps change it to disk=LABEL=STORAGE and see if that works?

If you have a USB keyboard you can create a directory, mount the SD card to the directory, then use cat/sed to read/change the content of the cmdline.txt file and reboot. If you don't, remove the SD card and edit it from another computer. It's in the root folder of the SD card.

I updated the box/tar files with https://github.com/chewitt/linux/…6b2f58878cb5c41 based on the original dts content and the 4.9 IRQ dump. Does that resolve the splat?

I'm also interested to know if this patch improves speed (untested): https://github.com/superna9999/li…1a72fb03b85d099

Sam shared the original "vero3_2g_16g.dts" and "vero3plus_2g_16g.dts" dts files with me earlier which explains why I couldn't find Vero"4"k files in the OSMC GitHub kernel repos. Vero4k is indeed p212 and Vero4k+ claims to be p231 but looks like the upstream p230 and inherits most of it's content from the Vero4k/p212 tree so but at least we have the truth on buttons (one reset, in the AV jack) and LEDs (one red) now. I suspect the blue + on the 4K is hard-wired, hence past user complaints. I can't see anything unusual in the external_mdio node but then I have no clue about IRQ/interrupt stuff.. it sounds likee you know way more than me

I've updated the box image and tar file in my share and pushed updated patches to kernel/LE branches. Boot logs appreciated..

LE does not release any ARM images in "ARCH=aarch64" format so we don't bother bulding add-ons we won't use. If you rebuild the image with ARCH=arm you will have a full complement of add-ons available.

It's the first time someone shows up with an S905W2 board and it's hard cum impossible to diagnose these things without seeing the UART (serial console) output from the box. That requires a UART cable and cracking the box open to connect it, which often involves soldering pins to the board. I'm always game for that - but most users aren't?

Quote from roterdrachen

Will this device be supported by the LibreELEC team?

I'm confident it will be supported. I'm less confident on when or how quickly it might be supported. LE will not be using vendor-kernels so we are dependent on the upstream kernel state for RK3588

Quote from HomerJau

I noticed ffmpeg 5 was released a couple days back. Do you know if this adds the HDR support needed by Kodi?

I'm not aware of there being "Kodi" related changes for HDR iin FFMpeg of any version (other than perhaps software HDR > SDR conversion which probably sucks due to 4K software decodiing). HDR is more about Linux DRM properties than codecs and decoding. NB: Kodi 20 is using FFMpeg 4.4 with a move to 5.0 in the early stages of investigation; Kodi has been using some deprecated APIs in places and 5.0 removes them completely so it's not a straight bump like 4.3 > 4.4.

The image I shared had similar changes already applied .. I hadn't pushed the patches to repos. Nice to confirm that the Ethernet works with the normal conventions and has good speed (would be nice to solve the IRQ splat though).

I think I understand the LED configuration now. 4K has no LEDs when powered OFF, blue when powered ON, red when panic is flagged. 4K+ has no LEDs when powered OFF, blue remains off when powered ON, red when panic is flagged.

https://discourse.osmc.tv/t/vero-4k-fried-cpu/86267 <= I don't see two LEDs, it looks like single multi-colour one, although it looks more like an IR sensor than anything else. Is the IR sensor only via the extension cable at the back I wonder?

Can you dump the factory device-tree with dtc to pastebin or a file?

Original Vero (S905X) box FCC shows the X96 connection https://fccid.io/2AI57VERO/Exte…ographs-3243007