FAQ Search Today's Posts Mark Forums Read

» Linux Archive
Home
New Posts
Search
FAQ


Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 08-14-2008, 12:51 AM
"Dave Burns"
 
Default kernel update confuses nvidia drivers, where's error message?

Laptop is a Dell Latitude D630 with NVIDIA Quadro NVS 135M. X was
working yesterday, until yum update installed new kernels. At boot it
complains:

"checking for module nvidia.ko [failed]
nvidia.ko for kernel ***14-108.PAE was not found
the nvidia driver will not be unabled until" blah blah

* Where could I find the full text of that error message after boot?
Is it just gone? Not in dmesg or /var/log/messages or /var/log/X*.

After some groping I figured out that all's well if I re-executed
nvidia-xconfig and boot from a kernel that matches one of my installed
kmod-nvidia s. Yum updated my kernels, livna is behind on kmod-nvidia,
I think this was discussed here recently. I decided to put some of my
breadcrumbs in this post in case someone else ends up in the same boat
or I ever have to remember what happened.

# grep 'Aug 12 ' /var/log/yum.log|grep -e kernel -e Erase
Aug 12 22:47:13 Updated: kernel-headers-2.6.25.14-108.fc9.i386
Aug 12 22:47:39 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:47:54 Installed: kernel-2.6.25.14-108.fc9.i686
Aug 12 22:48:15 Erased: kmod-nvidia-2.6.25.10-86.fc9.i686.PAE
Aug 12 22:48:16 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:48:16 Installed: kernel-2.6.25.14-108.fc9.i686


So I reinstalled what got erased.

yum install kmod-nvidia

Now...

# tail -n5 /var/log/yum.log
Aug 12 22:48:15 Erased: kmod-nvidia-2.6.25.10-86.fc9.i686.PAE
Aug 12 22:48:16 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:48:16 Installed: kernel-2.6.25.14-108.fc9.i686
Aug 13 09:16:10 Installed: kmod-nvidia-173.14.12-2.lvn9.i686
Aug 13 09:16:15 Installed:
kmod-nvidia-2.6.25.11-97.fc9.i686-173.14.12-2.lvn9.i686

But at boot it still complains.

Well, there is an nvidia.ko there now:
# rpm -q --filesbypkg kmod-nvidia-2.6.25.11-97.fc9.i686.i686
kmod-nvidia-2.6.25.11-97.fc9.i686
/lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia
kmod-nvidia-2.6.25.11-97.fc9.i686
/lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia/nvidia.ko

But it's not a match for the kernel I am currently using, which is:
# uname -a
Linux *** 2.6.25.14-108.fc9.i686.PAE #1 SMP Mon Aug 4 13:57:11 EDT
2008 i686 i686 i386 GNU/Linux

And...
rpm -qa|grep nvidia
xorg-x11-drv-nvidia-173.14.12-1.lvn9.i386
kmod-nvidia-2.6.25.11-97.fc9.i686-173.14.12-2.lvn9.i686
kmod-nvidia-PAE-173.14.12-2.lvn9.i686
kmod-nvidia-2.6.25.11-97.fc9.i686.PAE-173.14.12-2.lvn9.i686
kmod-nvidia-173.14.12-2.lvn9.i686

Is telling me that I have nvidia packages for kernel
2.6.25.11-97.fc9.i686 and 2.6.25.11-97.fc9.i686.PAE. So I should try
booting one of those kernels. Which worked. Don't forget to
nvidia-xconfig. And as always, with nvidia proprietary drivers
(installed from livna), the usual system/administration/display panel
doesn't work, instead use nvidia-settings from the command line.

buena suerte,
Dave

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-14-2008, 02:39 AM
Matthew Saltzman
 
Default kernel update confuses nvidia drivers, where's error message?

On Wed, 2008-08-13 at 13:51 -1000, Dave Burns wrote:
>
> Well, there is an nvidia.ko there now:
> # rpm -q --filesbypkg kmod-nvidia-2.6.25.11-97.fc9.i686.i686
> kmod-nvidia-2.6.25.11-97.fc9.i686
> /lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia
> kmod-nvidia-2.6.25.11-97.fc9.i686
> /lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia/nvidia.ko
>
> But it's not a match for the kernel I am currently using, which is:
> # uname -a
> Linux *** 2.6.25.14-108.fc9.i686.PAE #1 SMP Mon Aug 4 13:57:11 EDT
> 2008 i686 i686 i386 GNU/Linux
>
> And...
> rpm -qa|grep nvidia
> xorg-x11-drv-nvidia-173.14.12-1.lvn9.i386
> kmod-nvidia-2.6.25.11-97.fc9.i686-173.14.12-2.lvn9.i686
> kmod-nvidia-PAE-173.14.12-2.lvn9.i686
> kmod-nvidia-2.6.25.11-97.fc9.i686.PAE-173.14.12-2.lvn9.i686
> kmod-nvidia-173.14.12-2.lvn9.i686
>
> Is telling me that I have nvidia packages for kernel
> 2.6.25.11-97.fc9.i686 and 2.6.25.11-97.fc9.i686.PAE. So I should try
> booting one of those kernels. Which worked. Don't forget to
> nvidia-xconfig. And as always, with nvidia proprietary drivers
> (installed from livna), the usual system/administration/display panel
> doesn't work, instead use nvidia-settings from the command line.

