NVS 315 breaks with upgrade to 387.22 or 384.98
If I upgrade from 387.12 to 387.22, or try 384.98, I can see my initial kernel messages, but then lose both displays directly after that. I can't get anything on either X or VT. I've switched to using 381.22 because that version came up when I searched for NVS 315 drivers, and it works fine, but I'm not sure how to debug the issue with the newer drivers. I don't see any errors in dmesg. All I really see there is logs about mode setting and audio. Any advice? Thanks, Jameson
If I upgrade from 387.12 to 387.22, or try 384.98, I can see my initial kernel messages, but then lose both displays directly after that. I can't get anything on either X or VT. I've switched to using 381.22 because that version came up when I searched for NVS 315 drivers, and it works fine, but I'm not sure how to debug the issue with the newer drivers. I don't see any errors in dmesg. All I really see there is logs about mode setting and audio. Any advice?

Thanks,
Jameson

#1
Posted 11/03/2017 02:37 PM   
Please run nvidia-bug-report.sh and attach the nvidia-bug-report.log.gz file.
Please run nvidia-bug-report.sh and attach the nvidia-bug-report.log.gz file.

Aaron Plattner
NVIDIA Linux Graphics

#2
Posted 11/03/2017 04:38 PM   
I re-installed 387.22, and ran nvidia-bug-report.sh from a SSH session, and attached the results to the first post.
I re-installed 387.22, and ran nvidia-bug-report.sh from a SSH session, and attached the results to the first post.

#3
Posted 11/03/2017 07:15 PM   
I confirm same problem. When I've upgraded steamos, the new driver (387.22) led to blank screen on X loading.
I confirm same problem. When I've upgraded steamos, the new driver (387.22) led to blank screen on X loading.

#4
Posted 02/11/2018 12:08 PM   
mwprado, please also run nvidia-bug-report.sh as root and attach the resulting tar.gz file but first edit/create an xorg.conf setting [code]Option "ModeDebug" "true"[/code] in the device section.
mwprado, please also run nvidia-bug-report.sh as root and attach the resulting tar.gz file but first edit/create an xorg.conf setting
Option "ModeDebug" "true"

in the device section.

#5
Posted 02/11/2018 03:14 PM   
[quote=""]mwprado, please also run nvidia-bug-report.sh as root and attach the resulting tar.gz file but first edit/create an xorg.conf setting [code]Option "ModeDebug" "true"[/code] in the device section. [/quote] How do I attach I file here? I can't find a way.
said:mwprado, please also run nvidia-bug-report.sh as root and attach the resulting tar.gz file but first edit/create an xorg.conf setting
Option "ModeDebug" "true"

in the device section.


How do I attach I file here? I can't find a way.

#6
Posted 02/13/2018 04:38 PM   
Hover the mouse over your post and a paperclip will appear.
Hover the mouse over your post and a paperclip will appear.

#7
Posted 02/13/2018 04:52 PM   
oh, thanks!
oh, thanks!

#8
Posted 02/13/2018 05:14 PM   
Please put Option "ModeDebug" "true" in the device section of /etc/X11/xorg.conf. You put it in the nvidia outputclass which has only effect if there's no xorg.conf. Then run nvidia-bug-report.sh again.
Please put
Option "ModeDebug" "true"
in the device section of /etc/X11/xorg.conf. You put it in the nvidia outputclass which has only effect if there's no xorg.conf. Then run nvidia-bug-report.sh again.

#9
Posted 02/13/2018 05:38 PM   
[quote=""]Please put Option "ModeDebug" "true" in the device section of /etc/X11/xorg.conf. You put it in the nvidia outputclass which has only effect if there's no xorg.conf. Then run nvidia-bug-report.sh again.[/quote] new file:
said:Please put
Option "ModeDebug" "true"
in the device section of /etc/X11/xorg.conf. You put it in the nvidia outputclass which has only effect if there's no xorg.conf. Then run nvidia-bug-report.sh again.



new file:

#10
Posted 02/14/2018 06:09 PM   
Does this problem still occur with 390.25?
Does this problem still occur with 390.25?

Aaron Plattner
NVIDIA Linux Graphics

#11
Posted 02/14/2018 06:22 PM   
I have not tried it yet.
I have not tried it yet.

#12
Posted 02/14/2018 07:40 PM   
I haven't seen the issue with 390.25.
Answer Accepted by Forum Admin
I haven't seen the issue with 390.25.

#13
Posted 02/15/2018 01:38 PM   
Great, thanks for confirming!
Great, thanks for confirming!

Aaron Plattner
NVIDIA Linux Graphics

#14
Posted 02/15/2018 05:18 PM   
Scroll To Top

Add Reply