black screen when installing nvidia driver

seth · 2018-04-22 12:50:06

all with the same result

lightdm used to show but can't launch plasma

This is going absolutely nowhere unless you elaborate on your attempted setups and the actual failure (what you see, what you'd expect, what you do, what happens - and logs)
Right now, we're still at a "it doesn't work" level "description" of the poblem - nobody can help you on this base.

Skunky · 2018-04-22 12:57:16

If can help enabling nvidia-persistenced.service with systemctl solved some issues for me (i'm using nvidia 650M)

Last edited by Skunky (2018-04-22 12:57:56)

V1del · 2018-04-22 13:12:38

Agreed with seth, please stop creating moving goal posts. Focus on getting one setup working correctly. GDM is known for being able to do "more" which might further potential issues. Stay on SDDM for now. Can you confirm that you get an actual working setup with SDDM, apart from suspend? I.e. you can start plasma or whatever and

glxinfo | grep OpenGL

returns the Nvidia renderer? If that works and suspend "breaks" the system. Are you sure it is broken? Can you switch TTYs? If you cannot and your only option really is a hard reboot, enable REISUB reproduce the "crash" execute the REISUB sequence and post the complete output of a

journalctl -b-1

on the next boot.

step-2 · 2018-04-22 13:17:48

seth wrote:

all with the same result
lightdm used to show but can't launch plasma
This is going absolutely nowhere unless you elaborate on your attempted setups and the actual failure (what you see, what you'd expect, what you do, what happens - and logs)
Right now, we're still at a "it doesn't work" level "description" of the poblem - nobody can help you on this base.

sure , sorry about that ,

before doing any config or following the wiki with just nvidia driver installed sddm gives black screen with no backilght , xdm and lightdm works but can't launch any DE (xf86-video-intel were installed at this point),

after following the wiki no DM works except gdm and can launch gnome and plasma , after suspending the laptop i get a black screen and freeze which nothing fix but a hard reboot ,

my config :

https://wiki.archlinux.org/index.php/NV … ing_nvidia
https://wiki.archlinux.org/index.php/NVIDIA_Optimus#GDM
https://wiki.archlinux.org/index.php/NV … BBackspace
https://wiki.archlinux.org/index.php/NV … X_shutdown
https://wiki.archlinux.org/index.php/NV … tarts_fine

Last edited by step-2 (2018-04-22 13:20:52)

seth · 2018-04-22 13:23:29

can't launch any DE

is NOT a usable error description. Why can't they? What happens?
Your config are the files on your disk, not some wiki articles.

I'd rather suggest to get any DM out of the way and work on getting xinit/startx working. Ensure to install xterm & twm or post your xinitrc.

On the suspend issue, I suspect GDM to be the reason, in particular the fact that it will spawn an extra display server for the session.
In any case you should attempt to remote-access the system in this state, in case only the graphics stack/output is affected, this will allow a live inspection of the issue.

step-2 · 2018-04-22 13:29:06

seth wrote:

can't launch any DE
is NOT a usable error description. Why can't they? What happens?
Your config are the files on your disk, not some wiki articles.
I'd rather suggest to get any DM out of the way and work on getting xinit/startx working. Ensure to install xterm & twm or post your xinitrc.
On the suspend issue, I suspect GDM to be the reason, in particular the fact that it will spawn an extra display server for the session.
In any case you should attempt to remote-access the system in this state, in case only the graphics stack/output is affected, this will allow a live inspection of the issue.

sure here is som logs , xdm log :

https://pastebin.com/YMiuWjZH

X logs :

https://pastebin.com/EJF8skf1

https://pastebin.com/bFXadDF7

https://pastebin.com/QDr78z4y

Xinitrc file :

https://pastebin.com/8BAPE7hS

Last edited by step-2 (2018-04-22 13:32:20)

step-2 · 2018-04-22 13:35:21

V1del wrote:

Agreed with seth, please stop creating moving goal posts. Focus on getting one setup working correctly. GDM is known for being able to do "more" which might further potential issues. Stay on SDDM for now. Can you confirm that you get an actual working setup with SDDM, apart from suspend? I.e. you can start plasma or whatever and
glxinfo | grep OpenGL
returns the Nvidia renderer? If that works and suspend "breaks" the system. Are you sure it is broken? Can you switch TTYs? If you cannot and your only option really is a hard reboot, enable REISUB reproduce the "crash" execute the REISUB sequence and post the complete output of a
journalctl -b-1
on the next boot.

glxinfo | grep OpenGL :

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 940M/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 390.48
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 390.48
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.48
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

sorry but sddm won't sart unless i uninstall nvidia and remove /etc/X11/xorg.conf

and no i can't switch TTY , and sure will try your suggestion .

Last edited by step-2 (2018-04-22 13:46:01)

step-2 · 2018-04-22 13:52:43

.xsession-errors :

https://pastebin.com/1DBTvDTY

step-2 · 2018-04-22 14:22:38

V1del wrote:

Agreed with seth, please stop creating moving goal posts. Focus on getting one setup working correctly. GDM is known for being able to do "more" which might further potential issues. Stay on SDDM for now. Can you confirm that you get an actual working setup with SDDM, apart from suspend? I.e. you can start plasma or whatever and
glxinfo | grep OpenGL
returns the Nvidia renderer? If that works and suspend "breaks" the system. Are you sure it is broken? Can you switch TTYs? If you cannot and your only option really is a hard reboot, enable REISUB reproduce the "crash" execute the REISUB sequence and post the complete output of a
journalctl -b-1
on the next boot.

after deleting all the configs i got sddm to work with autologin , but the suspend issue still persist .

Last edited by step-2 (2018-04-22 14:23:14)

step-2 · 2018-04-22 16:15:24

also don't know what this mean :

https://i.imgur.com/yBHL1ab.png

V1del · 2018-04-22 16:32:47

Exactly what it says on the tin, use a generic xrandr compatible utility to control that, if you must. But this also shows that the prime setup works correctly. Have you tried Skunky's suggestion? And can you still post the journal output from recovering after a freeze? Also please don't bump your posts and rather make edits if there hasn't been another answer in between.

Last edited by V1del (2018-04-22 16:33:09)

step-2 · 2018-04-22 16:55:02

V1del wrote:

Exactly what it says on the tin, use a generic xrandr compatible utility to control that, if you must. But this also shows that the prime setup works correctly. Have you tried Skunky's suggestion? And can you still post the journal output from recovering after a freeze? Also please don't bump your posts and rather make edits if there hasn't been another answer in between.

yes i have tried Skunky's suggestion ,

sorry did'nt mean to bump , just trying to provide information .

journal :

https://pastebin.com/7Ydwqdsi

Last edited by step-2 (2018-04-22 17:14:16)

V1del · 2018-04-24 20:14:05

That looks truncated, use --no-pager or redirect into a file for the complete output. Also regarding Skunky's suggestion, you only enabled that directly in that session from which you provided the log. A simple enable will only activate the corresponding service on the next boot, so it will not have been active when the error occurred.

step-2 · 2018-04-24 20:27:11

V1del wrote:

That looks truncated, use --no-pager or redirect into a file for the complete output. Also regarding Skunky's suggestion, you only enabled that directly in that session from which you provided the log. A simple enable will only activate the corresponding service on the next boot, so it will not have been active when the error occurred.

It is truncated , is there a way to output it to file ?

And yes i mad sure to reboot after skunky's suggestion .

step-2 · 2018-04-28 02:03:58

does this mean anything :

https://i.imgur.com/C51x6ef.jpg

Arch Linux

#26 2018-04-22 12:50:06

Re: black screen when installing nvidia driver

#27 2018-04-22 12:57:16

Re: black screen when installing nvidia driver

#28 2018-04-22 13:12:38

Re: black screen when installing nvidia driver

#29 2018-04-22 13:17:48

Re: black screen when installing nvidia driver

#30 2018-04-22 13:23:29

Re: black screen when installing nvidia driver

#31 2018-04-22 13:29:06

Re: black screen when installing nvidia driver

#32 2018-04-22 13:35:21

Re: black screen when installing nvidia driver

#33 2018-04-22 13:52:43

Re: black screen when installing nvidia driver

#34 2018-04-22 14:22:38

Re: black screen when installing nvidia driver

#35 2018-04-22 16:15:24

Re: black screen when installing nvidia driver

#36 2018-04-22 16:32:47

Re: black screen when installing nvidia driver

#37 2018-04-22 16:55:02

Re: black screen when installing nvidia driver

#38 2018-04-24 20:14:05

Re: black screen when installing nvidia driver

#39 2018-04-24 20:27:11

Re: black screen when installing nvidia driver

#40 2018-04-28 02:03:58

Re: black screen when installing nvidia driver

Board footer