as mentioned in the title, I'm no longer able to load Ubuntu with the proprietary NVIDIA drivers since the update to kernel 3.13.0-27 and it is still not working for 29.
The nouveau drivers work fine, but as I'm using CUDA for some applications it won't do.
I tried to reinstall the drivers on several occasions (with sudo apt-get purge nvidia*
) but I always boot into the low graphics mode of the login screen and after login unity won't load.
I'm using nvidia-331-updates but also tried different versions, but all of them gave me the same results. Everything worked fine before the update and even after the update, until 3.13.0-29 I was able to load the drivers by starting with the 3.14.0-24 kernel. This, however, stopped working today with another update. I've also tried to re-install ubuntu-desktop and unity with no change in result. I've got an NVIDIA GTX 570. Any ideas?
Here's the output of lspci -nnk | grep -iA2 VGA
(after removing the nvidia drivers):
VGA compatible controller [0300]: NVIDIA Corporation GF110 [GeForce GTX 570 Rev. 2] [10de:1086] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:0871]
Kernel driver in use: nouveau
And here the output of grep -e '(EE)' /var/log/Xorg.0.log
(EE) Failed to load module "nvidia" (module does not exist, 0)
[ 19.612] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 19.652] (EE) [drm] KMS not enabled
[ 19.652] (EE) [drm] KMS not enabled
[ 19.652] (EE) open /dev/dri/card0: No such file or directory
[ 19.652] (EE) open /dev/dri/card0: No such file or directory
[ 19.652] (EE) open /dev/dri/card0: No such file or directory
[ 19.652] (EE) open /dev/dri/card0: No such file or directory
[ 19.667] (EE) Screen 0 deleted because of no matching config section.
[ 19.667] (EE) Screen 0 deleted because of no matching config section.
[ 19.700] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 19.735] (EE) AIGLX: reverting to software rendering
[ 20.383] (EE) FBDEV(0): FBIOBLANK: Invalid argument
lspci -nnk | grep -iA2 VGA
– JoKeR Jun 07 '14 at 06:47sudo nvidia-xconfig
was not recognized as a command, but I'm not sure whether that is related to the problem. – Tom Göckel Jun 10 '14 at 11:04