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
Jean-Pierre
2015-01-13 00:59:24 UTC
Permalink
"Please install the linux-headers-3.11.0-14-generic
package," [...]
See that? Now go and install that package.
Remember, the display worked fine for months
without it, but I'm *HAPPY* to install it if
it will just make the display work.

But, what's the trick to installing this
"linux-headers-3.11.0-14-generic" package?

$ sudo apt-get install linux-headers-3.11.0-14-generic
E: Package 'linux-headers-3.11.0-14-generic'
has no installation candidate

$ sudo apt-cache search linux-headers-3.11.0-14
Reports nothing whatsoever!

What's the trick to installing these kernel
header files on Kubuntu 14.04?
Mike Yetto
2015-01-13 05:47:12 UTC
Permalink
While walking through the streets of Soho in the rain
Post by Jean-Pierre
"Please install the linux-headers-3.11.0-14-generic
package," [...]
See that? Now go and install that package.
Remember, the display worked fine for months
without it, but I'm *HAPPY* to install it if
it will just make the display work.
But, what's the trick to installing this
"linux-headers-3.11.0-14-generic" package?
Try this:
$ sudo apt-get install linux-headers-generic

Mike "that will get the correct version for *you*" Yetto
--
"All superstition is much the same whether it be that of
astrology, dreams, omen, retributive judgment, or the like, in
all of which the deluded believers observe events which are
fulfilled, but neglect and pass over their failure, though it be
much more common."
- Francis Bacon
Jean-Pierre
2015-01-13 06:09:24 UTC
Permalink
Post by Mike Yetto
$ sudo apt-get install linux-headers-generic
Thanks for that suggestion.
Running the suggested command
indicates it was already 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.
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
Chris Ahlstrom
2015-01-12 18:09:17 UTC
Permalink
Post by Aragorn
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>
"Hole-in-the-head" you mean.
--
Yevtushenko has... an ego that can crack crystal at a distance of twenty feet.
-- John Cheever
Aragorn
2015-01-12 19:13:34 UTC
Permalink
On Monday 12 January 2015 19:09, Chris Ahlstrom conveyed the following
to alt.os.linux.ubuntu...
Post by Chris Ahlstrom
Post by Aragorn
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>
"Hole-in-the-head" you mean.
Well, that's the same thing, really. They're the same people. :p

Mike Yetto owns the copyright on that term, though. ;-)
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jonathan N. Little
2015-01-12 20:01:02 UTC
Permalink
Post by Aragorn
On Monday 12 January 2015 19:09, Chris Ahlstrom conveyed the following
to alt.os.linux.ubuntu...
<snip>
Post by Aragorn
Post by Chris Ahlstrom
Post by Aragorn
Might be another relative of the hole-in-the-name gang... <shakes head>
"Hole-in-the-head" you mean.
Well, that's the same thing, really. They're the same people. :p
Mike Yetto owns the copyright on that term, though. ;-)
<http://www.littleworksstudio.com/temp/usenet/rbtarget>
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Aragorn
2015-01-12 20:06:52 UTC
Permalink
On Monday 12 January 2015 21:01, Jonathan N. Little conveyed the
following to alt.os.linux.ubuntu...
Post by Jonathan N. Little
Post by Aragorn
On Monday 12 January 2015 19:09, Chris Ahlstrom conveyed the
following to alt.os.linux.ubuntu...
<snip>
Post by Aragorn
Post by Chris Ahlstrom
Post by Aragorn
Might be another relative of the hole-in-the-name gang... <shakes head>
"Hole-in-the-head" you mean.
Well, that's the same thing, really. They're the same people. :p
Mike Yetto owns the copyright on that term, though. ;-)
<http://www.littleworksstudio.com/temp/usenet/rbtarget>
:p

