Posts by chewitt

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.

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.

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.

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?

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.

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)

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.

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.

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.

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.

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?

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.

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.

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

Our general policy is not to touch the content of release branches outside of the Kodi version (usually the focus of the bump) unless there are known bugs or security issues solved. LE13 nightlies are stable if you really need the newer version.

BIOS update? .. See if you can boot an Ubuntu live image off USB reliably. If yes, switch the bootloader on the boot device from syslinux to grub2 (as used by Ubuntu). If there's no difference and no BIOS updates available, there's not much we can do as we didn't boot and run yet.

It's not particularly enlightening for me, but it might be more meaningful to a mesa developer

I'm currently building a GBM image based on the LE12 codebase. K22 contains some reworking to GLES shaders. So I'd like to run a test with K21 as it predates those changes and we can eliminate them from suspicion.