Blue screen with server x error message after nvidia driver update

Screen resolution, 3D Acceleration, nVidia, ATI
Forum rules
Before you post please read this
GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Wed Jun 19, 2019 7:33 pm

I recently update my nvidia drivers from 410 to 430, but after reboot I got the blue screen of death with an error message,
"The server X is now disabled. Restart MDM when it is configured correctly"
I hit
"ok"
and a second message popped up,
"Failed to start the X server (your graphical interface). It is likely that it is not setup correctly. Would you like to view the X server output to diagnose the problem?"
Which just led back to the first message.
I've tried booting and going through grub with nomodeset and it worked but I couldn't get into my server X settings and my pc wouldn't use any older drivers even after I re-downloaded them. Last thing I could think of was try reinstalling the 430 drivers...this was a mistake as I am back with the error screen, but this time nomodeset isn't wanting to work. Please, any help would be great! (I am running linux mint 18 sarah)

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Mon Jun 24, 2019 10:51 pm

Any suggestions would be great! :D

User avatar
WharfRat
Level 21
Level 21
Posts: 13376
Joined: Thu Apr 07, 2011 8:15 pm

Re: Blue screen with server x error message after nvidia driver update

Post by WharfRat » Tue Jun 25, 2019 8:42 am

Did you install the drivers from the repos or dl them from the nvidia site :?:

What I would recommend is to try and revert back to the open source nouveau driver to be able to boot.

I'm also moving this topic to Graphics Cards & Monitors since your problem is graphics driver related.
ImageImage

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Thu Jun 27, 2019 1:03 am

The 430 driver popped up in my driver manager as a new driver version and I installed it there... Can you walk me through how to revert back to the open source divers since I am unable to get to my desktop or anything past the blue screen.

User avatar
WharfRat
Level 21
Level 21
Posts: 13376
Joined: Thu Apr 07, 2011 8:15 pm

Re: Blue screen with server x error message after nvidia driver update

Post by WharfRat » Thu Jun 27, 2019 11:43 am

Boot the installation media and mount the root partition to /mnt.

If you don't know how to do that paste back sudo blkid from the live session.
ImageImage

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Fri Jun 28, 2019 7:18 pm

I'll give it a try.

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Tue Jul 02, 2019 1:15 am

My cd driver was having some problems (getting a new one) so in the meantime I tried checking out some options in recovery mode, and after an update was able to get into my pc.....but my resolution is stuck 1024x768 and I am unable to open NVIDIA X server settings (just like when I used nomodeset). Does this help at all or should I get a cd drive and go ahead and try to mount my root partition to /mnt?

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Tue Jul 02, 2019 1:17 am

WharfRat wrote:
Thu Jun 27, 2019 11:43 am
Boot the installation media and mount the root partition to /mnt.

If you don't know how to do that paste back sudo blkid from the live session.
Results from sudo blkid

/dev/sdb1: UUID="64943C48943C1ECC" TYPE="ntfs" PARTUUID="6c2aaca2-01"
/dev/sdb2: UUID="18F4AEE3F4AEC27C" TYPE="ntfs" PARTUUID="6c2aaca2-02"
/dev/sda1: UUID="8033-C77E" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="57aedfea-ef2d-4de1-bc9c-32860e70ed3d"
/dev/sda2: UUID="109ab695-a58f-48b2-924f-f47d057cb5bd" TYPE="ext4" PARTUUID="39f0888d-e646-44f3-b819-5d6e39dc9c56"
/dev/sda3: UUID="c4537f5c-f6a9-455d-b754-80509ea5a3fe" TYPE="swap" PARTUUID="26f28972-8ce5-4548-b9ac-050df97d1645"
/dev/sdc1: LABEL="ENDER" UUID="705E190C5E18CCAA" TYPE="ntfs" PARTUUID="c3072e18-01"

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Fri Jul 12, 2019 12:00 am

......... :?:

User avatar
WharfRat
Level 21
Level 21
Posts: 13376
Joined: Thu Apr 07, 2011 8:15 pm

Re: Blue screen with server x error message after nvidia driver update

Post by WharfRat » Fri Jul 12, 2019 6:41 am

If you can get into recovery mode then remove the nvidia driver from there.

apt search nvidia|grep ^i will identify the installed driver and use sudo apt-get purge driver_name to remove it.
ImageImage

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Mon Jul 15, 2019 11:15 pm

Ok I'll do that that.

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Wed Jul 17, 2019 1:15 pm

I purged the nvidia driver, what next?

User avatar
WharfRat
Level 21
Level 21
Posts: 13376
Joined: Thu Apr 07, 2011 8:15 pm

Re: Blue screen with server x error message after nvidia driver update

Post by WharfRat » Wed Jul 17, 2019 4:56 pm

Check for a file /etc/X11/xorg.conf and delete it.