I'm wondering what would happen if one happens to hit the white area...
What do you think: implosion or explosion? :-)
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jonathan N. Little
2015-01-12 20:55:46 UTC
Permalink
Post by Aragorn
On Monday 12 January 2015 21:01, Jonathan N. Little conveyed the
following to alt.os.linux.ubuntu...
Post by Jonathan N. Little
Post by Aragorn
On Monday 12 January 2015 19:09, Chris Ahlstrom conveyed the
following to alt.os.linux.ubuntu...
<snip>
Post by Aragorn
Post by Chris Ahlstrom
Post by Aragorn
Might be another relative of the hole-in-the-name gang... <shakes head>
"Hole-in-the-head" you mean.
Well, that's the same thing, really. They're the same people. :p
Mike Yetto owns the copyright on that term, though. ;-)
<http://www.littleworksstudio.com/temp/usenet/rbtarget>
:p
I'm wondering what would happen if one happens to hit the white area...
What do you think: implosion or explosion? :-)
Or teleport to another universe.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Cybe R. Wizard
2015-01-12 22:12:59 UTC
Permalink
On Mon, 12 Jan 2015 15:55:46 -0500
Post by Jonathan N. Little
Post by Aragorn
On Monday 12 January 2015 21:01, Jonathan N. Little conveyed the
following to alt.os.linux.ubuntu...
[...]
Post by Jonathan N. Little
Post by Aragorn
Post by Jonathan N. Little
<http://www.littleworksstudio.com/temp/usenet/rbtarget>
:p
I'm wondering what would happen if one happens to hit the white
area... What do you think: implosion or explosion? :-)
Or teleport to another universe.
Could we have the targeted one do the teleporting? Please???

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
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?
jeff g.
2015-01-13 02:31:45 UTC
Permalink
On 01/12/2015 05:56 PM, William Unruh wrote:

<snip>
Post by William Unruh
OK. Have you upgraded your kernel recently?
Also, I am still voting for harware problems. (Burned capacitor for
example).
I think he updated the kernel and now has to recompile that kernel with
nVidea driver. The best way to do this is visit the nVidia site, let
them tell him what driver to use, download *their* driver package, and
follow *their* very well documented install. I think he has trouble
figuring this out - its not easy, 1st time around, but nVidia has made
it somewhat simple with their script. he hasn't seemed to arrive there yet.
Jonathan N. Little
2015-01-13 02:55:53 UTC
Permalink
Post by Jonathan N. Little
<snip>
Post by William Unruh
OK. Have you upgraded your kernel recently?
Also, I am still voting for harware problems. (Burned capacitor for
example).
I think he updated the kernel and now has to recompile that kernel with
nVidea driver. The best way to do this is visit the nVidia site, let
them tell him what driver to use, download *their* driver package, and
follow *their* very well documented install. I think he has trouble
figuring this out - its not easy, 1st time around, but nVidia has made
it somewhat simple with their script. he hasn't seemed to arrive there yet.
It is the 340 driver, already looked it up for him. But he doesn't need
to go to nVidia site, the driver is available in the KDE Driver Manager.
He cannot seem to follow the more involved nVidia site's method despite
how very well documented it is. It is how he has gotten into this pickle
in the first place. And some of his problems could be
hardware...although describes how hot his laptop gets, he does not seem
to think it could be a factor. Hmmmmmmm.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 03:26:20 UTC
Permalink
Post by Jonathan N. Little
It is the 340 driver, already looked it up for him.
But he doesn't need to go to nVidia site, the driver
is available in the KDE Driver Manager.
You almost certainly haven't seen the first
post in this thread, where I showed *EXACTLY*
that the "KDE Driver Manager" does absolutely
nothing.

Here's a screenshot from that first post:
http://i59.tinypic.com/2nasp38.png

Notice the KDE Driver Manager can be set
to update the driver, but it won't take.

I must have run that KDE Driver Manager at
least a half-dozen times. It's useless.

