insufficient privileges to load firmware image nvidia_gsp_tu10x_fw

NapoleonWils0n

NapoleonWils0n

upgraded to the latest quarterly branch

im getting this error in dmesg
and crashes using mpv to play some youtube video

Code: 
firmware_get_flags: insufficient privileges to load firmware image nvidia_gsp_tu10x_fw

the only google search result is this posts on the forum by T-Aoki

T

Post in thread 'Trying to run KDE 6 Plasma with Wayland....'

ziomario said:
I have restarted from scratch....and it worked...I've been able to use the new driver and the new drm-61.ko. Unfortunately kde6 and wayland still don't work.

View attachment 19981

The new driver and the new drm.ko work worst than the older ones with kde6 and wayland.

View attachment 19982
Click to expand...
Your screenshot shows that nvidia-drm.ko is not loaded.
And nvidia-smi is complaining firmware_get_flags: insufficient privileges to load firmware image nvidia_gsp_tu10x_fw.

So my next questions are:
  1. If you kldload nvidia-drm (as root), does it pull in nvidia-modeset.ko...

kldstat grep nvidia

shows nvidia_gsp_tu10x_fw.ko isnt loaded

Code: 
kldstat| grep nvidia
14    2 0xffffffff837f9000   1507d8 nvidia-modeset.ko
15    2 0xffffffff83a00000  52ef728 nvidia.ko
18    1 0xffffffff83988000    149b0 nvidia-drm.ko

use kldload as root to load nvidia_gsp_tu10x_fw.ko

Code: 
su -
kldload nvidia_gsp_tu10x_fw.ko

then run kldstat | grep nvidia

Code: 
# kldstat | grep nvidia
14    2 0xffffffff837f9000   1507d8 nvidia-modeset.ko
15    2 0xffffffff83a00000  52ef728 nvidia.ko
18    1 0xffffffff83988000    149b0 nvidia-drm.ko
67    1 0xffffffff89600000  1b13538 nvidia_gsp_tu10x_fw.ko

and nvidia_gsp_tu10x_fw.ko is now loaded

so the question is how to get nvidia_gsp_tu10x_fw.ko to load automatically

this is my /etc/rc.conf

Code: 
/etc/rc.conf

and the kld_list with nvidia-modeset nvidia-drm

Code: 
kld_list="nvidia-modeset nvidia-drm linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

i dont have any nvidia settings in

Code: 
/boot/loader.conf

some people seem to suggest using loader.conf
while other suggest using the kld_list with rc.conf

Cath O'Deray

Solved Thread 'Appropriate use of loader.conf(5) for kernel modules'

There's a FreeBSD recommendation to use /boot/loader.conf for nvidia (with the latest driver for NVIDIA).

Is this use of loader.conf appropriate (with FreeBSD 13.0-RELEASE), or somewhat archaic?

loader.conf(5)

so i would have thought the fix in one of two things

1 - the kld_list in rc.conf needs another setting
in addition to nvidia-modeset nvidia-drm linux

2 - the nvidia-modeset needs to be set in the /boot/loader.conf
and not in the rc.conf kld_list so it loads the nvidia_gsp_tu10x_fw.ko module

i have always used the kld_list in rc.conf with nvidia
rather the loader.conf

freebsd root config

github.com

GitHub - NapoleonWils0n/freebsd-root-xps: freebsd root dotfiles for dell xps 15 2019

freebsd root dotfiles for dell xps 15 2019. Contribute to NapoleonWils0n/freebsd-root-xps development by creating an account on GitHub.
github.com github.com

nv-sglrun nvidia-smi output

Code: 
nv-sglrun nvidia-smi
/usr/local/lib/libc6-shim/libc6.so: shim init
Mon Apr  7 22:55:55 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.124.04             Driver Version: 570.124.04     CUDA Version: 12.8     |
|-----------------------------------------+------------------------+----------------------+
| 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 GTX 1650        Off |   00000000:01:00.0 Off |                  N/A |
| N/A   53C    P8              1W /   50W |       1MiB /   4096MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+
 
fixed the issue of the nvidia_gsp_tu10x_fw not being loaded

by loading the module in my kld_list in my rc.conf

Code: 
/etc/rc.conf

added nvidia_gsp_tu10x_fw to the kld_list

Code: 
kld_list="nvidia-modeset nvidia-drm nvidia_gsp_tu10x_fw linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

no errors with dmesg when booting

kldstat grep for nvidia

Code: 
kldstat| grep nvidia
14    2 0xffffffff837f9000   1507d8 nvidia-modeset.ko
15    2 0xffffffff83a00000  52ef728 nvidia.ko
18    1 0xffffffff83988000    149b0 nvidia-drm.ko
24    1 0xffffffff88e00000  1b13538 nvidia_gsp_tu10x_fw.ko
 
still getting crashes after loading nvidia_gsp_tu10x_fw.ko
on my Dell XPS 15 2019

playing a video with either Firefox or mpv just freezes the system
and i have to do a hard shutdown

