I'm probably missing a long discussion as I just subscribed to the list: (I was out on an adventure trying different distros and broke my mail) However, I'm kind of stuck on one element of the NVIDIA video card problem: According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO I should download kernel sources and the like to install the driver. That didn't work at all. Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK) Now, how do I verify if I really do have 3D support? SAX2 says I don't have it. Do I? The FTP site said to ignore the 3D errors I would get.... Since the fTP site directions didn't work 100% I'm less than confident.
On Tuesday 03 February 2004 03.56, Tom Allison wrote:
I'm probably missing a long discussion as I just subscribed to the list:
(I was out on an adventure trying different distros and broke my mail)
However, I'm kind of stuck on one element of the NVIDIA video card problem:
According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-H OWTO I should download kernel sources and the like to install the driver.
That didn't work at all.
Why not? Did you download the correct kernel sources, the kernel-source.rpm corresponding to your kernel version? Did you prepare the sources with cd /usr/src/linux make mrproper make cloneconfig make dep before running the nvidia installer?
Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK)
No need to reboot, it's just to save newbies the experience of going to text mode. The instructions are seriously confused. For example, some instructions say you should go to runlevel 3, while all that's really needed is to stop X. Oh well, all roads lead to Rome I guess
Now, how do I verify if I really do have 3D support?
glxinfo|grep "direct rendering" It should say Yes You may have to edit /etc/X11/XF86Config and change Driver from "nv" to "nvidia" in the Device section
Anders Johansson wrote:
On Tuesday 03 February 2004 03.56, Tom Allison wrote:
I'm probably missing a long discussion as I just subscribed to the list:
(I was out on an adventure trying different distros and broke my mail)
However, I'm kind of stuck on one element of the NVIDIA video card problem:
According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-H OWTO I should download kernel sources and the like to install the driver.
That didn't work at all.
Why not?
Did you download the correct kernel sources, the kernel-source.rpm corresponding to your kernel version? Did you prepare the sources with
cd /usr/src/linux make mrproper make cloneconfig make dep
before running the nvidia installer?
Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK)
No need to reboot, it's just to save newbies the experience of going to text mode. The instructions are seriously confused. For example, some instructions say you should go to runlevel 3, while all that's really needed is to stop X. Oh well, all roads lead to Rome I guess
Now, how do I verify if I really do have 3D support?
glxinfo|grep "direct rendering"
It should say Yes
You may have to edit /etc/X11/XF86Config and change Driver from "nv" to "nvidia" in the Device section
Everything you have here says it should work great. glxinfo shows direct rendering. Some of the 3D games are definitely kicking butt. Unfortunately I'm not sure what else I did. When I CTRL+ALT+F1 I am greeted with "OUT OF RANGE" on my monitor. This is bad, because it never did this before and if X fails I'm toast.
On Tuesday 03 February 2004 04.53, Tom Allison wrote:
glxinfo shows direct rendering. Some of the 3D games are definitely kicking butt.
cool
Unfortunately I'm not sure what else I did. When I CTRL+ALT+F1 I am greeted with "OUT OF RANGE" on my monitor. This is bad, because it never did this before and if X fails I'm toast.
Others have reported that as well, and I've seen it too although it was a long time ago. I don't know why it happens
Hey guys, I have no idea where this thread starts or stops so I'll just top-post to piss Shanahan off ;). I did snip out the Lookout headers etc just for you though Patrick, so I am making an effort at cleaning up my newbie act, and I want no comments about how I left in the full thread so poor Anders could figure out what he already said!!! My experience with nVidia reads like this... One of my machines here is an ASUS A7A266 running an nVidia Geforce 2 MX400 and with this I have only had issues installing the driver under Fedora1. Step 1. If you aren't running an unstable kernel or your card is not too new for the driver somehow, just download the correct Linux driver from the nVidia web site. Step 2. Follow the readme directions on the nVidia site by going su in a terminal window and executing telinit 3 to drop out of X. Step 3. Navigate to the folder where you saved the rpm file and execute the syntax that the instructions on nVidia told you to run...something like rpm -i <filename> and sit back while the installer runs. 4. Assuming that the installer completes your kernel recompile without failing, then you can type SaX2 at the prompt and run SaX2 to walk through the steps to confirm that your monitor is correct, etc. And that 3D is set to enabled on the new driver. 5. Make sure to edit the nVidia AGP driver selection before saving the SaX2 configuration, as the correct driver will be named nvidia and not the generic nv that ships with all Linux distros. If the installer ran correctly SaX2 will be able to find the driver named nvidia although you may have to play around on the list just a bit. After saving the configuration then either type reboot at the command prompt, or telinit 5 to restart the X server. After freshly installing an entire video driver that recompiles the kernel, I personally like to reboot to ensure that everything is purged from memory, but this is primarily because I am a Windows weenie at heart. The alternative to SaX2 is to go in as root and open your XFree86 config file and look for the nv entry there and change it to nvidia. You can also fully read the manual configuration stuff on the nVidia web site readme and then do your tweaks manually also. After you finish, do a test run with TuxRacer and if he looks and runs smoothly and with sound then your driver is correct. Personally, I find SaX2 much easier than manual edits using kedit or whatever. Good Luck! -Sheldon
On Tuesday 03 February 2004 03.56, Tom Allison wrote:
I'm probably missing a long discussion as I just subscribed to the list:
(I was out on an adventure trying different distros and broke my mail)
However, I'm kind of stuck on one element of the NVIDIA video card problem:
According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvi dia-instal ler-H OWTO I should download kernel sources and the like to install the driver.
That didn't work at all.
Why not?
Did you download the correct kernel sources, the kernel-source.rpm corresponding to your kernel version? Did you prepare the
Anders Johansson wrote: sources with
cd /usr/src/linux make mrproper make cloneconfig make dep
before running the nvidia installer?
Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK)
No need to reboot, it's just to save newbies the experience
of going
to text mode. The instructions are seriously confused. For example, some instructions say you should go to runlevel 3, while all that's really needed is to stop X. Oh well, all roads lead to Rome I guess
Now, how do I verify if I really do have 3D support?
glxinfo|grep "direct rendering"
It should say Yes
You may have to edit /etc/X11/XF86Config and change Driver from "nv" to "nvidia" in the Device section
Everything you have here says it should work great.
glxinfo shows direct rendering. Some of the 3D games are definitely kicking butt.
Unfortunately I'm not sure what else I did. When I CTRL+ALT+F1 I am greeted with "OUT OF RANGE" on my monitor. This is bad, because it never did this before and if X fails I'm toast.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Tom Allison wrote:
Anders Johansson wrote:
On Tuesday 03 February 2004 03.56, Tom Allison wrote:
I'm probably missing a long discussion as I just subscribed to the list:
(I was out on an adventure trying different distros and broke my mail)
However, I'm kind of stuck on one element of the NVIDIA video card problem:
According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-H
OWTO I should download kernel sources and the like to install the driver.
That didn't work at all.
Why not?
Did you download the correct kernel sources, the kernel-source.rpm corresponding to your kernel version? Did you prepare the sources with
cd /usr/src/linux make mrproper make cloneconfig make dep
before running the nvidia installer?
Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK)
No need to reboot, it's just to save newbies the experience of going to text mode. The instructions are seriously confused. For example, some instructions say you should go to runlevel 3, while all that's really needed is to stop X. Oh well, all roads lead to Rome I guess
Now, how do I verify if I really do have 3D support?
glxinfo|grep "direct rendering"
It should say Yes
You may have to edit /etc/X11/XF86Config and change Driver from "nv" to "nvidia" in the Device section
Everything you have here says it should work great.
glxinfo shows direct rendering. Some of the 3D games are definitely kicking butt.
Unfortunately I'm not sure what else I did. When I CTRL+ALT+F1 I am greeted with "OUT OF RANGE" on my monitor. This is bad, because it never did this before and if X fails I'm toast.
:-) You have hit the nVIDIA Driver Brickwall Syndrome. Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall. Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)? Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver. (What I concluded is that any driver after #4363 does not like something in the combination of the Athlon CPU and (?) any card below, say, FX5200 (eg MX 400, 440. This is a broad statement and is not meant to be authorative.) Cheers. -- All Scottish food is based on a dare.
:-)
You have hit the nVIDIA Driver Brickwall Syndrome.
Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall.
Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)?
Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver.
(What I concluded is that any driver after #4363 does not like something in the combination of the Athlon CPU and (?) any card below, say, FX5200 (eg MX 400, 440. This is a broad statement and is not meant to be authorative.)
Cheers.
Athlon 3200+ Gigabyte GA7n400 Pro2 nVidia GeForce MX 550 Linux 2.4.21-166-athlon #1 Kind of a bummer if true. Any plans to fix?
Tom Allison wrote:
:-)
You have hit the nVIDIA Driver Brickwall Syndrome.
Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall.
Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)?
Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver.
I'm finding a lot of threads about this problem. I'm not very happy with how the nVidia driver installation went the first time, but eventually running sh NVIDIA...run worked. The same script works under SuSE90?
Tom Allison wrote:
Tom Allison wrote:
:-)
You have hit the nVIDIA Driver Brickwall Syndrome.
Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall.
Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)?
Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver.
I'm finding a lot of threads about this problem.
I'm not very happy with how the nVidia driver installation went the first time, but eventually running sh NVIDIA...run worked.
The same script works under SuSE90?
As far as I am concerned, this script only runs on Suse v9.0 (and on subsequent releases I presume). For earlier versions of Suse you need to do other things -- it's all in the documentation, the README. There is also a link to the doco on the Suse site as well and one should read both to get the full picture on how to install the driver(s) [and depending on which version of Suse one has]. Because the driver has to be compiled as it is being installed one needs to make sure that the source code is installed for the kernel version used and also that the latest patch for the source has been installed. You mentioned earlier that the kernel you have is patched to 'version' #166. Go to /var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586 and see that kernel-source is there and it is patched to #166. After this, follow the instructions given in this forum by Anders or what is shown in the doco on the Suse site to install the driver (even if it the 4363 one). But remember to first uninstall the one you now have installed. Also, when you are installing the 4363 it will complain about 3 times about missing bits (or something). Just ignore the complaints and give it OK (or Continue or whatever) and all will work. Cheers. -- All Scottish food is based on a dare.
Tom Allison wrote:
:-)
You have hit the nVIDIA Driver Brickwall Syndrome.
Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall.
Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)?
Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver.
(What I concluded is that any driver after #4363 does not like something in the combination of the Athlon CPU and (?) any card below, say, FX5200 (eg MX 400, 440. This is a broad statement and is not meant to be authorative.)
Cheers.
Athlon 3200+ Gigabyte GA7n400 Pro2 nVidia GeForce MX 550 Linux 2.4.21-166-athlon #1
Yep, all the ingredients for a crippled driver are here.
Kind of a bummer if true. Any plans to fix?
This has been going on for many months (since the 4363's successor) so I don't think it is going to be fixed. There is nothing wrong with the 4363 and it works perfectly. So, install 4363 and allow your blood pressure to return to normal :-). Alternatively, invest in the FX5200 card (as a minimum), which is a better performer anyway and not expensive, and the latest 5336 driver will work with it. (This is how I found out because I had to put the MX440 into the other computer so bought myself the FX5200 (128Mb) to replace it, and just for a lark installed the 5336 only to get the pleasant surprise that it worked with the FX5200.) Cheers. -- All Scottish food is based on a dare.
Basil Chupin wrote:
You have hit the nVIDIA Driver Brickwall Syndrome. Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall. Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)? Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver. Cheers.
Thanks for the above info, and i hope it's ok to jump in here ? (newbie2?) I was a pleased Suse 8.0 user until that NVidia stuff hit the fan and ruined it for me. I have kernel 2.4.18_4GB with an AMD 2.4 G CPU on an Asus A7S333 M/Bd, with a GeForce2 MX64L -400 card, and i attempted to do the Suse security upgrade plus the NV driver (my first try -#4363 i think)), without doing enough reading and without killing X, so i ended up with a real mess - no video, no modem, Sax2 crippled etc. Now i've had to go back toWin98se to even get online, despite trying to reinstall Suse 8.0 Personal many times. What a disaster! Elitist bullshit? instead of help? Personally i feel NVidia should be shot with a ball of their own <scat>, and Suse should never have allowed us newbies to be treated so badly. Changed my plans to buy 8.2 or 9.0 until i see if another distro or an ATI card is the way out for me. If you'd care to enlighten me about this NV card and this AMD cpu, i would certainly like to know more about it. Thanks, BrianB.
Funny that you should mention that. I have had the opposite experience with my Athlon XP 3000 NForce 2 combination. No way maybe could I install the FX5700 card but my venerable Ti4200 as well as an MX card worked fine with any and every version of drivers. Suse was no help, neither was Nvidia. The original install went smoothly so I was particularly consternated to find a weird screen and be unable to access the GUI to load drivers and config XFree. So after fumbling for a week to ten days late one night after work I made the switch to an NVidia 4 MX and voila there Sax2 and Yast to play with.Once freed from the command line install of all drivers went smooth but even though I loaded the latest and greatest from NVidia the stubborn FX 5700 still would not work. So I simply switched cards. Suse is now quite comfortable with the Asus TI 4200 and my other NForce AMD combo running XP works fine with the FX5200. That set my dual boot plans back but what the hey. I feel the Suse 9.0 product is overall strong and compares favorabbly with say Red Hat 9.0 I was especially impressed with Samba. I can see every Windows share and drive without any extra work. I suspect the problem is exactly a bleeding edge Vid card and poor support for that particular prouct on any platform other than Windows. It is great for gaming but that makes it somewhat limiting if i wanted to say try to install say Free BSD or some other exotic flavor or distro. In all fairness to Suse Tech support they did try to help with the problem which is more thanI can say for NVidia who never returned my email. Donald Correll
RE:
You have hit the nVIDIA Driver Brickwall Syndrome. Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall. Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)? Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver. Cheers.
Thanks for the above info, and i hope it's ok to jump in here ? (newbie2?) I was a pleased Suse 8.0 user until that NVidia stuff hit the fan and ruined it for me. I have kernel 2.4.18_4GB with an AMD 2.4 G CPU on an Asus A7S333 M/Bd, with a GeForce2 MX64L -400 card, and i attempted to do the Suse security upgrade plus the NV driver (my first try -#4363 i think)), without doing enough reading and without killing X, so i ended up with a real mess - no video, no modem, Sax2 crippled etc. Now i've had to go back toWin98se to even get online, despite trying to reinstall Suse 8.0 Personal many times. What a disaster! Elitist bullshit? instead of help?
Personally i feel NVidia should be shot with a ball of their own <scat>, and Suse should never have allowed us newbies to be treated so badly. Changed my plans to buy 8.2 or 9.0 until i see if another distro or an ATI card is the way out for me. If you'd care to enlighten me about this NV card and this AMD cpu, i would certainly like to know more about it. Thanks, BrianB.
Brian Berrigan wrote:
Basil Chupin wrote:
You have hit the nVIDIA Driver Brickwall Syndrome. Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall. Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)? Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver. Cheers.
Thanks for the above info, and i hope it's ok to jump in here ? (newbie2?) I was a pleased Suse 8.0 user until that NVidia stuff hit the fan and ruined it for me. I have kernel 2.4.18_4GB with an AMD 2.4 G CPU on an Asus A7S333 M/Bd, with a GeForce2 MX64L -400 card, and i attempted to do the Suse security upgrade plus the NV driver (my first try -#4363 i think)), without doing enough reading and without killing X, so i ended up with a real mess - no video, no modem, Sax2 crippled etc. Now i've had to go back toWin98se to even get online, despite trying to reinstall Suse 8.0 Personal many times. What a disaster! Elitist bullshit? instead of help?
Personally i feel NVidia should be shot with a ball of their own <scat>, and Suse should never have allowed us newbies to be treated so badly. Changed my plans to buy 8.2 or 9.0 until i see if another distro or an ATI card is the way out for me. If you'd care to enlighten me about this NV card and this AMD cpu, i would certainly like to know more about it. Thanks, BrianB.
See my reply to Tom. There is nothing wrong with the 4363 driver. I had it installed (on v9.0) until I bought the FX5200 card a few weeks ago. I have it on the computer with the MX440 and on the one with the MX400 (all running v9.0). If you tried to re-install v8.0 many times without (apparent) success then it is not Suse's fault nor the driver's because the nVidia driver is not installed by Suse - you have to install it as a deliberate exercise; so you are doing somethng wrong to have the installation hassles. (Re looking for an alternate distro. I've tried them all and believe me Suse is the only one to work with.) Cheers. -- All Scottish food is based on a dare.
Basil Chupin wrote:
Brian Berrigan wrote:
Basil Chupin wrote:
You have hit the nVIDIA Driver Brickwall Syndrome. Even the very latest driver (5336), which is supposed to have fixed all sorts of problems, causes you to hit the Brickwall. Tell us (me) which video card you are using and which version of the kernel (Athlon or non-Athlon)? Depending on your answer, you may have to go back to the #4363 driver (you would uninstall the driver you just installed with 'nvidia-installer --uninstall' and then install the #4363 driver. Cheers.
Thanks for the above info, and i hope it's ok to jump in here ? (newbie2?) I was a pleased Suse 8.0 user until that NVidia stuff hit the fan and ruined it for me. I have kernel 2.4.18_4GB with an AMD 2.4 G CPU on an Asus A7S333 M/Bd, with a GeForce2 MX64L -400 card, and i attempted to do the Suse security upgrade plus the NV driver (my first try -#4363 i think)), without doing enough reading and without killing X, so i ended up with a real mess - no video, no modem, Sax2 crippled etc. Now i've had to go back toWin98se to even get online, despite trying to reinstall Suse 8.0 Personal many times. What a disaster! Elitist bullshit? instead of help?
Personally i feel NVidia should be shot with a ball of their own <scat>, and Suse should never have allowed us newbies to be treated so badly. Changed my plans to buy 8.2 or 9.0 until i see if another distro or an ATI card is the way out for me. If you'd care to enlighten me about this NV card and this AMD cpu, i would certainly like to know more about it. Thanks, BrianB.
See my reply to Tom.
There is nothing wrong with the 4363 driver. I had it installed (on v9.0) until I bought the FX5200 card a few weeks ago. I have it on the computer with the MX440 and on the one with the MX400 (all running v9.0).
If you tried to re-install v8.0 many times without (apparent) success then it is not Suse's fault nor the driver's because the nVidia driver is not installed by Suse - you have to install it as a deliberate exercise; so you are doing somethng wrong to have the installation hassles.
(Re looking for an alternate distro. I've tried them all and believe me Suse is the only one to work with.)
To quote Tylk's Law, "Assumption is the mother of all foul-ups". All the discussion so far re the nVidia driver(s) has been on the assumption that people want to use 3D - as opposed to 2D - after installing the driver(s). The driver(s) cause(s) the problems mentioned if you try and use 3D. However, it/they function OK if you only use 2D. The latest 5336, for example, works perfectly on my other computer with the MX440 using 2D (ie, having "nv" and not "nvidia" in the XF86Config file). Cheers. -- All Scottish food is based on a dare.
On Wednesday 04 February 2004 14.17, Basil Chupin wrote:
All the discussion so far re the nVidia driver(s) has been on the assumption that people want to use 3D - as opposed to 2D - after installing the driver(s).
The driver(s) cause(s) the problems mentioned if you try and use 3D.
However, it/they function OK if you only use 2D. The latest 5336, for example, works perfectly on my other computer with the MX440 using 2D (ie, having "nv" and not "nvidia" in the XF86Config file).
But then you're not using nvidia's drivers. Then you're using the attempted open source implementation, which - frankly - sucks
Anders Johansson wrote:
On Wednesday 04 February 2004 14.17, Basil Chupin wrote:
All the discussion so far re the nVidia driver(s) has been on the assumption that people want to use 3D - as opposed to 2D - after installing the driver(s).
The driver(s) cause(s) the problems mentioned if you try and use 3D.
However, it/they function OK if you only use 2D. The latest 5336, for example, works perfectly on my other computer with the MX440 using 2D (ie, having "nv" and not "nvidia" in the XF86Config file).
But then you're not using nvidia's drivers. Then you're using the attempted open source implementation, which - frankly - sucks
Aaah, thanks for sorting me out on this one! Should have realised this when I noticed that the nVidia logo splash-screen did not show when starting Suse. Cheers. -- All Scottish food is based on a dare.
Anders Johansson wrote:
Basil Chupin wrote:
The driver(s) cause(s) the problems mentioned if you try and use 3D.
However, it/they function OK if you only use 2D. (ie, having "nv"
and not "nvidia" in the XF86Config file).
But then you're not using nvidia's drivers. Then you're using the attempted open source implementation, which - frankly - sucks
I found as a 'newbie' that the advice i got was confusing and even contradictory at times, as to how to update the NVidia drivers, using the NV site and the Suse site (binaries, rpms, 2d, 3d, nv, nvidia, YOU), etc.. .. I read the very helpful list mails (like this one!) over and over, and i still messed it up when things didn't go right or simply for me. Anders you have always shown a patient and most helpful attitude where we dumb newbies are concerned and i thank you for it. BUT, I will never NEVER give one nickel to any thing that NV puts on the market. Their GD selfish stupidity cost me weeks of confusion and frustration. If Suse can't make NV and kernel upgrades simpler and easier to understand then i don't think they are much better than Gates and Windoze... I guess the main fault for me was the poor, cryptic documentation, and not much Suse help. BrianB.
I have been following the email, but not the content for several weeks now. So I assume it is not a good idea to buy an NVidia card. I need a 1.8 volt video card for a new 2.4 GHz mobo, but I'm not going to play video games on it, altho it would be nice to have fairly snappy results in Windows AutoCadLT 97. I'll send the output to a 19" Sony hi-res CRT display. What do the experts here suggest?
Since I'm having similar problem with Nvidia I'll just
jump in and tell my story....After installing the 5336
driver from nvidia whith the sh NVIDIA*.bin
everything was fine ...but I made the mistake of
ungrading my kernel with the newer kernel for
Athlon-166 ..the nvidia dirvers refuse to load
complaining that there is no matching kernel...I had
to modify the XF86Config file to load the nv driver
for me to get X going again..
Now what I found that kind work for now to get nvidia
loading again at least to see that screen that says
Nvidia before the login sceen load.. for some reason
when I try to update my system again, the nvidia
drivers was part of the list so I Select the Nvidia
driver then when the installation was compled I was
able to see the Nvidia screen again..
Nevertheless, I still have 2 problems that I dont know
how to solved.
1) the sceen flick a lot before the nvidia screen
comes on that indicate there is a problem loading the
drivers
2) Even after downloading the kernel src the
Nvidia*.bin still refuse to install still complaining
that there is non matching kernel at the end it failed
to compile a new kernel for me.
One question I have D/L and installed the kernel src
"kernel-source-2.4.21-166.src.rpm" but I'm unable to
find where the src where installed.. there is nothing
in /usr/src no linux directory
Thanks for any help
--- Basil Chupin
Tom Allison wrote:
Anders Johansson wrote:
===== \\|// - ? (o o) / =======oOOO=(_)OOo=====================\ email : ephlodur@rocketmail.com What we need is Awareness we can't get carelless. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/
On Wednesday 04 February 2004 00.54, MindBender wrote:
One question I have D/L and installed the kernel src "kernel-source-2.4.21-166.src.rpm"
That is not the kernel source. The kernel source rpm is called kernel-source.rpm. Unlike all other source rpms it looks like a binary rpm, but isn't. You also need to prepare it before you can compile drivers against it cd /usr/src/linux make mrproper make cloneconfig make dep after that, the nvidia compile will work
You should download KERNEL_SOURCE_***.RPM from SuSE and NVIDIA_LINUX_X86_1_0_5328_P.RUN from nvidia site. And then run the nvidia .run driver. That's what I did. And everything works well. Edwin. -----Original Message----- From: Tom Allison [mailto:tallison1@twmi.rr.com] Sent: Tuesday, February 03, 2004 9:56 AM To: Suse Subject: [SLE] Nvidia Drivers and SuSE 90 I'm probably missing a long discussion as I just subscribed to the list: (I was out on an adventure trying different distros and broke my mail) However, I'm kind of stuck on one element of the NVIDIA video card problem: According to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HO WTO I should download kernel sources and the like to install the driver. That didn't work at all. Then I hit the SuSE database and found another entry where you just manually select the fetchnvidia driver package and reboot (I never heard of rebooting a Linux box, but OK) Now, how do I verify if I really do have 3D support? SAX2 says I don't have it. Do I? The FTP site said to ignore the 3D errors I would get.... Since the fTP site directions didn't work 100% I'm less than confident. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (9)
-
Anders Johansson -
Basil Chupin -
Brian Berrigan -
Donald Correll -
Doug McGarrett -
edwin -
MindBender -
Sheldon Barron -
Tom Allison