Posts by chewitt

Nobody on staff has Jetson boards so it would need to be a community created effort.

Quote from adm

Any idea ? wrong dtb ?

From the level of useful info in your bug report, reading tea-leaves will be more pruductive at finding the problem (at least you get a cup of tea).

Quote from g7ruh

there are at least 2 users still out here . Keep up the hard work on Slice, please.

There are 79 of you in total (declining slowly with time). Currently there are no plans to release further Slice-specific images, e.g. LE10. I'm not entirely sure what the status of things is upstream and how realistic it is to configure Slice support using the RPi images. I think we hand everything back to the community to figure out.

LE 9.2.6 is/was a general release for all hardware inluding Slice boxes.

erbas thanks for confirming. The change CE made works but we create /storage/.cache/ssh via tmpfiles.d so IMHO the correct fix (which is in the image you tested) is simply adding a depedency on systemd-tmpfiles-setup.service (or perhaps network.target) to ensure it completes before the SSH daemon starts.

Perhaps install the "locale" add-on and change it to UTF8 or en_US (something other than POSIX)?

erbas I've never seen this problem in all my testing, but see if the images in Index of /testing/9.80/ change anything?

Quote from Wulfeken

I have no sound coming from my Pi to TV via HDMI... I have gone over the sound menu in detail.. made sure that pass through is checked... what am I missing, can someone please HELP???

HDMI is connected to the port nearest the power connector?

It looks like that logic has been ported to mainline u-boot: include/configs/mx6cuboxi.h · master · U-Boot / U-Boot · GitLab and there are similar configs for udoo and wandboard. It's not clear to me what changes might be needed for filenames and/or other files in the boot partition, I'm not sure extlinux is the best option here. Anyway.. it's late o'clock here so something to look into over the weekend.

HDR is not supported on RPi4 in any releases yet. Still being worked on. Still some way to go.

Ahh, indeed, that woud explain!

vpeter so I can see that the dual/quad versions all share the same u-boot defconfig, which supports the idea of consolidating images to three: cubox, udoo, wandboard. I can also see that wandboard has more dtb's than we currently create images for (revb1, revd1 were added upstream). It's simple to repackage and accomodate that, see Commits · chewitt/LibreELEC.tv · GitHub and I think the simplicity of image naming trumps adding more dedicated images (and I'm doing the same thing with Odroid N2/N2+ in the next Amlogic bump). I'm interested to know what happens when users with a quad board don't change the dtb name and boot using the dual dtb? (or should the defaults be switched to quad?). Also, looking at the device-tree files in the kernel, didn't we (you) also used to ship an image for the Hummingboard devices?

It might be missing the firmware, in which case you'll need to share "dmesg | paste" output so we can see the error message that tells us which file can't be found (so we can pick/add it).

I think the current plan is to use GLES shaders to handle the conversion. The shaders are already well known. The plumbing to use them with the all-new RPi video pipeline is not, we (mostly the Pi Foundation folks) will need to invent and implement more new stuff. HDR is also mind-bendingly not simple so I wouldn't expect this to happen too quickly.

The 2GB or 4GB versions are fine, there's no need for 8GB unless you plan to do other things with the board.

The beelink-s922x image on that page is designed to overwrite the internal emmc storage. It's not something you can use to boot the factory box from as vendor u-boot doesn't understand extlinux boot configurations. You'd need to boot from the box image first, then use 'emmctool' to overwrite emmc with the beelink image, but due to an issue which I haven't pinned down yet, when you attempt high I/O load when booted from vendor u-boot the box will deadlock and probably leaves the device in non-bootable state. It's possible to recover the box with Amlogic burning tool and a factory ROM image, but not everyone finds that simple. So you're welcome to experiment with those images but I do not support them. If you mess up your box, it's not my problem to help you sort it out.

I can see that you have GitHub - KODeKarnage/script.lazytv: XBMC Addon - LazyTV installed which wants to "recommend" things to you, although it sounds like it works more with the local library than add-ons. You look too be repeatedly playing ЧЕСНИЙ ЗЛОДІЙ. Офіційний трейлер (український) HD - YouTube (Ukrainian not Russian). Perhaps move /storage/.kodi to /storage/.kodi-old and start over, move DBs and add-on settings back bit at a time until you find the problem?

btw, the old OpenELEC repository.unofficial.addon.pro is still installed, which is unlikely to be useful these days.

In current nightlies (LE10) the HBR audio will work, but there is no 4K or HDR support. In current stable (LE9.2) 4K works, but there is no HDR and no HBR audio. Current develpment priority is getting the H264 hardware decder working with GBM/V4L2, then 4K, then 10-bit, then HDR .. so lots of work to be done.