Discussion:
What is going on with my display? (Debugging commands requested)
(too old to reply)
Jean-Pierre
2015-01-12 14:51:54 UTC
Permalink
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?

Something funny is going on, but I don't know what
and only need debugging commands.

Again, I repeat: I ask for help in DEBUGGING commands.

Here is the gory detail (but the request is for
debugging commands so that I UNDERSTAND what is
going on).

The Lenovo W510 laptop display was fine, for two days
(see previous thread).

Then the machine locked up, so I forced a hard button
shutdown, and when it came up, the screen was at
1024x768 instead of 1920x1080.

The funny thing was that the Nvidia driver was
in place according to the command line but
according to KDE System Settings, nouveau was
installed.

I tried to re-install the Nvidia driver using
KDE System Settings "Driver Manager", but it
wouldn't allow the "Apply" button (it was
greyed out) so I chose an earlier Nvidia driver
in the selection, and rebooted.
Loading Image...

The Nvidia driver is definitely loaded:
Loading Image...

As witnessed by:
$ modprobe -R nvidia
nvidia_331_updates

Yet, the display is limited to 1024x768:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0
848x480 0.0
640x480 60.0

The KDE System Settings "Display and Monitor"
are showing only "default" settings of
1024x768, even though the same GUI shows that
the Nvidia drivers are installed.
Loading Image...

The Google inxi -F command used to show that
LVDS-1 was connected primary 1920x1080, but
now it shows that the screen resolution is
limited to 1024x768.

$ inxi -F
Graphics:
Card: NVIDIA GT216GLM [Quadro FX 880M]
X.Org: 1.15.1 drivers: nvidia,fbdev,vesa,nouveau
Resolution: ***@61.0hz
GLX Renderer: N/A GLX Version: N/A

But the xdriinfo and glxinfo commands don't
tell us much.

$ xdriinfo
libGL is too old.

$ glxinfo
name of display: :0
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".

My grub was modified days before this happened:
$ grep CMDLINE /etc/default/grub
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""

And the modprobe directory file seems correct:
$ cat /etc/modprobe.d/nvidia-graphics-drivers.conf
# This file was installed by nvidia-331-updates
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-331
alias nvidia nvidia_331_updates
alias nvidia-uvm nvidia_331_updates-uvm
alias nouveau off

The controller card didn't change:
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2)

Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
William Unruh
2015-01-12 15:04:57 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
No. but do not rule out hardware problems.
Post by Jean-Pierre
Q2: Do you have any other DEBUGGING commands?
Something funny is going on, but I don't know what
and only need debugging commands.
Again, I repeat: I ask for help in DEBUGGING commands.
Why would you limit the help you get to debuggin commands?
Post by Jean-Pierre
Here is the gory detail (but the request is for
debugging commands so that I UNDERSTAND what is
going on).
Is your primary purpose to fix it, or to understand it? Had it not gone
wrong would you still be asking us for debugging commands or would you
have been happy to use it?
Post by Jean-Pierre
The Lenovo W510 laptop display was fine, for two days
(see previous thread).
video can be key reason for locking up. Driver or hardware problems.
Post by Jean-Pierre
Then the machine locked up, so I forced a hard button
shutdown, and when it came up, the screen was at
1024x768 instead of 1920x1080.
The funny thing was that the Nvidia driver was
in place according to the command line but
according to KDE System Settings, nouveau was
installed.
I tried to re-install the Nvidia driver using
KDE System Settings "Driver Manager", but it
wouldn't allow the "Apply" button (it was
greyed out) so I chose an earlier Nvidia driver
in the selection, and rebooted.
http://i59.tinypic.com/2nasp38.png
http://i58.tinypic.com/2r2pxrm.png
Is the noveau driver also loaded?
Jean-Pierre
2015-01-12 15:22:45 UTC
Permalink
Post by William Unruh
Why would you limit the help you get to debuggin commands?
Because I'm trying to figure out what is going on.
William Unruh
2015-01-12 15:45:43 UTC
Permalink
Post by Jean-Pierre
Post by William Unruh
Why would you limit the help you get to debuggin commands?
Because I'm trying to figure out what is going on.
To fix it or for its own sake?
I suspect to fix it, but then why would you want to limit the responses?
Note that one could always point you to the source code (although that
could be hard for the nvidia driver I admit).
Anyway, my guess is hardware problem, which would imply that there is
nothing to understand (what would you do if you discovered it was due to
a fried capacitor?)

Anyway, to "rule that out" try booting with Windows and see if the
problem persists. Or try reinstalling and see if the problem persisits
(Yes those are both debugging techniques)
Jean-Pierre
2015-01-12 16:09:29 UTC
Permalink
Post by William Unruh
To fix it or for its own sake?
1. If it would just work, I'd be very happy.
2. If I could fix it, without knowing what's
going on, I'd still be very happy.
3. If I could use some other driver than Nvidia,
and if it worked, I'd still be happy.

I just want my display back.

I've tried three attempts in the interim, and
all failed. Nvidia gives a seemingly good
log file, but it uses cryptic words.

For example:
The distribution-provided pre-install script failed!
Failed to install the kernel module through DKMS.
ERROR: Unable to find the kernel source tree for
the currently running kernel. Please make sure
you have installed the kernel source files for
your kernel and that they are properly configured;
on Red Hat Linux systems, for example, be sure you
have the 'kernel-source' or 'kernel-devel' RPM
installed. If you know the correct kernel source
files are installed, you may specify the kernel
source path with the '--kernel-source-path' command
line option.

Those are just excerpts (I'll include the full
log files separately).

But, what the heck is DKMS?
And what is a kernel source file?

Why doesn't the Nvidia script just work?
Jean-Pierre
2015-01-12 16:12:34 UTC
Permalink
Post by Jean-Pierre
Those are just excerpts
(I'll include the full log files separately).
Here are the three gory log files.
If they're trying to tell me something, they're
using terminology which I don't understand.

********************************************************************
This is the first of 3 failed attempts installing Nvidia drivers:
********************************************************************
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon Jan 12 07:34:38 2015
installer version: 340.65

PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

nvidia-installer command line:
./nvidia-installer

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 340.65.
-> Running distribution scripts
executing: '/usr/lib/nvidia/pre-install'...
-> done.
-> The distribution-provided pre-install script failed!
Are you sure you want to continue?
(Answer: Continue installation)
-> Would you like to register the kernel module sources with DKMS?
This will allow DKMS to automatically build a new module,
if you install a different kernel later.
(Answer: Yes)
-> Installing both new and classic TLS OpenGL libraries.
-> Installing both new and classic TLS 32bit OpenGL libraries.
-> Install NVIDIA's 32-bit compatibility libraries?
(Answer: Yes)
-> Skipping installation of the libvdpau wrapper library.
-> Searching for conflicting X files:
-> done.
-> Searching for conflicting OpenGL files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (340.65):
executing: '/sbin/ldconfig'...
-> done.
-> Driver file installation is complete.
-> Installing DKMS kernel module:
ERROR:
Failed to run `/usr/sbin/dkms build -m nvidia -v 340.65 -k 3.11.0-14-generic`:
Error! Your kernel headers for kernel 3.11.0-14-generic cannot be found.
Please install the linux-headers-3.11.0-14-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
-> error.
ERROR:
Failed to install the kernel module through DKMS.
No kernel module was installed; please try installing again without DKMS,
or check the DKMS logs for more information.
ERROR:
Installation has failed.
Please see the file '/var/log/nvidia-installer.log' for details.
You may find suggestions on fixing installation problems in the README
available on the Linux driver download page at www.nvidia.com.
********************************************************************
This is the second of three failed attempts:
********************************************************************
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon Jan 12 07:39:20 2015
installer version: 340.65

PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

nvidia-installer command line:
./nvidia-installer

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 340.65.
-> There appears to already be a driver installed on your system (version: 340.65). As part of installing this driver (version: 340.65), the existing driver will be uninstalled. Are you sure you want to continue? (Answer: Continue installation)
-> Running distribution scripts
executing: '/usr/lib/nvidia/pre-install'...
-> done.
-> The distribution-provided pre-install script failed! Are you sure you want to continue? (Answer: Continue installation)
-> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: No)
-> Performing CC sanity check with CC="/usr/bin/cc".
ERROR: Unable to find the kernel source tree for the currently running kernel. Please make sure you have installed the kernel source files for your kernel and that they are properly configured; on Red Hat Linux systems, for example, be sure you have the 'kernel-source' or 'kernel-devel' RPM installed. If you know the correct kernel source files are installed, you may specify the kernel source path with the '--kernel-source-path' command line option.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
********************************************************************
This is the third of three failed attempts:
********************************************************************
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon Jan 12 07:41:58 2015
installer version: 331.20

PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

nvidia-installer command line:
./nvidia-installer

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 331.20.
-> There appears to already be a driver installed on your system (version: 340.65). As part of installing this driver (version: 331.20), the existing driver will be uninstalled. Are you sure you want to continue? ('no' will abort installation) (Answer: Yes)
-> Running distribution scripts
executing: '/usr/lib/nvidia/pre-install'...
-> done.
-> The distribution-provided pre-install script failed! Continue installation anyway? (Answer: Yes)
-> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: No)
-> Performing CC sanity check with CC="cc".
ERROR: Unable to find the kernel source tree for the currently running kernel. Please make sure you have installed the kernel source files for your kernel and that they are properly configured; on Red Hat Linux systems, for example, be sure you have the 'kernel-source' or 'kernel-devel' RPM installed. If you know the correct kernel source files are installed, you may specify the kernel source path with the '--kernel-source-path' command line option.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
********************************************************************
End of three failed attempts at installing Nvidia drivers.
********************************************************************
Aragorn
2015-01-12 16:34:44 UTC
Permalink
On Monday 12 January 2015 17:12, Jean-Pierre conveyed the following to
alt.os.linux...
"Please install the linux-headers-3.11.0-14-generic package," [...]
See that? Now go and install that package.
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Mike Yetto
2015-01-12 16:32:58 UTC
Permalink
While walking through the streets of Soho in the rain
Post by Jean-Pierre
Error! Your kernel headers for kernel 3.11.0-14-generic cannot be found.
Please install the linux-headers-3.11.0-14-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
I think this would be a good place to start.

