You are not logged in.
I booted my PC today and was surprised and disappointed to discover that one of my monitors doesn't seem to be getting any signal from the system and is blank. I was also then surprised to see that I now have the 555 beta version of the nvidia driver installed - despite not explicitly installing it. Why on earth is a beta driver the default version of the driver? I know we're supposed to be "bleeding edge", but this seems to me to be taking that a little far.
Anyway -my monitors are both LG Ultrawide 2560x1080 and my GPU is an NVidia GeForce GTX 1070. My first (left) monitor is connected via the DVI port (using an HDMI adapter as the monitor only has HDMI and VGA inputs) and the right is connected via HDMI.
I have exactly the same problem on both Wayland and Xorg. If I run xrandr (which I was a little surprised to find working on Wayland) it does show both monitors, but still only one is showing any output.
If there are any configs/logs/error messages that would be useful - please let me know.
Many thanks in advance.
Edit: If it makes any difference to anything, the mouse can still be moved over to the left monitor and I can "interact" with it in terms of using shortcuts to move windows from it to the right monitor. Also, having temporarily rolled back my system to a version with nvidia 550, I now have both monitors...
Last edited by phunni (2024-07-01 14:28:06)
Offline
What version did you get, exactly? 555.58 is not beta.
As for the problem, look around, there are multiple threads on this already.
Online
Thanks for the reply. Apologies - I thought 555 was beta and 560 would be the stable version. My mistake.
I did search around for threads on this and didn't find any - at first. I searched again and found a few and all I can see, so far, is that the solution is to downgrade...
Offline
Same problem, reported here: https://bbs.archlinux.org/viewtopic.php?id=297196
Offline
I have the same issue with Nvidia 555 after I updated it yesterday. I saw another thread on the Gentoo forum where someone suggested disabling GSP firmware to fix the issue. For me, it's already disabled as I use GTX 1060 so I guess we need a fix from Nvidia. For now, I've downgraded everything to last week as a workaround.
Offline
Same problem with GTX 1050.
Offline
i have a single monitor setup, but same problem here i had to downgrade to the following versions of each package:
lib32-nvidia-utils -- 550.90.07-1, linux -- 6.9.6.arch1-1, linux-headers -- 6.9.6.arch1-1, nvidia-dkms -- 550.90.07-3,
nvidia-utils -- 550.90.07-1. i updated today, so i figured id just downgrade for now and wait for updates on this since everything i tried didnt work. no signal on startup, but when i downgraded these packages it started up fine. i am not sure which packages it is exactly i just assumed that it had to be all or at least one of the ones i listed i guess.
Just a random dude battling leukemia. New to Arch, but loving it.
Matrix: @bnowell44:matrix.org - Mail Alias: archlinux.washday284@passmail.net
Telegram: @nuckat520 - Discord: bradleynowell
Offline
DVI port
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
After 2 days tearing out my hair to understand...
I have the same problem with
- NVIDIA Geforce GTX 1060
- 2 monitors, one plugged with HDMI (it works), another plugged with DVI (it doesn't work)
If I understand right, the driver comes along with a specific version of the kernel, so downgrading only the nvidia driver was not enough...
Downgrading to this specific combination of drivers + version of the kernel fixes the issue for me
nvidia 550.90.07-4
nvidia-settings 555.58-1
nvidia-utils 550.90.07-4
linux 6.9.6.arch1-1
linux-headers 6.9.6.arch1-1
but I'm really not a fan of pinning the kernel version :'(
If someone has a better idea, I'd be glad to hearing from them
Offline
You can avoid pinning the kernel version by downgrading to the appropriate nvidia-dkms variant of 550.90.07 so the nvidia module gets automatically rebuilt for the kernel you have installed.
FWIW since it seems pretty clear there's a regression in specifically the DVI implementation, has anyone reported the problem to the nvidia bbs? -- There's at least this one: https://forums.developer.nvidia.com/t/5 … 293652/173
Last edited by V1del (2024-07-03 12:06:54)
Online
You can avoid pinning the kernel version by downgrading to the appropriate nvidia-dkms variant of 550.90.07 so the nvidia module gets automatically rebuilt for the kernel you have installed.
Thanks for the tip, it works :-)
Offline
I have the same issue with Nvidia 555 after I updated it yesterday. I saw another thread on the Gentoo forum where someone suggested disabling GSP firmware to fix the issue. For me, it's already disabled as I use GTX 1060 so I guess we need a fix from Nvidia. For now, I've downgraded everything to last week as a workaround.
I have a GTX 1650 and to be sure I tried disabling the GSP firmware and it didn't work
Offline
I think the actual issue could be with HDMI. I have the same problem with a single monitor connected through an HDMI port, but all display ports work just fine.
Offline
I've i single monitor
The problem appears when the monitor is connected with the DVI port.
While if I use the HDMI it works fine.
Offline
I've been using a DVI to HDMI adapter on my GTX 1050. After upgrading to the 555 drivers, I was not getting a signal to my monitor. However, using a DVI cable does work for me. Luckily, my monitor has a DVI port.
The adapter does work on the latest 550 drivers but not on 555.
Last edited by JimmyRoberts (2024-07-08 08:35:51)
Offline
If I were to downgrade to 550 along with downgrading my kernel - how do I know which version of the kernel (and related packages) I need to use?
Offline
If I were to downgrade to 550 along with downgrading my kernel - how do I know which version of the kernel (and related packages) I need to use?
550x seems to still work on 6.10 kernel (at least the dkms version) you shouldn't need to downgrade your kernel
Offline
The 550 dkms version does not appear to build anymore with kernel 6.12... if someone found a way to work around that issue, I'll be happy to hear it
Offline
What version do you have installed exactly? Version 550.135 builds fine for me with kernel 6.12
Offline