I've been trying to reproduce this issue but I didn't manage to have reproduces this errors:I removed virtio_icd.json, but there was no effect. The behavior is the same.Could you please check in trixie, what happens if you delete virtio_icd.json? I would like to know if virtio driver is taking preference over broadcom for some reason...
I will try to debug next week why this is happening, but installing the developer package shouldn't be needed.
Code:
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Bad file descriptorMESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Bad file descriptor, continuing without context...MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Bad file descriptorMESA: error: Failed to create virtgpu AddressSpaceStreamI managed to reproduce the issue of falkon needing the eglfs.json pointing on /dev/dri/card1 on Rpi5, but not needing it on RPi4. And I debugged it to eglfs just opening the first available video device without checking if the device is a KMS device. So it just fails when it opens the render node that doesn't have support for display.
A good example about how a KMS device could be identified is what kmscube is doing in find_drm_device when no device is passed as parameter: https://gitlab.freedesktop.org/mesa/kms ... heads#L204
Do you see any error if you run kmscube from the console in the same system. Maybe that could provide us a clue to what is different in your device.
Statistics: Posted by txenoo — Tue Jul 15, 2025 11:15 am