FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 03-24-2008, 11:18 PM
David Kramer
 
Default nvidia driver breaks with pretty much every F8 update

I simply don't understand why this is the case, but every time I upgrade
the . After some updates, the symlinks point to the wrong version, etc.
But I will only address my current situation. This is on a Dell D820.


Currently running the newly-installed 2.6.24.3-34 kernel.

This is the stdout/stderr when I startx:
---------------------------------------------------------
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora 8 Red Hat, Inc.
Current Operating System: Linux lexa.thekramers.net 2.6.24.3-34.fc8 #1
SMP Wed Mar 12 18:17:20 EDT 2008 i686

Build Date: 14 March 2008
Build ID: xorg-x11-server 1.3.0.0-44.fc8
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 24 20:00:40 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
FATAL: Error inserting nvidia_169_12
(/lib/modules/2.6.24.3-34.fc8/updates/drivers/video/nvidia/nvidia-169_12.ko):
Invalid module format

(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
---------------------------------------------------------

Notice the "Invalid module format"?

This is what I have installed:
---------------------------------------------------------
> rpm -qa | egrep -i '(nvidia|kernel|yum)' | sort
kernel-2.6.24.3-12.fc8
kernel-2.6.24.3-34.fc8
kernel-devel-2.6.24.3-12.fc8
kernel-devel-2.6.24.3-34.fc8
kernel-headers-2.6.24.3-34.fc8
nvidia-graphics169.09-169.09-95.fc8
nvidia-graphics169.09-kmdl-2.6.24.3-12.fc8-169.09-95.fc8
nvidia-graphics169.09-kmdl-2.6.24.3-34.fc8-169.09-95.fc8
nvidia-graphics169.09-libs-169.09-95.fc8
nvidia-graphics169.12-169.12-96.fc8
nvidia-graphics-169.12-25
nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8-169.12-96.fc8
nvidia-graphics169.12-libs-169.12-96.fc8
nvidia-graphics-devices-1.0-6.fc8
nvidia-graphics-helpers-0.0.26-27.fc8
yum-3.2.8-2.fc8
yum-changelog-1.1.11-1.fc8
yumex-2.0.4-1.fc8
yum-fedorakmod-1.1.11-1.fc8
yum-kernel-module-1.1.11-1.fc8
yum-metadata-parser-1.1.2-1.fc8
yum-plugin-kmdl-0.7-9.fc8
yum-priorities-1.1.11-1.fc8
yum-skip-broken-1.1.11-1.fc8
yum-updatesd-0.9-1.fc8
yum-utils-1.1.11-1.fc8
---------------------------------------------------------

Thanks for any advice you can offer.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-24-2008, 11:25 PM
Peter McNeil
 
Default nvidia driver breaks with pretty much every F8 update

For some reason the update to a new kernel seems to randomly point to a
kernel to boot by default which would be OK but the livna nvidia setup
breaks the older kernels nvidia module, so you need to make sure you
boot on the latest kernel by default (by editing /etc/grub.conf to point
to the latest kernel).


The "solution" is to install the nvidia module manually from the nvidia
site download, which is not really a simple option.




David Kramer wrote:
I simply don't understand why this is the case, but every time I
upgrade the . After some updates, the symlinks point to the wrong
version, etc. But I will only address my current situation. This is
on a Dell D820.


Currently running the newly-installed 2.6.24.3-34 kernel.

This is the stdout/stderr when I startx:
---------------------------------------------------------
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora 8 Red Hat, Inc.
Current Operating System: Linux lexa.thekramers.net 2.6.24.3-34.fc8 #1
SMP Wed Mar 12 18:17:20 EDT 2008 i686

Build Date: 14 March 2008
Build ID: xorg-x11-server 1.3.0.0-44.fc8
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 24 20:00:40 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
FATAL: Error inserting nvidia_169_12
(/lib/modules/2.6.24.3-34.fc8/updates/drivers/video/nvidia/nvidia-169_12.ko):
Invalid module format

(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
---------------------------------------------------------

Notice the "Invalid module format"?

This is what I have installed:
---------------------------------------------------------
> rpm -qa | egrep -i '(nvidia|kernel|yum)' | sort
kernel-2.6.24.3-12.fc8
kernel-2.6.24.3-34.fc8
kernel-devel-2.6.24.3-12.fc8
kernel-devel-2.6.24.3-34.fc8
kernel-headers-2.6.24.3-34.fc8
nvidia-graphics169.09-169.09-95.fc8
nvidia-graphics169.09-kmdl-2.6.24.3-12.fc8-169.09-95.fc8
nvidia-graphics169.09-kmdl-2.6.24.3-34.fc8-169.09-95.fc8
nvidia-graphics169.09-libs-169.09-95.fc8
nvidia-graphics169.12-169.12-96.fc8
nvidia-graphics-169.12-25
nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8-169.12-96.fc8
nvidia-graphics169.12-libs-169.12-96.fc8
nvidia-graphics-devices-1.0-6.fc8
nvidia-graphics-helpers-0.0.26-27.fc8
yum-3.2.8-2.fc8
yum-changelog-1.1.11-1.fc8
yumex-2.0.4-1.fc8
yum-fedorakmod-1.1.11-1.fc8
yum-kernel-module-1.1.11-1.fc8
yum-metadata-parser-1.1.2-1.fc8
yum-plugin-kmdl-0.7-9.fc8
yum-priorities-1.1.11-1.fc8
yum-skip-broken-1.1.11-1.fc8
yum-updatesd-0.9-1.fc8
yum-utils-1.1.11-1.fc8
---------------------------------------------------------

Thanks for any advice you can offer.



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-24-2008, 11:49 PM
David Kramer
 
Default nvidia driver breaks with pretty much every F8 update

Peter McNeil wrote:
For some reason the update to a new kernel seems to randomly point to a
kernel to boot by default which would be OK but the livna nvidia setup
breaks the older kernels nvidia module, so you need to make sure you
boot on the latest kernel by default (by editing /etc/grub.conf to point
to the latest kernel).


I checked with uname that I was running the most recent kernel.
Using the previous kernel, I was able to get X running in 800x600 mdel
(i.e. useless on my WSXGA+ screen).


Also, I got disgusted with the fights between livna and atrpms a long
time ago, and now I don't have a single livna package on my system.


The "solution" is to install the nvidia module manually from the nvidia
site download, which is not really a simple option.


Ugh. And then recompile it with every kernel update, right?


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 12:08 AM
"Paulo Cavalcanti"
 
Default nvidia driver breaks with pretty much every F8 update

On Mon, Mar 24, 2008 at 9:18 PM, David Kramer <david@thekramers.net> wrote:

I simply don't understand why this is the case, but every time I upgrade

the . *After some updates, the symlinks point to the wrong version, etc.

*But I will only address my current situation. *This is on a Dell D820.



Currently running the newly-installed 2.6.24.3-34 kernel.



This is the stdout/stderr when I startx:

---------------------------------------------------------

X Window System Version 1.3.0

Release Date: 19 April 2007

X Protocol Version 11, Revision 0, Release 1.3

Build Operating System: Fedora 8 Red Hat, Inc.

Current Operating System: Linux lexa.thekramers.net 2.6.24.3-34.fc8 #1

SMP Wed Mar 12 18:17:20 EDT 2008 i686

Build Date: 14 March 2008

Build ID: xorg-x11-server 1.3.0.0-44.fc8

* * * *Before reporting problems, check http://wiki.x.org

* * * *to make sure that you have the latest version.

Module Loader present

Markers: (--) probed, (**) from config file, (==) default setting,

* * * *(++) from command line, (!!) notice, (II) informational,

* * * *(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 24 20:00:40 2008

(==) Using config file: "/etc/X11/xorg.conf"

(II) Module already built-in

FATAL: Error inserting nvidia_169_12

(/lib/modules/2.6.24.3-34.fc8/updates/drivers/video/nvidia/nvidia-169_12.ko):

Invalid module format


It seems to me that you have the wrong module.

Try this:

rpm -q --qf "%{name}-%{version} : %{arch}
" kernel

rpm -q --qf "%{name}-%{version} : %{arch}
" nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8


--
Paulo Roma Cavalcanti
LCG - UFRJ
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 01:48 AM
David Kramer
 
Default nvidia driver breaks with pretty much every F8 update

Paulo Cavalcanti wrote:



On Mon, Mar 24, 2008 at 9:18 PM, David Kramer <david@thekramers.net
<mailto:david@thekramers.net>> wrote:


I simply don't understand why this is the case, but every time I upgrade
the . After some updates, the symlinks point to the wrong version, etc.
But I will only address my current situation. This is on a Dell D820.

Currently running the newly-installed 2.6.24.3-34 kernel.

This is the stdout/stderr when I startx:
---------------------------------------------------------
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora 8 Red Hat, Inc.
Current Operating System: Linux lexa.thekramers.net
<http://lexa.thekramers.net> 2.6.24.3-34.fc8 #1
SMP Wed Mar 12 18:17:20 EDT 2008 i686
Build Date: 14 March 2008
Build ID: xorg-x11-server 1.3.0.0-44.fc8
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 24 20:00:40 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
FATAL: Error inserting nvidia_169_12
(/lib/modules/2.6.24.3-34.fc8/updates/drivers/video/nvidia/nvidia-169_12.ko):
Invalid module format



It seems to me that you have the wrong module.

Try this:

rpm -q --qf "%{name}-%{version} : %{arch}
" kernel


kernel-2.6.24.3 : i686
kernel-2.6.24.3 : i686

rpm -q --qf "%{name}-%{version} : %{arch}
"
nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8


nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8-169.12 : i586

Looks good to me.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 01:58 AM
Matthew Saltzman
 
Default nvidia driver breaks with pretty much every F8 update

On Tue, 2008-03-25 at 11:25 +1100, Peter McNeil wrote:
> For some reason the update to a new kernel seems to randomly point to a
> kernel to boot by default which would be OK but the livna nvidia setup
> breaks the older kernels nvidia module, so you need to make sure you
> boot on the latest kernel by default (by editing /etc/grub.conf to point
> to the latest kernel).

Generally, it doesn't. There's a glitch when installing a new kernel
results in installing a new version of the nVidia driver.

>
> The "solution" is to install the nvidia module manually from the nvidia
> site download, which is not really a simple option.

...which has its own problems.

Search the archives of this list for how to rebuild new Livna nvidia
packages for the old kernel.

>
>
>
> David Kramer wrote:
> > I simply don't understand why this is the case, but every time I
> > upgrade the . After some updates, the symlinks point to the wrong
> > version, etc. But I will only address my current situation. This is
> > on a Dell D820.
> >
> > Currently running the newly-installed 2.6.24.3-34 kernel.
> >
> > [...]
> >
> > Thanks for any advice you can offer.
> >
>
>
--
Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 06:50 AM
"Paulo Cavalcanti"
 
Default nvidia driver breaks with pretty much every F8 update

On Mon, Mar 24, 2008 at 11:48 PM, David Kramer <david@thekramers.net> wrote:

Paulo Cavalcanti wrote:

>

>

> On Mon, Mar 24, 2008 at 9:18 PM, David Kramer <david@thekramers.net

> <mailto:david@thekramers.net>> wrote:

>

> * * I simply don't understand why this is the case, but every time I upgrade

> * * the . *After some updates, the symlinks point to the wrong version, etc.

> * * *But I will only address my current situation. *This is on a Dell D820.

>

> * * Currently running the newly-installed 2.6.24.3-34 kernel.

>

> * * This is the stdout/stderr when I startx:

> * * ---------------------------------------------------------

> * * X Window System Version 1.3.0

> * * Release Date: 19 April 2007

> * * X Protocol Version 11, Revision 0, Release 1.3

> * * Build Operating System: Fedora 8 Red Hat, Inc.

> * * Current Operating System: Linux lexa.thekramers.net

> * * <http://lexa.thekramers.net> 2.6.24.3-34.fc8 #1

> * * SMP Wed Mar 12 18:17:20 EDT 2008 i686

> * * Build Date: 14 March 2008

> * * Build ID: xorg-x11-server 1.3.0.0-44.fc8

> * * * * * *Before reporting problems, check http://wiki.x.org

> * * * * * *to make sure that you have the latest version.

> * * Module Loader present

> * * Markers: (--) probed, (**) from config file, (==) default setting,

> * * * * * *(++) from command line, (!!) notice, (II) informational,

> * * * * * *(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

> * * (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 24 20:00:40 2008

> * * (==) Using config file: "/etc/X11/xorg.conf"

> * * (II) Module already built-in

> * * FATAL: Error inserting nvidia_169_12

> * * (/lib/modules/2.6.24.3-34.fc8/updates/drivers/video/nvidia/nvidia-169_12.ko):

> * * Invalid module format

>

>

>

> It seems to me that you have the wrong module.

>

> Try this:

>

> rpm -q --qf "%{name}-%{version} : %{arch}
" kernel



kernel-2.6.24.3 : i686

kernel-2.6.24.3 : i686



> rpm -q --qf "%{name}-%{version} : %{arch}
"

> nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8



nvidia-graphics169.12-kmdl-2.6.24.3-34.fc8-169.12 : i586



Looks good to me.



No it is not. You are using an i586 nvidia module for an i686 kernel.

This is why the module is not loading. The architectures do not* match.


You have to uninstall the* i586 nvidia module and install its appropriate i686 version.

--
Paulo Roma Cavalcanti
LCG - UFRJ
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 12:13 PM
Claude Jones
 
Default nvidia driver breaks with pretty much every F8 update

On Mon March 24 2008, David Kramer wrote:
> Also, I got disgusted with the fights between livna and atrpms a long
> time ago, and now I don't have a single livna package on my system.
>
> > The "solution" is to install the nvidia module manually from the nvidia
> > site download, which is not really a simple option.
>
> Ugh. *And then recompile it with every kernel update, right?

there's a real easy solution to this - I use it on many, many, machines

freshrpms bundles a package called dkms with their version of the nVidia
driver: 'bundles' is not perhaps the correct word, but, dkms is installed as
well when you install the nVidia driver from freshrpms; freshrpms makes no
kernel-modules available at all; dkms is a script written by an active
participant in the Fedora project, who happens to work for Dell; the script,
after installation, runs at boot time and checks your nVidia kernel-module
against the kernel that's being booted - if the active kernel module doesn't
match the kernel that's being booted, it forks into a routine where it builds
a new kernel module on the fly -- once it's done, normal boot resumes and
when your machine comes up, it has the correct kernel-module built AND loaded
for the running kernel -- and that's why freshrpms makes no kernel-modules
available; with this system, you are completely automated - in several years
of using it, there was one hiccup where a new nVidia driver came out and the
script wouldn't run properly, as I recall -- the result was, the machines
reverted to nv driver that comes with Fedora in all cases - I lost some of
the features of the nVidia video drivers, but the machines kept working,
otherwise

using this method, you certainly wouldn't end up with a kernel of one
architecture and a kernel-module of another, which is causing your present
issues, and you can forget about worrying about new kernel-modules after
every kernel update

--
Claude Jones
Brunswick, MD, USA

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 12:14 PM
"Arthur Pemberton"
 
Default nvidia driver breaks with pretty much every F8 update

On Mon, Mar 24, 2008 at 6:49 PM, David Kramer <david@thekramers.net> wrote:
> Also, I got disgusted with the fights between livna and atrpms a long
> time ago, and now I don't have a single livna package on my system.

There in lies your problem. Always go with Livna.

--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 12:30 PM
Claude Jones
 
Default nvidia driver breaks with pretty much every F8 update

On Tue March 25 2008, Arthur Pemberton wrote:
> On Mon, Mar 24, 2008 at 6:49 PM, David Kramer <david@thekramers.net> wrote:
> > Also, I got disgusted with the fights between livna and atrpms a long
> > time ago, and now I don't have a single livna package on my system.
>
> There in lies your problem. Always go with Livna.
>

why? sorry, but this kind of statement always irritates me --

I explain: there was a time a few years back where Livna was having a hard
time getting sufficient manpower to keep their kernel-modules coming in a
timely fashion, and they were taking up to several days at one point to get
them out - there was even a public appeal for volunteers to help at one point
on one of these mail-lists

I was using freshrpms selectively at that time, because it provided Cinelerra
and all the packages that were needed for dependencies - and Livna did not

There were also issues with the mplayer that Livna was providing in this
time-frame

Somewhere along the way, someone on this list posted about the freshrpms
nvidia driver and the dkms script; I decided to try it. I post the results of
that experiment elsewhere in this thread

So, at some point, in that time-frame, I switched to freshrpms and disabled
Livna, and for some years, I have always gone with freshrpms

BUT, I don't advocate that anyone always go with anything in this regard. It
depends on your needs, and the mix of packages you depend on. I think the
advice that you do NOT keep both Livna AND the sourceforge repos enabled all
the time is still sound advice, I think -- though I don't monitor these
things closely enough to say that with absolute authority, I still keep
hearing that you can still get into dependency problems keeping both enabled

There is still the occasional time when I enable Livna to get a specific
package for some very specific reason - I never run a general update with it
enabled, though.


--
Claude Jones
Brunswick, MD, USA

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 07:14 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org