nvidia module - kernel

WhatsOnYourBrain · 10-09-2006, 12:52 PM

why did this happen? i'm not sure. but i'm confident that someone here will know what i should do.

somehow i ended up 'uninstalling' my nvidia module for my newest Kernel (i think)...
on bootup, a process which follows this one: http://stanton-finley.net/fedora_cor...ion_notes.html , including the auto-logon, etc., i see two Kernel choices at "GRUB" (?) before the Kernel loads. if i choose the "newest", the system will boot-- but i never really get my desktop because, i assume, it's 'invisible' due to the fact that the display isn't working (my guess), so i tried the 'other' option, the older Kernel, and the system boots, operational for the most part. however, the nVidia module is "Warning: Missing" from the older kernel.

attempting to install, i get the following dependency issues:
# rpm -ivh kmod*.rpm
error: Failed dependencies:
kernel-i686 = 2.6.17-1.2187_FC5xen0 is needed by kmod-nvidia-legacy-xen0-1.0.7184-2.2.6.17_1.2187_FC5.i686
nvidia-legacy-kmod-common >= 1.0.7184 is needed by kmod-nvidia-legacy-xen0-1.0.7184-2.2.6.17_1.2187_FC5.i686
[root@localhost RPMs]# rpm -ivh xorg*.rpm
error: Failed dependencies:
nvidia-legacy-kmod >= 1.0.7184 is needed by xorg-x11-drv-nvidia-legacy-1.0.7184-1.lvn5.i386
xorg-x11-drv-nvidia conflicts with xorg-x11-drv-nvidia-legacy-1.0.7184-1.lvn5.i386
xorg-x11-drv-nvidia-legacy conflicts with xorg-x11-drv-nvidia-1.0.8774-1.lvn5.i386

these are shown as installed modules: ( USERID = my private userid)
crw-rw-rw- 1 root root 1, 3 Oct 9 04:38 null
crw------- 1 USERID root 195, 0 Aug 25 00:07 nvidia0
crw------- 1 USERID root 195, 1 Aug 25 00:07 nvidia1
crw------- 1 USERID root 195, 2 Aug 25 00:07 nvidia2
crw------- 1 USERID root 195, 3 Aug 25 00:07 nvidia3
crw------- 1 USERID root 195, 255 Aug 25 00:07 nvidiactl
crw-rw---- 1 root root 10, 144 Oct 9 04:38 nvram
lrwxrwxrwx 1 root root 7 Oct 9 04:38 par0 -> usb/lp0
crw-rw---- 1 root lp 99, 0 Oct 9 04:38 parport0

what can i do to put things back in place where they need to be?

i don't know what exactly i did to get to this point... but it was probably due to my attempt to resolve these seemingly impossible issues i've been having w/ dependencies. (more on that here http://fedorashare.centrewebdesign.com/rhbugzilla/ and https://bugzilla.redhat.com/bugzilla....cgi?id=209378)

thank you for reading!! i look forward to your reply.

b0uncer · 10-10-2006, 07:05 AM

This sounds like:

- you had an older kernel
- you installed a newer kernel (or recompiled), where you installed your nvidia drivers
- the drivers did not work well due to configuration (or something else as well)
- since the driver was compiled against the new kernel (and modules), it does not work with the older one, and you get an error -- should pose no other problems

If that's the case (I've been there myself), you either want to find out if you can alter your configuration (X, maybe?) with the new kernel, or install a completely new kernel without nvidia drivers. I know a lot of driver installations (display-) end with an unusable desktop (black screen, no X, power-saving mode, ...) and the way to get around this is either use a kernel version that is tested to work with the drivers, or try to find out if some configuration might work with the current kernel.

The same thing comes if you install the driver succesfully to a kernel (so it's compiled against that version) and then update the kernel, after which you would need to reinstall the driver for the new kernel to make it work. Display drivers (since they include a kernel module) are kernel-specific so they need a bit more work than just installing drivers once and updating kernel multiple times..every time you change your kernel (or it's config), you'll need to reinstall the drivers.

The most important thing is to first make sure the driver version you're trying to install works with the kernel version you're running, and possibly back up any old configurations that work, and then install and reconfigure X as the driver's install istrructions say.

WhatsOnYourBrain · 10-11-2006, 02:20 AM

hey there b0uncer! sounds to me like you've done this before!

thanks for your conjunction with my malfunction.

