Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8082

Troubleshooting • vc4 doesn't load

$
0
0
What dmesg says

Code:

xlebnick@pi:~ $ dmesg | egrep -i 'vc4|v3d|hvs|drm' | tail -n 200[    0.000000] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0  numa=fake=8 system_heap.max_order=0 smsc95xx.macaddr=D8:3A:DD:DC:FF:48 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=tty1 root=PARTUUID=a1f070fb-02 rootfstype=ext4 fsck.repair=yes rootwait apparmor=1 security=apparmor systemd.unified_cgroup_hierarchy=false cma=512MB simpledrm.modeset=0[    1.277256] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...[    1.331495] systemd[1]: modprobe@drm.service: Deactivated successfully.[    1.332168] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.[    2.801805] vc4_hvs 107c580000.hvs: bcm2712_iommu_of_xlate: MMU 1000005200.iommu[    2.803537] vc4_hvs 107c580000.hvs: bcm2712_iommu_probe_device: MMU 1000005200.iommu[    2.805761] vc4_hvs 107c580000.hvs: bcm2712_iommu_device_group: MMU 1000005200.iommu[    2.810224] vc4_hvs 107c580000.hvs: Adding to iommu group 1[    2.810853] vc4_hvs 107c580000.hvs: bcm2712_iommu_attach_dev: MMU 1000005200.iommu[    2.832408] vc4-drm axi:gpu: bcm2712_iommu_of_xlate: MMU 1000005200.iommu[    2.836415] vc4-drm axi:gpu: bcm2712_iommu_probe_device: MMU 1000005200.iommu[    2.839601] vc4-drm axi:gpu: bcm2712_iommu_device_group: MMU 1000005200.iommu[    2.840111] vc4-drm axi:gpu: Adding to iommu group 1[    2.840492] vc4-drm axi:gpu: bcm2712_iommu_attach_dev: MMU 1000005200.iommu[    2.843199] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    2.843236] vc4_hvs 107c580000.hvs: Couldn't get core clock[    2.844897] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    2.844928] vc4_hvs 107c580000.hvs: Couldn't get core clock[    3.003780] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    3.003849] vc4_hvs 107c580000.hvs: Couldn't get core clock[    4.638237] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    4.638291] vc4_hvs 107c580000.hvs: Couldn't get core clock[    4.777799] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    4.777843] vc4_hvs 107c580000.hvs: Couldn't get core clock[    4.782961] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[    4.783010] vc4_hvs 107c580000.hvs: Couldn't get core clock[   14.818967] vc4-drm axi:gpu: [drm] Couldn't stop firmware display driver: -22[   14.818992] vc4_hvs 107c580000.hvs: Couldn't get core clock[   14.819025] platform 1002000000.v3d: deferred probe pending: v3d: Failed to get V3D clock

My config:

Code:

xlebnick@pi:~ $ cat /boot/firmware/config.txt# Read by the firmware very early — keep only early, global toggles heredisable_fw_kms_setup=1display_auto_detect=0# Use the Pi 5 device tree explicitlydevice_tree=bcm2712-rpi-5-b.dtb[all]include usercfg.txtxlebnick@pi:~ $ cat /boot/firmware/usercfg.txtdtoverlay=vc4-kms-v3d-pi5disable_fw_kms_setup=1max_framebuffers=2display_auto_detect=0camera_auto_detect=0hdmi_force_hotplug:0=1hdmi_group=1hdmi_mode=16xlebnick@pi:~ $ ls /boot/firmware/overlays/vc4-kms*/boot/firmware/overlays/vc4-kms-dpi-generic.dtbo        /boot/firmware/overlays/vc4-kms-dsi-ili9881-5inch.dtbo       /boot/firmware/overlays/vc4-kms-kippah-7inch.dtbo/boot/firmware/overlays/vc4-kms-dpi-hyperpixel2r.dtbo   /boot/firmware/overlays/vc4-kms-dsi-ili9881-7inch.dtbo       /boot/firmware/overlays/vc4-kms-v3d-pi4.dtbo/boot/firmware/overlays/vc4-kms-dpi-hyperpixel4.dtbo    /boot/firmware/overlays/vc4-kms-dsi-lt070me05000-v2.dtbo     /boot/firmware/overlays/vc4-kms-v3d-pi5.dtbo/boot/firmware/overlays/vc4-kms-dpi-hyperpixel4sq.dtbo  /boot/firmware/overlays/vc4-kms-dsi-lt070me05000.dtbo        /boot/firmware/overlays/vc4-kms-v3d.dtbo/boot/firmware/overlays/vc4-kms-dpi-panel.dtbo          /boot/firmware/overlays/vc4-kms-dsi-waveshare-800x480.dtbo   /boot/firmware/overlays/vc4-kms-vga666.dtbo/boot/firmware/overlays/vc4-kms-dsi-7inch.dtbo          /boot/firmware/overlays/vc4-kms-dsi-waveshare-panel-v2.dtbo/boot/firmware/overlays/vc4-kms-dsi-generic.dtbo        /boot/firmware/overlays/vc4-kms-dsi-waveshare-panel.dtboxlebnick@pi:~ $ ls /boot/firmware/overlays/vc4-kms-v3d*/boot/firmware/overlays/vc4-kms-v3d-pi4.dtbo  /boot/firmware/overlays/vc4-kms-v3d-pi5.dtbo  /boot/firmware/overlays/vc4-kms-v3d.dtboxlebnick@pi:~ $ cat /boot/firmware/cmdline.txtconsole=tty1 root=PARTUUID=a1f070fb-02 rootfstype=ext4 fsck.repair=yes rootwait apparmor=1 security=apparmor systemd.unified_cgroup_hierarchy=false cma=512MB simpledrm.modeset=0[xlebnick@pi:~ $ cat /etc/os-releasePRETTY_NAME="Debian GNU/Linux 12 (bookworm)"NAME="Debian GNU/Linux"VERSION_ID="12"VERSION="12 (bookworm)"VERSION_CODENAME=bookwormID=debianHOME_URL="https://www.debian.org/"SUPPORT_URL="https://www.debian.org/support"BUG_REPORT_URL="https://bugs.debian.org/"xlebnick@pi:~ $ uname -aLinux pi 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux


What I've tried:
- update practically everything
- switch to vc4-kms-v3d instead of vc4-kms-v3d-pi5

Statistics: Posted by XlebNick — Sun Nov 02, 2025 2:25 pm



Viewing all articles
Browse latest Browse all 8082

Trending Articles