There was a note yesterday or so that the Livna nvidia packages for the
latest kernel are delayed. Keep trying....

>
> buena suerte,
> Dave
>
>
--
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 08-14-2008, 08:50 AM
Mogens Kjaer
 
Default kernel update confuses nvidia drivers, where's error message?

Matthew Saltzman wrote:
...

There was a note yesterday or so that the Livna nvidia packages for the
latest kernel are delayed. Keep trying....


I fetched livna SRPMS:

buildsys-build-rpmfusion-9.1-9.lvn9.src.rpm
nvidia-kmod-173.14.12-2.lvn9.src.rpm

Install the first, edit:
/usr/src/redhat/SOURCES/buildsys-build-rpmfusion-kerneldevpkgs-*
and insert the names of the new kernel.

Rebuild&install buildsys.

Install the nvidia-kmod src rpm, and rebuild.

Install the generated .rpm

telinit 3
telinit 5

Mogens


--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@crc.dk Homepage: http://www.crc.dk

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-14-2008, 08:11 PM
"Dave Burns"
 
Default kernel update confuses nvidia drivers, where's error message?

No hints where to find the boot-time error messages if not in dmesg?

On Wed, Aug 13, 2008 at 9:50 PM, Mogens Kjaer <mk@crc.dk> wrote:
> I fetched livna SRPMS:
>
> buildsys-build-rpmfusion-9.1-9.lvn9.src.rpm
> nvidia-kmod-173.14.12-2.lvn9.src.rpm
>
> Install the first, edit:
> /usr/src/redhat/SOURCES/buildsys-build-rpmfusion-kerneldevpkgs-*
> and insert the names of the new kernel.
>
> Rebuild&install buildsys.


using rpmbuild command? What switches? I've never done anything with
source rpms, new territory for me. Otherwise it would be obvious what
you're doing?


> Install the nvidia-kmod src rpm, and rebuild.

rebuild what?

> Install the generated .rpm
>
> telinit 3
> telinit 5
>
> Mogens


Thanks for hints.
Dave

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-15-2008, 06:10 AM
Mogens Kjaer
 
Default kernel update confuses nvidia drivers, where's error message?

Dave Burns wrote:
...
using rpmbuild command? What switches?


This is not rocket science :-)

For my x86_64 machine:

# rpm -i nvidia-kmod-173.14.12-2.lvn9.src.rpm
# rpm -i buildsys-build-rpmfusion-9.1-9.lvn9.src.rpm

# cd /usr/src/redhat/SOURCES
# vi buildsys-build-rpmfusion-kerneldevpkgs-*
s/11-97/14-108/g
# cd ../SPECS
# rpmbuild -bb buildsys-build-rpmfusion.spec
# cd ../RPMS/x86_64
# rpm -Uvh buildsys-build-rpmfusion-*
# cd ../../SPECS
# rpmbuild -bb nvidia-kmod.spec
# cd ../RPMS/x86_64
# rpm -i kmod-nvidia-2.6.25.14-108.fc9.x86_64-173.14.12-2.fc9.x86_64.rpm
# telinit 3
Log in on console as root
# telinit 5

If "rpm -i" complains about packages already installed, they might
need to be removed first.

Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@crc.dk Homepage: http://www.crc.dk

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-15-2008, 06:40 AM
Thorsten Leemhuis
 
Default kernel update confuses nvidia drivers, where's error message?

On 15.08.2008 07:10, Mogens Kjaer wrote:

Dave Burns wrote:
...
using rpmbuild command? What switches?

This is not rocket science :-)

For my x86_64 machine:

# rpm -i nvidia-kmod-173.14.12-2.lvn9.src.rpm
# rpm -i buildsys-build-rpmfusion-9.1-9.lvn9.src.rpm


Just FYI, you don't need to download or modify buildsys-build-rpmfusion
to build a single kmod; it's way easier then that; quoting


http://rpmfusion.org/Packaging/KernelModules/Kmods2


=== Is it possible to compile a kmod against self compiled or other kernels? ===

Yes, easily, it's just a few steps. If you don't have a rpm build environment set one up like this
{{{
$ su -c "yum -y install rpmdevtools kmodtool kernel-devel"
$ rpmdev-setuptree
}}}

