Posts by chewitt

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

https://chewitt.libreelec.tv/testing/LibreE…arm-10.85.0.tar <= I set the p230 style external PHY setup for Ethernet and changed the LED config around. I'd like to see what this looks like if possible.

CONFIG_EXTCON=y

CONFIG_EXTCON_AXP288=m

From 30 seconds of "git grep" .. ^ You need a custom image with those options added to the kernel build config.

I'd be interested in what dmesg shows with an update to https://chewitt.libreelec.tv/testing/LibreE…arm-10.85.0.tar and a switch to the dts that I created "meson-gxl-s905d-vero4k-plus.dtb" .. I pushed new images to https://chewitt.libreelec.tv/testing/ - this time they have the dtb files present.

I have debug output for MPEG2 and can replicate "audio, no video" playback easily. In short .. frames go into the decoder and nothing comes out. It will need someone with way more coding knowledge than me to figure out what's up.

I spotted a comment from Sam Nazarco (owner of OSMC) in their forums talked about the 4K+ having Gbit "muxed to the internal PHY" so I'm not sure what's been done inside the box but if you're booting p231 fine that would corroborate the statement. Interesting spot on the OID but not too surprising as Amediatech is one of the main ODM box suppliers (the other large ones being SEI Robotics and Videostrong).

Latest "box" image in https://chewitt.libreelec.tv/testing/ has my attempt at 4K/4K+ device trees, see:

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

The OSMC Vero 4K and 4K+ devices are based on the Amlogic P231 S905D reference design. The Vero 4K has 10/100 Ethernet and a prominent &quot;+&quot; power…

github.com

I've asked Sam to share the original dts files to remove guesswork. I've seen comments that suggest there's a red power LED somewhere on both boxes and the reset button is at the end of the CVBS/AV jack according to the board pics lodged with the FCC.

MPEG2 needs driver fixes. It's been flagged. It will take time.

You will probably need to force recovery boot via whatever method works on your box, e.g. holding in a reset button when power is applied to the box and releasing after a few seconds (so-called toothpick method) etc.

https://www.raspberrypi.com/software/ <= Click here. Download the imager app for your OS. Create an SD card - LibreELEC is in the list of OS that you can choose/install to the SD card.

Your box has banned add-ons intalled. You are welcome to remove them from the box - if you want further support in this forum.

Random Q .. are you sure that you have the Vero 4k plus? .. You've used the p231 dts as the base and this uses internal PHY (should be 10/100) where the plus (according to the website) has Gigabit which would be using the external PHY and p230 would be the right dts base. I think you have the 4k (non-plus) model. I'm no expert on OSMC hardware though

Thanks. Can I ask you to drop the sd-uhs* caps from the node and repeat the 'after' test. Although things are 'detected' I'm not sure it makes any difference and it's always best to submit minimal changes upstream.