before i forget to include it, have a look at this: take note of the kernel version -- where only the newer shows the nvidia module

Code:

[@localhost ~]$ locate /lib/modules/2.6.17-1.2157_FC5/*/nvidia
[@localhost ~]$ locate /lib/modules/2.6.17-1.2187_FC5/*/nvidia
/lib/modules/2.6.17-1.2187_FC5/extra/nvidia
/lib/modules/2.6.17-1.2187_FC5/extra/nvidia/nvidia.ko

actually, your 3rd tick down: - the drivers did not work well due to configuration (or something else as well) is not QUITE what happened.

the nvidia module / kernel incompatibility and dependency issue came some time AFTER everything had actually been working fine w/ a stable up-to-date kernel configuration. i'm pretty sure it was "Picasa", which requested i CHMOD 666 as ROOT two files, which i'm 89.5% sure contained the name 'nvidia' themselves. this CHMOD issue arose at some point after my system had already been YumEx updated w/ the 2.6.17-1.2187_FC5 kernel.

i had used Picasa on this system pretty much from day-one w/out any problems. it was specifically my manual re-installation of the nvidia module AFTER the 2.6.17-1.2187_FC5 kernel update which i believe caused this CHMOD request, and ultimately this nvidia module / kernel malfunction. why did i manually reinstall the nvidia module? simply because i couldn't recall if i had done it yet. i decided that no harm would come of re-doing it, so i proceeded in the action yum -y --enablerepo livna install kmod-nvidia, which was probably the 2nd time it was done, and i noticed nothing unusual beyond that until this CHMOD request. had i not tried to open Picasa, and not done the CHMOD, maybe i wouldn't be in this situation? but why was Picasa requesting this CHMOD when it didn't before? what critical variables had changed, and why? and how do i un-do it?

