Linux MESA-LOADER missing device information

daeron · Tuesday at 5:43 PM

After a weekend ports update, the linux-brave browser is now core dumping a bit after complaining "MESA-LOADER: failed to retrieve device information".
I've rebuilt mesa and linux-rl9 ports to no avail, suggestions would be welcomed.

Code:

% brave-browser
[4029:104481:0804/182109.623544:ERROR:device/udev_linux/udev_watcher.cc:51] Failed to initialize a udev monitor.
[0804/182109.701139:ERROR:third_party/crashpad/crashpad/util/linux/ptracer.cc:44] ptrace: Invalid argument (22)
[0804/182109.701183:WARNING:third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400] Couldn't initialize main thread.
[0804/182109.701203:ERROR:third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[0804/182109.701215:WARNING:third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391] thread ID 4029 not found in process
[0804/182109.701273:ERROR:third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129] thread not found 4029
[0804/182109.701490:ERROR:third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
kmsro: driver missing
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
kmsro: driver missing
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Trace/BPT trap (core dumped)

fahrenheit · Tuesday at 6:44 PM

daeron can you confirm that the freebsd drm driver (amdgpu, radeon, i915kms or nvidia) started fine and you are not running a non accelerated desktop?

How to figure out:

check dmesg or X log for error
use drm_info (# pkg install drm_info && drm_info | grep Driver)
glxinfo -B (# pkg install mesa-demos && glxinfo -B | grep Device )

daeron · Tuesday at 7:47 PM

Ta,
Looks ok, and glclock's running happily.

Code:

% drm_info | grep Driver
├───Driver: nvidia-drm (NVIDIA DRM driver) version 0.0.0 (20160202)
%
% glxinfo -B | grep Device
%
% kldstat | grep nvidia
 5    1 0xffffffff83710000    14a88 nvidia-drm.ko
11    2 0xffffffff83800000  6075420 nvidia.ko
15    1 0xffffffff89883000   1662f8 nvidia-modeset.ko
%
% nvidia-smi
Wed Aug  5 04:21:27 2026       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.173.02             Driver Version: 580.173.02     CUDA Version: N/A      |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GT 1030         Off |   00000000:07:00.0  On |                  N/A |
| 35%   37C    P0            N/A  /   19W |     594MiB /   4096MiB |      7%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+
%
% glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4096 MB
    Total available memory: 4096 MB
    Currently available dedicated video memory: 3429 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 1030/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 580.173.02
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 580.173.02
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 580.173.02
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

fahrenheit · Tuesday at 11:27 PM

Yeah, the driver appears to be loaded. I have some doubts the output of glxinfo, I see much more information on my radeon but your output could be fine.

Try checking if brave changed the rendering engine or some such. See if you can launch it on software renderer and see the chrome page that lists the current hardware, maybe chrome:gpu or brave:gpu, that may help.

monwarez · Wednesday at 6:01 AM

Assuming that you have graphics/linux-rl9-vulkan, can you run /compat/linux/bin/vkcubepp and report which gpu was selected.
Was it the nvidia one, or the non-accelerated llvmpipe ?

I am assuming that you have installed the x11/linux-nvidia-libs drivers ?

Another possibility that could be it is affected by the same issue as mesa for linuxulator here PR 278363

daeron · Wednesday at 6:43 AM

nvidia-smi and glxinfo -B both show the GT 1030 working with the 580.173.02 driver
ungoogled-chromium works chrome://gpu looks healthy
I've tested Linux Google Chrome 150.0.7871.186 which seems fine with hardware acceleration (ANGLE + NVIDIA).
Linux Brave 150.1.92.144keeps core dumping.

Code:

Failed to initialize a udev monitor
ptrace: Invalid argument (22)          ← Crashpad
... thread not found ...
MESA-LOADER: failed to retrieve device information
kmsro: driver missing
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Trace/BPT trap (core dumped)

I tried (--disable-gpu, --use-gl=swiftshader, --single-process, --disable-crash-reporter, --disable-features=Crashpad,..., __GLX_VENDOR_LIBRARY_NAME=nvidia, etc.)
Brave still aborts on the Crashpad ptrace failure. The MESA-LOADER / kmsro messages disappear when GPU is disabled, but the Crashpad abort remains.
I have x11/linux-nvidia-libs installed.

Thanx monwarez
% /compat/linux/bin/vkcubepp
Selected WSI platform: xcb
Selected GPU 0: NVIDIA GeForce GT 1030, type: DiscreteGpu

fahrenheit · Wednesday at 7:50 AM

monwarez the issue you mention shouldn't be the cause, but if it helps you can try this method: https://forums.freebsd.org/threads/how-to-enable-vulkan-on-compat-linux.101997/

Assuming you only have one card it will create the entries.

But the crash appears to point to missing drm drivers on the rocky side. daeron check that you have installed linux-rl9-dri and linux-nvidia-utils-580 as linux-nvidia-utils now points to the 595 driver that does not support your card.

monwarez · Wednesday at 6:01 PM

fahrenheit said:
monwarez the issue you mention shouldn't be the cause, but if it helps you can try this method: https://forums.freebsd.org/threads/how-to-enable-vulkan-on-compat-linux.101997/

Thanks, but I don't really need this since it is already fixed by linux-steam-utils, and handle the multiple gpu case.

daeron · 2026-08-06T07:25:52+0100

fahrenheit said:
But the crash appears to point to missing drm drivers on the rocky side. daeron check that you have installed linux-rl9-dri and linux-nvidia-utils-580 as linux-nvidia-utils now points to the 595 driver that does not support your card.

I'm guessing you were thinking linux-nvidia-libs, in any event

% pkg info | egrep 'linux-rl9-dri|linux-nvidia'
linux-nvidia-libs-580-580.173.02 NVIDIA graphics libraries and programs (Linux)
linux-rl9-dri-25.2.7 Mesa libGL runtime libraries (Rocky Linux 9.8)

fahrenheit · 2026-08-06T08:02:27+0100

daeron said:
I'm guessing you were thinking linux-nvidia-libs, in any event

% pkg info | egrep 'linux-rl9-dri|linux-nvidia'
linux-nvidia-libs-580-580.173.02 NVIDIA graphics libraries and programs (Linux)
linux-rl9-dri-25.2.7 Mesa libGL runtime libraries (Rocky Linux 9.8)

Yes, it was libs, don't know why I kept writing utils..

In any case, I'm out of ideas then.
Maybe try to open a bug to see if one of the dev team can help or try on the mailing lists.