Now download the kmod src.rpm to the local directory and rebuild it for the running kernel:
{{{
$ yumdownloader --source kmod-foo
$ rpmbuild --rebuild foo-kmod*.src.rpm --define "kernels $(uname -r)" --target $(uname -m)
}}}

At the end of the build output you will see the names of the RPMs rpmbuild built. Use yum to install it with a command like this
{{{
$ su -c "yum --nogpgcheck install ~/rpmbuild/RPMS/i686/kmod-foo-1.0-4.i686.rpm"
}}}



More details and notes:
http://rpmfusion.org/Packaging/KernelModules/Kmods2#head-a6ef94d0e888ea41a2335d30fe7da26814e23f8f

CU
knurd

P.S.: Hopefully the livna builder is back up in a few hours

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-16-2008, 10:26 AM
John Austin
 
Default kernel update confuses nvidia drivers, where's error message?

On Fri, 2008-08-15 at 07:40 +0200, Thorsten Leemhuis wrote:
> On 15.08.2008 07:10, Mogens Kjaer wrote:
> > Dave Burns wrote:
> > ...
> >> using rpmbuild command? What switches?
> > This is not rocket science :-)
> >
> > For my x86_64 machine:
> >
> > # rpm -i nvidia-kmod-173.14.12-2.lvn9.src.rpm
> > # rpm -i buildsys-build-rpmfusion-9.1-9.lvn9.src.rpm
>
> Just FYI, you don't need to download or modify buildsys-build-rpmfusion
> to build a single kmod; it's way easier then that; quoting
>
> http://rpmfusion.org/Packaging/KernelModules/Kmods2
>
> > === Is it possible to compile a kmod against self compiled or other kernels? ===
> >
> > Yes, easily, it's just a few steps. If you don't have a rpm build environment set one up like this
> > {{{
> > $ su -c "yum -y install rpmdevtools kmodtool kernel-devel"
> > $ rpmdev-setuptree
> > }}}
> >
> > Now download the kmod src.rpm to the local directory and rebuild it for the running kernel:
> > {{{
> > $ yumdownloader --source kmod-foo
> > $ rpmbuild --rebuild foo-kmod*.src.rpm --define "kernels $(uname -r)" --target $(uname -m)
> > }}}
> >
> > At the end of the build output you will see the names of the RPMs rpmbuild built. Use yum to install it with a command like this
> > {{{
> > $ su -c "yum --nogpgcheck install ~/rpmbuild/RPMS/i686/kmod-foo-1.0-4.i686.rpm"
> > }}}
>
>
> More details and notes:
> http://rpmfusion.org/Packaging/KernelModules/Kmods2#head-a6ef94d0e888ea41a2335d30fe7da26814e23f8f
>
> CU
> knurd
>
> P.S.: Hopefully the livna builder is back up in a few hours
>

Hi

My version of Rocket Science !!

John


A new day !! A clean start
As ja
cd ~
rm -rf rpmbuild
rpmdev-setuptree
This downloads source rpms into home directory
yumdownloader --enable=livna --source nvidia-kmod-173.14.12-2.lvn9.
yumdownloader --enable=livna --source xorg-x11-drv-nvidia-173.14.12-1.lvn9

This rebuilds the binary rpms in the rpmbuild directory structure
rpmbuild --rebuild nvidia-kmod-173.14.12-2.lvn9.src.rpm --define "kernels $(uname -r)" --target $(uname -m)
rpmbuild --rebuild xorg-x11-drv-nvidia-173.14.12-1.lvn9.src.rpm --define "kernels $(uname -r)" --target $(uname -m)

su
cd rpmbuild/RPMS/x86_64
ls -l
-rw-r--r-- 1 ja sysadmin 2688970 2008-08-16 09:45 kmod-nvidia-2.6.25.14-108.fc9.x86_64-173.14.12-2.fc9.x86_64.rpm
-rw-r--r-- 1 ja sysadmin 572099 2008-08-16 09:45 nvidia-kmod-debuginfo-173.14.12-2.fc9.x86_64.rpm
-rw-r--r-- 1 ja sysadmin 3221967 2008-08-16 09:47 xorg-x11-drv-nvidia-173.14.12-1.fc9.x86_64.rpm
-rw-r--r-- 1 ja sysadmin 24655 2008-08-16 09:47 xorg-x11-drv-nvidia-debuginfo-173.14.12-1.fc9.x86_64.rpm
-rw-r--r-- 1 ja sysadmin 163031 2008-08-16 09:47 xorg-x11-drv-nvidia-devel-173.14.12-1.fc9.x86_64.rpm
-rw-r--r-- 1 ja sysadmin 6016490 2008-08-16 09:47 xorg-x11-drv-nvidia-libs-173.14.12-1.fc9.x86_64.rpm