Also if grep nouveau /etc/modprobe.d/* lists a file delete it.
ImageImage

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Fri Jul 19, 2019 12:35 pm

When I did /etc/X11/xorg.conf I got "No such file or directory" and same with "grep nouveau /etc/modprobe.d/*"

User avatar
WharfRat
Level 21
Level 21
Posts: 13376
Joined: Thu Apr 07, 2011 8:15 pm

Re: Blue screen with server x error message after nvidia driver update

Post by WharfRat » Fri Jul 19, 2019 12:52 pm

Try rebuilding the initrd.img using the following booted to the live media

Code: Select all

sudo -i
mount /dev/sda2 /mnt 
mount /dev/sda1 /mnt/boot/efi
mount -t proc none /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev
/usr/sbin/chroot /mnt /bin/bash
source /etc/profile
echo "nameserver 8.8.8.8" >> /etc/resolv.conf
export PS1="\[\033[1;33m\]chroot to ->\[\033[1;31m\](system) #\[\e[0m\] "
/etc/kernel/postinst.d/initramfs-tools all
exit
reboot
ImageImage

User avatar
roblm
Level 11
Level 11
Posts: 3575
Joined: Sun Feb 24, 2013 2:41 pm

Re: Blue screen with server x error message after nvidia driver update

Post by roblm » Fri Jul 19, 2019 1:22 pm

GhostlyIce wrote:
Fri Jul 19, 2019 12:35 pm
When I did /etc/X11/xorg.conf I got "No such file or directory" and same with "grep nouveau /etc/modprobe.d/*"
Newer Nvidia driver version installations may create the nvidia-graphics-drivers.conf file, which blacklists the nouveau driver, in /lib/modprobe.d.

So modify WharfRat’s command to this: grep nouveau /lib/modprobe.d/*


EDITED: If that file is found, then also use this command after removing it, and then reboot: sudo update-initramfs -u

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Sun Jul 21, 2019 10:30 am

roblm wrote:
Fri Jul 19, 2019 1:22 pm
GhostlyIce wrote:
Fri Jul 19, 2019 12:35 pm
When I did /etc/X11/xorg.conf I got "No such file or directory" and same with "grep nouveau /etc/modprobe.d/*"
Newer Nvidia driver version installations may create the nvidia-graphics-drivers.conf file, which blacklists the nouveau driver, in /lib/modprobe.d.

So modify WharfRat’s command to this: grep nouveau /lib/modprobe.d/*


EDITED: If that file is found, then also use this command after removing it, and then reboot: sudo update-initramfs -u
/lib/modprobe.d/aliases.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-101-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-103-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-104-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-109-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-112-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-116-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-119-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-122-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-124-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-127-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-128-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-130-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-131-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-133-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-134-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-135-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-137-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-138-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-139-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-140-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-141-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-142-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-143-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-145-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-146-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-148-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-154-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-21-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-53-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-57-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-59-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-62-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-63-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-64-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-66-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-67-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-70-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-71-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-72-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-75-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-77-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-78-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-79-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-81-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-83-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-87-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-89-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-91-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-92-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-93-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-96-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-97-generic.conf: ASCII text
/lib/modprobe.d/blacklist_linux_4.4.0-98-generic.conf: ASCII text

^ this is what I got when I typed in file grep nouveau /lib/modprobe.d/*

update-initramfs: Generating /boot/initrd.img-4.4.0-154-generic
cp: cannot stat '/etc/modprobe.d/*': No such file or directory
Warning: No support for locale: en_US.utf8

^ this was from sudo update-initramfs -u

User avatar
roblm
Level 11
Level 11
Posts: 3575
Joined: Sun Feb 24, 2013 2:41 pm

Re: Blue screen with server x error message after nvidia driver update

Post by roblm » Sun Jul 21, 2019 12:17 pm

Use this command to upload the Xorg.0.log file to terminal.com pastebin:
cat /var/log/Xorg.0.log | nc termbin.com 9999

Post the URL link that displays in the Terminal window.

GhostlyIce
Level 1
Level 1
Posts: 20
Joined: Wed Jun 19, 2019 7:09 pm

Re: Blue screen with server x error message after nvidia driver update

Post by GhostlyIce » Mon Jul 22, 2019 11:07 pm


User avatar
roblm
Level 11
Level 11
Posts: 3575
Joined: Sun Feb 24, 2013 2:41 pm

Re: Blue screen with server x error message after nvidia driver update

Post by roblm » Tue Jul 23, 2019 7:22 pm

Use this command and then reboot: apt purge *nvidia*

Upload the Xorg.0.log file again: cat /var/log/Xorg.0.log | nc termbin.com 9999

Post the URL link that displays in the Terminal window.

Post Reply

Return to “Graphics Cards & Monitors”