Black screen after update. Cant boot from 39-generic

[PungPillaren]

Hi!

I got notified there were updates available so I just installed them like normal and pressed the restart icon when it was done.
Now the computer won't boot.
After grub I see the standard kubuntu loading screen (kubuntu and 5 dots) and after that I get this a black screen with a blinking brown/orange cursor.


Specs:
Kubuntu 14.04, installed last weekend.
Dual boot with windows 7
I only use 23gb of 230gb (500gb ssd with dual boot, split 50/50).
Video card is nvidia 770
Dual monitors



I've tried booting with 37-generic and it didn't work either, so I ran 37-generic recovery mode and did the following:
When I tried to ran startx I got a "cant lock file" problem so I ran fcsk to put the disk into read/write mode. Fcsk ran ok.
After the fcsk i could run startx. After it started i get the KDE Crash handler saying plasma-desktop and KDE daemon has stopped working.
I tried to run plasma-desktop and it crashed instantly and I got quite an output. I don't know what it all means but I get phrases such as:
"QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave."
I then ran: "rm -f /root/.X*" and "rm -f /home/<user>/.X*" because I still got some errors regarding .XAuthority
After that I could boot normally into 37-generic but not 39.

When I try to run startx from 39-generic I just get a black screen and a blinking white cursor.


Everything was working fine this morning.
Is there something in the new kernel that is messing up my system?

Any help is appreciated.

[oshunluvr]

Sounds like a video issue.
Can you get to text mode with CRTL-ATL-F1 from 39? If not, boot to 37 then, from either text mode with 39 or in a konsole in 37:

dkms status

If the new kernel does not have your nvidia driver listed as "installed", then install the linux-headers for 39 and let dkms re-build

sudo apt-get install linux-headers-3.13.0-39-generic

then reboot again

[PungPillaren]

"dkms status" - nvidia (and bbswitch) drivers installed for all kernels (32, 37, 39) on both 39 and 37.

I checked package manager and linux-.headers-3.13.0-39-generic is installed.

[vinnywright]

Humm ....just got home ,,,,and see the new kernel upgrade @hear ,,,,,,,,will install (now)and see if we get breakage.

VINNY

[oshunluvr]

Any errors worth mentioning in Xorg.0.log or system.log?

[vinnywright]

console output looks good .............................................

Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-3.13.0-39 linux-headers-3.13.0-39-generic
  linux-image-3.13.0-39-generic linux-image-extra-3.13.0-39-generic
The following packages will be upgraded:
  linux-generic linux-headers-generic linux-image-generic linux-libc-dev
