Liste des Groupes | Revenir à col advocacy |
On Fri, 24 May 2024 07:47:54 -0400, Andrzej Matuch <andrzej@matu.ch> wroteWhy are you removing them? Were they problematic?
in <v2pupa$2ae8o$1@dont-email.me>:
On 2024-05-23 9:15 p.m., vallor wrote:They are the open ones from Nvidia. (Not nouveau, but the "open" versionSo after building a kernel and booting it, I've found it easiest to>
take the system to single-user mode with
>
$ telinit 1
>
...which will take the system to single-user ("rescue") mode and
ask for your root password before proceeding. (Make sure you have one
set.)
>
Then I build the open Nvidia drivers, install them,
then remove the existing Nvidia drivers with the following command
(that I've scripted):
>
rmmod nvidia_drm nvidia_modeset nvidia_uvm nvidia
>
...which removes the modules in the proper order,
accounting for dependencies.
>
Finally, everything is ready to go, so:
>
# telinit 5
>
...and the system comes up in all its graphical glory.
>
I do it this way rather than rebooting because sometimes,
the drivers don't load right when I boot, and windows tear when they
move. If that happens, I do the "telinit 1"-"rmmod"-"telinit 5"
dance, which has always solved the problem.
>
(I was pleasantly surprised to find out that systemd knows about init
runlevels. Very helpful.)
>
Finally, if you want to shutdown the display manager and just use vty's
with getty logins, you could
>
$ telinit 3
>
These runlevels are the same as they were with SysV init on Linux.
I'm curious: are you removing the NVIDIA proprietary drivers here or the
open ones? I'm reading that there are issues with the open-kernel ones
because they're in alpha. I was under the impression that you didn't
have too much trouble with them.
of their proprietary drivers.)
https://github.com/NVIDIA/open-gpu-kernel-modules
Les messages affichés proviennent d'usenet.