Posts by chewitt

I've no idea what patches and changes _emanuel_ adds to his images (he is not pushlishing the sources to his GitHub account) but I doubt he deviates far from AMGLX.

It sounds like it falls back to the 5.1 'core' audio. Have you checked cables? - it requires high bandwidth and if the HDMI connection can't handle that it will cause fallback. Please also enable debug logging in Kodi, demonstrate the issue by playing something, and then run "pastekodi" over SSH and share the URL generated.

Some comments:

• Can't explain 10.0.0.0 without knowledge of the correct DHCP scope, or there's a rogue DHCP server in the network
• RPi WiFi is never brilliant so you probably need to move the device closer to the router
• The invalid-key error is a known but unresolved connection issue - signal strength is a factor (as above)
• The usual reason SSH password login fails is people enabling the disable password feature?
• Once you get in, there is intentionally no sudo or apt package manager (we are not Debian based)

In general WiFi on RPi boards is a bit rubbish, and while "invalid-key" is a genuine bug that needs to be resolved, it's influenced by signal strength. If running an Ethernet cable is truly impossible you may need to use an external USB WiFi dongle with a proper antenna that provides better range than the onboard card.

Quote from elmangomez

Is there an LE Matrix version that has a supporting kernel? Anything I can do to make it work on Matrix?

No, but you can self-build an image with a newer kernel and related kernel and intel firmware packages. There are instructions for self-building in the wiki, although it won't give you explicit directions on how to go around bumping packages. There's lots of prior art for that in the buildysystem though, so a little initiative and curiosity should get you over the line.

Plan B .. time to fathom the overly modified skin.

Use the first command and the change will be applied on each boot. No idea what the difference is, there's not much that changed in the release aside from Kodi and kernel bumps. I'm also using an RPi5 and haven't noticed anything.

No problems, the RAM size is irrelevant to Kodi.

echo 'modetest -M vc4 -w "32:Broadcast RGB:1"' > /storage/.config/autostart.sh

I've not commented my crib notes, but I think that's the command. If you want to test ad-hoc:

systemctl stop kodi
modetest -M vc4 -w 32:"Broadcast RGB":1
systemctl start kodi

Files are in /storage/.kodi/userdata .. If you are simply moving to a new SD card on the same hardware, take a backup in the LE settings add-on, clean install, then restore the backup.

If you want a dedicated vendor kernel image with all features working .. LE 9.0.2

If you want to experiment with upstream kernels which are less featured but generally usable as long as your media needs and expectations are not exotic, use the AMLGX image. You can manually migrate data like Kodi DB files between installs, but you cannot update in-place between LE 9.0.2 and LE 12 (or LE13 nightlies) as the boot files, kernel, kodi (everything basically) are different.

Read https://wiki.libreelec.tv/hardware/amlogic for more info and instructions.

EDIT: Current images in my test share have the previous patch reverted and something added that forces EGL_DEPTH_SIZE to zero (EGL_STENCIL_SIZE is already zero). As always, no guarantees my guesswork is correct. Please run tests again.

Just swap the SD card and you boot a whole new OS (with retroarch). Cores are emulators; there are lots of them so you only need to download and install the ones you need and/or are appropriate for your hardware.

Quote from 4k3or3et

When i set 23.98 on my Windows PC it show 23Hz

The firmware in the projector has some rounding logic for display then, and when Kodi sends 23.976 it's showing you 24Hz. The Windows PC may not be using 100% the same modeline as Linux (different code, different calculations) and this could explain why one OS results in the firmware rounding down to 23 and the other results in rounding up to 24. I was going to make a comment on this being possible in the previous post, but chose to wait and let you explain first.

The real-world test is: do you see periodic sync glitches during playback, or is playback smooth?. If you don't (and I suspect you don't with well prepared media) there's no issue.

<advancedsettings version="1.0">
  <!-- enable debug logging -->
  <loglevel hide="false">1</loglevel>
</advancedsettings>

That ^ works for me.

I can see from the Kodi crashlog that my patch changes the issue and we're not generating the nouveau error. I've pushed updated images which revert that to restore the original crash. NB: I'm only interested in the "pastekodi" output as this contains both Kodi and system log in one paste.

Have you swapped the WiFi dongle from a USB 2.0 port to a USB 3.0 port? - If yes, move it back.

If no, see if this makes a difference (unlikely):

echo "options mt76_usb disable_usb_sg=1" > /storage/.config/modprobe.d/mt76x2u.conf
reboot

Any difference?

echo 'module nouveau +p' > /sys/kernel/debug/dynamic_debug/control
dmesg -n 8
systemctl restart kodi

On the GBM image can you do that ^ .. it should put nouveau into debug mode and that might generate some log info on interaction with mesa and upper layers of the graphics stack.

NB: There's no need to unpack .tar files, just put them in /storage/.update and reboot. Nothing in /storage will be touched by an update unless a Kodi version bump happens (and then only minor changes to /storage/.kodi).

The GBM log doesn't contain as much debug output from nouveau, but that could be due to kodi.conf not being present? Otherwise it looks no different, which was largely expected.

Have you tried the Geforce 9400GT card recently? - I rather suspect Kodi logic for outscan format is to blame, but I'm also wondering if age of hardware (and thus features exposed to nouveau) are related. It would be interesting to see if the 'modetest' output from the Geforce 9400GT card is any different from 6100.

Settings > Services > Control > Application Control > Allow remote control from applications on other systems > enable

Have you done that ^ ?

2025-01-24 08:35:39.301 T:986      info <general>: Opening stream: 0 source: 256
2025-01-24 08:35:39.301 T:986      info <general>: [WHITELIST] Searching the whitelist for: width: 3840, height: 2160, fps: 23.976, 3D: false
2025-01-24 08:35:39.301 T:986     debug <general>: [WHITELIST] Searching for an exact resolution with an exact refresh rate
2025-01-24 08:35:39.301 T:986     debug <general>: [WHITELIST] Matched an exact resolution with an exact refresh rate 3840x2160 @ 23.976025 Hz (32)
2025-01-24 08:35:39.301 T:986      info <general>: Display resolution ADJUST : 3840x2160 @ 23.976025 Hz (32) (weight: 0.000)

This ^ shows Kodi correctly detecting and selecting the [email protected] mode.

2025-01-24 08:35:39.659 T:899     debug <general>: CDRMUtils::SetMode - found crtc mode: 3840x2160 @ 24 Hz

This ^ means some code is rounding the value to 24Hz. I'm not sure if it's Kodi or the underlying kernel DRM layer, but I see the same on an LG TV and I have no playback issues, so this can be ignored.

I can see from the log that you didn't whitelist any 1080p modes. That's probably a bad idea, but not related to this issue. Have a read of the wiki acticle here for recommendations: https://wiki.libreelec.tv/configuration/4k-hdr

If seeing bad values in the log wasn't the issue? - how do you determine the projector is at 24Hz?