| View previous topic :: View next topic |
| Author |
Message |
jms.gentoo
Tux's lil' helper
Joined: 07 May 2009
Posts: 102
|
 Posted: Sat Jun 29, 2024 10:47 pm Post subject: nvidia-drivers-555.58 DVI output not working on monitor |
 |
|
Hey everyone,
Just wondering if anyone else is having trouble with this new driver?
I've been rocking a sweet Nvidia setup for 5 years now, with no issues running my dual monitor setup... until this driver update. Now only one monitor shows anything, even though I see info pop up on the second one during boot process.
reverting back to nvidia-drivers-550.90.07 solve the issue
Anyone else experiencing this weirdness?
Last edited by jms.gentoo on Sun Jun 30, 2024 8:11 pm; edited 1 time in total |
|
| Back to top |
|
 |
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2856
|
| Posted: Sun Jun 30, 2024 3:50 am Post subject: |
|
|
If it's a recent'ish card (GTX 1650+), may want to try disabling its use of the GSP firmware. NVIDIA started to use it by default in 555 and it's the primary cause of regressions.
The ebuild briefly warn about this the first time 555 is emerged too (see the noted nvidia.conf):
| Code: | if use !kernel-open && [[ ${REPLACING_VERSIONS##* } ]] &&
ver_test ${REPLACING_VERSIONS##* } -lt 555
then
elog
elog "If using a Turing/Ampere+ GPU (aka GTX 1650+), note that >=nvidia-drivers-555"
elog "enables the use of the GSP firmware by default. *If* experience regressions,"
elog "please see '${EROOT}/etc/modprobe.d/nvidia.conf' to optionally disable."
fi |
|
|
| Back to top |
|
|
jms.gentoo
Tux's lil' helper
Joined: 07 May 2009
Posts: 102
|
| Posted: Sun Jun 30, 2024 8:09 pm Post subject: |
|
|
| Ionen wrote: | If it's a recent'ish card (GTX 1650+), may want to try disabling its use of the GSP firmware. NVIDIA started to use it by default in 555 and it's the primary cause of regressions.
The ebuild briefly warn about this the first time 555 is emerged too (see the noted nvidia.conf):
| Code: | if use !kernel-open && [[ ${REPLACING_VERSIONS##* } ]] &&
ver_test ${REPLACING_VERSIONS##* } -lt 555
then
elog
elog "If using a Turing/Ampere+ GPU (aka GTX 1650+), note that >=nvidia-drivers-555"
elog "enables the use of the GSP firmware by default. *If* experience regressions,"
elog "please see '${EROOT}/etc/modprobe.d/nvidia.conf' to optionally disable."
fi |
|
Thanks Ionen for you re help.
I didn't check the log  .
For info: curiously enough this message didn't appear when I installed it the first time
I did have a "Info: postinst" but no "Log: postinst " containing this info maybe because I updated my gentoo-kernel at the same time ?
But upon second reinstall the message did appear.
I did try to disable use of the GSP firmware with no effect
| Code: |
# Disable use of the GSP firmware which has newly been enabled by default
# for GPUs that support it (Turing/Ampere+ GPUs, aka GTX 1650+). Not
# recommended unless experience regressions for which disabling helps.
# Cannot be disabled if using USE="kernel-open".
options nvidia NVreg_EnableGpuFirmware=0
|
I have an older card
NVIDIA GeForce GTX 1050
to check for enabled or not GSP enabled
| Code: | nvidia-smi -q
.
.
GSP Firmware Version : N/A
|
I am surprised no one got this problem.
for info
I didn't change anything (that I can think of wich vould have any obvious impact)
Using openrc plasma 6.1.1 under x or wayland it's the same result.
My 2 monitor are the same
One using nvidia HDMI to HDMI and the other DVI output to HDMI
and the one having problem is DVI output to HDMI
changing connection show that the DVI output to HDMI is the problematic one.
if anyone curious about it here is my emerge --info
https://dpaste.com/727YDD5EC
nvidia-smi -q
http://dpaste.com/HVFVDMRSU
I will go back to nvidia-drivers-550.90.07
thanks again Ionen for pointing out the GSP firmware potential problem and remind me to check my ebuild log 
Last edited by jms.gentoo on Mon Jul 01, 2024 4:34 am; edited 1 time in total |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2856
|
| Posted: Mon Jul 01, 2024 12:30 am Post subject: |
|
|
Yeah for a 1050 GSP is unrelated then, I don't know what may be causing this (I don't think I heard about it). The message also only show when upgrading from 550 to 555 (not installing 555 on its own), but either way it doesn't apply to you.
You could always browse the 555 thread on nvidia forums and see if someone mention it (the thread is pretty big though, so it'shard to find anything). No harm in sticking to still-supported stable drivers though (550 is a production branch, while 555 is an experimental new feature branch that will never be stabilized), if luck has it may be resolved by the time of the next production branch. |
|
| Back to top |
|
|
jms.gentoo
Tux's lil' helper
Joined: 07 May 2009
Posts: 102
|
| Posted: Mon Jul 01, 2024 4:32 am Post subject: |
|
|
| Ionen wrote: | | No harm in sticking to still-supported stable drivers though (550 is a production branch, while 555 is an experimental new feature branch that will never be stabilized), if luck has it may be resolved by the time of the next production branch. |
yes will do that ,it's not worth the hassle.
Also it seems that this is not an isolated case ,I found some arch users with DVI output problem with this driver.
https://bbs.archlinux.org/post.php?tid=297229&qid=2181018 |
|
| Back to top |
|
|
|
Kernel & Hardware