The results never take.
Post by Jonathan N. Little
cannot seem to follow the more involved
nVidia site's method despite how very well
documented it is.
You must not have seen all the subsequent
posts, where, when the KDE Driver Manager
failed, I followed *EXACTLY* the steps in
the Nvidia web site.

I even posted three logs verbatim, which
showed that the Nvidia web site instructions
are absolutely horrendous.

Sure, they're great if everything works.
But they don't tell you one thing about
how to install the DKMS header files.

And, at the moment, if those Kubuntu DKMS
header files aren't installed, *NOTHING*
will work from the Nvidia web site.

While I appreciate your help immensely,
you have to realize I am VERY FAITHFULLY
following all your instructions - and all
are failing - mainly because NONE OF YOU
know what the commands are on Kubuntu 14.04.

You all seem to know what the generic
problem is, and I appreciate that.

In the case of the KDE Driver Manager, it's
just not working. It says all the right
things, but as I showed in the very first
post, it's just not working. What more can
I do? I can't possibly follow instructions
more faithfully.

In the case of the Nvidia site's instructions,
again, I followed them EXACTLY. I showed that.
Many times. I never skipped a step!

The problem is that the log file shows that
DKMS header files aren't installed. OK. How
do you install them? Nobody knows. Nvidia
doesn't say. Nobody here can say.

Sure, I've googled. Everyone else has the
SAME problem! The DKMS header files can't
be installed.

--------
http://unix.stackexchange.com/questions/139816/unable-to-get-nvidia-9600gt-working-with-kubuntu-14-04

$ 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 03:15:58 UTC
Permalink
Post by jeff g.
I think he updated the kernel and now has to recompile that kernel with
nVidea driver. The best way to do this is visit the nVidia site, let them
tell him what driver to use, download *their* driver package, and follow
*their* very well documented install. I think he has trouble figuring
this out - its not easy, 1st time around, but nVidia has made it somewhat
simple with their script. he hasn't seemed to arrive there yet.
This is sound advice, but, you might recall that
this was the very *FIRST* thing I ever did.

Many people told me (in the other thread) that
it was *STUPID* to follow the Nvidia directions
at the Nvidia site (they said to use apt-get).

But, you may recall that I tried *MANY TIMES*
following *EXACTLY* the directions at the Nvidia
web site (and posted three log files).

Apparently Nvidia's directions don't tell you
*ANYTHING* about how to add the required DKMS
headers to supplement what they called the
"kernel source" (which is really just headers).

Googling, the commands found all fail:
$ 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
jeff g.
2015-01-13 04:45:16 UTC
Permalink
Post by Jean-Pierre
Post by jeff g.
I think he updated the kernel and now has to recompile that kernel with
nVidea driver. The best way to do this is visit the nVidia site, let them
tell him what driver to use, download *their* driver package, and follow
*their* very well documented install. I think he has trouble figuring
this out - its not easy, 1st time around, but nVidia has made it somewhat
simple with their script. he hasn't seemed to arrive there yet.
This is sound advice, but, you might recall that
this was the very *FIRST* thing I ever did.
Many people told me (in the other thread) that
it was *STUPID* to follow the Nvidia directions
at the Nvidia site (they said to use apt-get).
But, you may recall that I tried *MANY TIMES*
following *EXACTLY* the directions at the Nvidia
web site (and posted three log files).
Apparently Nvidia's directions don't tell you
*ANYTHING* about how to add the required DKMS
headers to supplement what they called the
"kernel source" (which is really just headers).
Thats bs because it won't go further without them
Post by Jean-Pierre
$ 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
google till the cows come home - you will find 97 out of 100 hits (and
there are thousands) to be incorrect, thereby making you chase your tail
and just botch everything up.
Jean-Pierre
2015-01-13 05:19:57 UTC
Permalink
Post by jeff g.
Thats bs because it won't go further without them
I don't know how you can call it BS when there
isn't ANYWHERE in the entire Nvidia page that
says HOW to install them.

