Posts by chewitt

Did you run "PROJECT=Generic ARCH=i386 make image" ??? .. it should create .tar and .img.gz files. The .system file is "SYSTEM" not a full image (hence it does not boot/work).

Even if you solve .mxf format detection in Kodi, an RPi4 cannot hardware decode 4K H264 media (the H264 IP block is the same as an RPi3Bs and it supports only up to 1080p) and it will not have the CPU grunt to handle software decoding gracefully. Your best option is to use an app like Handbrake to re-encode the files to 4K HEVC (8-bit) which is supported. If you can change the camera to use HEVC instead of H264 you can skip this step in the future. NB: OMXplayer exists in LE 9.2 images as an alternative to MMAL decoding for older RPi devies. OMXplayer support was removed from Kodi 19 so it is not present in LE10 images. It is not the solution, because no RPi device supports 4K H264 hardware decode.

See odroid-c2 diffs · GitHub for a comparative diff of the working (left) and current (right) dtb files. This flags only two changes in the dtb, neither of which has any connection to emmc.

Change #1: arm64: dts: amlogic: misc DT schema fixups · torvalds/linux@d9421d6 · GitHub

Change #2: arm64: dts: meson: set 128bytes FIFO size on uart A · torvalds/linux@a270a2b · GitHub

The only other thing which touched mmc (on GX devices) semi-recently is arm64: dts: amlogic: Assign a fixed index to mmc devices · torvalds/linux@ab547c4 · GitHub but we mount the first partition using disk labels not /dev/mmcblkX devices and it's present in both dtb's so it's not relevant.

So

1. USB is an on/off problem with C2 in the upstream kernel so it's possible OTG isn't working this kernel cycle. I'd expect to find issues with devices being hotplugged.

2. I don't see the USB ID's in the kernel driver, which is a simple patch you can test next time I build/push an image update.

3. No HDMI device is deliberate since we don't support IEC958 modes in dw-hdmi yet (no pass-through) but the "Analogue" output works with HDMI fine (output is multi-channel PCM). I'm still tracking down an issue where 48KHz media doesn't output unless Kodi audio configuration is forced to 44.1KHz (used fixed mode). I've seen this on WP2 (also a GXBB device) but not GXL/GXM devices. I've no idea what the issue is.

SMB or NFS would be more efficient (no TLS encryption overhead)

Is the remote the original white, silver, or newer black remote? Can you see raw commands via ir-keytable when Kodi is stopped?

See https://wiki.libreelec.tv/configuration/ir-remotes

I've seen too many weird issue reports from users with Argon cases, so see what happens without the case and a normal RPi4 PSU. I use a lircc receiver on all kinds of hardware and have never seen that behaviour.

rm /storage/.cach/services/samba.disabled
rm /storage/.config/samba.conf
systemctl start samba-config.service

^ that should get the service running from the CLI. You only need to create /storage/.config/samba.conf if you want to modify how the service runs, it has no effect on whether the service does/doesn't run.

OE has very (very) distant origins in the OpenBricks buildsystem but it's effectively a custom buildsystem. It's using PKG_DEPENDS to create the build sequence, but there's isn't anything that allows you to visualise what that sequence is (and these days LE does parallel build which would make that much more variable; OE is at least sequential not parallel so the sequence will be consistent. If you want to trace package dependencies "git grep" on the package names is about as good as it gets.

Quote from semen.by

I installed this build on KIII pro and in general it works as expected. But in tvheadend is no any DBV devices

If they are USB devices and they are supported in the vanilla upstream kernel I can help. If you're trying to use the tuners in the box, there is no support for them in the mainline kernel (we have out-of-tree patches for tuners and demod, but there is no V4L2 demux). People keep expressing interest in helping to work on the drivers, but then they realise it's a bigger task than they expected and they fade away.

If you're comfortable at the command-line and know what Kodi files are important and where they live it's pretty simple to do a manual update from 9.2.x to 10.0.x .. the only problem thing is add-ons (so move them out of the way before updating). I'd guesstimate that 85% of our userbase is not comfortable, and staff don't want to be drowned in "but my add-ons broke" support work, which is why the clean-install advice is pushed.

popcornmix ^

It's a known issue but nobody submitted a fix yet. Use "bluetoothctl" to make the pairing .. this works from the CLI.

Crazycat and similar are a pain in the arse once you start bumping kernels. Just disable them.

See Generic: disable dvb add-ons by CvH · Pull Request #5600 · LibreELEC/LibreELEC.tv · GitHub

Quote from DaBuddha

I've tried most everything to get to the grub prompt, no luck.

What am I missing?

You're missing grub, since we don't use it. Put the same thing on the APPEND line in syslinux.conf in the first partition on the USB.

Get a Flirc Kodi case .. temps will be in the 50-55ºC range in normal LE use but this is passive cooling (no fans) and it looks fab. RPi4 was designed to run happily at much higher thermal temps than most users are mentally comfortable with. You need to have some cooling but active cooling cases with noisy fans are not required.

It's hard to understand what you're trying to do now

It's just a hunch .. I'm fairly clueless about compiling stuff