Mike "probably won't be the end" Yetto
--
"Errors using inadequate data are much less than those using no
data at all."
- Charles Babbage
Aragorn
2015-01-12 16:37:47 UTC
Permalink
On Monday 12 January 2015 17:32, Mike Yetto conveyed the following to
alt.os.linux...
Post by Mike Yetto
While walking through the streets of Soho in the rain
Post by Jean-Pierre
Failed to run `/usr/sbin/dkms build -m nvidia -v 340.65 -k
3.11.0-14-generic`: Error! Your kernel headers for kernel
3.11.0-14-generic cannot be found. Please install the
linux-headers-3.11.0-14-generic package, or use the --kernelsourcedir
option to tell DKMS where it's located
I think this would be a good place to start.
Mike "probably won't be the end" Yetto
Might be another relative of the hole-in-the-name gang... <shakes head>
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
DecadentLinuxUserNumeroUno
2015-01-12 17:32:49 UTC
Permalink
While walking through the streets of Soho in the rain Jean-Pierre
Post by Jean-Pierre
Failed to run `/usr/sbin/dkms build -m nvidia -v 340.65 -k
Error! Your kernel headers for kernel 3.11.0-14-generic cannot be
found. Please install the linux-headers-3.11.0-14-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
I think this would be a good place to start.
Mike "probably won't be the end" Yetto
So, the driver never really got built to start with.

Imagine that. Maybe that is why it was not ever loaded after his
"install session".
Jean-Pierre
2015-01-13 00:45:50 UTC
Permalink
Post by DecadentLinuxUserNumeroUno
So, the driver never really got built to
start with. Imagine that. Maybe that is
why it was not ever loaded after his
"install session".
Yet, why did the display work fine just
yesterday?
Jean-Pierre
2015-01-13 00:45:10 UTC
Permalink
Post by Jean-Pierre
Please install the linux-headers-3.11.0-14-generic
package, or use the --kernelsourcedir option to
tell DKMS where it's located
I think this would be a good place to start.
Remember, the drivers were working fine for
months, and they were working just a couple of
days ago. All without whatever it is that
Nvidia says needs to be installed.

Still, I'm *HAPPY* to install anything to get
the display to work properly.

But, I already tried the first suggestion:
"Please install linux-headers-3.11.0-14-generic"
$ sudo apt-get install linux-headers-3.11.0-14-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.11.0-14-generic is
not available, but is referred to by another
package. This may mean that the package is
missing, has been obsoleted, or is only
available from another source

So that failed the moment I tried it.

And, where am I supposed to use "--kernelsourcedir"?
And, even if I knew what command to run
to use "--kernelsourcedir", where would I
I point for that "kernal source dir"?

I never needed a "kernel source dir" in my
entire life, and, the display was working
fine for a while, without it.
William Unruh
2015-01-13 01:56:26 UTC
Permalink
Post by Jean-Pierre
Post by Jean-Pierre
Please install the linux-headers-3.11.0-14-generic
package, or use the --kernelsourcedir option to
tell DKMS where it's located
I think this would be a good place to start.
Remember, the drivers were working fine for
months, and they were working just a couple of
days ago. All without whatever it is that
Nvidia says needs to be installed.
OK. Have you upgraded your kernel recently?

Also, I am still voting for harware problems. (Burned capacitor for
example).
Post by Jean-Pierre
Still, I'm *HAPPY* to install anything to get
the display to work properly.
"Please install linux-headers-3.11.0-14-generic"
$ sudo apt-get install linux-headers-3.11.0-14-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.11.0-14-generic is
not available, but is referred to by another
package. This may mean that the package is
missing, has been obsoleted, or is only
available from another source
So that failed the moment I tried it.
And, where am I supposed to use "--kernelsourcedir"?
And, even if I knew what command to run
to use "--kernelsourcedir", where would I
I point for that "kernal source dir"?
I never needed a "kernel source dir" in my
entire life, and, the display was working
fine for a while, without it.
ls /usr/src
what do you see?

uname -a
what does it say?
Jean-Pierre
2015-01-13 03:12:57 UTC
Permalink
Post by William Unruh
OK. Have you upgraded your kernel recently?
Personally, I think that's what screwed up
the driver in the first place.

But, I really don't know.
Post by William Unruh
Also, I am still voting for harware problems.
(Burned capacitor for example).
The display works perfectly.
It just is the wrong resolution.
I doubt it's hardware (but, without debugging
commands, who knows?)
Post by William Unruh
ls /usr/src what do you see?
uname -a what does it say?
$ uname -a
Linux x 3.11.0-14-generic #21-Ubuntu
SMP Tue Nov 12 17:04:55 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

$ ls /usr/src
bbswitch-0.7 linux-headers-3.13.0-43-generic
linux-headers-3.13.0-37 nvidia-340-340.65
linux-headers-3.13.0-37-generic nvidia-340-uvm-340.65
linux-headers-3.13.0-43
William Unruh
2015-01-13 06:19:44 UTC
Permalink
Post by Jean-Pierre
Post by William Unruh
OK. Have you upgraded your kernel recently?
Personally, I think that's what screwed up
the driver in the first place.
I presume that means yes. That means that the system has to recompile
the glue between the system and the actual closed source nvidia driver.
You must have dkms installed. You MUST have kernel-devel installed. I do
not run any debian derivative so do not knowWhat they call the
kernel-devel tree.
Post by Jean-Pierre
But, I really don't know.
ls /usr/src
What does it say?
Post by Jean-Pierre
Post by William Unruh
Also, I am still voting for harware problems.
(Burned capacitor for example).
The display works perfectly.
It just is the wrong resolution.
Harware problems do not necessarily destroy the display, they could
destroy the resolutions as well, or almost anything else. But since you
have said that did a kernel upgrade, that is where my suspicioun lies.

ls /usr/src
find out what package those contents came from
Install those packages for the new kernel.
Post by Jean-Pierre
I doubt it's hardware (but, without debugging
commands, who knows?)
As I said, Try running Windows or reinstall. That will tell you.
Post by Jean-Pierre
Post by William Unruh
ls /usr/src what do you see?
uname -a what does it say?
$ uname -a
Linux x 3.11.0-14-generic #21-Ubuntu
SMP Tue Nov 12 17:04:55 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
$ ls /usr/src
bbswitch-0.7 linux-headers-3.13.0-43-generic
linux-headers-3.13.0-37 nvidia-340-340.65
linux-headers-3.13.0-37-generic nvidia-340-uvm-340.65
linux-headers-3.13.0-43
Weird. You are runnint 3.11 kernel, but all your headers are 3.13. that
makes little sense.

When you boot, why not try booting to a 3.13 kernel instead.
Jean-Pierre
2015-01-13 17:25:47 UTC
Permalink
ls /usr/src What does it say?
This was the key missing debug command!
Cybe R. Wizard
2015-01-13 09:09:10 UTC
Permalink
On Mon, 12 Jan 2015 21:12:57 -0600
Post by Jean-Pierre
Personally, I think that's what screwed up
the driver in the first place.
But, I really don't know.
If you, "really don't know," then it is a really bad idea to have a
preferred opinion.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 11:20:26 UTC
Permalink
Post by Cybe R. Wizard
If you, "really don't know," then it is a
really bad idea to have a
preferred opinion.
I think whoever it was that pointed out that
the kernel is at 3.11.0-14-generic, yet
everything else seems to be at 3.13, has
figured out the problem.

Since I've never touched a kernel before, it
didn't occur to me that this might be the problem.

How do I synchronize the kernel with 3.13?
Jean-Pierre
2015-01-13 11:40:57 UTC
Permalink
Post by Jean-Pierre
How do I synchronize the kernel with 3.13?
Googling, is this the correct process for how
to update the Kubuntu 14.04 kernel from 3.11
to 3.13?

http://ubuntuhandbook.org/index.php/2014/08/install-upgrade-linux-kernel-3-16/
Cybe R. Wizard
2015-01-13 14:36:25 UTC
Permalink
On Tue, 13 Jan 2015 05:40:57 -0600
Post by Jean-Pierre
Post by Jean-Pierre
How do I synchronize the kernel with 3.13?
Googling, is this the correct process for how
to update the Kubuntu 14.04 kernel from 3.11
to 3.13?
http://ubuntuhandbook.org/index.php/2014/08/install-upgrade-linux-kernel-3-16/
Really? Do either 3.11 or 3.13 look like 3.16 to you?

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Wildman
2015-01-13 15:23:57 UTC
Permalink
On Tue, 13 Jan 2015 08:36:25 -0600
Post by Cybe R. Wizard
On Tue, 13 Jan 2015 05:40:57 -0600
Post by Jean-Pierre
Post by Jean-Pierre
How do I synchronize the kernel with 3.13?
Googling, is this the correct process for how
to update the Kubuntu 14.04 kernel from 3.11
to 3.13?
[useless link]
Really? Do either 3.11 or 3.13 look like 3.16 to you?
Cybe R. Wizard
This is looking more and more like a rousing game of
"Why don't you - Yes, but..." Just like what the hole
in the name gang use to play. Mr. Yetto may be on to
something.
--
<Wildman> GNU/Linux user #557453
The cow died so I don't need your bull!
Jean-Pierre
2015-01-13 15:39:30 UTC
Permalink
Post by Wildman
This is looking more and more like a rousing
game of "Why don't you - Yes, but..." Just
like what the hole in the name gang use to play.
I find it odd that, if someone tries to solve a
problem, and, if they solve the problem, but,
they solve it by trying everything that is
suggested and giving log files of it all,
then they are accused of trolling.

Anyway, I'm going through the thread to
find what the takeaways are, but, the keys
from Aragorn and Richard Kettlewell were
what unlocked the treasure.
Cybe R. Wizard
2015-01-13 14:33:30 UTC
Permalink
On Tue, 13 Jan 2015 05:20:26 -0600
Post by Jean-Pierre
How do I synchronize the kernel with 3.13?
What?

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jonathan N. Little
2015-01-13 16:03:20 UTC
Permalink
Post by Jean-Pierre
Post by Cybe R. Wizard
If you, "really don't know," then it is a
really bad idea to have a
preferred opinion.
I think whoever it was that pointed out that
the kernel is at 3.11.0-14-generic, yet
everything else seems to be at 3.13, has
figured out the problem.
Since I've never touched a kernel before, it
didn't occur to me that this might be the problem.
How do I synchronize the kernel with 3.13?
sudo apt-get dist-upgrade

then you will boot into the 3.13 kernel.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 17:18:57 UTC
Permalink
Post by Jean-Pierre
sudo apt-get dist-upgrade
then you will boot into the 3.13 kernel.
Thanks for that suggestion.
I didn't get a chance to try the "dist-upgrade"
because Richard Kettlewell's suggestion to use
the following command worked first:

$ sudo apt-get install linux-image-generic
David W. Hodgins
2015-01-12 18:24:09 UTC
Permalink
Post by Jean-Pierre
Here are the three gory log files.
If they're trying to tell me something, they're
using terminology which I don't understand.
DKMS == Dynamic Kernel Module Support. It means it's a third party
kernel module, that is distributed as source code, and needs to be
compiled (either at install, or during the first boot) for the currently
running kernel. In order to compile the code, the proper kernel source
code headers must also be installed. On a Mageia system that will be in
the kernel-desktop-devel-latest rpm package (replace desktop with the
kernel version in use, such as server, desktop586, etc.). Note that it's
only the header files from the kernel, not the full kernel source, that's
needed. The full kernel source is only needed if you want to compile your
own version of the kernel.

I've never used ubuntu, or kubuntu, so have no idea what they use for
the kernel headers package name.

Regards, Dave Hodgins
--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
Jean-Pierre
2015-01-13 00:56:41 UTC
Permalink
Post by David W. Hodgins
so have no idea what they use for
the kernel headers package name.
That was a *GREAT* explanation of why Nvidia
wanted DKMS! Thanks.

What is amazing is how much you need to know
just to get the Nvidia display driver to
install on Kubuntu!

It's like it was never ever tested.
Anyway, if I can find the name for these
"Kernel Source Headers", I will install
them.

Googling, the hits are all over the map:
https://www.google.com/search?client=ubuntu&channel=fs&q=kubuntu+14.04+kernel+source+headers+sudo+apt-get+install&ie=utf-8&oe=utf-8

$ uname -r
3.11.0-14-generic

$ sudo apt-get install linux-headers-3.11.0-14-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.11.0-14-generic is
not available, but is referred to by another
package.
This may mean that the package is missing,
has been obsoleted, or is only available
from another source

$ sudo apt-get install linux-headers-3.11.0-14*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'linux-headers-3.11.0-14-generic'
for regex 'linux-headers-3.11.0-14*'
Note, selecting 'linux-headers-3.11.0-12-generic'
for regex 'linux-headers-3.11.0-14*'
Note, selecting 'linux-headers-3.11.0-13-generic'
for regex 'linux-headers-3.11.0-14*'

I give up.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.


E: Package 'linux-headers-3.11.0-14-generic' has no installation candidate
Cybe R. Wizard
2015-01-13 08:47:16 UTC
Permalink
On Mon, 12 Jan 2015 18:56:41 -0600
Post by Jean-Pierre
What is amazing is how much you need to know
just to get the Nvidia display driver to
install on Kubuntu!
...if you insist on using some back-alley software found 'somewhere on
the 'net.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Aragorn
2015-01-12 16:32:03 UTC
Permalink
On Monday 12 January 2015 17:09, Jean-Pierre conveyed the following to
alt.os.linux...
Post by Jean-Pierre
Post by William Unruh
To fix it or for its own sake?
1. If it would just work, I'd be very happy.
2. If I could fix it, without knowing what's
going on, I'd still be very happy.
3. If I could use some other driver than Nvidia,
and if it worked, I'd still be happy.
I just want my display back.
I've tried three attempts in the interim, and
all failed. Nvidia gives a seemingly good
log file, but it uses cryptic words.
The distribution-provided pre-install script failed!
Failed to install the kernel module through DKMS.
ERROR: Unable to find the kernel source tree for
the currently running kernel. Please make sure
you have installed the kernel source files for
your kernel and that they are properly configured;
on Red Hat Linux systems, for example, be sure you
have the 'kernel-source' or 'kernel-devel' RPM
installed. If you know the correct kernel source
files are installed, you may specify the kernel
source path with the '--kernel-source-path' command
line option.
It tells you: You need to have the kernel sources installed. I believe
the package would be called something with "kernelsrc" in its name, and
a version number. That version number has to match the kernel you're
running.

$ uname -r

... will tell you the kernel version.
Post by Jean-Pierre
Those are just excerpts (I'll include the full
log files separately).
But, what the heck is DKMS?
I have explained that to you elsewhere in the thread. Don't you read
the replies you're getting?
Post by Jean-Pierre
And what is a kernel source file?
It's not a file but a whole directory structure with source code files
which are all used to build the kernel from. Source code is the code in
the respective programming language ─ for the kernel, that will mostly
be C and a bit of assembler.
Post by Jean-Pierre
Why doesn't the Nvidia script just work?
It told you exactly why. You don't have the kernel sources installed.
They should normally go under /usr/src/linux-<version>, with
/usr/src/linux being a symbolic link _to_ that directory.
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jean-Pierre
2015-01-12 15:26:36 UTC
Permalink
Post by William Unruh
Had it not gone
wrong would you still be asking us for
debugging commands or would you
have been happy to use it?
You understand me well.

I have no desire to become an expert in graphics.
In fact, if the graphics would just work, as it
had for more than a year, I'd be perfectly fine
(fat, dumb, and happy).

But, now the graphics is doing funny things that
are not caused by me. This last problem happened
only after the machine locked up and had to be
hard rebooted.

From what I can tell, the right driver is installed,
yet, KDE thinks that the highest display resolution
is 1024x768 when it's actually 1920x1080.

Is KDE at fault?
Is the Nvidia driver at fault?
Did the nouveau driver sneak in again?

I don't know.
I just want to know WHY KDE won't display properly.
William Unruh
2015-01-12 15:47:06 UTC
Permalink
Post by Jean-Pierre
Post by William Unruh
Had it not gone
wrong would you still be asking us for
debugging commands or would you
have been happy to use it?
You understand me well.
I have no desire to become an expert in graphics.
In fact, if the graphics would just work, as it
had for more than a year, I'd be perfectly fine
(fat, dumb, and happy).
But, now the graphics is doing funny things that
are not caused by me. This last problem happened
only after the machine locked up and had to be
hard rebooted.
From what I can tell, the right driver is installed,
yet, KDE thinks that the highest display resolution
is 1024x768 when it's actually 1920x1080.
Is KDE at fault?
Is the Nvidia driver at fault?
Did the nouveau driver sneak in again?
I don't know.
I just want to know WHY KDE won't display properly.
No. As you said, you just want to fix it so that it displays properly.
Jean-Pierre
2015-01-12 16:13:45 UTC
Permalink
Post by William Unruh
No. As you said, you just want to fix it
so that it displays properly.
Yes.

I will try to contact Nvidia support, but, one
thing I'm learning is to NEVER ever ever ever
ever ever ever ever buy a computer with Nvidia
in it.

Can I just use some other driver?
William Unruh
2015-01-12 17:27:01 UTC
Permalink
Post by Jean-Pierre
Post by William Unruh
No. As you said, you just want to fix it
so that it displays properly.
Yes.
I will try to contact Nvidia support, but, one
thing I'm learning is to NEVER ever ever ever
ever ever ever ever buy a computer with Nvidia
in it.
Can I just use some other driver?
Yes. noveau or whatever it is called. But why oh why do you not listen
to what people are telling your. Your system is incomplete. It CANNOT
install the new nvidia drivers. It keeps telling you that, and you keep
ignoring that.
Jean-Pierre
2015-01-13 01:01:01 UTC
Permalink
Post by William Unruh
Your system is incomplete.
It CANNOT install
the new nvidia drivers.
It says to install these kernel headers but
it won't actually install the kernel headers.

So, what part of the command below is wrong?
$ sudo apt-get install linux-headers-3.11.0-14-generic
E: Package 'linux-headers-3.11.0-14-generic'
has no installation candidate
Mike Yetto
2015-01-13 05:53:20 UTC
Permalink
While walking through the streets of Soho in the rain
Post by Jean-Pierre
Post by William Unruh
Your system is incomplete.
It CANNOT install
the new nvidia drivers.
It says to install these kernel headers but
it won't actually install the kernel headers.
So, what part of the command below is wrong?
$ sudo apt-get install linux-headers-3.11.0-14-generic
E: Package 'linux-headers-3.11.0-14-generic'
has no installation candidate
However linux-headers-generic does.

Mike "strongly suspect the hole-in-the-name gang" Yetto
--
“Fables should be taught as fables, myths as myths, and miracles
as poetic fantasies. To teach superstitions as truths is a most
terrible thing. The child mind accepts and believes them, and
only through great pain and perhaps tragedy can he be in later
years relieved of them."
- Hypatia
Jean-Pierre
2015-01-13 06:23:29 UTC
Permalink
Post by Mike Yetto
However linux-headers-generic does.
Except that it's already installed
(and always was installed).

$ sudo apt-get install linux-headers-generic

Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Jean-Pierre
2015-01-13 06:30:56 UTC
Permalink
Except that it's already installed (and always was installed).
$ sudo apt-get install linux-headers-generic
Here is what the (nearly useless)
KDE Driver Manager shows:
Loading Image...
William Unruh
2015-01-13 06:42:25 UTC
Permalink
Post by Jean-Pierre
Post by Mike Yetto
However linux-headers-generic does.
Except that it's already installed
(and always was installed).
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Every kernel has its own headers. ls /usr/src told us that you have
three kernel headers for 3.13 kernels but none for the 3.11 kernel you
are actually running.
Jean-Pierre
2015-01-13 07:04:01 UTC
Permalink
Every kernel has its own headers. ls /usr/src told us that you have three
kernel headers for 3.13 kernels but none for the 3.11 kernel you are
actually running.
I think you found a (the?) critical problem.

I've NEVER messed with a kernel before.
I don't care WHAT kernel I have (as long as it works).

Trying the steps on this page just now:
http://www.dedoimedo.com/computers/ubuntu-ringtail-nvidia.html

I ran the following:
$ sudo /sbin/lsmod | grep nvidia
Returns nothing.
$ sudo depmod -a
Returns nothing.
$ sudo apt-get update
$ sudo apt-get dist-upgrade

An error was:
Error! Bad return status for module build
on kernel: 3.13.0-44-generic (x86_64)
Consult /var/lib/dkms/nvidia-340-uvm/340.65/build/make.log
for more information.

$ cat /var/lib/dkms/nvidia-340-uvm/340.65/build/make.log
DKMS make.log for nvidia-340-uvm-340.65 for kernel 3.13.0-44-generic (x86_64)
Mon Jan 12 22:58:12 PST 2015
cd /var/lib/dkms/nvidia-340/340.65/build; make module SYSSRC=/lib/modules/3.13.0-44-generic/build SYSOUT=/lib/modules/3.13.0-44-generic/build KBUILD_EXTMOD=/var/lib/dkms/nvidia-340/340.65/build
make[1]: Entering directory `/var/lib/dkms/nvidia-340/340.65/build'
NVIDIA: calling KBUILD...
make[2]: Entering directory `/usr/src/linux-headers-3.13.0-44-generic'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /var/lib/dkms/nvidia-340/340.65/build/.tmp_versions ; rm -f /var/lib/dkms/nvidia-340/340.65/build/.tmp_versions/*
make -f scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.65/build
cc -Wp,-MD,/var/lib/dkms/nvidia-340/340.65/build/.nv.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.8/include -I/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include -Iarch/x86/include/generated -Iinclude -I/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-headers-3.13.0-44-generic/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-headers-3.13.0-44-generic/include/linux/kconfig.h -Iubuntu/include -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-mmx -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -fstack-protector -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=1024 -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_DEBUG -DNDEBUG -I/var/lib/dkms/nvidia-340/340.65/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.65\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\" -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/lib/dkms/nvidia-340/340.65/build/.tmp_nv.o /var/lib/dkms/nvidia-340/340.65/build/nv.c
In file included from include/uapi/linux/stddef.h:1:0,
from include/linux/stddef.h:4,
from /usr/src/linux-headers-3.13.0-44-generic/include/uapi/linux/posix_types.h:4,
from include/uapi/linux/types.h:13,
from include/linux/types.h:5,
from include/uapi/linux/capability.h:16,
from include/linux/capability.h:15,
from include/linux/sched.h:13,
from include/linux/utsname.h:5,
from /var/lib/dkms/nvidia-340/340.65/build/nv-linux.h:44,
from /var/lib/dkms/nvidia-340/340.65/build/nv.c:13:
/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include/asm/uaccess.h: In function 'copy_from_user':
/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include/asm/uaccess.h:612:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (likely(sz < 0 || sz >= n))
^
include/linux/compiler.h:152:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include/asm/uaccess.h: In function 'copy_to_user':
/usr/src/linux-headers-3.13.0-44-generic/arch/x86/include/asm/uaccess.h:630:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (likely(sz < 0 || sz >= n))
^
include/linux/compiler.h:152:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
objdump: '/var/lib/dkms/nvidia-340/340.65/build/.tmp_nv.o': No such file
mv: cannot stat '/var/lib/dkms/nvidia-340/340.65/build/.tmp_nv.o': No such file or directory
make[3]: *** [/var/lib/dkms/nvidia-340/340.65/build/nv.o] Error 1
make[2]: *** [_module_/var/lib/dkms/nvidia-340/340.65/build] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-3.13.0-44-generic'
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [nvidia.ko] Error 1
make[1]: Leaving directory `/var/lib/dkms/nvidia-340/340.65/build'
make: *** [/var/lib/dkms/nvidia-340/340.65/build/Module.symvers] Error 2

