Linux Help
- Thread starter Eagle
- Start date
OP
- Thread Starter
- #22
OK, I ran the NVIDIA_GLX-1.0-4191.i386.rpm and then I rand the NVIDIA_kernel-1.0-4191.rh80up_2.4.18_18.8.0.i686.rpm
Then I opened /var/log/XFree86.0.log and found the location of the XF86Config file my system was using. Then I opened that file and changed nv to nvidia in the device section, and added Load "glx" to the module section and removed Load "dri" from the same section. Then I rebooted.
When it booted it flashed the command login several times then took me to a blue screen with a blue box in the middle with two boxes that looked like they should be buttons (basically a primitive GUI) However all the text was giberish. One of the buttons did nothing the other brought me back to the command prompt login where I could login.
Then I opened /var/log/XFree86.0.log and found the location of the XF86Config file my system was using. Then I opened that file and changed nv to nvidia in the device section, and added Load "glx" to the module section and removed Load "dri" from the same section. Then I rebooted.
When it booted it flashed the command login several times then took me to a blue screen with a blue box in the middle with two boxes that looked like they should be buttons (basically a primitive GUI) However all the text was giberish. One of the buttons did nothing the other brought me back to the command prompt login where I could login.
You can check that the kernel module is loaded correctly (run 'lsmod').
You can also set the resolution to something standard (640*480*16bits at 60Hz) to see what happen. It has to be done
in the xf86config file...
When you are log in (in console mode), if you try to run xwindow, is there any particular error or warning message ?
Damn, nvidia drivers are really weird sometimes, either on windows or linux.... :/
You can also set the resolution to something standard (640*480*16bits at 60Hz) to see what happen. It has to be done
in the xf86config file...
When you are log in (in console mode), if you try to run xwindow, is there any particular error or warning message ?
Damn, nvidia drivers are really weird sometimes, either on windows or linux.... :/
AlphaWolf
I prey, not pray.
Eagle said:
Depends on your processor. If its an older generation processor (e.g. pentium or below), use i386. If its a pentium 2 or up, use i686. If you use an athlon, use the "athlon" (not athlon64) rpm, because your processor will run it faster than the i686 drivers because of the 3dnow extensions.
All 3 of those RPMs should run on an athlon, don't think the athlon one will run on an intel though.
AlphaWolf
I prey, not pray.
Ah, I knew this has been discussed before. Heres your answer:
http://www.emutalk.net/showthread.php?s=&threadid=11091&perpage=15&highlight=pico&pagenumber=1
http://www.emutalk.net/showthread.php?s=&threadid=11091&perpage=15&highlight=pico&pagenumber=1
AlphaWolf
I prey, not pray.
i686 binary is faster for pentium 2 and better processors. Will not run on anything below a pentium 2 class. i386 will run on...well...any 32-bit x86.
Your best bet though, is always to compile the driver sources on your own, because in effect your drivers will be binary optimized for your specific system. It's not hard at all to do this, but it may confuse you if you are new to linux. There are about 3 extra steps involved, the nvidia driver readme explains it.
Your best bet though, is always to compile the driver sources on your own, because in effect your drivers will be binary optimized for your specific system. It's not hard at all to do this, but it may confuse you if you are new to linux. There are about 3 extra steps involved, the nvidia driver readme explains it.
Malcolm
Not a Moderator
When ever you are unsure always use the lower number 
i386 and i686 have different processor optimizations. i386 are optimized for no processor.
i686 are optimized for Pent II and AMD k7 (durons/athlons).
Don't use the i386/i686 packs under a 64-bit processor, they won't work.
At any time you are unsure enough to post the question somewhere, just grab the source and compile it yourself. Often when you compile ANYTHING is will be faster and take up less hard drive space then a pre-compiled/package install.
Compiling = good
when you compile you can add in options that make the driver/software faster and more stable, and you can customize many of the defaults making the OS what you want it to be.
The only downfall to this is having to read the muanual that comes along with the driver and/or software to know which options you need st set, or which you can alter.
I hope you got some useable information for that gabble up there
i386 and i686 have different processor optimizations. i386 are optimized for no processor.
i686 are optimized for Pent II and AMD k7 (durons/athlons).
Don't use the i386/i686 packs under a 64-bit processor, they won't work.
At any time you are unsure enough to post the question somewhere, just grab the source and compile it yourself. Often when you compile ANYTHING is will be faster and take up less hard drive space then a pre-compiled/package install.
Compiling = good
when you compile you can add in options that make the driver/software faster and more stable, and you can customize many of the defaults making the OS what you want it to be.
The only downfall to this is having to read the muanual that comes along with the driver and/or software to know which options you need st set, or which you can alter.
I hope you got some useable information for that gabble up there