| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 30328 | 2003-02-16 04:53:00 | nVidia Driver update troubles in RedHat 8 | Chilling_Silence (9) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 121648 | 2003-02-16 04:53:00 | When updating my drivers in redhat 8 to the latest ones for my GF4 MX 440, I run into major troubles. Ive read the readme from nVidia.com and ran svchooser or whatever from the site and downlaoded the right ones. I installed them all correctly now when I modify my XF86config file, under the Module section, I add: Load "glx" and I remove Load "dri" I would remove the Load "Glcore" only it isnt there! That all works fine if I then resboot, with the driver still set to "vesa". Now, if I try and switch it to "nv" or "nvidia" I run into trouble. My monitor can do 1024x768 using: H=48-49 V=60-61 anything else and it throws a wobbly. Now, my default login is text-mode, so when I login and type init 5, you'd expect it to work, seeing as everything is setup and configured right.. supposedly anyway. It doesnt. It trys a couple of times, and fails, then comes up with a weird blue screen (Sorta BSOD style) only I cant read it. I hit enter 3 times and it comes up with a configurator that resets my XF86config file to use 800x600 and the vesa driver again. What's going wrong here? Any help much appreciated. Thanks Chilling_Silence BTW - I tried ssh'ing to it and it was pretty cool, a success! Even switched to a GUI when i typed init 5, which I thought was pretty cool! I use PuTTY.exe - What does anybody else here use? |
Chilling_Silence (9) | ||
| 121649 | 2003-02-16 15:38:00 | I was having a wee check of the SuSE Support DB and noticed a reference to problems with nVidia driver installations. They have noted that the nVidia's download servers aren't high availability and this can actually cause the RPM to be short. So check the downloaded file against the MD5 checksum to ensure that you have a complete download. One possible cause for your prob. |
Gorela (901) | ||
| 121650 | 2003-02-16 20:49:00 | Yeah, 3 downloads actually, all same size. I tried modprobe nvidia and it didnt work, so Im assuming I didnt install it correctly, but when I try to install/upgrade it it comes up complaining its already there. Im formatting anyways right now, had left it on logged in as root (Modifying the fstab file) and one of the younger siblings friend had found my wireless keyboard, thought it was broken coz there was no wire, and he's effectively killed a few things.. dunno how. No worries, will try again and let you know. Thanks Chilling_Silence |
Chilling_Silence (9) | ||
| 121651 | 2003-02-16 22:12:00 | I just tried installing the drivers again. I went: rpm -ivh NVIDIA_kernal.......rpm it prepared it to 100% (Im in text-only) installation got to 100% it then said: Fail to install nvidia.o erro: %post(NVIDIA_kerl.....rpm) scriptlet failed, exit status 1 What does all this mean? Thanks Chilling_Silence |
Chilling_Silence (9) | ||
| 121652 | 2003-02-17 02:46:00 | You were doing it as root? Often there are a couple of scripts which are run before and after a rpm package is installed . It looks as if the "post" (after) script failed . It's all very well being up to date . Did the previous nvidia . o work? If so, why break it if it doesn't need fixing? |
Graham L (2) | ||
| 121653 | 2003-02-17 04:54:00 | Okay, what's nVidia.o, and yes, I was root. Should I not have been? |
Chilling_Silence (9) | ||
| 121654 | 2003-02-17 05:10:00 | It should refuse to install if you aren't root . :D That's system stuff, and security stops ordinary users from messing about with it . anything . o is an object-code module . That's what modprobe, insmod, etc handle . It's the "driver" . The "%post" is a bit suspicious . . . the % means "substitute the value of this environment variable" . So you shouldn't see that, you should see the string value of the variable called "post" . |
Graham L (2) | ||
| 121655 | 2003-02-17 07:40:00 | You say your updating? is that upgrading already installed rpms? I assume not since you are doing the XF86Config thing. I got that BSOD with garbled writing and as well as the English. Basically it's saying there's a problem with X and that you can use that BSOD screen to fix the problem (except it's garbled) first of all removed the rpms you installed. rpm -e whatever.rpm Keep the XF86Config as it is since it's how it should be (driver is nvidia not nv). Reboot using a bootdisk and at the boot prompt type Linux 1 or 2 (I forgot which one it is, 1 would definitely work anyway) su root install the RPMs and reboot. Hopefully that works. It's how I got mine working. If you were booting with GUI you would noticed the NVidia splash screen which would tell you that it's installed correctly. |
Kame (312) | ||
| 1 | |||||