have to switch back to linux
 
NapoleonWils0n said:
i dont have any nvidia settings in

/boot/loader.conf
some people seem to suggest using loader.conf
while other suggest using the kld_list with rc.conf
Click to expand...
This could be the problem.

Loading nvidia-drm.ko via /etc/rc.conf is perfectly fine and strongly recommended.

But you need hw.nvidiadrm.modeset=1 in your /boot/loader.conf to make nvidia-drm.ko to work.
This is because hw.nvidiadrm.modeset is a read-only tunable, so it must be set before nvidia-drm.ko is loaded. Otherwise it would be ignored (fixed with default 0) or racy.

Once nvidia-drm.ko is properly initialized, it would automatically attempt to load GSP firmware module when applicable (GPUs before Turing generation does not have GSP in it, thus, the firmwares are unneeded).

And if you have any problem with GSP enabled by nvidia-drm.ko, you can disable it by setting hw.nvidia.registry.EnableGpuFirmware=0 in your /boot/loader.conf could help. See PR 285803 for details.
 
Loading nvidia-drm.ko via /etc/rc.conf is perfectly fine and strongly recommended.
But you need hw.nvidiadrm.modeset=1 in your /boot/loader.conf to make nvidia-drm.ko to work.

thats even worse
it crashes the system as soon as i open a video

Code: 
/boot/loader.conf

Code: 
hw.nvidiadrm.modeset=1

Code: 
/etc/rc.conf

in conjunction with hw.nvidiadrm.modeset=1

tried this

Code: 
kld_list="nvidia-modeset nvidia-drm nvidia_gsp_tu10x_fw linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

and this

Code: 
kld_list="nvidia-drm nvidia_gsp_tu10x_fw linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

and this

Code: 
kld_list="nvidia-drm nvidia_gsp_tu10x_fw linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

and this

Code: 
kld_list="nvidia-drm inux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

nvidia_gsp_tu10x_fw linux only gets loaded with if its in the kld_list
it doesnt get loaded with hw.nvidiadrm.modeset=1 in loader.conf

and virtual_oss has stopped working

Code: 
/etc/rc.conf

Code: 
# virtual oss
virtual_oss_enable="YES"
virtual_oss_configs="dsp"
virtual_oss_dsp="-T /dev/sndstat -S -Q 0 -C 2 -c 2 -r 48000 -b 16 -s 1024 -P /dev/dsp1 -R /dev/null -w vdsp.wav -l dsp -t vdsp.ctl"
# sndiod audio
sndiod_enable="YES"

vdsp.ctl doesnt get created
 
fixed the virtual_oss issue by removing -T /dev/sndstat

on the nvidia side tried this

Code: 
kld_list="nvidia nvidia-modeset nvidia-drm nvidia_gsp_tu10x_fw linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

still crashes

tried seeting the following in loader.conf

Code: 
hw.nvidiadrm.modeset=1

without anything in the kld_list

Code: 
kld_list="linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

nvidia not loaded at all

been through all the permutations and nothing works
its a bit of a flustercluck

only conclusion is the latest driver is fubar

dont see what options are left to try
only option left is to wipe the machine and install Ubuntu 25.04 when it comes out
 
tried this fix from this post

Code: 
hw.nvidia.registry.EnableGpuFirmware=0

in loader.conf

on its own and with

Code: 
hw.nvidiadrm.modeset=1

didnt worked

latest nvidia driver just crashes the system

really lame,
have to switch back to Ubuntu :(

G

Post in thread 'Help with NVIDIA drm set up'

T-Aoki said:
GPUs older than Turing generation does not have GSP in them, so setting hw.nvidia.registry.EnableGpuFirmware=0 has no effect for these
Click to expand...
As informed earlier I have GTX-1650 ( last of the series ) and my earlier AMD GPU had no problem. Testing found that setting of hw.nvidia.registry.EnableGpuFirmware=0 has effect some how. It is working as intended.
 
Another option would be not to load GSP firmware module.

Once nvidia-drm.ko is enabled via tunable hw.nvidiadrm-modeset, it automatically loads corresponding GSP firmware module when applicable.

If GPS firmware causes anything harmful (currently, it is known to avoid suspend/resume at least on certain 570 series which are currently available upstream), you can try setting hw.nvidia.registry.EnableGpuFirmware=0 to your loader.conf.
 
cheers mate

dont want to tempt fate
but this combination seems to work

Code: 
/boot/loader.conf

Code: 
hw.nvidia.registry.EnableGpuFirmware=0

Code: 
/etc/rc.conf

Code: 
kld_list="nvidia-modeset nvidia-drm linux linux64 i915kms ext2fs mac_priority fusefs vmm nmdm"

using the following in loader.conf
just crashes the system

Code: 
hw.nvidiadrm.modeset=1

played a video with mpv and firefox and didnt crash
have to play a few more videos and see if i get any crashes
 
You must log in or register to reply here.
Back
Top