Where do you see the instructions on here?
http://www.nvidia.com/Download/index.aspx?lang=en-us
Cybe R. Wizard
2015-01-13 09:16:31 UTC
Permalink
On Mon, 12 Jan 2015 23:19:57 -0600
Post by Jean-Pierre
Post by jeff g.
Thats bs because it won't go further without them
I don't know how you can call it BS when there
isn't ANYWHERE in the entire Nvidia page that
says HOW to install them.
Where do you see the instructions on here?
http://www.nvidia.com/Download/index.aspx?lang=en-us
Perhaps if you looked in the right place:
<http://us.download.nvidia.com/XFree86/Linux-x86/100.14.11/README/index.html>

Personally, I think you ought to try appendix H /first/.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Jean-Pierre
2015-01-13 11:23:25 UTC
Permalink
Post by Cybe R. Wizard
<http://us.download.nvidia.com/XFree86/Linux-x86/100.14.11/README/index.html>
Looking at
http://us.download.nvidia.com/XFree86/Linux-x86/100.14.11/README/index.html
It says it need them.
It says it will ftp them if it can.
But it NEVER tells you how to get them on Kubuntu 14.04.
Jean-Pierre
2015-01-13 11:46:23 UTC
Permalink
Post by Jean-Pierre
But it NEVER tells you how to get
them on Kubuntu 14.04.
I'm Googling, specifically for Kubuntu 14.04
kernel upgrade instructions (from 3.11 to 3.13).

If I have to guess at the procedure, is this
the correct one?

http://www.cyberciti.biz/faq/linux-kernel-upgrade-howto/
DecadentLinuxUserNumeroUno
2015-01-13 12:03:45 UTC
Permalink
Post by Jean-Pierre
But it NEVER tells you how to get them on Kubuntu 14.04.
I'm Googling, specifically for Kubuntu 14.04 kernel upgrade instructions
(from 3.11 to 3.13).
If I have to guess at the procedure, is this the correct one?
http://www.cyberciti.biz/faq/linux-kernel-upgrade-howto/
Solve it yourself. Just DL the kernel sources and compile *YOUR OWN*
kernel and CONFIGURE it without the nv module in it. THEN the nvidia
driver install will work IF you perform it from a console with NO x up.

voila.
No hunting anything up.

Hell, you can even compile a very recent bleeding edge version straight
from Linus himself.
Jean-Pierre
2015-01-13 12:40:52 UTC
Permalink
Post by DecadentLinuxUserNumeroUno
Solve it yourself.
Just DL the kernel sources and compile *YOUR OWN*
There is no way I'm going to do that without
step by step instructions.

Do I really have to COMPILE the kernel?
Isn't there an easier way?

And, why is it that ONLY nvidia has a problem
with my kernel?
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.
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/
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-13 00:39:46 UTC
Permalink
Post by Aragorn
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
I have never heard the word "kernel source" before,
so, if it told me that I need one, then it's likely
correct. But I don't (yet) know how to get one.

When I run "uname -r", it tells me I'm running
3.11.0-14-generic
Post by Aragorn
I have explained that to you elsewhere in the thread.
Don't you read the replies you're getting?
I read *EVERYTHING*. But, I leave for work, and
then read, and then leave for a meeting, and then
read, and then do some work, and then read.

When I read, I read top down threaded.
So, if you already explained what DKMS is and
what Nvidia is telling me to do with DKMS, then
I will get to it when I read that post (which
must be further down in the thread).
Post by Aragorn
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
I had the Nvidia driver working last week
for months on end, and I didn't have the
"kernel sources" then, so, I don't see why
I need the "kernel sources" now.

I even got the Nvidia driver working just
a few days ago, and I didn't have the
"kernel sources" then either.

Still. If that's the problem (which I really
doubt it is), then I'm *HAPPY* to add the
kernel sources. I just want my display to
work.

$ ls -ld /usr/src/linux
ls: cannot access /usr/src/linux:
No such file or directory

