Kernel 6.13.0-rc1/6.12.3 bcm2712-rpi-5-b.dtb issue #6520
Comments
Dark-Sky
changed the title
|
Thanks for the report. It is working for me with X.Org on 6.130-rc1 with the latest dtb and either the 2711 or 2712 defconfig, which points to there being something different about your configuration. The fbdev failures suggests the kernel driver has failed - what does |
|
Not using fbdev is expected as it should be modesetting (and appears to be doing so and finding a load of modes). |
I had a feeling you would say that. lol This has happened in the past at times and I believe it had to do with my VIZIO tv then. Hooking up another monitor and it worked but I do not have another monitor to test now.
That warning has always been there. I always thought it would try fbdev 1st then move on. I did try using fbdev and fkms and xf86-video-fbdev and I was able to log in and boot to desktop but there was a ton of artifacts and my system would lock up. So fkms was a total disaster. dmesg with new .dtb that boots up to graphics mode and dies: dmesg with older .dtb that boots ok. inxi with older dtb when booted up: |
|
I just built 6.13-rc2 and it has the same issue here. With older .dtb it works ok. I made the pi5/6.13-rc2 kernel available in the forums to test and 2 members reported back saying they ran into the same issue. They use KDE Plasma and SDDM for a display manager on regular computer monitors. Another user with pi4/6.13-rc2 kernel and Plasma and SDDM and Acer Monitor had no issue. |
|
@6by9 I found the problem. I was using the overlays from raspberrpi-firmware git. I did not know evidently something changed in the overlays in kernel's 7.12/6.13 also to go along with their new pi5 dtb's. I used to provide the overlays from the kernel being compiled until the pi5 came out and had to add the second 16k kernel to our images as pacman will not allow the same files in 2 different packages. |
Describe the bug
Will not boot into lightdm display manager to log in with kernel's 6.13.0-rc1/6.12.3 bcm2712-rpi-5-b.dtb installed on my pi5. Boots ok using older v6.12.1 generated bcm2712-rpi-5-b.dtb. I also noticed that having kernel8.img set in config.txt does the same thing trying to boot that image with any other kernel with the pi5 when the 6.13.0-rc1/6.12.3 generated bcm2712-rpi-5-b.dtb is installed.
It appears to me from the logs that the monitor is not detected at all when the boot process tries to go in graphics mode.
Steps to reproduce the behaviour
Compile kernel using "make bcm2712_defconfig" to generate the .config. Install 6.13.0-rc1 or 6.12.3 kernel and it's generated bcm2712-rpi-5-b.dtb and reboot.
Device (s)
Raspberry Pi 5
System
Manjaro XFCE DE
VIZIO TV monitor
[ray@jellyfin ~]$ sudo vcgencmd version
2024/11/12 16:10:44
Copyright (c) 2012 Broadcom
version 4b019946 (release) (embedded)
Linux jellyfin 6.13.0-rc1-v8-16k #1 SMP PREEMPT Fri Dec 6 05:09:49 CST 2024 aarch64 GNU/Linux
Logs
Dec 06 05:36:30 jellyfin systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Dec 06 05:36:30 jellyfin systemd[1]: lightdm.service: Failed with result 'exit-code'.
Dec 06 05:36:30 jellyfin systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Failed with result 'exit-code'.
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Failed with result 'exit-code'.
Dec 06 05:36:31 jellyfin systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Dec 06 05:36:32 jellyfin systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Dec 06 05:36:32 jellyfin systemd[1]: lightdm.service: Failed with result 'exit-code'.
Dec 06 05:36:32 jellyfin systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
I forgot the Xorg-log when it fails with the newer dtb:
[ 17.986]
X.Org X Server 1.21.1.14
X Protocol Version 11, Revision 0
[ 17.986] Current Operating System: Linux jellyfin 6.12.3-1-MANJARO-RPI5 #1 SMP PREEMPT Sat Dec 7 13:46:09 UTC 2024 aarch64
[ 17.986] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95xx.macaddr=D8:3A:DD:BB:67:3A vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 root=PARTUUID=cb41f4dc-03 rw rootwait console=ttyAMA10,115200 console=tty0 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 usbhid.mousepoll=8 audit=0 cgroup_enable=memory psi=1 delayacct lsm=landlock,lockdown,yama,integrity,apparmor,bpf
[ 17.986]
[ 17.986] Current version of pixman: 0.44.2
[ 17.986] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 17.986] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 17.986] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 7 09:02:19 2024
[ 17.986] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 17.986] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 17.986] (==) No Layout section. Using the first Screen section.
[ 17.986] (==) No screen section available. Using defaults.
[ 17.986] () |-->Screen "Default Screen Section" (0)
[ 17.986] () | |-->Monitor ""
[ 17.986] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 17.986] () Allowing byte-swapped clients
[ 17.986] (==) Automatically adding devices
[ 17.986] (==) Automatically enabling devices
[ 17.986] (==) Automatically adding GPU devices
[ 17.986] (==) Automatically binding GPU devices
[ 17.986] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 17.986] (WW)
fonts.dir' not found (or not valid) in "/usr/share/fonts/misc". [ 17.986] Entry deleted from font path. [ 17.986] (Run 'mkfontdir' on "/usr/share/fonts/misc"). [ 17.986] (WW)fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".[ 17.986] Entry deleted from font path.
[ 17.986] (Run 'mkfontdir' on "/usr/share/fonts/TTF").
[ 17.986] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF".
[ 17.986] Entry deleted from font path.
[ 17.986] (Run 'mkfontdir' on "/usr/share/fonts/OTF").
[ 17.986] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[ 17.986] Entry deleted from font path.
[ 17.986] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[ 17.986] Entry deleted from font path.
[ 17.986] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[ 17.986] Entry deleted from font path.
[ 17.986] (==) FontPath set to:
[ 17.986] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 17.986] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 17.986] (II) Module ABI versions:
[ 17.986] X.Org ANSI C Emulation: 0.4
[ 17.986] X.Org Video Driver: 25.2
[ 17.986] X.Org XInput driver : 24.4
[ 17.986] X.Org Server Extension : 10.0
[ 17.987] (++) using VT number 7
[ 17.987] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 17.987] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 17.987] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[ 17.987] (II) no primary bus or device found
[ 17.987] falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
[ 17.987] (II) LoadModule: "glx"
[ 17.987] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 17.989] (II) Module glx: vendor="X.Org Foundation"
[ 17.989] compiled for 1.21.1.14, module version = 1.0.0
[ 17.989] ABI class: X.Org Server Extension, version 10.0
[ 17.989] (==) Matched modesetting as autoconfigured driver 0
[ 17.989] (==) Matched fbdev as autoconfigured driver 1
[ 17.989] (==) Assigned the driver to the xf86ConfigLayout
[ 17.989] (II) LoadModule: "modesetting"
[ 17.989] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 18.012] (II) Module modesetting: vendor="X.Org Foundation"
[ 18.012] compiled for 1.21.1.14, module version = 1.21.1
[ 18.012] Module class: X.Org Video Driver
[ 18.012] ABI class: X.Org Video Driver, version 25.2
[ 18.012] (II) LoadModule: "fbdev"
[ 18.012] (WW) Warning, couldn't open module fbdev
[ 18.012] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 18.012] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 18.012] (WW) Falling back to old probe method for modesetting
[ 18.012] (WW) Falling back to old probe method for modesetting
[ 18.012] (EE) No devices detected.
[ 18.012] (EE)
Fatal server error:
[ 18.012] (EE) no screens found(EE)
[ 18.012] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 18.012] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 18.012] (EE)
[ 18.013] (EE) Server terminated with error (1). Closing log file.
Additional context
I have only tested with the pi5 device. Do not know if the same issue exists on the other pi devices and their .dtb's with the latest kernels or not. All of the latest firmware is installed. I also tried setting the edid.dat in cmdline.txt with no luck.
I gave the xorg log above when it fails with new .dtb. Here is the xorg log when the older .dtb is used that has all working right:
The text was updated successfully, but these errors were encountered: