Strange Displaymanager Nvidia Behaviour long time solved

Topic: Strange Displaymanager Nvidia Behaviour long time solved (Read 1656 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Strange Displaymanager Nvidia Behaviour long time solved

20 February 2018, 04:04:56

Last update Nvidia was updated after reboot no display manager, no nvidia, no window manager nothing, can't login very strange.
Checked logs , systemd not found nvidia not found, what they they are both installed, clean reinstalled both systemd-dummy, Nvidia still no display manager ,checked in terminal lxdm enabled and working, login from command line good now starting desktop. still no display manager.
Enable displaymanager-openrc terminal reports already running again strange, reboot no displaymanager so finally I removed displaymanager-openrc, clean reinstalled and enabled changed xdm back to lxdm back working everything is now fine including a lag displaying icons fonts on 1st app opened on a new session

I have the skill to fix little things like this many users don't
Why did this happen in the 1st place

Re: Strange Displaymanager Nvidia Behaviour

Reply #1 – 23 March 2018, 23:07:33

I'm having the best luck so far with the DKMS version. Only issue I have with it is after a kernel or nvidia update you have to dkms autoinstall before you reboot or when the system comes back up you're dropped back to a console window that is flashing a million times a second and it's hard to get your password typed in between the flashes.

Code: [Select]

nvidia-dkms 390.42-4
nvidia-settings 390.42-1
nvidia-utils 390.42-1

Re: Strange Displaymanager Nvidia Behaviour

Reply #2 – 23 March 2018, 23:12:08

Quote from: mandog – on 20 February 2018, 04:04:56

Why did this happen in the 1st place

No idea, I am no longer on nvidia card.
If there was a dedicated maintainer for nvidia stuff, it would be welcome.

Re: Strange Displaymanager Nvidia Behaviour

Reply #3 – 24 March 2018, 01:16:01

what kernel are you on?
what display manager?
if you can get into console, are you able to do startx? what errors do you get?
what errors do you see in dmesge or /var/log/messages (or whatever log file you use)? what about /var/log/Xorg.0.log?
what about .xsession-errors?
try modprobe nvidia (as root) and see what dmesg spits out?
need a lot more info
i use nvidia with regular linux kernel and have no issues. i did get the "flashing console" with linux-ck and had to rebuild by hand to get it to work, but I ended up going back to play linux pacakge which works fine

Re: Strange Displaymanager Nvidia Behaviour long time solved

Reply #4 – 24 March 2018, 02:27:02

I put it here as a reference for others.

Re: Strange Displaymanager Nvidia Behaviour

Reply #5 – 24 March 2018, 17:46:44

Quote from: toxygen – on 24 March 2018, 01:16:01

what kernel are you on?
what display manager?
if you can get into console, are you able to do startx? what errors do you get?
what errors do you see in dmesge or /var/log/messages (or whatever log file you use)? what about /var/log/Xorg.0.log?
what about .xsession-errors?
try modprobe nvidia (as root) and see what dmesg spits out?
need a lot more info
i use nvidia with regular linux kernel and have no issues. i did get the "flashing console" with linux-ck and had to rebuild by hand to get it to work, but I ended up going back to play linux pacakge which works fine

For me it doesn't matter what version of the kernel or Nvidia driver it is. The issue for me is that after the updates, dkms isn't being called to build the module for the new kernel. If I forget to dkms autoinstall before rebooting the I'm stuck with the screen flash at a console. I haven't tried manually starting X because dkms autoinstall was the first thing I've ever done that fixed it right away. It takes me ~20 minutes to get my password entered properly while it's flashing so I usually don't mess around after finally getting in. If I had ssh enabled this would probably take a minute but I have Artix on a workstation that I don't leave remote access services running on because I'm in a large environment with a lot of bored developers that like to mess around. I had the same problem on Arch with ATI in the past and think at the time I just threw dkms autoinstall into /etc/rc.local so it would run on every reboot and I wouldn't have to worry about it. Also, running Cinnamon for a DE but this issue is before DE/DM launch.

Re: Strange Displaymanager Nvidia Behaviour long time solved

Reply #6 – 24 March 2018, 19:20:31

If you run the updates in a terminal dkms works it is pamac and buildiso that can't handle dkms yet?

Re: Strange Displaymanager Nvidia Behaviour long time solved

Reply #7 – 24 March 2018, 19:25:34

You might have just nailed it! I do use pamac for the update notifications and when I'm lazy I just click it and let it do the updates while I go back to working. For the next Nvidia or Kernel update I will test without using pamac. Thanks for pointing that out!