4 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 62.3 MB of archives.
After this operation, 271 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-3.13.0-39-generic amd64 3.13.0-39.66 [15.2 MB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-extra-3.13.0-39-generic amd64 3.13.0-39.66 [36.7 MB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-generic amd64 3.13.0.39.46 [1,784 B]
Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-generic amd64 3.13.0.39.46 [2,418 B]
Get:5 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-headers-3.13.0-39 all 3.13.0-39.66 [8,892 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-headers-3.13.0-39-generic amd64 3.13.0-39.66 [728 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-headers-generic amd64 3.13.0.39.46 [2,404 B]
Get:8 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-libc-dev amd64 3.13.0-39.66 [798 kB]
Fetched 62.3 MB in 47s (1,315 kB/s)                                            
Selecting previously unselected package linux-image-3.13.0-39-generic.
(Reading database ... 176849 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-39-generic_3.13.0-39.66_amd64.deb ...
Done.
Unpacking linux-image-3.13.0-39-generic (3.13.0-39.66) ...
Selecting previously unselected package linux-image-extra-3.13.0-39-generic.
Preparing to unpack .../linux-image-extra-3.13.0-39-generic_3.13.0-39.66_amd64.deb ...
Unpacking linux-image-extra-3.13.0-39-generic (3.13.0-39.66) ...
Preparing to unpack .../linux-generic_3.13.0.39.46_amd64.deb ...
Unpacking linux-generic (3.13.0.39.46) over (3.13.0.37.44) ...
Preparing to unpack .../linux-image-generic_3.13.0.39.46_amd64.deb ...
Unpacking linux-image-generic (3.13.0.39.46) over (3.13.0.37.44) ...
Selecting previously unselected package linux-headers-3.13.0-39.
Preparing to unpack .../linux-headers-3.13.0-39_3.13.0-39.66_all.deb ...
Unpacking linux-headers-3.13.0-39 (3.13.0-39.66) ...
Selecting previously unselected package linux-headers-3.13.0-39-generic.
Preparing to unpack .../linux-headers-3.13.0-39-generic_3.13.0-39.66_amd64.deb ...
Unpacking linux-headers-3.13.0-39-generic (3.13.0-39.66) ...
Preparing to unpack .../linux-headers-generic_3.13.0.39.46_amd64.deb ...
Unpacking linux-headers-generic (3.13.0.39.46) over (3.13.0.37.44) ...
Preparing to unpack .../linux-libc-dev_3.13.0-39.66_amd64.deb ...
Unpacking linux-libc-dev:amd64 (3.13.0-39.66) over (3.13.0-37.64) ...
Setting up linux-image-3.13.0-39-generic (3.13.0-39.66) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-39-generic
Found initrd image: /boot/initrd.img-3.13.0-39-generic
Found linux image: /boot/vmlinuz-3.13.0-37-generic
Found initrd image: /boot/initrd.img-3.13.0-37-generic
Found linux image: /boot/vmlinuz-3.13.0-32-generic
Found initrd image: /boot/initrd.img-3.13.0-32-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 14.04.1 LTS (14.04) on /dev/sda1
Found Ubuntu 14.10 (14.10) on /dev/sda5
done
Setting up linux-image-extra-3.13.0-39-generic (3.13.0-39.66) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-39-generic
Found initrd image: /boot/initrd.img-3.13.0-39-generic
Found linux image: /boot/vmlinuz-3.13.0-37-generic
Found initrd image: /boot/initrd.img-3.13.0-37-generic
Found linux image: /boot/vmlinuz-3.13.0-32-generic
Found initrd image: /boot/initrd.img-3.13.0-32-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 14.04.1 LTS (14.04) on /dev/sda1
Found Ubuntu 14.10 (14.10) on /dev/sda5
done
Setting up linux-image-generic (3.13.0.39.46) ...
Setting up linux-headers-3.13.0-39 (3.13.0-39.66) ...
Setting up linux-headers-3.13.0-39-generic (3.13.0-39.66) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-39-generic /boot/vmlinuz-3.13.0-39-generic
Setting up linux-headers-generic (3.13.0.39.46) ...
Setting up linux-generic (3.13.0.39.46) ...
Setting up linux-libc-dev:amd64 (3.13.0-39.66) ...
vinny@vinny-Bonobo-Extreme:~$ dkms status
bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed
bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
nvidia-331-updates, 331.38, 3.13.0-32-generic, x86_64: installed
nvidia-331-updates, 331.38, 3.13.0-37-generic, x86_64: installed
nvidia-331-updates, 331.38, 3.13.0-39-generic, x86_64: installed
vinny@vinny-Bonobo-Extreme:~$

time to reboot .............

VINNY

[vinnywright]

no problems @ hear ,,,,,,,

I started to think that since you had a .Xauthority problem you may have other permission problems ,,,,,,,,,but you boot fine in the old kernel so maby not.

VINNY

[PungPillaren]

Maybe this?
syslog:

NVRM: API mismatch: the client has the version 340.46, but this kernel module has the version 331.38. Please make sure that this kernel module and all NVIDIA driver components have the same version.
NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22
X-server died during startup
X-server for display :0 cannot be started, session disabled.

After I installed kubuntu, the OS installed the 331 drivers (which are the ones who show up in dkms status), but I checked nvidias homepage right afterwards and found the latest drivers which are 340. I downloaded and ran the .run file.
I don't know if the installation was successful since it was just a black screen with a blinking cursor after i ran the file, but the system worked fine after reboot anyway.
I guess it got somewhat half done.

I assume I have to uninstall this 340 driver, but I don't know how. There is no package installed for it.

[oshunluvr]

Well, now we know your problem. The nVidia drivers available from the repositories are packaged for Ubuntu. The ones you downloaded from nVidia are not. The biggest differences: The nVidia driver puts some of the files in different locations. If you stick with the Ubuntu drivers you will get update notifications, from nVidia you will not. The Ubuntu drivers will let you install them while using the GUI and then reboot when it's convenient, nVidia's will not.

Since the nVidia drivers install from a binary and not a deb package, you're going to have to search the web to find out how to delete all the files associated with the binary and clean them from your system. You may potentially have to purge all nVidia stuff, locate what's left and delete it, then re-install.

I don't know if you're new to Linux or new to the Ubuntu world or just new to this forum: But generally, anytime you install something from outside the Debian/Ubuntu world there is a potential for problems. I wouldn't hesitate to try out a game or some new app that looks cool, but I would advise staying away from drivers unless they are absolutely required (as in your video card wasn't working at all with the current Ubuntu drivers) and you do a fair amount of research to be sure you're not going to render your system unusable. The Ubuntu drivers rarely drag more than a few weeks or months behind their binary releases and that time is spent packaging and testing them so the developers know they work with Ubuntu. Consider that a bonus - not a delay.

Frankly, unless you have a lot of time invested in your current install, you might be better off re-installing from scratch. It will take less time than seeking out the conflicts.

[PungPillaren]

Yeah I thought it was this bad. I'm not new to Linux, just new to the graphical/driver part of it. The drivers on linux were so far behind the ones on Windows so I thought an update would fix it. I guess I learned my lesson
I spent a full day configuring applications and installing a theme, so I might just run on 37 for a while and reinstall in the future.

Thanks for your help!

[oshunluvr]

Alternately, you could purge the Ubuntu drivers and re-install from the nVidia binary. Maybe, if you hang on a bit the 340 drivers will become available from Ubuntu and maybe the update will solve the issue. Sorry I don't have better news for you.

[PungPillaren]

I did one last shot and ran
./NVIDIA-340.48.run --uninstall

It purged it successfully.
I booted 39 and got to the login screen (which is weird because I login automatically). But when I tried to login the screen flickered and returned to the login screen again.
In the system log it said it couldnt find the file /usr/share/kde/.../.default.face (cant remember exact path).

After that I gave up and reinstalled.

[oshunluvr]

Not finding the default face is not a fatal error. Usually, when you get a looping login (which is why you didn't get to autologin) it's because either your home is full or a needed file in your home has become owned by root.

Likely, this could have been tracked down and fixed - but too late.

If this happens again - switch to terminal mode and log in there. Then check your /home and fullness of your partitions.

[PungPillaren]

Yeah, I actually did a chown + chmod but it didnt work. I also tried removing .XAuthority again.
Neither of those thing did anything.

My partition was at 10% (25/250gb)

Anyway, all is well now. It didn't take too long to re-install and configure. And now I won't dabble with any non-ubuntu drivers