yum --nogpgcheck localinstall
kmod-nvidia-2.6.25.14-108.fc9.x86_64-173.14.12-2.fc9.x86_64.rpm
xorg-x11-drv-nvidia-173.14.12-1.fc9.x86_64.rpm
xorg-x11-drv-nvidia-libs-173.14.12-1.fc9.x86_64.rpm

Add remove livna/nvidia rpms as yum complains and repeat above
yum --enable=livna install livna-config-display
yum remove nvidia-settings If present


Reboot ??


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-16-2008, 03:52 PM
Mike
 
Default kernel update confuses nvidia drivers, where's error message?

John Austin <ja <at> jaa.org.uk> writes:


> rpmdev-setuptree
> This downloads source rpms into home directory
> yumdownloader --enable=livna --source nvidia-kmod-173.14.12-2.lvn9.
> yumdownloader --enable=livna --source xorg-x11-drv-nvidia-173.14.12-1.lvn9
>
> This rebuilds the binary rpms in the rpmbuild directory structure
> rpmbuild --rebuild nvidia-kmod-173.14.12-2.lvn9.src.rpm --define "kernels
$(uname -r)" --target
> $(uname -m)

I tried rebuilding the kmod-nvidia module for f8 using this method -
it failed with:

error: Failed build dependencies:

kernel-devel-i686 = kernel-2.6.25.14-69.fc8
is needed by nvidia-kmod-173.14.12-1.fc8.i686


That was using the command:
rpmbuild --rebuild nvidia-kmod-173.14.12-1.lvn8.src.rpm
--define "kernels kernel-2.6.25.14-69.fc8" --target $(uname -m)

I also booted into the latest kernel and tried using
--define "kernels $(uname -r)"
but it gave the same error....

The source files for f8 that were available were:
nvidia-kmod-173.14.12-1.lvn8.src.rpm
xorg-x11-drv-nvidia-173.14.12-1.lvn8.src.rpm

Any ideas on this?

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-16-2008, 05:57 PM
John Austin
 
Default kernel update confuses nvidia drivers, where's error message?

On Sat, 2008-08-16 at 14:52 +0000, Mike wrote:
> John Austin <ja <at> jaa.org.uk> writes:
>
>
> > rpmdev-setuptree
> > This downloads source rpms into home directory
> > yumdownloader --enable=livna --source nvidia-kmod-173.14.12-2.lvn9.
> > yumdownloader --enable=livna --source xorg-x11-drv-nvidia-173.14.12-1.lvn9
> >
> > This rebuilds the binary rpms in the rpmbuild directory structure
> > rpmbuild --rebuild nvidia-kmod-173.14.12-2.lvn9.src.rpm --define "kernels
> $(uname -r)" --target
> > $(uname -m)
>
> I tried rebuilding the kmod-nvidia module for f8 using this method -
> it failed with:
>
> error: Failed build dependencies:
>
> kernel-devel-i686 = kernel-2.6.25.14-69.fc8
> is needed by nvidia-kmod-173.14.12-1.fc8.i686
>
>
> That was using the command:
> rpmbuild --rebuild nvidia-kmod-173.14.12-1.lvn8.src.rpm
> --define "kernels kernel-2.6.25.14-69.fc8" --target $(uname -m)
>
> I also booted into the latest kernel and tried using
> --define "kernels $(uname -r)"
> but it gave the same error....
>
> The source files for f8 that were available were:
> nvidia-kmod-173.14.12-1.lvn8.src.rpm
> xorg-x11-drv-nvidia-173.14.12-1.lvn8.src.rpm
>
> Any ideas on this?
>

I was running the latest kernel when carrying out
the procedure
stokes ~ 731# uname -a
Linux stokes 2.6.25.14-108.fc9.x86_64 #1 SMP Mon Aug 4 13:46:35 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
and had these rpms installed

stokes ~ 730# rpm -qa|grep -i kernel|grep -i 14-108
kernel-devel-2.6.25.14-108.fc9.x86_64
kernel-2.6.25.14-108.fc9.x86_64
kernel-headers-2.6.25.14-108.fc9.x86_64

So I would just try installing the matching kernel-devel for your system
yum install kernel-devel
should pull the one for the current kernel

Good luck

John


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-16-2008, 06:27 PM
Mike
 
Default kernel update confuses nvidia drivers, where's error message?

John Austin <ja <at> jaa.org.uk> writes:

> So I would just try installing the matching kernel-devel for your system
> yum install kernel-devel
> should pull the one for the current kernel

Well, I have not tried on my F9 systems but in F8 I did already have kernel-devel
installed for the new kernel - at the time I posted the problem that was already
the case - have you tried this for F8? Later in the weekend I will try on my
F9 system and I expect that will work OK.



--
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 12:06 PM.

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