Solved Upgrade to Nvidia 570.169 was nessesary after installing Main-n278713-bf4d2a45b991

HI

I Upgraded my laptop (Fujitsu H7510 with Nvidia mobile Quadro 1000 ) to a recent ( yestedays 13 th July )
15-current Main-n278713-bf4d2a45b991.

Nvidia 570-144 DRM drivers caused Kernel Panic with this Freebsd version , although the Non.DRM driver was stable.

Uppgrading the whole Nvidia platform to 570.169 solved the issue.

Regards
 
When you have an already installed system and need to uppgrade the Nvidia DRM drivers its a three stage process,
the three packages drm-61-kmod , nvidia-drm-61-kmod , nvidia-drm needs to be rebuilt,
by looking at several historical posts here, its obvious that even if this works when installing from PORTS the first time, the rebuild of drm-61-kmod package is not invoked if /boot/modules/drm.ko and dmabuf.ko is preexisting in the filesystem. Then you have a situation where Nvidia-drm.ko has been rebuilt but the Drm.ko and dmabuf.ko is still the old version,

Only solution I have found when working from PORTS is to rebuild drm-6 1-kmod first , then nvidia-drm-61-kmod and finaly Nvidia-drm , which is backwards for the way the dependencies been setup in the PKG system .
 
When you have an already installed system and need to uppgrade the Nvidia DRM drivers its a three stage process,
the three packages drm-61-kmod , nvidia-drm-61-kmod , nvidia-drm needs to be rebuilt,
by looking at several historical posts here, its obvious that even if this works when installing from PORTS the first time, the rebuild of drm-61-kmod package is not invoked if /boot/modules/drm.ko and dmabuf.ko is preexisting in the filesystem. Then you have a situation where Nvidia-drm.ko has been rebuilt but the Drm.ko and dmabuf.ko is still the old version,

Only solution I have found when working from PORTS is to rebuild drm-6 1-kmod first , then nvidia-drm-61-kmod and finaly Nvidia-drm , which is backwards for the way the dependencies been setup in the PKG system .
It should happen only when graphics/drm-61-kmod is NOT built against your running kernel.

On testing upgrades for nvidia driver sets before submitting patches to Bugzilla and Phabricator, I (currently) rebuild x11/nvidia-driver, x11/linux-nvidia-libs, graphics/nvidia-drm-61-kmod and (just to be sure) graphics/nvidia-drm-kmod in case Production Branch of drivers is released. For New Feature Branch (NFB) of drivers, -devel versions instead.

Once all build succeeds, install them and restart to make them working.

Once confirmed these works fine without unknown issues (for me), try building/packaging graphics/nvidia-drm-*-kmod[-devel], except *-66-* version, as I'm on stable/14 and *-66-* only supports main (aka Current) to be built.

Once I've confirmed above, I submit my patches and wait for review/land.
 
T-Aoki Wrote;
It should happen only when graphics/drm-61-kmod is NOT built against your running kernel.

Yes thats when it happends ,
In the Upgrade scenarios

thanks for this info


 
Back
Top