So, if my kernel is wrong, (a) how did it get wrong,
and, more importantly (b) how do I fix it?
Jean-Pierre
2015-01-13 11:24:44 UTC
Permalink
Post by Jean-Pierre
So, if my kernel is wrong, (a) how did it get wrong,
and, more importantly (b) how do I fix it?
This is the key question.
Cybe R. Wizard
2015-01-13 09:21:19 UTC
Permalink
On Tue, 13 Jan 2015 00:53:20 -0500
Post by Mike Yetto
Mike "strongly suspect the hole-in-the-name gang" Yetto
+1

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
mechanic
2015-01-13 12:04:21 UTC
Permalink
Post by Cybe R. Wizard
On Tue, 13 Jan 2015 00:53:20 -0500
Post by Mike Yetto
Mike "strongly suspect the hole-in-the-name gang" Yetto
+1
Classic (2): Linux fans stumped by problem, resort to troll calling.
Paul
2015-01-13 12:27:07 UTC
Permalink
Post by mechanic
Post by Cybe R. Wizard
On Tue, 13 Jan 2015 00:53:20 -0500
Post by Mike Yetto
Mike "strongly suspect the hole-in-the-name gang" Yetto
+1
Classic (2): Linux fans stumped by problem, resort to troll calling.
That's funny. I can see a simple solution.

1) Save the home directory.
2) Reinstall the OS.
3) Done

Troll or not, this is the solution, and the end of the thread.

Paul
Jean-Pierre
2015-01-13 12:55:06 UTC
Permalink
Post by Paul
1) Save the home directory.
2) Reinstall the OS.
3) Done
Reinstalling the OS isn't that simple.

I guess it would be if EVERYTHING you
ever did was in the home directory.

Or, if you never installed any programs,
and never customized them.

Or, if there was only one operating
system.

And if you didn't have a shared NTFS
partition between the two, in addition
to stored software on the DOS partition.

In short, fixing a car is easier than
replacing the entire engine.
Paul
2015-01-13 13:23:55 UTC
Permalink
Post by Jean-Pierre
Post by Paul
1) Save the home directory.
2) Reinstall the OS.
3) Done
Reinstalling the OS isn't that simple.
I guess it would be if EVERYTHING you
ever did was in the home directory.
Or, if you never installed any programs,
and never customized them.
Or, if there was only one operating
system.
And if you didn't have a shared NTFS
partition between the two, in addition
to stored software on the DOS partition.
In short, fixing a car is easier than
replacing the entire engine.
When you mess up computer software bad enough,
this is how you fix it.

It's not a car, it's computer software, and
eventually a decision has to be made to cut your
losses and move on.

Paul
Jean-Pierre
2015-01-13 14:13:01 UTC
Permalink
Post by Paul
When you mess up computer software bad enough,
this is how you fix it.
That might be the case, especially since I finally
realized that this KDE Driver Manager Software is
a POS that nobody who recommends it even realizes.

It fails quietly. No log. No warning.

You run it. You select the Nvidia driver. You
hit APPLY. And it says you have the Nvidia driver.

But, you don't.
It's a POS and I'm sorry I ever resorted to using
it as it plumb doesn't work.
Cybe R. Wizard
2015-01-13 14:50:32 UTC
Permalink
On Tue, 13 Jan 2015 08:13:01 -0600
Post by Jean-Pierre
You run it. You select the Nvidia driver. You
hit APPLY. And it says you have the Nvidia driver.
But, you don't.
Consider that you might be installing the wrong thing.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 15:24:46 UTC
Permalink
Post by Cybe R. Wizard
Consider that you might be installing the wrong thing.
It's pretty clear, in hindsight, what happened.

1. First thing is to NEVER use the POS KDE
Driver Management Software. I'm sure the
stuff works in fair weather, but, in foul
weather, it just fails. No log. No message.
No nothing. It just plain fails.

2. Second thing is to use the Nvidia installation
method, which, interestingly, provides a
decent log - but - that log file is cryptic.

If it wasn't for the person who recognized
that the log was telling me that the versions
were mismatched between the kernel and the
header files, we'd never have solved the
problem.

3. Third thing is to realize, quite unnaturally,
that you have to solve the problem backward.

You can't update the headers to match the
kernel. You have to update the kernel to
match the headers.

4. Once those four things are taken into
consideration, the problem is easy to solve.

Even the POS KDE Driver Management Software
can see when it's working:
Loading Image...

The debugging commands turned out to be to
check the match between these simple commands:

$ uname -r
$ dpkg -l | grep linux-headers
$ dpkg -l | grep linux-image
Jean-Pierre
2015-01-13 17:02:57 UTC
Permalink
Post by Paul
When you mess up computer software bad enough,
this is how you fix it.
Luckily, the solution was to realize
1. There was a kernel-to-header mismatch, and
2. The suggestion to update the headers
was doomed to fail, and, that,
3. The suggestion to use Synaptic was likewise
doomed to failure, and that,
4. The suggestion to use the POS KDE Driver
Manager Software was doomed to failure, and,
5. The suggestion to throw the baby away with
the bathwater and reinstall the OS was
a bit too drastic, and, that
6. The real solution was to update the kernel,
7. And then follow Nvidia directions as before.

So, my key mistake, from the start, was in
not realizing that the problem was a mismatch
in versions, and for not knowing the specific
way to resolve that (which has to be done
backwards).
Jonathan N. Little
2015-01-13 17:00:03 UTC
Permalink
Post by Jean-Pierre
Post by Paul
1) Save the home directory.
2) Reinstall the OS.
3) Done
Reinstalling the OS isn't that simple.
I guess it would be if EVERYTHING you
ever did was in the home directory.
Firstly your stuff should only be in /home/you
Post by Jean-Pierre
Or, if you never installed any programs,
and never customized them.
So save your application install list

dpkg --get-selections | awk '!/deinstall|purge|hold/ {print $1}' > MyApps

Then reinstall:

xargs -a MyApps sudo apt-get install


Save your configs then, tar your /etc directory and restore the custom
configs or run installer over in situ and when prompted opt to keep
existing configs that you altered.
Post by Jean-Pierre
Or, if there was only one operating
system.
Just make sure you install to the correct partition. Of course it goes
without saying backup first.
Post by Jean-Pierre
And if you didn't have a shared NTFS
partition between the two, in addition
to stored software on the DOS partition.
Just make sure you install to the correct partition.
Post by Jean-Pierre
In short, fixing a car is easier than
replacing the entire engine.
Not if you foobared the car in so many places that finding all the
problems would be more laborious or beyond your skill set
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
DecadentLinuxUserNumeroUno
2015-01-13 17:52:33 UTC
Permalink
Post by Jonathan N. Little
So save your application install list
dpkg --get-selections | awk '!/deinstall|purge|hold/ {print $1}' > MyApps
xargs -a MyApps sudo apt-get install
I like this procedure. A lot.

On my cubox-i ARM machine, however, it ONLY boots from a microSD stick
(ala Android)(so far), and it is just as easy to image the entire stick,
and voila'! all backed up.

The other benefit is that if I keep the apps to devapps (which is all
the boys desire of a and update it, I can strip the id from it, and
upload it for others to use pre-updated.

That is what is cool about this method. The drawback being they are 4GB
images which only compress as you have less installed.

We usually put them on larger sticks after set-up locally, then expand
that volume to finalize an install. Cool method.

I have about 5 Open-ELEC installs here. I was all KODI and Android this
week, and then I installed Debian Jessie (ARM) and it installed, and ran
fine, and even installed MAME on ARM!!! Then, it updated and even DIST-
updated. I am so impressed. That is why I want to smooth this one out
real good and re-upload it back.

That is one cool thing about all of us having the same hardware (cubox-
i), and with a slight text file edit, the Hummingbird guys can use the
image too.
Jean-Pierre
2015-01-13 18:07:26 UTC
Permalink
Post by Jonathan N. Little
dpkg --get-selections | awk '!/deinstall|purge|hold/ {print $1}' > MyApps
xargs -a MyApps sudo apt-get install
Nice. Very nice. Thanks!
Jean-Pierre
2015-01-13 16:57:49 UTC
Permalink
Post by Paul
That's funny. I can see a simple solution.
1) Save the home directory.
2) Reinstall the OS.
3) Done
The solution turned out to be far simpler.
1) Update the kernel to the same version as the headers.
2) Install the Nvidia driver as per Nvidia.

