Posts by chewitt

**chewitt** · Game Stick 4K Lite version 6.0 **chewitt** January 24, 2025 at 6:57 AM

It also has an unsupported RK3032 chip.

**chewitt**

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.

**chewitt** · nVidia Nouveau Driver **chewitt** January 24, 2025 at 5:55 AM

In GBM images we can find the plane details, e.g. this is from an Amlogic S905 board:

Code

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 DRM

The GUI is using plane 37 so we can check the plane capabilities using modetest output:

Code

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: 1

Display More

Here you can see that the plane supports LINEAR formats.

From the 'Nouveau' GBM kodi.log:

Code

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 DRM

Plane 38 has the following capabilities:

Code

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: 1

Folks 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:

Diff

--- 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)));
           }

Display More

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.

**chewitt** · nVidia Nouveau Driver **chewitt** January 23, 2025 at 4:42 PM

Johpin can you run "modetest | paste" on the 'Nouveau' (GBM) image and share the URL please.

**chewitt** · nVidia Nouveau Driver **chewitt** January 23, 2025 at 4:26 PM

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.

**chewitt**

Code

RPi5:~ # ls -l /flash/overlays/*pwm*
-rwxr-xr-x    1 root     root          1825 Jan 17 14:26 /flash/overlays/i2c-pwm-pca9685a.dtbo
-rwxr-xr-x    1 root     root          1059 Jan 17 14:26 /flash/overlays/pwm-2chan.dtbo
-rwxr-xr-x    1 root     root          3558 Jan 17 14:26 /flash/overlays/pwm-gpio-fan.dtbo
-rwxr-xr-x    1 root     root          1006 Jan 17 14:26 /flash/overlays/pwm-gpio.dtbo
-rwxr-xr-x    1 root     root          1035 Jan 17 14:26 /flash/overlays/pwm-ir-tx.dtbo
-rwxr-xr-x    1 root     root          1010 Jan 17 14:26 /flash/overlays/pwm-pio.dtbo
-rwxr-xr-x    1 root     root           948 Jan 17 14:26 /flash/overlays/pwm.dtbo
-rwxr-xr-x    1 root     root          1493 Jan 17 14:26 /flash/overlays/pwm1.dtbo

From a current LE13 nightly with RPi Linux 6.12.y kernel ^ - I don't have an LE12 device but we bumped the kernel for the 12.0.2 release (shipped last night) so if RPi devs backported the change to their Linux 6.6.y kernel it should be included there too.

**chewitt**

Some things to experiment with:

a) Remove the SD card and see if the RPi firmware screen shows?

b) Use a different mini-HDMI to HDMI cable; do not use adapter + cables

c) Use a different HDMI port on the TV

d) Use video=HDMI-A-1:1920x1080M@60 not video=HDMI-A-1:1920x1080@60D

e) Update the firmware on the board using RPi imager

f) Use LE 12.0.2 which was released last night, or an LE 13 nightly

From experience I'd point fingers at cables or ports being the issue.

**chewitt**

You boot from Ubuntu and install grub to the boot device, then create a grub-format bootloader config file. Start with seeing if the device will reliably boot Ubuntu on the hardware?

**chewitt**

Code

info <general>: CDRMUtils::FindConnector - using connector: HDMI-A-2

^ this shows you are using the HDMI connector furthest from the power connector. Move HDMI to the port nearest the power port and CEC will work again. Support for CEC on both connectors has been intentionally removed due to problems seen when multiple HDMI connections are active. It is now only supported on HDMI-A-1.

**chewitt** · nVidia Nouveau Driver **chewitt** January 23, 2025 at 1:45 PM

mglae See the IRC chat that starts here: https://oftc.irclog.whitequark.org/dri-devel/2025-01-23#33941062

This change causes the dri2 error under X11: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29969 - so I've added support for legacy-x11=dri2 in mesa package.mk

Johpin I've pushed an updated pair of images to https://chewitt.libreelec.tv/testing/ and I have a hunch "Nouveau-Legacy" with DRI2 support should now work? - If it does, please test whether this /storage/.config/xorg.conf also works? (probably not)

