echo 'modetest -M vc4 -w "32:Broadcast RGB:1"' > /storage/.config/autostart.shI'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 kodiFiles 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.
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
rebootAny difference?
echo 'module nouveau +p' > /sys/kernel/debug/dynamic_debug/control
dmesg -n 8
systemctl restart kodiOn 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 HzThis ^ 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?
It also has an unsupported RK3032 chip.
If you are connecting the project through an AVR, remove it from the HDMI chain and connect direct to confirm things working as expected (then blame the AVR). If not doing that, put Kodi into debug mode, reboot, demonstrate the issue with 23.976 media, then run "pastekodi" and share the URL so we can see the DRM modes available and what Kodi selects.
In GBM images we can find the plane details, e.g. this is from an Amlogic S905 board:
2025-01-20 19:16:58.075 T:734 info <general>: CDRMUtils::FindConnector - using connector: HDMI-A-1
2025-01-20 19:16:58.075 T:734 info <general>: CDRMUtils::FindEncoder - using encoder: 34
2025-01-20 19:16:58.075 T:734 debug <general>: CDRMUtils::FindCrtc - original crtc mode: 3840x2160 @ 60 Hz
2025-01-20 19:16:58.075 T:734 info <general>: CDRMUtils::FindPlanes - using crtc: 43
2025-01-20 19:16:58.075 T:734 debug <general>: CDRMUtils::FindPlanes - using video plane 40
2025-01-20 19:16:58.075 T:734 debug <general>: CDRMUtils::FindPlanes - using gui plane 37
2025-01-20 19:16:58.076 T:734 debug <general>: CDRMAtomic::InitDrm - initialized atomic DRMThe GUI is using plane 37 so we can check the plane capabilities using modetest output:
Planes:
id crtc fb CRTC x,y x,y gamma size possible crtcs
37 43 49 0,0 0,0 0 0x000000ff
formats: AR24 AB24 XR24 XB24 RG24 RG16
props:
8 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 1
30 IN_FORMATS:
flags: immutable blob
blobs:
value:
01000000000000000600000018000000
01000000300000004152323441423234
58523234584232345247323452473136
3f000000000000000000000000000000
0000000000000000
in_formats blob decoded:
AR24: LINEAR(0x0)
AB24: LINEAR(0x0)
XR24: LINEAR(0x0)
XB24: LINEAR(0x0)
RG24: LINEAR(0x0)
RG16: LINEAR(0x0)
39 zpos:
flags: immutable range
values: 1 1
value: 1Here you can see that the plane supports LINEAR formats.
From the 'Nouveau' GBM kodi.log:
2025-01-23 16:04:45.957 T:917 info <general>: CDRMUtils::FindConnector - using connector: DVI-D-1
2025-01-23 16:04:45.957 T:917 info <general>: CDRMUtils::FindEncoder - using encoder: 45
2025-01-23 16:04:45.957 T:917 debug <general>: CDRMUtils::FindCrtc - original crtc mode: 1920x1080 @ 60 Hz
2025-01-23 16:04:45.957 T:917 info <general>: CDRMUtils::FindPlanes - using crtc: 39
2025-01-23 16:04:45.957 T:917 debug <general>: CDRMUtils::FindPlanes - using gui plane 38
2025-01-23 16:04:45.957 T:917 debug <general>: CDRMLegacy::InitDrm - initialized legacy DRMPlane 38 has the following capabilities:
Planes:
id crtc fb CRTC x,y x,y gamma size possible crtcs
38 39 61 0,0 0,0 0 0x00000001
formats: XR24 RG16 XR15
props:
8 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 1Folks on IRC said "Seems like the GPU doesn't like the pushbuf due to an invalid render target format. I would guess the framebuffer isn't properly set at the time of the flush and the userspace driver just flushes the current (invalid) state, which has the GPU grumpy." and also "you can't use a linear frontbuffer with depth" .. not clear to me if that refers to zpos or alpha-channel.
I've opened https://github.com/xbmc/xbmc/issues/26345 to discuss with Kodi devs.
In the background I also created this:
--- a/xbmc/windowing/gbm/drm/DRMUtils.cpp
+++ b/xbmc/windowing/gbm/drm/DRMUtils.cpp
@@ -191,7 +191,7 @@ bool CDRMUtils::FindPlanes()
auto videoPlane = std::find_if(m_planes.begin(), m_planes.end(), [&i](auto& plane) {
if (plane->GetPossibleCrtcs() & (1 << i))
{
- return plane->SupportsFormat(DRM_FORMAT_NV12);
+ return (plane->SupportsFormat(DRM_FORMAT_NV12) || plane->SupportsFormat(DRM_FORMAT_XRGB8888));
}
return false;
});
@@ -206,7 +206,8 @@ bool CDRMUtils::FindPlanes()
if (plane->GetPossibleCrtcs() & (1 << i))
{
return (plane->GetPlaneId() != videoPlaneId &&
- (videoPlaneId == 0 || plane->SupportsFormat(DRM_FORMAT_ARGB8888)) &&
+ (videoPlaneId == 0 || plane->SupportsFormat(DRM_FORMAT_ARGB8888) ||
+ plane->SupportsFormat(DRM_FORMAT_XRGB8888)) &&
(plane->SupportsFormat(DRM_FORMAT_XRGB2101010) ||
plane->SupportsFormat(DRM_FORMAT_XRGB8888)));
}This is partly inspired by a patch previously used with Odroid XU4 boards that don't support YUV formats and needed some extra help to use XRGB8888 output, but I'm honestly guessing in the wind. I'm not sure there's a real issue with selecting planes (as we select a plane) but I'm interested to see if anything changes - so please update to the latest images pushed to my test share and do the usual log sharing again.
Johpin can you run "modetest | paste" on the 'Nouveau' (GBM) image and share the URL please.
Xorg now looks generally happy (some xorg.conf tweaking can clean some minor things up) but it now clearly shows an identical fault to the GBM image, so the IRC comments about "using linear scanout with depth" apply and we need to tweak something on the Kodi side to resolve this.