The solution came only when it was realized
a) There was a mismatch between kernel & header,
b) None of the KDE or Kubuntu tools would work.
Jean-Pierre
2015-01-13 16:55:41 UTC
Permalink
Post by Mike Yetto
However linux-headers-generic does
Failed every time.

The solution wasn't the headers.
It was the kernel.

Every single suggestion to add the headers
was doomed to failure, simply because they
don't exist for Kubuntu 14.04.
Aragorn
2015-01-12 16:36:40 UTC
Permalink
On Monday 12 January 2015 16:26, Jean-Pierre conveyed the following to
alt.os.linux...
Post by Jean-Pierre
Had it not gone wrong would you still be asking us for
debugging commands or would you have been happy to use it?
You understand me well.
I have no desire to become an expert in graphics.
In fact, if the graphics would just work, as it
had for more than a year, I'd be perfectly fine
(fat, dumb, and happy).
But, now the graphics is doing funny things that
are not caused by me. This last problem happened
only after the machine locked up and had to be
hard rebooted.
From what I can tell, the right driver is installed,
yet, KDE thinks that the highest display resolution
is 1024x768 when it's actually 1920x1080.
Is KDE at fault?
Is the Nvidia driver at fault?
Did the nouveau driver sneak in again?
I don't know.
I just want to know WHY KDE won't display properly.
PEBKAC. Or PICNIC, if you will.
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jonathan N. Little
2015-01-12 15:37:27 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
Something funny is going on, but I don't know what
and only need debugging commands.
Again, I repeat: I ask for help in DEBUGGING commands.
Here is the gory detail (but the request is for
debugging commands so that I UNDERSTAND what is
going on).
The Lenovo W510 laptop display was fine, for two days
(see previous thread).
Then the machine locked up, so I forced a hard button
shutdown, and when it came up, the screen was at
1024x768 instead of 1920x1080.
The funny thing was that the Nvidia driver was
in place according to the command line but
according to KDE System Settings, nouveau was
installed.
I tried to re-install the Nvidia driver using
KDE System Settings "Driver Manager", but it
wouldn't allow the "Apply" button (it was
greyed out) so I chose an earlier Nvidia driver
in the selection, and rebooted.
http://i59.tinypic.com/2nasp38.png
http://i58.tinypic.com/2r2pxrm.png
$ modprobe -R nvidia
nvidia_331_updates
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0
848x480 0.0
640x480 60.0
The KDE System Settings "Display and Monitor"
are showing only "default" settings of
1024x768, even though the same GUI shows that
the Nvidia drivers are installed.
http://i58.tinypic.com/2j61noj.png
The Google inxi -F command used to show that
LVDS-1 was connected primary 1920x1080, but
now it shows that the screen resolution is
limited to 1024x768.
$ inxi -F
Card: NVIDIA GT216GLM [Quadro FX 880M]
X.Org: 1.15.1 drivers: nvidia,fbdev,vesa,nouveau
GLX Renderer: N/A GLX Version: N/A
But the xdriinfo and glxinfo commands don't
tell us much.
$ xdriinfo
libGL is too old.
$ glxinfo
name of display: :0
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
$ grep CMDLINE /etc/default/grub
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""
$ cat /etc/modprobe.d/nvidia-graphics-drivers.conf
# This file was installed by nvidia-331-updates
# Do not edit this file manually
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-331
alias nvidia nvidia_331_updates
alias nvidia-uvm nvidia_331_updates-uvm
alias nouveau off
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2)
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
Why do you keep swapping drivers like underwear? The "pasta"[1] method
can often do more hard than good by mucking conflicting settings.

IIRC to reset your settings the command is:

sudo nvidia-xconfig

According to nvidia the your card is supported with 340 driver
<http://www.nvidia.com/Download/driverResults.aspx/80647/en-us>
so stick with it.

This is a laptop driving an external monitor, there could be other
reasons why you are hanging that have nothing to do with the driver. The
first one that come to mind is overheating. Laptops != Desktops and the
compromises effect power and cooling.

[1]Like pasta keep throwing it at the wall to see what sticks.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-12 16:15:49 UTC
Permalink
Post by Jonathan N. Little
Why do you keep swapping drivers like underwear?
NONE (absolutely none!) of the suggested methods
work.

For example, I had THOUGHT that the KDE System
Settings panel worked last time, but it didn't
work this time. So that method failed.

I also tried, this morning, three times, the
exact procedure on the Nvidia site, and it
failed all three times.

So, absolutely NONE of the suggested methods
works.

that's why.
Jonathan N. Little
2015-01-12 17:11:41 UTC
Permalink
Post by Jean-Pierre
Post by Jonathan N. Little
Why do you keep swapping drivers like underwear?
NONE (absolutely none!) of the suggested methods
work.
For example, I had THOUGHT that the KDE System
Settings panel worked last time, but it didn't
work this time. So that method failed.
I also tried, this morning, three times, the
exact procedure on the Nvidia site, and it
failed all three times.
So, absolutely NONE of the suggested methods
works.
that's why.
Because you snipped out what I bet was the real problem:

"This is a laptop driving an external monitor, there could be other
reasons why you are hanging that have nothing to do with the driver. The
first one that come to mind is overheating. Laptops != Desktops and the
compromises effect power and cooling."

I have seen this situation often. Works just fine with laptop display
but then overheats driving a larger monitor. Especially if the laptop's
cooling is compromised in any way, clogged fan, dying fan, loose
heatsink, clogged heatsink, bad caps on mb, ...
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 01:07:22 UTC
Permalink
Post by Jonathan N. Little
Because you snipped out what I bet was
In the three Nvidia logs, I snipped absolutely
nothing.
Post by Jonathan N. Little
"This is a laptop driving an external monitor
It's a Lenovo W510 laptop driving nothing.
I don't even own an external monitor.
Post by Jonathan N. Little
there could be other reasons why you are
hanging that have nothing to do with the driver.
That's almost certainly true.
I don't think I ever said the crashes are due to
the driver. The only thing was that the driver
was messed up after a crash.
Post by Jonathan N. Little
first one that come to mind is overheating.
The laptop is hot as blazes on the side where
the fan pushes out heat. So, yes, it's HOT.
(It always was.)
Post by Jonathan N. Little
then overheats driving a larger monitor.
Except there is no external monitor in this
case. Although it generally crashes while
watching video on Firefox.

So, I don't doubt the crash can be caused
by anything (including heat), all I want is
for the display to work (even when cold).
William Unruh
2015-01-13 02:00:13 UTC
Permalink
Post by Jean-Pierre
Post by Jonathan N. Little
Because you snipped out what I bet was
In the three Nvidia logs, I snipped absolutely
nothing.
Post by Jonathan N. Little
"This is a laptop driving an external monitor
It's a Lenovo W510 laptop driving nothing.
I don't even own an external monitor.
Post by Jonathan N. Little
there could be other reasons why you are
hanging that have nothing to do with the driver.
That's almost certainly true.
I don't think I ever said the crashes are due to
the driver. The only thing was that the driver
was messed up after a crash.
No. video was messed up after a crash. We still do not know it was the
driver.
Post by Jean-Pierre
Post by Jonathan N. Little
first one that come to mind is overheating.
The laptop is hot as blazes on the side where
the fan pushes out heat. So, yes, it's HOT.
Heat migrates ions in a chip. eventually that shorts out some path in
the chip.
Post by Jean-Pierre
(It always was.)
Post by Jonathan N. Little
then overheats driving a larger monitor.
Except there is no external monitor in this
case. Although it generally crashes while
watching video on Firefox.
So, I don't doubt the crash can be caused
by anything (including heat), all I want is
for the display to work (even when cold).
Once the ions have migrated, they do not migrate back.
Jean-Pierre
2015-01-13 03:27:47 UTC
Permalink
Post by William Unruh
Once the ions have migrated, they do not migrate back.
That's not the problem.
The display is perfect.
It's just the wrong resolution.
It's a driver, for sure.

What nobody knows is how to debug it.
Nor, how to install DKMS headers on Kubuntu 14.04.
Least of all, me.

Everything I tried failed (as fully documented already).
Peter Köhlmann
2015-01-12 18:31:10 UTC
Permalink
Post by Jean-Pierre
Post by Jonathan N. Little
Why do you keep swapping drivers like underwear?
NONE (absolutely none!) of the suggested methods
work.
For example, I had THOUGHT that the KDE System
Settings panel worked last time, but it didn't
work this time. So that method failed.
I also tried, this morning, three times, the
exact procedure on the Nvidia site, and it
failed all three times.
So, absolutely NONE of the suggested methods
works.
that's why.
Noen of the methods work for you. Because you don't want them to
mike
2015-01-13 01:50:05 UTC
Permalink
Post by Peter Köhlmann
Post by Jean-Pierre
Post by Jonathan N. Little
Why do you keep swapping drivers like underwear?
NONE (absolutely none!) of the suggested methods
work.
For example, I had THOUGHT that the KDE System
Settings panel worked last time, but it didn't
work this time. So that method failed.
I also tried, this morning, three times, the
exact procedure on the Nvidia site, and it
failed all three times.
So, absolutely NONE of the suggested methods
works.
that's why.
Noen of the methods work for you. Because you don't want them to
Did you read this before you sent it?

How would you feel if you called the car dealer and said,
"My car won't start," and the dealer replied,
"It's because you don't want it to?"

Or maybe you were presented with a three-ring-circus of complex
install this that and the other and see it it starts now...presented
by random unknown people who drive different cars.

And your car still didn't start.

Wonder what it would be like if we teleported to another universe
where you could just click on "reinstall driver" and it just worked?
Or you could automagically search online for the latest driver with one
click and it would install and just work.
Or maybe you changed stuff and could just select from available drivers
and install that one and it just worked.

Or we could stay here and call each other names.
Jean-Pierre
2015-01-13 03:48:41 UTC
Permalink
Post by mike
Or we could stay here and call each
other names.
In addition ...

I should note that I have tried EVERY SINGLE
SUGGESTION that was suggested. Not only did
I try every single suggestion, but I DOCUMENTED
what happened when I tried it. In detail.

I repeat I have reported back EXACTLY what
the command line or log files said in EVERY
single instance.

I don't mind REPEATING what I did.
If anyone missed the steps, let me know and
I will show you what I did and what the results
were.

At the moment, the KDE Device Manager is failing
every single time, without any log that I know
of.

The Nvidia method is failing every time, saying
that the DKMS headers need to be added, but,
nowhere in this thread or on the net is there
a command that works to INSTALL those DKMS
headers.

For example, this fails:
$ dpkg --get-selections | grep nvidia
nvidia-331-updates install
nvidia-331-updates-uvm install
nvidia-libopencl1-331-updates install
nvidia-opencl-icd-331-updates install
nvidia-prime install
nvidia-settings install

$ sudo apt-get install nvidia-kernel-dkms nvidia-xconfig nvidia-settings
E: Package 'nvidia-kernel-dkms' has no installation candidate
E: Unable to locate package nvidia-xconfig

$ ubuntu-drivers devices | grep recommended
driver : nvidia-340 - third-party free recommended

<control><alt><F1>
$ [login]
$ sudo service lightdm stop
$ sudo apt-get install nvidia-340
$ sudo reboot
Jean-Pierre
2015-01-13 05:23:05 UTC
Permalink
Post by Jean-Pierre
I should note that I have tried EVERY SINGLE
SUGGESTION that was suggested. Not only did
I try every single suggestion, but I DOCUMENTED
what happened when I tried it. In detail.
Here's the latest attempt, following the apt
suggestion to just purge all things nvidia,
and start from scratch with the KDE Driver
Manager GUI.