i'm sorry there's so much text here, but i feel it's important to illustrate precisely the succession of events leading up to the current system state, so to reiterate-- this system history is:
0 fresh 120GB drive: 1 install OS Fedora Core 5 2.6.17-1.2157_FC5 > 2 system works fine (did i or did i not install kmod-nvidia here? i think i did) > 3 YumEx Updates Kernel to 2.6.17-1.2187_FC5 (among other updates of course) > 4 initaite what is possibly the second yum -y --enablerepo livna install kmod-nvidia > 5 proceed to use the system w/ no errors > 6 attempt to lauch (or shutdown) a software which instead displays a pop-up (a system-notification i thought, but the pop-up was unique in appearance-- about 700x150 px in size-- looked like a resized Terminal because of the black text on white background). the dialogue complained something about i needed to CHMOD a file... i believe it was "cannot [ do something w/ (Picasa?) ] because the [ forgotten-name ] file is [ locked / unwritable / being a bitch ]. please CHMOD 666 the files /???/nvdia... ??? and /???/nvidia/??" [i'm the screencapture king, and of all times for me NOT to do a screencap of the error!] > 7 complete the CHMOD as requested. > 8 continue to use the system, operating okay until the next shutdown/ restart > 9 system boots into 'newest kernel' but ultimately, no visibility / no display / black screen.

what should be my course of action to remedy this situation? what else do you need to know which hasn't been presented?

profuse thanks for your help!!

farslayer · 10-11-2006, 08:28 AM

xorg-x11-drv-nvidia-legacy conflicts with xorg-x11-drv-nvidia-1.0.8774-1.lvn5.i386

You have 2 different versions of the driver installed the Legacy driver is for Older nvidia cards such as the Geforce 2 the newer driver does not support older cards. Older cards will NOT work with the current batch of drivers fromnVidia..

Before you can fix anything you really need to figure out WHICH direction you need to move.. Legacy or Current..

Then uninstall the inappropriate drivers and modules. re-install the appropriate components.

WhatsOnYourBrain · 10-11-2006, 06:46 PM

Quote:

Originally Posted by farslayer

Before you can fix anything you really need to figure out WHICH direction you need to move.. Legacy or Current..

if i don't already have that info, then how do i determine that?

Quote:

Originally Posted by farslayer

Then uninstall the inappropriate drivers and modules. re-install the appropriate components.

i don't have the luxury of changing the video card-- this one is all i've got... an old geforce model 32MB maybe?... (i don't know how to scan it w/ Fedora, or i'd provide details.... it's definitely old-- doesn't even have a fan, but it does have s-vid-- i find that significant because i have another geforce w/ bigger memory and a noisey old fan... but no s-vid. i'd estimate its about 5 yrs old, and nothing spectacular even of its generation.

regardless of the card itself, i don't understand why there is any speculation over whether i would want to get back to using the 2.6.17-1.2187_FC5 kernel w/ the nvidia kernel module.
i certainly appreciate the effort, but i'm afraid i require a more guided hand for any success to come of this thread. sad but true.

farslayer · 10-11-2006, 07:16 PM

if you have an OLD nvidia card your only choice is to use the legacy drivers the new Drivers do NOT support the old cards..

lspci will give you information about what card you have

Cards supported by the Legacy Drivers
http://www.nvidia.com/object/1.0-718..._products.html

Cards supported by the Current Driver
http://www.nvidia.com/object/IO_18897.html

You will need to uninstall the nonlegacy drivers and make sure all the drivers you have installed are the legacy version.

Easy fix.

WhatsOnYourBrain · 10-11-2006, 08:49 PM

how do i tell which is which: legacy vs non-legacy?

all i know in terms of nvidia software is [ yum -y --enablerepo livna install kmod-nvidia ]. where will i find the proper legacy module, compatible w/ the 2.6.17-1.2187_FC5 kernel?

what is the recommended method for doing the removal / installation? (yum vs rpm vs ?)

what can i expect to happen during the process? (ie. there will be loss of video once i do X Y Z ; once i get to ___ i can safely reboot...; etc)

after all is said and done and i've got the the nvidia module/drivers squared away, i expect that i can simply reboot into the 2.6.17-1.2187_FC5 kernel and everything will be operational. correct?

farslayer · 10-11-2006, 11:23 PM

Legacy has legacy in the package name....
http://rpm.livna.org/kernel-modules.html

NON LEGACY (the ones that won't work on your card. If they are installed un-install them)

Quote:

nvidia-glx
kernel-module-nvidia

LEGACY DRIVERS (the proper drivers for your card.. )

Quote:

nvidia-glx-legacy
kernel-module-nvidia-legacy

You shouldn't need the devel package to get your card working

I don't know Fedora but wouldn't it be something like .. Remove the incorrect package then reinstall the correct ones ?

Code:

yum remove xorg-x11-drv-nvidia
yum --enablrepo=livna install nvidia-glx-legacy kernel-module-nvidia-legacy-$(uname -r)

WhatsOnYourBrain · 10-13-2006, 04:30 PM

cool. thanks for your continued help on this issue, farslayer
EDIT: what do you mean by "...legacy-$(uname -r)" -- are you saying this is to find my current, or previous kernel? because uname -r presently shows 2.6.17-1.2157_FC5, but the other kernel i've got, as i indicated in post#3 above, is 2.6.17-1.2187_FC5

Quote:

Originally Posted by farslayer

reinstall the correct ones ?

Code:

yum remove xorg-x11-drv-nvidia
yum --enablrepo=livna install nvidia-glx-legacy kernel-module-nvidia-legacy-$(uname -r)

this part is definitely useful, having specified precisely what you recommeded i remove... that's where i was unsure, but it makes more sense now.

according to what nvida tells us here, http://www.nvidia.com/object/linux_d..._1.0-7184.html
perhaps i needn't bother w/ so much specific uninstall / reinstall after all?

EDIT: it's a little more complicated for the nvidia 'oem' driver-- they want me to install outside of the x-server, which requires some mod of the runlevel so i don't boot into X. i think maybe i'll try your suggestion first, farslayer, as it seems more 'conventional'. if that doesn't work, and if i end up totally screwed, at least i've got the 'guest-room' box where i can log on and get further support to get this main box back online. here goes...

WhatsOnYourBrain · 10-13-2006, 04:56 PM

proceeding w/ the removal, yum reports:

Code:

Removing:
 xorg-x11-drv-nvidia     i386       1.0.8774-1.lvn5  installed          12 M
Removing for dependencies:
 kmod-nvidia             i686       1.0.8774-1.2.6.17_1.2187_FC5  installed         4.9 M

to which i will reply 'Y'

just FYI, so you know where i am in the process...

EDIT:
...and after that successful action, :

Code:

Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for kmod-nvidia-legacy to pack into transaction set.
kmod-nvidia-legacy-1.0.71 100% |=========================|  15 kB    00:00
---> Package kmod-nvidia-legacy.i586 0:1.0.7184-2.2.6.17_1.2187_FC5 set to be installed
--> Running transaction check
--> Processing Dependency: kernel-i586 = 2.6.17-1.2187_FC5 for package: kmod-nvidia-legacy
--> Processing Dependency: nvidia-legacy-kmod-common >= 1.0.7184 for package: kmod-nvidia-legacy
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for kernel to pack into transaction set.
kernel-2.6.17-1.2187_FC5. 100% |=========================| 166 kB    00:05
---> Package kernel.i586 0:2.6.17-1.2187_FC5 set to be installed
---> Downloading header for xorg-x11-drv-nvidia-legacy to pack into transaction set.
xorg-x11-drv-nvidia-legac 100% |=========================|  22 kB    00:00
---> Package xorg-x11-drv-nvidia-legacy.i386 0:1.0.7184-2.lvn5 set to be updated
--> Running transaction check
--> Populating transaction set with selected packages. Please wait.
---> Package kernel.i686 0:2.6.17-1.2187_FC5 set to be erased
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 kmod-nvidia-legacy      i586       1.0.7184-2.2.6.17_1.2187_FC5  livna             1.3 M
Removing:
 kernel                  i686       2.6.17-1.2187_FC5  installed          37 M
Installing for dependencies:
 kernel                  i586       2.6.17-1.2187_FC5  updates            14 M
 xorg-x11-drv-nvidia-legacy  i386       1.0.7184-2.lvn5  livna             3.6 M

Transaction Summary

to which i will also respond 'Y'. i assume this takes me back up to the 'newest' Kernel, yes? i mean-- it's installing it now at Installing for dependencies:
kernel i586 2.6.17-1.2187_FC5 updates 14 M, right?

(proceeding...)
and here's how that turned out:

Code:

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 kmod-nvidia-legacy      i586       1.0.7184-2.2.6.17_1.2187_FC5  livna             1.3 M
Removing:
 kernel                  i686       2.6.17-1.2187_FC5  installed          37 M
Installing for dependencies:
 kernel                  i586       2.6.17-1.2187_FC5  updates            14 M
 xorg-x11-drv-nvidia-legacy  i386       1.0.7184-2.lvn5  livna             3.6 M

Transaction Summary
=============================================================================
Install      3 Package(s)
Update       0 Package(s)
Remove       1 Package(s)
Total download size: 19 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): kernel-2.6.17-1.21 100% |=========================|  14 MB    04:58
(2/3): kmod-nvidia-legacy 100% |=========================| 1.3 MB    00:15
(3/3): xorg-x11-drv-nvidi 100% |=========================| 3.6 MB    00:46
Running Transaction Test
Finished Transaction Test


Transaction Check Error:   package kernel-2.6.17-1.2187_FC5 is already installed

so... i guess only time will tell as to whether it's going to boot properly w/ the supporting module? or do i know that already from this info?

if this isn't 'right', what is your recommendation at this point (anyone)?

thank you!

EDIT:
yum list n* shows:
nvidia-x11-drv.i386 1.0.8774-3 freshrpms
yum list x* shows:
xorg-x11-drv-i810-devel.i386 1.4.1.3-3.1 core
xorg-x11-drv-tek4957.i386 1.0.0.1-1.2 core
xorg-x11-drv-via-devel.i386 0.1.33.2-2 core
xorg-x11-fonts-ISO8859-14-100dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-14-75dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-15-100dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-15-75dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-2-100dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-2-75dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-9-100dpi.noarch 7.0-3 core
xorg-x11-fonts-ISO8859-9-75dpi.noarch 7.0-3 core
xorg-x11-fonts-cyrillic.noarch 7.0-3 core
xorg-x11-fonts-ethiopic.noarch 7.0-3 core
xorg-x11-fonts-syriac.noarch 7.0-3 core
xorg-x11-resutils.i386 1.0.1-1.2 core
xorg-x11-server-Xdmx.i386 1.0.1-9.fc5.5 updates
xorg-x11-server-Xnest.i386 1.0.1-9.fc5.5 updates
xorg-x11-server-Xvfb.i386 1.0.1-9.fc5.5 updates
xorg-x11-server-sdk.i386 1.0.1-9.fc5.5 updates
xorg-x11-util-macros.i386 1.0.1-1.2 core
xorg-x11-xbitmaps.i386 1.0.1-3 core
xorg-x11-xfs-utils.i386 1:1.0.1-4.FC5.0 updates
xorg-x11-xfwp.i386 1.0.1-1.2 core
xorg-x11-xsm.i386 1.0.1-1.2 core

Crito · 10-13-2006, 05:20 PM

Your safety net is Linux's ability to run completely without a GUI. Just reboot into runlevel 3, edit xorg.conf with vi and change driver to VESA. You should then be able to boot "normally" (with a GUI, that is) using your new kernel.
http://www.fedorafaq.org/basics/

And next time use "yum info" to find out what's installed and what's available. Note repo line says "installed" for first one.

Code:

[climber@blackhole ~]$ yum info kmod-nvidia*
Loading "installonlyn" plugin
Setting up repositories
livna                                                                [1/5]
core                                                                 [2/5]
updates                                                              [3/5]
freshrpms                                                            [4/5]
extras                                                               [5/5]
Reading repository metadata in from local files
Installed Packages
Name   : kmod-nvidia
Arch   : i686
Version: 1.0.8774
Release: 1.2.6.17_1.2187_FC5
Size   : 4.9 M
Repo   : installed
Summary: nvidia kernel module(s)

Description:
 This package provides the nvidia kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5 for the i686 family of processors.


Available Packages
Name   : kmod-nvidia
Arch   : i586
Version: 1.0.8774
Release: 1.2.6.17_1.2187_FC5
Size   : 1.6 M
Repo   : livna
Summary: nvidia kernel module(s)
Description:
 This package provides the nvidia kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5 for the i586 family of processors.

Name   : kmod-nvidia-kdump
Arch   : i686
Version: 1.0.8774
Release: 1.2.6.17_1.2187_FC5
Size   : 1.6 M
Repo   : livna
Summary: nvidia kernel module(s)
Description:
 This package provides the nvidia kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5kdump for the i686 family of processors.

Name   : kmod-nvidia-legacy
Arch   : i586
Version: 1.0.7184
Release: 2.2.6.17_1.2187_FC5
Size   : 1.3 M
Repo   : livna
Summary: nvidia-legacy kernel module(s)
Description:
 This package provides the nvidia-legacy kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5 for the i586 family of processors.

Name   : kmod-nvidia-legacy
Arch   : i686
Version: 1.0.7184
Release: 2.2.6.17_1.2187_FC5
Size   : 1.3 M
Repo   : livna
Summary: nvidia-legacy kernel module(s)
Description:
 This package provides the nvidia-legacy kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5 for the i686 family of processors.

Name   : kmod-nvidia-legacy-kdump
Arch   : i686
Version: 1.0.7184
Release: 2.2.6.17_1.2187_FC5
Size   : 1.3 M
Repo   : livna
Summary: nvidia-legacy kernel module(s)
Description:
 This package provides the nvidia-legacy kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5kdump for the i686 family of processors.

Name   : kmod-nvidia-legacy-smp
Arch   : i686
Version: 1.0.7184
Release: 2.2.6.17_1.2187_FC5
Size   : 1.3 M
Repo   : livna
Summary: nvidia-legacy kernel module(s)
Description:
 This package provides the nvidia-legacy kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5smp for the i686 family of processors.

Name   : kmod-nvidia-legacy-xen0
Arch   : i686
Version: 1.0.7184
Release: 2.2.6.17_1.2187_FC5
Size   : 1.3 M
Repo   : livna
Summary: nvidia-legacy kernel module(s)
Description:
 This package provides the nvidia-legacy kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5xen0 for the i686 family of processors.

Name   : kmod-nvidia-smp
Arch   : i686
Version: 1.0.8774
Release: 1.2.6.17_1.2187_FC5
Size   : 1.6 M
Repo   : livna
Summary: nvidia kernel module(s)
Description:
 This package provides the nvidia kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5smp for the i686 family of processors.

Name   : kmod-nvidia-xen0
Arch   : i686
Version: 1.0.8774
Release: 1.2.6.17_1.2187_FC5
Size   : 1.6 M
Repo   : livna
Summary: nvidia kernel module(s)
Description:
 This package provides the nvidia kernel modules built for the Linux
kernel 2.6.17-1.2187_FC5xen0 for the i686 family of processors.

Like farslayer keeps saying, you only need one of them.

WhatsOnYourBrain · 10-13-2006, 05:27 PM

hmm from that same query, my sys shows this:

Code:

[root@localhost ~]# yum info kmod-nvidia*
Loading "installonlyn" plugin
Setting up repositories
dries                                                                [1/7]
macromedia                                                           [2/7]
rpmforge                                                             [3/7]
core                                                                 [4/7]
updates                                                              [5/7]
freshrpms                                                            [6/7]
extras                                                               [7/7]
Reading repository metadata in from local files
[root@localhost ~]#

note also what i EDIT updated above re: xorg* and nvida* via yum list

WhatsOnYourBrain · 10-13-2006, 05:41 PM

this doesn't look right to me... or is it?

Code:

Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package xorg-x11-drv-nvidia-legacy.i386 0:1.0.7184-2.lvn5 set to be updated
--> Running transaction check
--> Processing Dependency: nvidia-legacy-kmod >= 1.0.7184 for package: xorg-x11-drv-nvidia-legacy
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for kmod-nvidia-legacy to pack into transaction set.
kmod-nvidia-legacy-1.0.71 100% |=========================|  15 kB    00:00
---> Package kmod-nvidia-legacy.i686 0:1.0.7184-2.2.6.17_1.2187_FC5 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 xorg-x11-drv-nvidia-legacy  i386       1.0.7184-2.lvn5  livna             3.6 M
Installing for dependencies:
 kmod-nvidia-legacy      i686       1.0.7184-2.2.6.17_1.2187_FC5  livna             1.3 M

Transaction Summary
=============================================================================
Install      2 Package(s)
Update       0 Package(s)
Remove       0 Package(s)
Total download size: 4.8 M
Is this ok [y/N]: y
Downloading Packages:
(1/1): kmod-nvidia-legacy 100% |=========================| 1.3 MB    00:13
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: kmod-nvidia-legacy           ######################### [1/2]
FATAL: Could not open '/boot/System.map-2.6.17-1.2187_FC5': No such file or directory
  Installing: xorg-x11-drv-nvidia-legacy   ######################### [2/2]
FATAL: Module nvidia not found.

Installed: xorg-x11-drv-nvidia-legacy.i386 0:1.0.7184-2.lvn5
Dependency Installed: kmod-nvidia-legacy.i686 0:1.0.7184-2.2.6.17_1.2187_FC5
Complete!
[root@localhost ~]#

it looks to me like it keeps erring due to the *.2187_FC5 kernel
mine is (uname -r)2.6.17-1.2157_FC5

what am i missing / doing wrong?

WhatsOnYourBrain · 10-13-2006, 06:09 PM

Quote:

Originally Posted by Crito

Just reboot into runlevel 3, edit xorg.conf with vi and change driver to VESA.

i don't know how to boot to runlevel 3, nor where to find xorg.conf ... might be able to launch vi, but last i checked... it's not just vi on Fedora Core 5... so i'll have to figure out what to use... and driver to VESA... another guess... i assume there's some indication as to which is a driver setting...

ha! i guess none of these things will cause any massive explosion, so i've got that consolation. although i may find my brains oozing onto the floor nonetheless...

so, how does one go about changing the runlevel? all i see is runlevel utmp -- which is apparently not a txt file?

discovery!
i know now which of the files i CHMOD to 666. while trying to figure out of if my recent set of yumming around caused any favorable changes to the system, i tried launching Picasa, which again (just as before) shows

Quote:

Originally Posted by Picasa for Linux

/dev/nvidia0 or /dev/nvidiactl are not accessable. Picasa will crash if these files are not accessable. To fix this, as root, please run: chmod 666 /dev/nvidia0 /dev/nvidiactl

which i believe is the same action i ran when i first started having problems. what does anyone know about these files? how are they related to whatever else i'm supposed to do to fix this system?

thanks!!

WhatsOnYourBrain · 10-13-2006, 07:47 PM

i'm back to the 2.6.17-1.2187_FC5 kernel now
all it took was rebooting, failing the x-server login, but the 'automatic' process (requiring my root p/w at commandline) restarted the x-server upon 'trying' w/ a new config.

once the x-server started, i was prompted w/ a GNOME-ish display-settings screen, into which i plugged 1280x1024 (up from 1024x768) and from 'thousands' of colors, i bumped it up to millions.

but, it didn't boot into KDE as such. i can't seem to get my 1280x1024 resolution back. it's not showing up in the KDE display config (in the 'Control Center').

suggestions?