Code

Section "Device"
    Identifier "Nouveau"
    Driver "nouveau"
    Option "DRI" "3"
EndSection

The main mission is still to get GBM working so nouveau can be added to the normal Generic image. I'll need to chat with Kodi devs about that though, I'm not really understanding the DRM format comments in the IRC chat.

**chewitt** · nVidia Nouveau Driver **chewitt** January 23, 2025 at 9:37 AM

I don't see any difference in the log, which is positive as we can eliminate Kodi changes from suspicion and focus on interaction between libgallium and the kernel driver. I think it's time to push discussion to the mesa mailing list.

NB: Rolling back the mesa version back that far will require more than a simple version/sha256 change in package.mk as the build options have changed format and things have been added/removed over time (look at the git history for mesa package.mk). I did look at reverting, but in the end we need to fix the current version so better to pursue that for now.

**chewitt** · LibreELEC (Omega) 12.0.2 **chewitt** January 23, 2025 at 7:56 AM

dvelev I don't see [FAILED] anywhere in that log, and the kodi.log shows Kodi is up/running. All I see is a normal system and normal startup

EDIT: spotted by CvH : usb 3-1: device descriptor read/64, error -71 is at the logs, so something attatched to the usb port isn't working.

**chewitt** · [x86-64] Can't Install LibreELEC **chewitt** January 23, 2025 at 7:06 AM

**chewitt** · LibreELEC (Omega) 12.0.2 **chewitt** January 23, 2025 at 7:06 AM

Quote from dvelev

[FAILED] Failed to start nmbd.service.
[FAILED] Failed to start smbd.service.
[FAILED] Failed to start kodi.service.

Run "pastekodi" and share the log. Eyeballs on logs are better than ESP when it comes to guessing the issue.

**chewitt** · LibreELEC (Omega) 12.0.2 **chewitt** January 23, 2025 at 7:04 AM

Quote from DavidCNZ

I forgot to add there is a folder named 15699.72.0 not 15699.72.0.0

Rename it to 15699.72.0.0 and see what happens?

**chewitt** · [RPi4] Video Cuts Out Randomly **chewitt** January 23, 2025 at 4:50 AM

Quote from npolite

I may get a mini-HDMI cable to HDMI and see if that works better.

Proper end-to-end cables are always better than cheap adapter + normal HDMI cable combinations; based on user reports here.

**chewitt** · nVidia Nouveau Driver **chewitt** January 23, 2025 at 1:30 AM

I uploaded some LE 12.0.2 images to https://chewitt.libreelec.tv/testing/ .. please run the "Nouveau" image with Kodi in debug mode (via advancedsettings.xml) and with the kodi.conf changes, and and see if it works or not. If not (which is the expectation) and share the crash log and system log (if not included in the crash log). Thanks.

**chewitt** · [RPi4] AV1 Capabilities **chewitt** January 23, 2025 at 1:25 AM

Answered in the other thread. In short, no libdav1d updates to LE12, use LE13 nightlies if you need to.

Posts by chewitt

Game Stick 4K Lite version 6.0

[RPi5] Refresh Rate Problem on Optoma CinemaX D2 Projector

nVidia Nouveau Driver

nVidia Nouveau Driver

nVidia Nouveau Driver

PWM Fan Control for 3 pin / wire GPIO fans for Raspberry Pi

[RPi4] Blank Screen on LG 32UN880P Monitor

[x86-64] LibreELEC Generic-legacy Not Installing

[RPi5] CEC no longer working on LibreELEC 12.0.2

nVidia Nouveau Driver

nVidia Nouveau Driver

LibreELEC (Omega) 12.0.2

[x86-64] Can't Install LibreELEC

LibreELEC (Omega) 12.0.2

LibreELEC (Omega) 12.0.2

[RPi4] Video Cuts Out Randomly

nVidia Nouveau Driver

[RPi4] AV1 Capabilities