---------------
$ script $HOME/purge.log
Script started on Mon 12 Jan 2015 08:08:05 PM PST
Unable to connect to X server
Unable to connect to X server
---------------
$ sudo apt-get purge nvidia*
Reading package lists... 0%Reading package lists... 100%Reading package lists... Done
Building dependency tree... 0%Building dependency tree... 0%Building dependency tree... 50%Building dependency tree... 50%Building dependency tree
Reading state information... 0%Reading state information... 0%Reading state information... Done
Note, selecting 'nvidia-340-updates' for regex 'nvidia*'
Note, selecting 'nvidia-331-dev' for regex 'nvidia*'
Note, selecting 'nvidia-compute-profiler' for regex 'nvidia*'
Note, selecting 'nvidia-319-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-cg-dev' for regex 'nvidia*'
Note, selecting 'nvidia-310-dev' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-doc' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1' for regex 'nvidia*'
Note, selecting 'nvidia-visual-profiler' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304-updates' for regex 'nvidia*'
Note, selecting 'nvidia-persistenced' for regex 'nvidia*'
Note, selecting 'nvidia-driver' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-304-dev' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331-updates' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-304-updates' for regex 'nvidia*'
Note, selecting 'nvidia-settings-updates' for regex 'nvidia*'
Note, selecting 'nvidia-cg-doc' for regex 'nvidia*'
Note, selecting 'nvidia-343-uvm' for regex 'nvidia*'
Note, selecting 'nvidia-settings' for regex 'nvidia*'
Note, selecting 'nvidia-304-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-gdb' for regex 'nvidia*'
Note, selecting 'nvidia-kernel-486' for regex 'nvidia*'
Note, selecting 'nvidia-common' for regex 'nvidia*'
Note, selecting 'nvidia-343-dev' for regex 'nvidia*'
Note, selecting 'nvidia-glx' for regex 'nvidia*'
Note, selecting 'nvidia-settings-binary' for regex 'nvidia*'
Note, selecting 'nvidia-325-updates' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-331-updates' for regex 'nvidia*'
Note, selecting 'nvidia-kernel-686-pae' for regex 'nvidia*'
Note, selecting 'nvidia-current-dev' for regex 'nvidia*'
Note, selecting 'nvidia' for regex 'nvidia*'
Note, selecting 'nvidia-343-updates' for regex 'nvidia*'
Note, selecting 'nvidia-settings-310-updates' for regex 'nvidia*'
Note, selecting 'nvidia-304' for regex 'nvidia*'
Note, selecting 'nvidia-current-updates' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-310-dev' for regex 'nvidia*'
Note, selecting 'nvidia-kernel-amd64' for regex 'nvidia*'
Note, selecting 'nvidia-310' for regex 'nvidia*'
Note, selecting 'nvidia-313' for regex 'nvidia*'
Note, selecting 'nvidia-319' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-304' for regex 'nvidia*'
Note, selecting 'nvidia-nsight' for regex 'nvidia*'
Note, selecting 'nvidia-331-updates-uvm' for regex 'nvidia*'
Note, selecting 'nvidia-325' for regex 'nvidia*'
Note, selecting 'nvidia-settings-319-updates' for regex 'nvidia*'
Note, selecting 'nvidia-331' for regex 'nvidia*'
Note, selecting 'nvidia-310-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-cg-toolkit' for regex 'nvidia*'
Note, selecting 'nvidia-331-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-340' for regex 'nvidia*'
Note, selecting 'nvidia-343' for regex 'nvidia*'
Note, selecting 'nvidia-346' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-331' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-debugger' for regex 'nvidia*'
Note, selecting 'nvidia-driver-binary' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-340' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-343' for regex 'nvidia*'
Note, selecting 'bumblebee-nvidia' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-346' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-toolkit' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-dev' for regex 'nvidia*'
Note, selecting 'nvidia-313-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-profiler' for regex 'nvidia*'
Note, selecting 'nvidia-settings-experimental-304' for regex 'nvidia*'
Note, selecting 'nvidia-319-dev' for regex 'nvidia*'
Note, selecting 'nvidia-310-updates' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304' for regex 'nvidia*'
Note, selecting 'nvidia-current-updates-dev' for regex 'nvidia*'
Note, selecting 'nvidia-319-updates' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331' for regex 'nvidia*'
Note, selecting 'nvidia-texture-tools' for regex 'nvidia*'
Note, selecting 'nvidia-settings-304' for regex 'nvidia*'
Note, selecting 'libgl1-nvidia-glx' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-340' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-343' for regex 'nvidia*'
Note, selecting 'nvidia-opencl-icd-346' for regex 'nvidia*'
Note, selecting 'nvidia-kernel-dkms' for regex 'nvidia*'
Note, selecting 'nvidia-settings-310' for regex 'nvidia*'
Note, selecting 'nvidia-settings-319' for regex 'nvidia*'
Note, selecting 'nvidia-va-driver' for regex 'nvidia*'
Note, selecting 'nvidia-settings-304-updates' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-profiler' for regex 'nvidia*'
Note, selecting 'nvidia-current' for regex 'nvidia*'
Note, selecting 'nvidia-settings-331' for regex 'nvidia*'
Note, selecting 'nvidia-uvm' for regex 'nvidia*'
Note, selecting 'nvidia-prime' for regex 'nvidia*'
Note, selecting 'nvidia-340-uvm' for regex 'nvidia*'
Note, selecting 'nvidia-settings-313-updates' for regex 'nvidia*'
Note, selecting 'nvidia-346-uvm' for regex 'nvidia*'
Note, selecting 'nvidia-340-dev' for regex 'nvidia*'
Note, selecting 'nvidia-173-dev' for regex 'nvidia*'
Note, selecting 'nvidia-346-dev' for regex 'nvidia*'
Note, selecting 'nvidia-libopencl1-dev' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-304' for regex 'nvidia*'
Note, selecting 'nvidia-304-dev' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-310' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-313' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-319' for regex 'nvidia*'
Note, selecting 'boinc-nvidia-cuda' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-325' for regex 'nvidia*'
Note, selecting 'nvidia-vdpau-driver' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-331' for regex 'nvidia*'
Note, selecting 'nvidia-cuda-dev' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-340' for regex 'nvidia*'
Note, selecting 'nvidia-experimental-343' for regex 'nvidia*'
Note, selecting 'nvidia-304-updates' for regex 'nvidia*'
Note, selecting 'nvidia-profiler' for regex 'nvidia*'
Note, selecting 'nvidia-173' for regex 'nvidia*'
Note, selecting 'nvidia-313-updates' for regex 'nvidia*'
Note, selecting 'libgl1-nvidia-alternatives' for regex 'nvidia*'
Note, selecting 'nvidia-331-updates' for regex 'nvidia*'
Note, selecting 'nvidia-331-uvm' for regex 'nvidia*'
Package 'libgl1-nvidia-alternatives' is not installed, so not removed
Package 'nvidia-vdpau-driver' is not installed, so not removed
Package 'nvidia-driver' is not installed, so not removed
Package 'nvidia-glx' is not installed, so not removed
Package 'nvidia-kernel-dkms' is not installed, so not removed
Package 'nvidia-kernel-amd64' is not installed, so not removed
Package 'nvidia-kernel-686-pae' is not installed, so not removed
Package 'nvidia-kernel-486' is not installed, so not removed
Package 'nvidia' is not installed, so not removed
Package 'nvidia-313' is not installed, so not removed
Package 'nvidia-experimental-313' is not installed, so not removed
Package 'nvidia-experimental-319' is not installed, so not removed
Package 'nvidia-325' is not installed, so not removed
Package 'nvidia-325-updates' is not installed, so not removed
Package 'nvidia-experimental-325' is not installed, so not removed
Package 'nvidia-experimental-331' is not installed, so not removed
Note, selecting 'libnvtt-bin' instead of 'nvidia-texture-tools'
Package 'nvidia-libopencl1-dev' is not installed, so not removed
Note, selecting 'vdpau-va-driver' instead of 'nvidia-va-driver'
Package 'libgl1-nvidia-glx' is not installed, so not removed
Package 'nvidia-cuda-debugger' is not installed, so not removed
Package 'nvidia-libopencl1' is not installed, so not removed
Package 'nvidia-compute-profiler' is not installed, so not removed
Package 'nvidia-cuda-profiler' is not installed, so not removed
Package 'nvidia-opencl-profiler' is not installed, so not removed
Package 'nvidia-340-updates' is not installed, so not removed
Package 'nvidia-experimental-340' is not installed, so not removed
Package 'nvidia-343-updates' is not installed, so not removed
Package 'nvidia-experimental-343' is not installed, so not removed
Package 'nvidia-173' is not installed, so not removed
Package 'nvidia-173-dev' is not installed, so not removed
Package 'nvidia-310' is not installed, so not removed
Package 'nvidia-310-dev' is not installed, so not removed
Package 'nvidia-310-updates' is not installed, so not removed
Package 'nvidia-310-updates-dev' is not installed, so not removed
Package 'nvidia-313-updates' is not installed, so not removed
Package 'nvidia-313-updates-dev' is not installed, so not removed
Package 'nvidia-experimental-310' is not installed, so not removed
Package 'nvidia-experimental-310-dev' is not installed, so not removed
Package 'boinc-nvidia-cuda' is not installed, so not removed
Package 'nvidia-cg-dev' is not installed, so not removed
Package 'nvidia-cg-doc' is not installed, so not removed
Package 'nvidia-cg-toolkit' is not installed, so not removed
Package 'nvidia-cuda-dev' is not installed, so not removed
Package 'nvidia-cuda-doc' is not installed, so not removed
Package 'nvidia-cuda-gdb' is not installed, so not removed
Package 'nvidia-cuda-toolkit' is not installed, so not removed
Package 'nvidia-nsight' is not installed, so not removed
Package 'nvidia-opencl-dev' is not installed, so not removed
Package 'nvidia-profiler' is not installed, so not removed
Package 'nvidia-visual-profiler' is not installed, so not removed
Package 'nvidia-304-updates' is not installed, so not removed
Package 'nvidia-304-updates-dev' is not installed, so not removed
Package 'nvidia-319-updates' is not installed, so not removed
Package 'nvidia-319-updates-dev' is not installed, so not removed
Package 'nvidia-331-updates-dev' is not installed, so not removed
Package 'nvidia-331-updates-uvm' is not installed, so not removed
Package 'nvidia-current-updates' is not installed, so not removed
Package 'nvidia-current-updates-dev' is not installed, so not removed
Package 'nvidia-experimental-304' is not installed, so not removed
Package 'nvidia-experimental-304-dev' is not installed, so not removed
Package 'nvidia-libopencl1-304-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-304-updates' is not installed, so not removed
Package 'nvidia-common' is not installed, so not removed
Package 'nvidia-persistenced' is not installed, so not removed
Package 'nvidia-settings-331' is not installed, so not removed
Package 'nvidia-current' is not installed, so not removed
Package 'nvidia-current-dev' is not installed, so not removed
Package 'nvidia-settings-updates' is not installed, so not removed
Package 'bumblebee-nvidia' is not installed, so not removed
Package 'nvidia-settings-experimental-304' is not installed, so not removed
Package 'nvidia-304' is not installed, so not removed
Package 'nvidia-304-dev' is not installed, so not removed
Package 'nvidia-settings-304' is not installed, so not removed
Package 'nvidia-settings-304-updates' is not installed, so not removed
Package 'nvidia-settings-310' is not installed, so not removed
Package 'nvidia-settings-310-updates' is not installed, so not removed
Package 'nvidia-settings-313-updates' is not installed, so not removed
Package 'nvidia-319' is not installed, so not removed
Package 'nvidia-319-dev' is not installed, so not removed
Package 'nvidia-settings-319' is not installed, so not removed
Package 'nvidia-settings-319-updates' is not installed, so not removed
Package 'nvidia-331' is not installed, so not removed
Package 'nvidia-331-dev' is not installed, so not removed
Package 'nvidia-libopencl1-331' is not installed, so not removed
Package 'nvidia-opencl-icd-331' is not installed, so not removed
Package 'nvidia-331-uvm' is not installed, so not removed
Package 'nvidia-libopencl1-304' is not installed, so not removed
Package 'nvidia-opencl-icd-304' is not installed, so not removed
Package 'nvidia-340-dev' is not installed, so not removed
Package 'nvidia-libopencl1-340' is not installed, so not removed
Package 'nvidia-opencl-icd-340' is not installed, so not removed
Package 'nvidia-343' is not installed, so not removed
Package 'nvidia-343-dev' is not installed, so not removed
Package 'nvidia-libopencl1-343' is not installed, so not removed
Package 'nvidia-opencl-icd-343' is not installed, so not removed
Package 'nvidia-343-uvm' is not installed, so not removed
Package 'nvidia-346' is not installed, so not removed
Package 'nvidia-346-dev' is not installed, so not removed
Package 'nvidia-libopencl1-346' is not installed, so not removed
Package 'nvidia-opencl-icd-346' is not installed, so not removed
Package 'nvidia-346-uvm' is not installed, so not removed
The following packages will be REMOVED:
nvidia-331-updates* nvidia-340* nvidia-340-uvm*
nvidia-libopencl1-331-updates* nvidia-opencl-icd-331-updates* nvidia-prime*
nvidia-settings*
0 upgraded, 0 newly installed, 7 to remove and 12 not upgraded.
After this operation, 301 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 294764 files and directories currently installed.)
Removing nvidia-331-updates (331.113-0ubuntu0.0.4) ...
Purging configuration files for nvidia-331-updates (331.113-0ubuntu0.0.4) ...
stop: Unknown job: nvidia-persistenced
update-initramfs: deferring update (trigger activated)
Removing nvidia-340-uvm (340.65-0ubuntu1~xedgers14.04.1) ...
Removing all DKMS Modules
Done.
Removing nvidia-340 (340.65-0ubuntu1~xedgers14.04.1) ...
Removing all DKMS Modules
Done.
update-alternatives: using /usr/lib/nvidia-340-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode
update-alternatives: using /usr/lib/nvidia-340-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode
update-alternatives: using /usr/lib/i386-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
INFO:Disable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
update-initramfs: deferring update (trigger activated)
Purging configuration files for nvidia-340 (340.65-0ubuntu1~xedgers14.04.1) ...
update-initramfs: deferring update (trigger activated)
Removing nvidia-opencl-icd-331-updates (331.113-0ubuntu0.0.4) ...
Purging configuration files for nvidia-opencl-icd-331-updates (331.113-0ubuntu0.0.4) ...
Removing nvidia-libopencl1-331-updates (331.113-0ubuntu0.0.4) ...
Purging configuration files for nvidia-libopencl1-331-updates (331.113-0ubuntu0.0.4) ...
Removing nvidia-prime (0.6.2) ...
Purging configuration files for nvidia-prime (0.6.2) ...
Removing nvidia-settings (346.22-0ubuntu1~xedgers14.04.1) ...
Purging configuration files for nvidia-settings (346.22-0ubuntu1~xedgers14.04.1) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.11.0-14-generic
Processing triggers for libc-bin (2.19-0ubuntu6.4) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
@:~/nvidia$ exit
exit
---------------
Script done on Mon 12 Jan 2015 08:09:48 PM PST
---------------
$ script -a $HOME/purge.log
Script started on Mon Jan 12 20:13:46 2015
---------------
$ modprobe -R nvidia
modprobe: FATAL: Module nvidia not found.
---------------
$ xdriinfo
Screen 0: not direct rendering capable.
---------------
$ glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig
---------------
$ inxi -F
...
Graphics: Card: NVIDIA GT216GLM [Quadro FX 880M]
drivers: nvidia,fbdev,nouveau (unloaded: vesa) Resolution:***@73.0hz
---------------
$ cat /etc/default/grub|grep CMDLINE
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""
---------------
$ cat /etc/modprobe.d/nvidia-graphics-drivers.conf
---------------
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2)
---------------
$ exit
Script done on Mon Jan 12 20:19:20 2015
---------------
$ sudo reboot
---------------
(KDE)System Settings > Driver Manager
(set to the latest Recommended Nvidia)
---------------
(KDE)System Settings > Display & Monitor
(try to set to 1920x1080 - but it will
be impossible)
---------------
$ script -a $HOME/purge.log
Script started on Mon Jan 12 20:19:22 2015
---------------
$ modprobe -R nvidia
nvidia_340
---------------
$ xdriinfo
libGL is too old.
---------------
$ glxinfo
name of display: :0
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
---------------
$ inxi -F
Graphics: Card:NVIDIA GT216GLM [Quadro FX 880M]
X.Org:1.15.1 drivers:nvidia,fbdev,nouveau (unloaded: vesa) Resolution:***@73.0hz
---------------
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
default connected primary 640x480+0+0 0mm x 0mm
640x480 73.0*
---------------
$ cat /etc/modprobe.d/nvidi a-graphics-drivers.conf
# This file was installed by nvidia-340
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-current
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-340-updates
alias nvidia nvidia_340
alias nvidia-uvm nvidia_340-uvm
alias nouveau off
alias lbm-nouveau off
---------------
$ exit
Script done on Mon Jan 12 20:27:30 2015
---------------
No change.
William Unruh
2015-01-13 06:22:37 UTC
Permalink
Post by Jean-Pierre
Post by mike
Or we could stay here and call each
other names.
In addition ...
I should note that I have tried EVERY SINGLE
SUGGESTION that was suggested. Not only did
I try every single suggestion, but I DOCUMENTED
what happened when I tried it. In detail.
I repeat I have reported back EXACTLY what
the command line or log files said in EVERY
single instance.
I don't mind REPEATING what I did.
If anyone missed the steps, let me know and
I will show you what I did and what the results
were.
At the moment, the KDE Device Manager is failing
every single time, without any log that I know
of.
The Nvidia method is failing every time, saying
that the DKMS headers need to be added, but,
nowhere in this thread or on the net is there
a command that works to INSTALL those DKMS
headers.
No. It did NOT say that DKMS headers were missing. It said that the
kernel headers were missing. YOu have kernel headers for a number of
3.13 kernels, but none for 3.11 kernel you are now running for some
reason.
Post by Jean-Pierre
$ dpkg --get-selections | grep nvidia
nvidia-331-updates install
nvidia-331-updates-uvm install
nvidia-libopencl1-331-updates install
nvidia-opencl-icd-331-updates install
nvidia-prime install
nvidia-settings install
$ sudo apt-get install nvidia-kernel-dkms nvidia-xconfig nvidia-settings
E: Package 'nvidia-kernel-dkms' has no installation candidate
E: Unable to locate package nvidia-xconfig
$ ubuntu-drivers devices | grep recommended
driver : nvidia-340 - third-party free recommended
<control><alt><F1>
$ [login]
$ sudo service lightdm stop
$ sudo apt-get install nvidia-340
$ sudo reboot
Jean-Pierre
2015-01-13 06:34:03 UTC
Permalink
No. It did NOT say that DKMS headers were missing. It said that the kernel
headers were missing. YOu have kernel headers for a number of 3.13
kernels, but none for 3.11 kernel you are now running for some reason.
Hmmmmmmm..... OK. This makes sense.