$ ls /usr/src/
total 28
drwxr-xr-x 2 root root 4096 Jan 9 11:43 bbswitch-0.7
drwxr-xr-x 24 root root 4096 Oct 9 02:06 linux-headers-3.13.0-37
drwxr-xr-x 7 root root 4096 Oct 9 02:06 linux-headers-3.13.0-37-generic
drwxr-xr-x 24 root root 4096 Jan 7 14:29 linux-headers-3.13.0-43
drwxr-xr-x 7 root root 4096 Jan 7 14:29 linux-headers-3.13.0-43-generic
drwxr-xr-x 3 root root 4096 Jan 12 07:47 nvidia-331-updates-331.113
drwxr-xr-x 3 root root 4096 Jan 12 07:47 nvidia-331-updates-uvm-331.113

Does this tell you anything about what is
missing?
Cybe R. Wizard
2015-01-13 08:45:27 UTC
Permalink
On Mon, 12 Jan 2015 18:39:46 -0600
Post by Jean-Pierre
I have never heard the word "kernel source" before,
so, if it told me that I need one, then it's likely
correct. But I don't (yet) know how to get one.
This is why you don't venture out of the official repos.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Aragorn
2015-01-13 12:04:19 UTC
Permalink
On Tuesday 13 January 2015 01:39, Jean-Pierre conveyed the following to
alt.os.linux.ubuntu...
Post by Jean-Pierre
Post by Aragorn
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
When I run "uname -r", it tells me I'm running
3.11.0-14-generic
[...]
$ ls /usr/src/
total 28
drwxr-xr-x 2 root root 4096 Jan 9 11:43 bbswitch-0.7
drwxr-xr-x 24 root root 4096 Oct 9 02:06 linux-headers-3.13.0-37
drwxr-xr-x 7 root root 4096 Oct 9 02:06
linux-headers-3.13.0-37-generic
drwxr-xr-x 24 root root 4096 Jan 7 14:29 linux-headers-3.13.0-43
drwxr-xr-x 7 root root 4096 Jan 7 14:29
linux-headers-3.13.0-43-generic
drwxr-xr-x 3 root root 4096 Jan 12 07:47 nvidia-331-updates-331.113
drwxr-xr-x 3 root root 4096 Jan 12 07:47
nvidia-331-updates-uvm-331.113
Does this tell you anything about what is
missing?
Yes, it does: 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.
--
= Aragorn =

http://www.linuxcounter.net - registrant #223157
Jean-Pierre
2015-01-13 12:51:50 UTC
Permalink
Post by Aragorn
Yes, it does: 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.
Everything seems backward, in that I don't seem
to have the same headers as the kernel, so,
instead of updating the headers, I update the
kernel.

But, to answer the first of two questions in
this thread, that is almost certainly the
problem.

I have a kernel of 3.11 but the headers
(for whatever reason) are later (3.13).

While it's strange that this only affects
Nvidia, and even stranger that I can't just
install the version 3.11 headers, at least
I understand the proposed solution, which is
to update the kernel to the same version as
that of the headers.

While the kernel is found by:
$ uname -r -m
3.11.0-14-generic x86_64

I don't remember the command that confirms
the version of the headers. I think it was
an ls of an nvidia directory.
$ ls /usr/src/linux-headers-3.13.0-37/

May I ask what debugging command I run to
confirm whatever header version I am
trying to update the kernel to?

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
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
Jean-Pierre
2015-01-13 01:01:34 UTC
Permalink
Post by Aragorn
PEBKAC. Or PICNIC, if you will.
? huh ?
Aragorn
2015-01-13 12:06:07 UTC
Permalink
On Tuesday 13 January 2015 02:01, Jean-Pierre conveyed the following to
alt.os.linux.ubuntu...
Post by Jean-Pierre
Post by Aragorn
PEBKAC. Or PICNIC, if you will.
? huh ?
PEBKAC = Problem Exists Between Keyboard And Chair

