| View previous topic :: View next topic |
| Author |
Message |
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 778
|
 Posted: Sat Apr 05, 2025 5:18 am Post subject: nvidia-drivers-570.133.07 gives blank console |
 |
|
After emerging from x11-drivers/nvidia-drivers-570.124.04 to x11-drivers/nvidia-drivers-570.133.07 (and rebooting) when I switch to a console (ex: <crrl>-<alt>- F2) I get a blank screen. If I return to x-windows (ex: <ctrl>-<alt>-F1) the X session re-appears. The consoles works after a reboot until I use X11. (I do not use a graphical login manager, I login on the console and then 'exec startx'). I do not see any errors in /var/log/messages. (I forgot to look in /var/log/Xorg.0.log before I rebooted.)
Temporary fix: emerge (downgrade) to x11-drivers/nvidia-drivers-570.124.04 Now I can switch between X11 and console without issue.
Anyone have any idea what is wrong? |
|
| Back to top |
|
 |
netfab
Advocate
Joined: 03 Mar 2005
Posts: 2020
Location: 127.0.0.1
|
| Posted: Mon Apr 07, 2025 8:44 am Post subject: |
|
|
Please post the output of :
| Code: |
# cat /sys/module/nvidia_drm/parameters/modeset
|
Also, what is your kernel ?
That's funny because on a system, since a long time with nvidia-drivers, I have the opposite problem : I can switch to TTY, but when I want to come back to X the screen is blank. |
|
| Back to top |
|
|
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 778
|
| Posted: Mon Apr 07, 2025 7:12 pm Post subject: |
|
|
| Code: | # cat /sys/module/nvidia_drm/parameters/modeset
N |
That is from the slightly older, but working x11-drivers/nvidia-drivers-570.124.04.
If you think it would be different, I would need to re-emerge nvidia-drivers-570.133.07 which I have masked on my system.
> Also, what is your kernel ?
sys-kernel/gentoo-sources-6.13.9
Also, even though the display is blank, keyboard input seemed to work. (I typed "root<enter><root password><enter>shutdown -r now" and the system rebooted. |
|
| Back to top |
|
|
netfab
Advocate
Joined: 03 Mar 2005
Posts: 2020
Location: 127.0.0.1
|
| Posted: Mon Apr 07, 2025 8:15 pm Post subject: |
|
|
You should try to add these options on your kernel command line to see if it makes a difference :
| Code: |
nvidia-drm.modeset=1 nvidia-drm.fbdev=1
|
You can find comments about these optiions in /etc/modprobe.d/nvidia.conf. |
|
| Back to top |
|
|
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 778
|
| Posted: Mon Apr 07, 2025 9:54 pm Post subject: |
|
|
I'll try adding "nvidia-drm.modeset=1 nvidia-drm.fbdev=1 " to the end of the kernel command line after "upgrading" back to nvidia-drivers-570.133.07 later this week.
I am a little concerned about the modeset=1 after reading the nvidia comments from this post:
https://forums.developer.nvidia.com/t/understanding-nvidia-drm-modeset-1-nvidia-linux-driver-modesetting/204068/5
If I read the comments correctly and apply modeset=1, nvidia-driver would drive the console which means I would need to reboot after changing/upgrading the nvidia-driver module because I could no longer "modprobe -r <nvidia modules>" and subsequently "modprobe <nvidia modules>" which works if X11 is not running. I guess I will find out. |
|
| Back to top |
|
|
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 778
|
| Posted: Wed Apr 09, 2025 4:30 pm Post subject: |
|
|
netfab:
Yes, adding
| Code: | | nvidia-drm.modeset=1 nvidia-drm.fbdev=1 |
to the end of my kernel boot line does solve my original issue. (I assume I could also just modify /etc/modprobe.d/nvidia.conf to do the same thing.)
As I suspected with this "fix" you can not remove nvida_drm module. (When not using X at all, and at the console my system would let me "modprobe -r nvidia_drm" but then all console displays did not work.)
So my current choices:
1. Use the latest "stable" nvidia driver and require a reboot if I change nvidia-drivers. (With suggested kernel line additions.)
or
2. Use a slightly older nvidia driver and not need a reboot to change nvidia-drivers.
I am trying option one for now. (as a bonus, using nvidia-drivers to drive the console lets you have a higher resolution console.)
Also, upgrading my kernel from gentoo-sources-6.13.9 to 6.13.10 made no difference. |
|
| Back to top |
|
|
netfab
Advocate
Joined: 03 Mar 2005
Posts: 2020
Location: 127.0.0.1
|
| Posted: Fri Apr 11, 2025 10:10 am Post subject: |
|
|
Another way is to use Hybrid graphics.
In this way the iGPU is handling tty consoles framebuffer and xorg desktop displays.
The dGPU (nvidia) is handling heavy tasks and interacts with iGPU.
In this mode you can easily update nvidia-drivers, modprobe -r nvidia, and reload everything without rebooting.
Works fine here with intel i915 and latest nvidia-drivers. |
|
| Back to top |
|
|
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 778
|
| Posted: Fri Apr 11, 2025 7:41 pm Post subject: |
|
|
netfab, thanks for the Hybrid graphics link. I'll take a look.
My current solution for changing nvidia-drivers and NOT rebooting when nvidia-drivers drive the console is just the below script. The issue I was having was no display when I was running most of the commands. I guess I could also ssh into my system and run the commands that way.
| Code: | #/bin/bash
#
# After changing the nvidia-drivers (ex: emerge nvidia-drivers)
# this will ensure the matching nvidia-drivers modules are used.
# Use this when nvidia-drivers is driving the console.
# If you try this by hand your console will not show.
# Do not have X11 up and running when executing the following.
#
modprobe -r nvidia_uvm
modprobe -r nvidia_drm
modprobe -r nvidia_modeset
modprobe -r nvidia
sleep 1
modprobe nvidia
modprobe nvidia_modeset
modprobe nvidia_drm
modprobe nvidia_uvm |
|
|
| Back to top |
|
|
|
Desktop Environments