I don't care WHAT kernel I am running.
Would you suggest I update the kernel?

Is that what the "12 not upgraded" is
trying to tell me?

$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Jonathan N. Little
2015-01-13 16:18:30 UTC
Permalink
Post by Jean-Pierre
No. It did NOT say that DKMS headers were missing. It said that the kernel
headers were missing. YOu have kernel headers for a number of 3.13
kernels, but none for 3.11 kernel you are now running for some reason.
Hmmmmmmm..... OK. This makes sense.
I don't care WHAT kernel I am running.
Would you suggest I update the kernel?
Is that what the "12 not upgraded" is
trying to tell me?
Yes. That is exactly what it is say...especially if you review the list
of packages *above* that summary.
Post by Jean-Pierre
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
No. Do:

sudo apt-get dist-upgrade && sudo reboot

Then you will boot into the same kernel which you are trying to install
drivers complied for.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Cybe R. Wizard
2015-01-13 08:55:15 UTC
Permalink
On Mon, 12 Jan 2015 17:50:05 -0800
Post by mike
How would you feel if you called the car dealer and said,
"My car won't start," and the dealer replied,
"It's because you don't want it to?"
If I were driving a Chevy but kept trying to use Chrysler parts and a
Ford repair book, then kept on whining about how nothing worked I'd
think it to be completely justified.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 11:26:11 UTC
Permalink
If I were driving a Chevy but kept trying to use Chrysler parts and a Ford
repair book, then kept on whining about how nothing worked I'd think it to
be completely justified.
Actually, now that we know it's a kernel mismatch,
I think it's more like I am trying to fix a Chevy
but the parts guy gave me a waterpump for a Chrysler.

My problem appears to be that I have a kernel for
3.11 but parts from 3.13.
DecadentLinuxUserNumeroUno
2015-01-13 11:57:45 UTC
Permalink
Post by Jean-Pierre
Post by Cybe R. Wizard
If I were driving a Chevy but kept trying to use Chrysler parts and a
Ford repair book, then kept on whining about how nothing worked I'd
think it to be completely justified.
Actually, now that we know it's a kernel mismatch,
I think it's more like I am trying to fix a Chevy but the parts guy gave
me a waterpump for a Chrysler.
My problem appears to be that I have a kernel for 3.11 but parts from
3.13.
Perhaps you updated your kernel, but you are still booting the old one,
while everything else expects to see the new one.

You probably are even the one who overwrote it it in your fix it zeal.

Have you ever even ran "update-grub"?
Jean-Pierre
2015-01-13 12:57:30 UTC
Permalink
Post by DecadentLinuxUserNumeroUno
Have you ever even ran "update-grub"?
I ran "update-grub" when I modified the
grub to add the nomodeset parameter that
was suggested here.

I do have MULTIPLE versions of Kubuntu
that I can install from, so, I will try
that out.

The one thing I'm confused is that I lost
the command that tells me which header
versions I have.

I can find my kernel with "uname -r" but
do you remember the command for telling me
the header file versions that are installed?
Jean-Pierre
2015-01-13 13:35:03 UTC
Permalink
The one thing I'm confused is that I lost the command that tells me which
header versions I have.
I found that header version command here.
http://askubuntu.com/questions/224942/why-are-linux-headers-not-upgraded-by-apt-git-dist-upgrade

So I appear to have the "3.11.0-14-generic" kernel
but the "3.13.0-37-generic" & "3.13.0-44-generic"
headers.

Why this command doesn't work is beyond my comprehension,
because, if it did, we'd be done long ago.
$ sudo apt-get install build-essential linux-headers-`uname -r`
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.11.0-14-generic is not available,
but is referred to by another package.
This may mean that the package is missing,
has been obsoleted, or is only available from another source
E: Package 'linux-headers-3.11.0-14-generic' has no
installation candidate

Why this fails is also beyond my comprehension:
$ sudo apt-get install linux-headers-generic
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Since all attempts to 'fix' the headers seems fraught
to fail, the only thing left is to 'fix' the kernel.

But how?
Richard Kettlewell
2015-01-13 13:45:18 UTC
Permalink
Post by Jean-Pierre
The one thing I'm confused is that I lost the command that tells me
which header versions I have.
I found that header version command here.
http://askubuntu.com/questions/224942/why-are-linux-headers-not-upgraded-by-apt-git-dist-upgrade
So I appear to have the "3.11.0-14-generic" kernel
but the "3.13.0-37-generic" & "3.13.0-44-generic"
headers.
3.11.0-14-generic only exists in precise (12.04); the other two exist in
both precise and trusty (14.04). Which of the two versions of Ubuntu
are you attempting to use?
Post by Jean-Pierre
Why this command doesn't work is beyond my comprehension,
because, if it did, we'd be done long ago.
$ sudo apt-get install build-essential linux-headers-`uname -r`
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.11.0-14-generic is not available,
but is referred to by another package.
This may mean that the package is missing,
has been obsoleted, or is only available from another source
E: Package 'linux-headers-3.11.0-14-generic' has no
installation candidate
$ sudo apt-get install linux-headers-generic
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Since all attempts to 'fix' the headers seems fraught
to fail, the only thing left is to 'fix' the kernel.
But how?
Install linux-image-generic and reboot?
--
http://www.greenend.org.uk/rjk/
Jean-Pierre
2015-01-13 14:19:36 UTC
Permalink
Post by Richard Kettlewell
3.11.0-14-generic only exists in precise
(12.04);
the other two exist in both precise and
trusty (14.04).
Which of the two versions of Ubuntu are
you attempting to use?
I don't care WHICH version I use, but I only
have Kubuntu version 14.04 as far as I know.
$ lsb_release -d
Description: Ubuntu 14.04.1 LTS

I'm not sure which command tells me it's
Kubuntu and not Ubuntu though.
Post by Richard Kettlewell
Install linux-image-generic and reboot?
I've already tried that.
The ugly log file will be in the next post
so as to not mess up this suggestion.
Jean-Pierre
2015-01-13 14:22:27 UTC
Permalink
Post by Jean-Pierre
The ugly log file will be in the next post
I'm rebooting now - but here's the ugly
log file after running the suggested command.