PICNIC = Problem In Chair Not In Computer
--
= 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).
jeff g.
2015-01-13 02:33:20 UTC
Permalink
Post by Jean-Pierre
It's a Lenovo W510 laptop driving nothing.
I don't even own an external monitor.
your use of xrandr would indicate otherwise - are you the 1st owner of
this box?
Jean-Pierre
2015-01-13 03:28:46 UTC
Permalink
Post by jeff g.
your use of xrandr would indicate otherwise -
are you the 1st owner of this box?
I was told to use xrandr, in the other
thread, so I used it.

Yes. I've owned the laptop since it was
a Windows laptop (years ago).
jeff g.
2015-01-13 04:47:06 UTC
Permalink
Post by Jean-Pierre
Post by jeff g.
your use of xrandr would indicate otherwise -
are you the 1st owner of this box?
I was told to use xrandr, in the other
thread, so I used it.
Since you don't have a 2nd monitor, what did you use it for???

Do you even know?
jeff g.
2015-01-13 05:08:32 UTC
Permalink
Post by jeff g.
Post by Jean-Pierre
Post by jeff g.
your use of xrandr would indicate otherwise -
are you the 1st owner of this box?
I was told to use xrandr, in the other
thread, so I used it.
Since you don't have a 2nd monitor, what did you use it for???
Do you even know?
I may be off here - randr will give you the state of multiple outputs
and the means to set them but with nVidia, nVidia config (for xorg) and
its display settings widget do that job - I don't know if randr is
compatible with nVidia's drivers but I suspect not.
Jean-Pierre
2015-01-13 05:21:22 UTC
Permalink
Post by jeff g.
Since you don't have a 2nd monitor, what did you use it for???
Do you even know?
What did I use "what" for?
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.
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"?
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?
jeff g.
2015-01-13 04:51:06 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.
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?
hoo, boy...

Jonathan?
Jonathan N. Little
2015-01-13 05:02:09 UTC
Permalink
Post by jeff g.
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.
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?
hoo, boy...
Jonathan?
Yep. So much harder once the mess is made.
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 05:26:58 UTC
Permalink
Post by Jonathan N. Little
Yep. So much harder once the mess is made.
It failed.
The detailed log file is below.
The bad news was that the first attempt
left the max resolution stuck on something
like VGA, yet the second attempt (choosing
an older driver) moved the max resolution
to 1024x768 (which is still not 1920x1024).

---------------
$ 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
---------------
Jonathan N. Little
2015-01-13 05:56:05 UTC
Permalink
Post by Jean-Pierre
It failed.
The detailed log file is below.
The bad news was that the first attempt
left the max resolution stuck on something
like VGA,
Which it would because you would be using a basic VESA VGA
driver...Think Windows before your install the nVidia driver...remember
you still have nouveau blacklisted which would not have been in a fresh
Ubuntu install.
Post by Jean-Pierre
yet the second attempt (choosing
an older driver) moved the max resolution
to 1024x768 (which is still not 1920x1024).
Why? Why did you not select the 340 driver which even in your Driver
Manager has it flagged as *Recommended*?
--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Jean-Pierre
2015-01-13 06:25:10 UTC
Permalink
Post by Jonathan N. Little
Why? Why did you not select the 340 driver which even in your Driver
Manager has it flagged as *Recommended*?
I think you missed (or I didn't say) that I
first chose the 340 driver.

Since that ended up with VGA-like resolution,
I tried again, this time with the older driver.

I have tried the 340 driver so many times, I'm
not sure if doing it a seventh time will have
a different effect (given the definition of crazy).
Jean-Pierre
2015-01-13 06:35:30 UTC
Permalink
I first chose the 340 driver.
Here is a screenshot I did just now
http://i59.tinypic.com/r47.png

I can't count the number of times I have
selected the 340 driver in the KDE
driver manager GUI.
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.
Continue reading on narkive:
Loading...