Nvidia 570.153.02.run

[malcolmlewis]

@deebido AFAIK fbdev should help that, well just logging into a VT (tty) login as root user and run systemctl isolate multi-user.target install the NVIDIA driver, then systemctl isolate graphical.target should suffice. If it was a kernel update, then I would boot to runlevel 3 in the new kernel. Normally I use systemctl set-default multi-user.target reboot to new kernel, install the driver, systemctl set-default graphical.target then reboot…

[dart364]

The reason why the monitor is turning off is (at least in my case) even in runlevel 3 the nvidia drivers are still loaded and take over from fbcon so until the new driver is compiled and loaded the monitor will unload any driver that is previously compiled and go blank. You can get around this by hitting “e” at the grub menu and appending module_blacklist=nvidia 3 to the cmdline so only fbcon gets loaded

@pilotgi I use this nvidia page to search for my drivers … if you use <nvidia.runfile> -s it will install in silent mode with no questions much like the cmdline @malcolmlewis uses … then you just wait until your monitor comes back on after the run file gets done compiling and loads the new driver … if you want the “open kernel” version of the proprietary driver you would need to append --kernel-module-type=open to the command line along with -s … I don’t use the --no-install-libglvnd option … of course on a new kernel install there is no previous driver to unload so monitor blanking doesn’t happen

Edit: In Wayland modeset=1 is mandatory

dart@windeath:~> cat /etc/modprobe.d/90-nvidia.conf 
# See "modinfo nvidia" for others
# Sleep/Hibernate
options nvidia \
	NVreg_PreserveVideoMemoryAllocations=1

# For Wayland 
options nvidia_drm modeset=1

[deebido]

Okay ya so if I remove nvidia-drm.modeset=1 by hitting ‘e’ at the grub screen and add nomodeset 3 while im in there, I can then use the run file installer in TTY without the monitor shutting off. Is this the same as adding module_blacklist=nvidia 3? Solved

[dart364]

No … not the same … dracut will put the nvidia driver in initrd … I have this file to see that doesn’t happen

dart@windeath:~> cat /etc/dracut.conf.d/90-nvidia-conf 
# Omit the nvidia driver from the ramdisk
omit_drivers+="nvidia nvidia-drm nvidia-modeset"

[dart364]

By putting my parameters in modprobe.d/90-nvidia.conf and using the dracut omit drivers conf file when I go to runlevel 3 only fbcon is used regardless of whether I use the module_blacklist=nvidia or not … I only needed that when the drivers were added to initrd before I put the dracut conf file in /etc/dracut.conf.d

[pilotgi]

@malcolmlewis

@deebido AFAIK fbdev should help that, well just logging into a VT (tty) login as root user and run systemctl isolate multi-user.target install the NVIDIA driver, then systemctl isolate graphical.target should suffice. If it was a kernel update, then I would boot to runlevel 3 in the new kernel. Normally I use systemctl set-default multi-user.target reboot to new kernel, install the driver, systemctl set-default graphical.target then reboot…

I followed these instructions and was able to install 570.153.02. My display still went blank but only for about 2 minutes, then I got a message that the driver was installed.

By the way, the option -- ui=none was not accepted.

Edit: Oh, I see. There shouldn’t be a space before ui.