Script started on Tue Jan 13 06:16:39 2015
$ sudo apt-get install linux-image-generic
Reading package lists... 0%Reading package lists... 100%Reading package lists... Done
Building dependency tree... 0%Building dependency tree... 0%Building dependency tree... 50%Building dependency tree... 50%Building dependency tree
Reading state information... 0%Reading state information... 0%Reading state information... Done
The following extra packages will be installed:
linux-image-3.13.0-44-generic linux-image-extra-3.13.0-44-generic
Suggested packages:
fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
The following packages will be REMOVED:
linux-image-3.13.0-44-generic:i386 linux-image-extra-3.13.0-44-generic:i386
linux-image-generic:i386 linux-image-generic-pae:i386
The following NEW packages will be installed:
linux-image-3.13.0-44-generic linux-image-extra-3.13.0-44-generic
linux-image-generic
0 upgraded, 3 newly installed, 4 to remove and 0 not upgraded.
Need to get 51.8 MB of archives.
After this operation, 48.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
0% [Working] Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-3.13.0-44-generic amd64 3.13.0-44.73 [15.1 MB]
0% [1 linux-image-3.13.0-44-generic 2641 B/15.1 MB 0%]0% [1 linux-image-3.13.0-44-generic 136 kB/15.1 MB 1%]1% [1 linux-image-3.13.0-44-generic 388 kB/15.1 MB 3%]1% [1 linux-image-3.13.0-44-generic 637 kB/15.1 MB 4%]2% [1 linux-image-3.13.0-44-generic 961 kB/15.1 MB 6%] 3% [1 linux-image-3.13.0-44-generic 1315 kB/15.1 MB 9%] 3% [1 linux-image-3.13.0-44-generic 1707 kB/15.1 MB 11%]4% [1 linux-image-3.13.0-44-generic 2094 kB/15.1 MB 14%]5% [1 linux-image-3.13.0-44-generic 2626 kB/15.1 MB 17%]6% [1 linux-image-3.13.0-44-generic 3194 kB/15.1 MB 21%]7% [1 linux-image-3.13.0-44-generic 3869 kB/15.1 MB 26%]9% [1 linux-image-3.13.0-44-generic 4571 kB/15.1 MB 30%] 10% [1 linux-image-3.13.0-44-generic 5398 kB/15.1 MB 36%] 844 kB/s 55s12% [1 linux-image-3.13.0-44-generic 6107 kB/15.1 MB 40%] 844 kB/s 54s13% [1 linux-image-3.13.0-44-generic 6827 kB/15.1 MB 45%] 844 kB/s 53s15% [1 linux-image-3.13.0-44-generic 7639 kB/15.1 MB 51%] 844 kB/s 52s16% [1 linux-image-3.13.0-44-generic 8453 kB/15.1 MB 56%] 844 kB/s 51s18% [1 linux-image-3.13.0-44-generic 9213 kB/15.1 MB 61%] 844 kB/s 50s20% [1 linux-image-3.13.0-44-generic 10.3 MB/15.1 MB 68%] 844 kB/s 49s21% [1 linux-image-3.13.0-44-generic 10.8 MB/15.1 MB 71%] 844 kB/s 48s23% [1 linux-image-3.13.0-44-generic 12.1 MB/15.1 MB 80%] 844 kB/s 47s25% [1 linux-image-3.13.0-44-generic 13.1 MB/15.1 MB 86%] 844 kB/s 45s27% [1 linux-image-3.13.0-44-generic 13.9 MB/15.1 MB 92%] 844 kB/s 44s29% [1 linux-image-3.13.0-44-generic 14.8 MB/15.1 MB 98%] 844 kB/s 43s29% [Working] 844 kB/s 43s Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-extra-3.13.0-44-generic amd64 3.13.0-44.73 [36.7 MB]
29% [2 linux-image-extra-3.13.0-44-generic 2640 B/36.7 MB 0%] 844 kB/s 43s31% [2 linux-image-extra-3.13.0-44-generic 825 kB/36.7 MB 2%] 1652 kB/s 21s32% [2 linux-image-extra-3.13.0-44-generic 1734 kB/36.7 MB 5%] 1652 kB/s 21s34% [2 linux-image-extra-3.13.0-44-generic 2583 kB/36.7 MB 7%] 1652 kB/s 20s35% [2 linux-image-extra-3.13.0-44-generic 3217 kB/36.7 MB 9%] 1652 kB/s 20s36% [2 linux-image-extra-3.13.0-44-generic 3654 kB/36.7 MB 10%] 1652 kB/s 20s37% [2 linux-image-extra-3.13.0-44-generic 4332 kB/36.7 MB 12%] 1652 kB/s 19s39% [2 linux-image-extra-3.13.0-44-generic 4866 kB/36.7 MB 13%] 1652 kB/s 19s40% [2 linux-image-extra-3.13.0-44-generic 5698 kB/36.7 MB 16%] 1652 kB/s 18s42% [2 linux-image-extra-3.13.0-44-generic 6482 kB/36.7 MB 18%] 1652 kB/s 18s43% [2 linux-image-extra-3.13.0-44-generic 7315 kB/36.7 MB 20%] 1652 kB/s 17s45% [2 linux-image-extra-3.13.0-44-generic 8052 kB/36.7 MB 22%] 1652 kB/s 17s46% [2 linux-image-extra-3.13.0-44-generic 8885 kB/36.7 MB 24%] 1652 kB/s 16s48% [2 linux-image-extra-3.13.0-44-generic 9565 kB/36.7 MB 26%] 1455 kB/s 18s49% [2 linux-image-extra-3.13.0-44-generic 10.4 MB/36.7 MB 28%] 1455 kB/s 18s51% [2 linux-image-extra-3.13.0-44-generic 11.3 MB/36.7 MB 31%] 1455 kB/s 17s52% [2 linux-image-extra-3.13.0-44-generic 12.0 MB/36.7 MB 33%] 1455 kB/s 17s54% [2 linux-image-extra-3.13.0-44-generic 12.8 MB/36.7 MB 35%] 1455 kB/s 16s55% [2 linux-image-extra-3.13.0-44-generic 13.4 MB/36.7 MB 37%] 1455 kB/s 16s56% [2 linux-image-extra-3.13.0-44-generic 14.1 MB/36.7 MB 38%] 1455 kB/s 15s58% [2 linux-image-extra-3.13.0-44-generic 14.8 MB/36.7 MB 40%] 1455 kB/s 15s59% [2 linux-image-extra-3.13.0-44-generic 15.5 MB/36.7 MB 42%] 1455 kB/s 14s59% [2 linux-image-extra-3.13.0-44-generic 15.7 MB/36.7 MB 43%] 1455 kB/s 14s61% [2 linux-image-extra-3.13.0-44-generic 16.3 MB/36.7 MB 44%] 1455 kB/s 14s62% [2 linux-image-extra-3.13.0-44-generic 17.0 MB/36.7 MB 46%] 1455 kB/s 13s63% [2 linux-image-extra-3.13.0-44-generic 17.6 MB/36.7 MB 48%] 1340 kB/s 14s64% [2 linux-image-extra-3.13.0-44-generic 18.1 MB/36.7 MB 49%] 1340 kB/s 13s65% [2 linux-image-extra-3.13.0-44-generic 18.6 MB/36.7 MB 51%] 1340 kB/s 13s66% [2 linux-image-extra-3.13.0-44-generic 19.3 MB/36.7 MB 53%] 1340 kB/s 13s68% [2 linux-image-extra-3.13.0-44-generic 20.0 MB/36.7 MB 54%] 1340 kB/s 12s69% [2 linux-image-extra-3.13.0-44-generic 20.5 MB/36.7 MB 56%] 1340 kB/s 12s70% [2 linux-image-extra-3.13.0-44-generic 21.1 MB/36.7 MB 57%] 1340 kB/s 11s71% [2 linux-image-extra-3.13.0-44-generic 21.6 MB/36.7 MB 59%] 1340 kB/s 11s72% [2 linux-image-extra-3.13.0-44-generic 22.2 MB/36.7 MB 60%] 1340 kB/s 10s73% [2 linux-image-extra-3.13.0-44-generic 22.8 MB/36.7 MB 62%] 1340 kB/s 10s74% [2 linux-image-extra-3.13.0-44-generic 23.3 MB/36.7 MB 64%] 1340 kB/s 10s75% [2 linux-image-extra-3.13.0-44-generic 23.8 MB/36.7 MB 65%] 1340 kB/s 9s76% [2 linux-image-extra-3.13.0-44-generic 24.3 MB/36.7 MB 66%] 1109 kB/s 11s77% [2 linux-image-extra-3.13.0-44-generic 24.9 MB/36.7 MB 68%] 1109 kB/s 10s78% [2 linux-image-extra-3.13.0-44-generic 25.3 MB/36.7 MB 69%] 1109 kB/s 10s79% [2 linux-image-extra-3.13.0-44-generic 25.8 MB/36.7 MB 70%] 1109 kB/s 9s80% [2 linux-image-extra-3.13.0-44-generic 26.4 MB/36.7 MB 72%] 1109 kB/s 9s81% [2 linux-image-extra-3.13.0-44-generic 27.0 MB/36.7 MB 74%] 1109 kB/s 8s83% [2 linux-image-extra-3.13.0-44-generic 27.7 MB/36.7 MB 75%] 1109 kB/s 8s84% [2 linux-image-extra-3.13.0-44-generic 28.2 MB/36.7 MB 77%] 1109 kB/s 7s84% [2 linux-image-extra-3.13.0-44-generic 28.6 MB/36.7 MB 78%] 1109 kB/s 7s85% [2 linux-image-extra-3.13.0-44-generic 28.9 MB/36.7 MB 79%] 1109 kB/s 7s86% [2 linux-image-extra-3.13.0-44-generic 29.4 MB/36.7 MB 80%] 1109 kB/s 6s87% [2 linux-image-extra-3.13.0-44-generic 30.0 MB/36.7 MB 82%] 1109 kB/s 6s88% [2 linux-image-extra-3.13.0-44-generic 30.5 MB/36.7 MB 83%] 1043 kB/s 5s89% [2 linux-image-extra-3.13.0-44-generic 31.2 MB/36.7 MB 85%] 1043 kB/s 5s91% [2 linux-image-extra-3.13.0-44-generic 31.8 MB/36.7 MB 87%] 1043 kB/s 4s92% [2 linux-image-extra-3.13.0-44-generic 32.4 MB/36.7 MB 88%] 1043 kB/s 4s93% [2 linux-image-extra-3.13.0-44-generic 33.0 MB/36.7 MB 90%] 1043 kB/s 3s94% [2 linux-image-extra-3.13.0-44-generic 33.6 MB/36.7 MB 91%] 1043 kB/s 3s95% [2 linux-image-extra-3.13.0-44-generic 34.1 MB/36.7 MB 93%] 1043 kB/s 2s96% [2 linux-image-extra-3.13.0-44-generic 34.8 MB/36.7 MB 95%] 1043 kB/s 1s98% [2 linux-image-extra-3.13.0-44-generic 35.6 MB/36.7 MB 97%] 1043 kB/s 1s99% [2 linux-image-extra-3.13.0-44-generic 36.3 MB/36.7 MB 99%] 1043 kB/s 0s100% [Working] 1043 kB/s 0s Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-generic amd64 3.13.0.44.51 [2800 B]
100% [3 linux-image-generic 1200 B/2800 B 43%] 1043 kB/s 0s100% [Working] 1043 kB/s 0s Fetched 51.8 MB in 41s (1243 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en",
LC_ALL = (unset),
LC_TIME = "en_C.UTF-8",
LC_MONETARY = "en_C.UTF-8",
LC_ADDRESS = "en_C.UTF-8",
LC_TELEPHONE = "en_C.UTF-8",
LC_NAME = "en_C.UTF-8",
LC_MEASUREMENT = "en_C.UTF-8",
LC_IDENTIFICATION = "en_C.UTF-8",
LC_NUMERIC = "en_C.UTF-8",
LC_PAPER = "en_C.UTF-8",
LANG = "en_C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 303455 files and directories currently installed.)
Removing linux-image-generic-pae (3.13.0.44.51) ...
Removing linux-image-generic (3.13.0.44.51) ...
Removing linux-image-extra-3.13.0-44-generic (3.13.0-44.73) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-44-generic
Found initrd image: /boot/initrd.img-3.13.0-44-generic
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
done
Removing linux-image-3.13.0-44-generic (3.13.0-44.73) ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
dkms: removing: bbswitch 0.7 (3.13.0-44-generic) (x86_64)

-------- Uninstall Beginning --------
Module: bbswitch
Version: 0.7
Kernel: 3.13.0-44-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

bbswitch.ko:
- Uninstallation
- Deleting from: /lib/modules/3.13.0-44-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 0.7
completely from the DKMS tree.
------------------------------
Done.
dkms: removing: nvidia-340-uvm 340.65 (3.13.0-44-generic) (x86_64)

-------- Uninstall Beginning --------
Module: nvidia-340-uvm
Version: 340.65
Kernel: 3.13.0-44-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia-340-uvm.ko:
- Uninstallation
- Deleting from: /lib/modules/3.13.0-44-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 340.65
completely from the DKMS tree.
------------------------------
Done.
dkms: removing: nvidia-340 340.65 (3.13.0-44-generic) (x86_64)

-------- Uninstall Beginning --------
Module: nvidia-340
Version: 340.65
Kernel: 3.13.0-44-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia_340.ko:
- Uninstallation
- Deleting from: /lib/modules/3.13.0-44-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 340.65
completely from the DKMS tree.
------------------------------
Done.
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-44-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]
Selecting previously unselected package linux-image-3.13.0-44-generic.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 298468 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-44-generic_3.13.0-44.73_amd64.deb ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Done.
Unpacking linux-image-3.13.0-44-generic (3.13.0-44.73) ...
Selecting previously unselected package linux-image-extra-3.13.0-44-generic.
Preparing to unpack .../linux-image-extra-3.13.0-44-generic_3.13.0-44.73_amd64.deb ...
Unpacking linux-image-extra-3.13.0-44-generic (3.13.0-44.73) ...
Selecting previously unselected package linux-image-generic.
Preparing to unpack .../linux-image-generic_3.13.0.44.51_amd64.deb ...
Unpacking linux-image-generic (3.13.0.44.51) ...
Setting up linux-image-3.13.0-44-generic (3.13.0-44.73) ...
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-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-44-generic
Found initrd image: /boot/initrd.img-3.13.0-44-generic
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
done
Setting up linux-image-extra-3.13.0-44-generic (3.13.0-44.73) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-44-generic /boot/vmlinuz-3.13.0-44-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-44-generic
Found initrd image: /boot/initrd.img-3.13.0-44-generic
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
done
Setting up linux-image-generic (3.13.0.44.51) ...
$ exit
exit

Script done on Tue Jan 13 06:19:38 2015
Jean-Pierre
2015-01-13 14:46:50 UTC
Permalink
Post by Jean-Pierre
I'm rebooting now
I think your suggestion was the best to date
in that the kernel version mismatch with the
header file version was apparently preventing
the POS KDE Driver Management Software from
working.

The POS KDE Driver Management software is
still not working, but, with the match now
of the kernel with the header files, I am
hopeful that the Nvidia-prescribed
installation method will work.

Here's the new result after running your
suggested command:
$ sudo apt-get install linux-image-generic
$ sudo reboot
$ sudo update-grub
$ uname -r
3.13.0-44-generic
$ dpkg -l | grep linux-headers
ii linux-headers-3.13.0-37 3.13.0-37.64 all Header files related to Linux kernel version 3.13.0
ii linux-headers-3.13.0-37-generic 3.13.0-37.64 amd64 Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii linux-headers-3.13.0-44 3.13.0-44.73 all Header files related to Linux kernel version 3.13.0
ii linux-headers-3.13.0-44-generic 3.13.0-44.73 amd64 Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii linux-headers-generic 3.13.0.44.51 amd64 Generic Linux kernel headers

Notice that even though the POS KDE
Driver Management Software still fails,
at least the headers match the kernel.

So, I'll run through the formal Nvidia
installation procedure now (which requires
a reboot since you can never get out of
<control><alt><F1> back to X).
Cybe R. Wizard
2015-01-13 14:56:14 UTC
Permalink
On Tue, 13 Jan 2015 08:46:50 -0600
Post by Jean-Pierre
since you can never get out of
<control><alt><F1> back to X).
Nonsense. Have you tried all the F<numbers>?

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 15:29:53 UTC
Permalink
Post by Cybe R. Wizard
Nonsense. Have you tried all the F<numbers>?
I've tried F1 and F7.
But, at this point, I'm done as the problem is
resolved!

I will try to write a concise summary, so others
benefit, but the main less is

