Click to See Complete Forum and Search --> : Mandrake 9 and nvidia finally!


mocnicom
12-21-2002, 08:36 PM
Well I haven't been able to get this to work for ages, and today I gave it another shot. I followed the same directions as I always did (similar to these: http://linuxnewbie.org/forum/showthread.php?s=&threadid=77741&highlight=mandrake+nvidia )
and I got the same problems and errors when trying to start X. So I opened up XF86Config-4 in VI and noticed that the word "work" was grayed out. It seems it got pushed over somehow and thus wasn't in it's comment line anymore. I commented it and now the driver is working! Anyone else getting an error that they can't fix may want to carefully study their config file for similar errors. And btw I think the driver installer somehow was responsible for pushing over the text. Now time to dl that Quake3 point release for linux!

bosox79
12-21-2002, 08:58 PM
Originally posted by mocnicom
Well I haven't been able to get this to work for ages, and today I gave it another shot. I followed the same directions as I always did (similar to these: http://linuxnewbie.org/forum/showthread.php?s=&threadid=77741&highlight=mandrake+nvidia )
and I got the same problems and errors when trying to start X. So I opened up XF86Config-4 in VI and noticed that the word "work" was grayed out. It seems it got pushed over somehow and thus wasn't in it's comment line anymore. I commented it and now the driver is working! Anyone else getting an error that they can't fix may want to carefully study their config file for similar errors. And btw I think the driver installer somehow was responsible for pushing over the text. Now time to dl that Quake3 point release for linux!

very good point mocnicom, it pays to be careful & always doubble check things:D

bwkaz
12-27-2002, 01:41 PM
If you happened to edit the config file yourself (note: the nVidia installer does NOT touch your XF86Config file, if that's the config file you saw the problem with...), then don't use pico. Maybe that was the problem?

If you use normal pico, it will word-wrap with carriage returns at the width of your terminal window. If you use pico -w, though, it won't. I don't know whether nano does the same, but I'd guess it does.

vim and/or emacs don't have problems like that, because they don't do word wrap with carriage return characters (i.e. they don't change the file you're editing unless you tell them to).

So maybe that explains what happened...

tvance
12-28-2002, 12:16 AM
I was going to put a step by step ultra newbie HOW TO for my TNT2 Card,,,, with Drake9 -- do you think this is needed?

Do you have TNT? If you think so let me know, I was going to go step by step of what 'THIS ULTRA NEWB' did to get it to work perfectly.

lemme know,
tv

mocnicom
12-28-2002, 01:56 PM
tvance: No I don't have a TNT2. Feel free to make the guide though.