1. Never use the POS KDE Driver Manager Software
unless you know it will work (because when it
fails, it doesn't tell you anything).

2. Always use the Nvidia web site installer but
make sure there are NO ERRORS in the log file.

Of course, the trick was whoever was the genius
that figured out what the log file was saying
about DKMS (being that the kernel and headers
were mismatched in versions).

3. The third trick came from Richard Kettlewell,
who figured out that you have to solve the
problem backward.

You can't bring the headers to the level of
the kernel; you have to bring the kernel to
the level of the headers.

With those three things in mind, the solution to
the problem was simple!

Thanks to the folks here!
Jean-Pierre
2015-01-13 15:26:20 UTC
Permalink
Post by Richard Kettlewell
Install linux-image-generic and reboot?
This WAS the solution!
http://i62.tinypic.com/16jrc0g.jpg
Jean-Pierre
2015-01-13 17:09:53 UTC
Permalink
Post by Richard Kettlewell
3.11.0-14-generic only exists in precise (12.04)
This explained why all the advice to update the
headers to match the kernel was doomed to fail.
Jean-Pierre
2015-01-13 17:08:30 UTC
Permalink
Post by DecadentLinuxUserNumeroUno
Perhaps you updated your kernel, but you
are still booting the old one,
while everything else expects to see the new one.
It turns out I only had one kernel.

And, it turns out that you can't update the headers
to match that of the kernel.

You have to update the kernel to match that of
the headers.

The other thing it turns out is to never use the
KDE tools unless everything works. The moment
things don't work, the problem with the KDE tools
is that none of them have useful error messages.

Even the Nvidia error message is cryptic, but,
some people here were able to decipher it.

So, the problem boils down to the simple fact
that the kernel had to be updated to synchronize
with the headers and that the Nvidia tool had
to be used instead of the KDE tools.
DecadentLinuxUserNumeroUno
2015-01-13 17:53:35 UTC
Permalink
And, it turns out that you can't update the headers to match that of the
kernel.
Maybe in your world.
Jean-Pierre
2015-01-13 18:12:56 UTC
Permalink
Post by DecadentLinuxUserNumeroUno
Maybe in your world.
It never would have worked, as shown by Richard Kettlewell.
But, luckily, it works now.

The debugging trick was these commands needed to match results:
1. uname -r
2. dpkg -l

The installation trick was that these had to run in sequence:
1. sudo apt-get install linux-image-generic
2. sh NVIDIA-Linux-x86_64-340.65.run

Thanks!

Cybe R. Wizard
2015-01-13 14:35:36 UTC
Permalink
On Tue, 13 Jan 2015 05:26:11 -0600
Post by Jean-Pierre
Post by Cybe R. Wizard
If I were driving a Chevy but kept trying to use Chrysler parts and
a Ford repair book, then kept on whining about how nothing worked
I'd think it to be completely justified.
Actually, now that we know it's a kernel mismatch,
I think it's more like I am trying to fix a Chevy
but the parts guy gave me a waterpump for a Chrysler.
My problem appears to be that I have a kernel for
3.11 but parts from 3.13.
?? Both are kernels. What was wrong with Linux for Workgroups?

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Aragorn
2015-01-13 15:50:24 UTC
Permalink
On Tuesday 13 January 2015 15:35, Cybe R. Wizard conveyed the following
to alt.os.linux...
Post by Cybe R. Wizard
On Tue, 13 Jan 2015 05:26:11 -0600
Post by Jean-Pierre
Post by Cybe R. Wizard
If I were driving a Chevy but kept trying to use Chrysler parts and
a Ford repair book, then kept on whining about how nothing worked
I'd think it to be completely justified.
Actually, now that we know it's a kernel mismatch,
I think it's more like I am trying to fix a Chevy
but the parts guy gave me a waterpump for a Chrysler.
My problem appears to be that I have a kernel for
3.11 but parts from 3.13.
?? Both are kernels. What was wrong with Linux for Workgroups?
He was trying to run the nvidia driver installer, which requires the
kernel headers. He had the headers for 3.13 installed, but not for
3.11, and he was running 3.11.

So the nvidia driver installer script barfed, which is only natural.
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jean-Pierre
2015-01-13 17:05:49 UTC
Permalink
Post by Peter Köhlmann
Noen of the methods work for you.
Because you don't want them to
Of all the advice, this was the least useful.

Luckily, half the advice here worked.
The other half would never have worked.

Only after having taken all of the advice,
would I have known that.

Thanks.
Dirk T. Verbeek
2015-01-12 17:56:41 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
Something funny is going on, but I don't know what
and only need debugging commands.
Again, I repeat: I ask for help in DEBUGGING commands.
Here is the gory detail (but the request is for
debugging commands so that I UNDERSTAND what is
going on).
The Lenovo W510 laptop display was fine, for two days
(see previous thread).
Then the machine locked up, so I forced a hard button
shutdown, and when it came up, the screen was at
1024x768 instead of 1920x1080.
The funny thing was that the Nvidia driver was
in place according to the command line but
according to KDE System Settings, nouveau was
installed.
I tried to re-install the Nvidia driver using
KDE System Settings "Driver Manager", but it
wouldn't allow the "Apply" button (it was
greyed out) so I chose an earlier Nvidia driver
in the selection, and rebooted.
http://i59.tinypic.com/2nasp38.png
http://i58.tinypic.com/2r2pxrm.png
$ modprobe -R nvidia
nvidia_331_updates
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0
848x480 0.0
640x480 60.0
The KDE System Settings "Display and Monitor"
are showing only "default" settings of
1024x768, even though the same GUI shows that
the Nvidia drivers are installed.
http://i58.tinypic.com/2j61noj.png
The Google inxi -F command used to show that
LVDS-1 was connected primary 1920x1080, but
now it shows that the screen resolution is
limited to 1024x768.
$ inxi -F
Card: NVIDIA GT216GLM [Quadro FX 880M]
X.Org: 1.15.1 drivers: nvidia,fbdev,vesa,nouveau
GLX Renderer: N/A GLX Version: N/A
But the xdriinfo and glxinfo commands don't
tell us much.
$ xdriinfo
libGL is too old.
$ glxinfo
name of display: :0
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
Xlib: extension "GLX" missing on display ":0".
$ grep CMDLINE /etc/default/grub
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""
$ cat /etc/modprobe.d/nvidia-graphics-drivers.conf
# This file was installed by nvidia-331-updates
# Do not edit this file manually
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-331
alias nvidia nvidia_331_updates
alias nvidia-uvm nvidia_331_updates-uvm
alias nouveau off
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2)
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
When running the official nVidia driver forget about xrandr and KDE
display settings but instead use the nVidia X Server Settings.
/usr/bin/nvidia-settings

Running Kubuntu either with nouveau or nVidia on a W510 should (as you
experienced before) be dead simple and out of the box.
Jean-Pierre
2015-01-13 01:14:34 UTC
Permalink
Post by Dirk T. Verbeek
use the nVidia X Server Settings.
/usr/bin/nvidia-settings
That brings up a GUI, but that GUI doesn't
seem to actually do much that is useful.
Loading Image...
Post by Dirk T. Verbeek
Running Kubuntu either with nouveau
or nVidia on a W510 should (as you
experienced before) be dead simple
and out of the box.
I agree.
When I installed the original OS, I
remember having some problems, but then
it worked. And it worked for a long time.
Until recently.
Jonathan N. Little
2015-01-13 02:27:51 UTC
Permalink
Post by Jean-Pierre
Post by Dirk T. Verbeek
use the nVidia X Server Settings.
/usr/bin/nvidia-settings
That brings up a GUI, but that GUI doesn't
seem to actually do much that is useful.
http://i61.tinypic.com/erh0s9.png
Post by Dirk T. Verbeek
Running Kubuntu either with nouveau
or nVidia on a W510 should (as you
experienced before) be dead simple
and out of the box.
I agree.
When I installed the original OS, I
remember having some problems, but then
it worked. And it worked for a long time.
Until recently.
You must of totally foobar'd your setup with a partial mix of nouveau
and manual proprietary install script failures. It *IS* simple when you
don't do all the crap that you have done, re-done, and continue to redo!
Yes, you *used* to have to muck about in earlier versions of Ubuntu to
install the nVidia driver (mostly because of nVidia's lack of
cooperation), but it is not needed now.

This installed with no compiling, no install scripts, no hand tweaking,
hair pulling...just from Additional Drivers (Driver Manager KDE) I
selected the driver from the list and then rebooted:

<http://www.littleworksstudio.com/temp/usenet/nVidiaSettings>

It installs the correct driver, the correct setting tools, and disabled
the nouveau driver and dependencies all with ONE simple click selection
from a list!!!!

How to fix your mess? I'd purge all nvidia components to put you back on
original default nouveau and then ONLY change via the Driver Manager.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 03:58:56 UTC
Permalink
Post by Jonathan N. Little
How to fix your mess?
I'd purge all nvidia components to put
you back on original default nouveau
and then ONLY change via the Driver Manager.
That sounds like good advice.
To purge, I presume you mean the following:
$ sudo apt-get purge nvidia*

Of course, the question is always WHEN to run
that command, considering lightdm is running,
so, I presume you imply that I need to press
<control><alt><F1> first, and then login
and then stop lightdm with
$ sudo service lightdm stop

Only then, I presume you mean to run the
purge command, so, that's what I will do,
and report back.

Unfortunately, the <control><alt><F7> never
gets me BACK into X windows, so, I have to
reboot.

In short, I'll follow your directions, adding
what you implied, by running the following:

1. <control><alt>F1
2. Login as the user
3. sudo service lightdm stop
4. sudo apt-get purge nvidia*
5. sudo reboot
6. KDE System Settings "Driver Manager"
7. Set the driver and click "Apply".

Is that EXACTLY what you are suggesting?
William Unruh
2015-01-13 06:13:48 UTC
Permalink
Post by Jean-Pierre
Post by Jonathan N. Little
How to fix your mess?
I'd purge all nvidia components to put
you back on original default nouveau
and then ONLY change via the Driver Manager.
That sounds like good advice.
$ sudo apt-get purge nvidia*
Of course, the question is always WHEN to run
that command, considering lightdm is running,
so, I presume you imply that I need to press
<control><alt><F1> first, and then login
and then stop lightdm with
$ sudo service lightdm stop
Only then, I presume you mean to run the
purge command, so, that's what I will do,
and report back.
Unfortunately, the <control><alt><F7> never
gets me BACK into X windows, so, I have to
reboot.
X changes things so it is now ctrl-alt-F1 -- ie the same as the terminal
that was used to start X.

Or if not a-C F1 try the others, AC F2-F11
Post by Jean-Pierre
In short, I'll follow your directions, adding
1. <control><alt>F1
2. Login as the user
3. sudo service lightdm stop
4. sudo apt-get purge nvidia*
5. sudo reboot
6. KDE System Settings "Driver Manager"
7. Set the driver and click "Apply".
Is that EXACTLY what you are suggesting?
Cybe R. Wizard
2015-01-12 18:59:21 UTC
Permalink
On Mon, 12 Jan 2015 08:51:54 -0600
Post by Jean-Pierre
The funny thing was that the Nvidia driver was
in place
Judging from your last 6 days of problems I'd have to hazard a guess
that you won't be doing much traveling by car in the future:
<http://www.engadget.com/2015/01/12/nvidia-ces-interview/?ncid=rss_truncated>

;-]

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 01:17:31 UTC
Permalink
Post by Cybe R. Wizard
Judging from your last 6 days of problems
I'd have to hazard a guess that
you won't be doing much traveling
Ha ha. I drove on San Tomas Expressway today,
and passed by the Nvidia headquarters in
Santa Clara on my way home, and I felt like
throwing a rock into their gleaming corporate
HQ windows!
Jean-Pierre
2015-01-13 01:28:35 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
I found a similar problem here:
http://unix.stackexchange.com/questions/139816/unable-to-get-nvidia-9600gt-working-with-kubuntu-14-04

They didn't solve it either, but, they ran
this command, which I'll add to the debuggin
repertoire.

$ dpkg --get-selections | grep nvidia
nvidia-331-updates install
nvidia-331-updates-uvm install
nvidia-libopencl1-331-updates install
nvidia-opencl-icd-331-updates install
nvidia-prime install
nvidia-settings install

I'm not sure what that is actually telling
me though. I think it means they're installed,
but it might mean they should be installed.
Jean-Pierre
2015-01-13 01:47:17 UTC
Permalink
One by one, I'll try these methods:

1. Unable to get NVidia 9600GT working with Kubuntu 14.04
http://unix.stackexchange.com/questions/139816/unable-to-get-nvidia-9600gt-working-with-kubuntu-14-04

2. Installing an Nvidia proprietary driver manually problem
http://ubuntuforums.org/showthread.php?t=2216881

3. How do I install the latest NVIDIA drivers from the .run file?
http://askubuntu.com/questions/66328/how-do-i-install-the-latest-nvidia-drivers-from-the-run-file

4. Ubuntu Nvidia Manual
https://help.ubuntu.com/community/NvidiaManual

5. How to install Nvidia drivers in Ubuntu 13.04
http://www.dedoimedo.com/computers/ubuntu-ringtail-nvidia.html

Notice this comment, which shows that I'm not the
only one finding it impossible to install Nvidia
drivers into Ubuntu/Kubuntu.

"The last several releases of Ubuntu are less
than stellar when it comes to installing Nvidia
drivers on your machines. You are likely to end
up with an unbootable system, just by using the
same methods that used to work flawlessly in the
past."

I'll read and try all those in that order and
then report back.
Jean-Pierre
2015-01-13 06:11:30 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
I contacted Nvidia support.
They did the "live chat" thing, and said that
nobody was online that knew Linux, but, that
they'd get back to me.

I suspect they'll send me a shell script to
run, which gathers information.

Then, I'll send the results back to them.
Then, let's hope (cross your fingers) they
know how to install the driver on Kubuntu 14.10.

Thanks for all your help.
If you know of anything that I haven't tried,
let me know.
Jean-Pierre
2015-01-13 06:26:19 UTC
Permalink
Post by Jean-Pierre
Kubuntu 14.10.
I mean Kubuntu 14.04.
Jean-Pierre
2015-01-13 17:34:27 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
I just went through the whole thread again, and
pulled out the following nuggets of genius as
kudos to those who helped solve the problem.

Thanks to the following people for the following help!
Post by Jean-Pierre
You don't have the kernel sources installed.
They should normally go under /usr/src/linux-<version>
That version number has to match the kernel
you're running.
$ sudo apt-get install linux-headers-generic
Mike "that will get the correct version for *you*" Yetto
ls /usr/src What does it say?
"Please install the linux-headers-3.11.0-14-generic package," [...]
See that? Now go and install that package.
you don't have linux-headers-3.11.0-14-generic. Which is
what the output from the nvidia installer script told you, albeit that it
didn't mention the version number.
The kernel headers you have installed are for a _later_ kernel version
than the one you're actually running. So you must get the newer kernel
from the repository using Synaptic or apt-get, and if that newer version
does not match the version of the kernel headers you have, then you must
also install the kernel headers of that newer kernel.
Every kernel has its own headers. ls /usr/src told us that you have three
kernel headers for 3.13 kernels but none for the 3.11 kernel you are
actually running.
3.11.0-14-generic only exists in precise (12.04)
It did NOT say that DKMS headers were missing. It said that the kernel
headers were missing. YOu have kernel headers for a number of 3.13
kernels, but none for 3.11 kernel you are now running for some reason.
The best way to do this is visit the nVidia site,
download *their* driver package, and follow
*their* install.
the driver never really got built to start with.
DKMS == Dynamic Kernel Module Support. It means it's a third party
kernel module, that is distributed as source code, and needs to be
compiled (either at install, or during the first boot) for the currently
running kernel. In order to compile the code, the proper kernel source
code headers must also be installed.
Jean-Pierre
2015-01-13 17:37:40 UTC
Permalink
Post by Jean-Pierre
Q1: Can you tell what is going on from this info?
Q2: Do you have any other DEBUGGING commands?
Q1: Can you tell what is going on from this info?
A1: The kernal version didn't match the header version.

Q2: Do you have any other DEBUGGING commands?
A2: The key debugging commands were these two:
$ uname -r
$ dpkg -l | grep linux-headers
Continue reading on narkive:
Loading...