Ok, so I made the switch to nvidia, 6600GT. Now what? Following the instructions on the nvidia website I used YOU to install the patch and all seemed to go well there. It then said, "...logout, login back in and you're fine..." Apparently not. Check with SAX2 still shows card as VESA framebuffer device. I tried deleting that and specifying the 6600GT card and got some hiccups and a big burp. Lost the X system. Is there something else I need to do to get the card recognized and running? Should I follow the X configure step listed even though the site seemed to think this would be done already? Sorry. I am a babe in the woods here. Richard
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed December 22 2004 16:27, Lists wrote:
Hello Richard, I have the same card with X working fine. Go to the nvidia site (http://www.nvidia.com/object/linux_display_ia32_1.0-6629.html) download the nvidia driver. Once downloaded make sure that you have the kernel sources installed and updated, both via Yast, and then configure them thus ( you need to be root);
#>cd /usr/src/linux #>make cloneconfig && make dep
Close but not quite. Yes, make sure the kernel source is install, and to a "make cloneconfig". However if your running kernel source for 2.6.x then make dep is no longer used or function: # Crusher-1:/usr/src/linux # uname -r # 2.6.5-7.111.5-default # Crusher-1:/usr/src/linux # make dep # *** Warning: make dep is unnecessary now. Though you might be well served by issueing: # make prepare-all in place of "make dep". Also, Mr Lists is correct about needing to be in "init 3" . if when running #>sh NVIDIA-Linux-x86-1.0-6629-pkg1.run they're is a built in command help list that you can use - often times it's needed to use the install program to uninstall the drivers first before reinstallation (and pay attention to the "pkg1" part, sometimes they issue "pkg2" or "pkgX" and this has made a diff in the past). There a few tricks you can do if the installer is being cranky and uncooperative, and with the built help, online help, google, or the list will be able to address these. Mr Lists pretty much spells out what to do and it's very important to install in init 3, install cleanly (remove previous installs - and in some case tracking down files not removed, which shouldn't be a problem but has been in the past), and make sure XF86Config is properly set up - "glx" in the modules section and that indeed Device section also is setup. Note the once you get the 3D working and X and nVidia behave their is quite a few option you can use similar to those one could add to the X file for ATi cards - but it is much better documented and more thourough. I too have and ATi card (9600XT) and the drivers and support (ha there's a laugh) from ATi in inferior, nVidia is far superior IMHO. When upgrade time comes I'm back to nVidia. If you have any problems post the output to the list so we might better find the problems. Cheers, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! In the Ocean it's called salvage, on land it's called grave robbing! "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." - -US Senator Orrin Hatch, (R) Utah (courtesy of Fred Miller). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFByQnr7CQBg4DqqCwRAorkAJ9xzTLIDOmHFSP+0C7JW45P5v0E+ACgj5+k h3NkCaE5724M4oECXEjurgk= =wepu -----END PGP SIGNATURE-----
<snip>
Close but not quite. Yes, make sure the kernel source is install, and to a "make cloneconfig". However if your running kernel source for 2.6.x then make dep is no longer used or function: <snip> # *** Warning: make dep is unnecessary now.
found that out, but everything else seemed to proceed ok.
Though you might be well served by issueing:
# make prepare-all
in place of "make dep".
Didn't do this, being well on my way into my own little adventure.
Also, Mr Lists is correct about needing to be in "init 3" . if when running #>sh NVIDIA-Linux-x86-1.0-6629-pkg1.run they're is a built in command help list that you can use - often times it's needed to use the install program to uninstall the drivers first before reinstallation (and pay attention to the "pkg1" part, sometimes they issue "pkg2" or "pkgX" and this has made a diff in the past). There a few tricks you can do if the installer is being cranky and uncooperative, and with the built help, online help, google, or the list will be able to address these.
Mr Lists pretty much spells out what to do and it's very important to install in init 3, install cleanly (remove previous installs - and in some case tracking down files not removed, which shouldn't be a problem but has been in the past), and make sure XF86Config is properly set up - "glx" in the modules section and that indeed Device section also is setup. Note the once you get the 3D working and X and nVidia behave their is quite a few option you can use similar to those one could add to the X file for ATi cards - but it is much better documented and more thourough. I too have and ATi card (9600XT) and the drivers and support (ha there's a laugh) from ATi in inferior, nVidia is far superior IMHO. When upgrade time comes I'm back to nVidia.
If you have any problems post the output to the list so we might better find the problems.
Cheers, Curtis.
Installer program was VERY cranky about my previous attempt to load the driver from YOU online update, but did un-install it and seemed happy afterward, or less peevish anyway. I did not see much option to built-in help and the questions about un-installing a previous version did not arise...the program just did it without asking me to consider it...in retrospect, a wise decision since I seem to like to experiment, especially with things I don't understand. I did restart the system a few minutes ago, to make sure it would still boot and be able to come up. Seemed to go fine, I am back in GUI, though I did not see the Nvidia logo this time, unless the quick flash just before the logon screen was the logo. Hard to tell. Also, the install program noted I apparently have a module rivafb available and threatened me to not try to run both that and nvidia module at the same time. Is this (rivafb) a module I can comfortably delete/disable so I do not inadvertantly run it in the future? I assume the ...fb refers to framebuffer and riva sounds like an old (ATI) vesa card. Would this be what was running by default, before I installed the nvidia driver? It seems it would be safe to eliminate it then, because shore as shooting if there is something I was warned not to do, I will forget and try to do it sometime down the road.... Nvidia does show in the list with lsmod, so it must be installed, and I have display, so it must be working. I just ran sax2 again, just to see what it was finding, shows the correct card and monitor but did not have 3D enabled which I understood earlier would be enabled when all was correctly done. I enabled it. Will have to see what happens next. Thanks for your advice. Richard
On Thursday 23 December 2004 00:27, Richard wrote:
Ok, so I made the switch to nvidia, 6600GT. Now what? Following the instructions on the nvidia website I used YOU to install the patch and all seemed to go well there. It then said, "...logout, login back in and you're fine..." Apparently not. Check with SAX2 still shows card as VESA framebuffer device. I tried deleting that and specifying the 6600GT card and got some hiccups and a big burp. Lost the X system. Is there something else I need to do to get the card recognized and running? Should I follow the X configure step listed even though the site seemed to think this would be done already? Sorry. I am a babe in the woods here. Richard
Hello Richard, I have the same card with X working fine. Go to the nvidia site (http://www.nvidia.com/object/linux_display_ia32_1.0-6629.html) download the nvidia driver. Once downloaded make sure that you have the kernel sources installed and updated, both via Yast, and then configure them thus ( you need to be root); #>cd /usr/src/linux #>make cloneconfig && make dep Shut down and restart your computer and boot to runlevel 3 (by typing "init 3" at the grub boot screen), login as root. (you can do this from an X session by Run Command> init 3, I think). (Note; you will have to be able to use a text editor from the terminal you log in to. MC is what I use.) Then run the downloaded shell script thus (change your current directory to the directory where you downloaded the file); #>sh NVIDIA-Linux-x86-1.0-6629-pkg1.run It will ask you whether you want to check if there is an already compiled version of the driver on the Nvidia site, answer No to this. It will then compile and install the 6629 driver. In the process it might also ask whether you want to uninstall an old version of the driver (if you have one installed), say Yes to this. Start the text editor (mc at the command prompt for Midnight Commander) and edit the file /etc/X11/XF86Config. Save the old configuration in that directory as XF86Config.old. Close XF86Config.old and reopen XF86Config. Look for the section that starts "Section 'Module'", and make sure that it looks like this; Section "Module" Load "glx" Load "dbe" Load "extmod" Load "freetype" Load "v4l" Load "type1" Load "speedo" EndSection Look for the section that starts "Section 'Device'" and make sure that it looks like this; Section "Device" BoardName "NVIDIA GEFORCE 6600 GT" BusID "1:0:0" Driver "nvidia" Identifier "Device[0]" Option "NvAGP" "0" Screen 0 VendorName "NVIDIA" EndSection There are many other options that you can set here but the above works for me. Your monitor section is also a crucial one, but I am assuming that you have already set it up once via Sax2 for an old driver. If you do not know what you are doing do not alter anything else in this file, especially the monitor settings and the modes. Save the file, close the editor and try to start X with the 'startx' command. If you see the nvidia logo then the driver has loaded and you can go into runlevel 5 as normal. If it does not work, rename /etc/X11/XF86Config.old to /etc/X11/XF86Config, and repost with the relevant excerpts from /var/log/XFree86.0.log. Hope this helps, Allister -- Public Key to be found at www.keyserver.net. Search for tag@ukfsn
<snip>
directory as XF86Config.old. Close XF86Config.old and reopen XF86Config. Look for the section that starts "Section 'Module'", and make sure that it looks like this;
Section "Module" Load "glx" Load "dbe" Load "extmod" Load "freetype" Load "v4l" Load "type1" Load "speedo" EndSection
Look for the section that starts "Section 'Device'" and make sure that it looks like this;
Section "Device" BoardName "NVIDIA GEFORCE 6600 GT" BusID "1:0:0" Driver "nvidia" Identifier "Device[0]" Option "NvAGP" "0" Screen 0 VendorName "NVIDIA" EndSection
There are many other options that you can set here but the above works for me. Your monitor section is also a crucial one, but I am assuming that you have already set it up once via Sax2 for an old driver. If you do not know what you are doing do not alter anything else in this file, especially the monitor settings and the modes. Save the file, close the editor and try to start X with the 'startx' command. If you see the nvidia logo then the driver has loaded and you can go into runlevel 5 as normal. If it does not work, rename /etc/X11/XF86Config.old to /etc/X11/XF86Config, and repost with the relevant excerpts from /var/log/XFree86.0.log. Hope this helps, Allister
Thank you. I think that has worked. Growing up as a disobedient child (so my mother says), after running the nvidia program (mine for 86_64) I went to a terminal (??, ctrl-alt-F2), init 3, and ran sax2. When I had looked at the XF86config file first I saw Device section for the Vesa framebuffer device that was originally installed by Sax and decided that I could not have both in there and I was not willing to just charge into deleting that section and fixing references to screen 0 or 1, and so on. Too late I now notice that the nvidia site rec'd that be run as, "sax2 -m 0=nvidia". After running sax2 i then went to look at the XF86config file and found the framebuffer device gone and the sections you listed much as you described. The line for BusID was absent and while I noticed it I didn't fix it. Well, it seems to have fixed me. Return to init 5 and proceed and screen went blank, well, with some garbage, large line segments, a mess. Unable to go to another terminal I re-booted...to a blank screen tho I think I saw a fleeting nvidia logo, nothing else. Re-booted to runlevel 3, edited XF86Config to include the BusID line, change to init 5...and life seems to be good. Saw logo long enough to actually read it, went into X and appears good. While I seem not to have totally "learned my lesson" as my mother always said I would...I do have a couple of other questions: 1- I did not add the reference to "speedo" in the Module section. Is this important, what does it do? 2- My Device section contains the option "rotate" "off". Any idea what that is? My monitor can be rotated, isn't, but wouldn't that be in the monitor section? 3- I did not add to the Device section the option "NvAGP" "0". Should I? Again, what does it do, or not do? Thanks for your kind attention and detailed handholding. After several years of using linux I still feel I know just enough to be dangerous, but not quite enough to be effective. Richard
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed December 22 2004 21:52, Richard wrote:
<snip>
directory as XF86Config.old. Close XF86Config.old and reopen XF86Config. Look for the section that starts "Section 'Module'", and make sure that it looks like this;
Section "Module" Load "glx" Load "dbe" Load "extmod" Load "freetype" Load "v4l" Load "type1" Load "speedo" EndSection
Thank you. I think that has worked. Growing up as a disobedient child (so my mother says), after running the nvidia program (mine for 86_64) I went to a terminal (??, ctrl-alt-F2), init 3, and ran sax2. When I had looked at the XF86config file first I saw Device section for the Vesa framebuffer device that was originally installed by Sax and decided that I could not have both in there and I was not willing to just charge into deleting that section and fixing references to screen 0 or 1, and so on. Too late I now notice that the nvidia site rec'd that be run as, "sax2 -m 0=nvidia". After running sax2 i then went to look at the XF86config file and found the framebuffer device gone and the sections you listed much as you described. The line for BusID was absent and while I noticed it I didn't fix it. Well, it seems to have fixed me. Return to init 5 and proceed and screen went blank, well, with some garbage, large line segments, a mess. Unable to go to another terminal I re-booted...to a blank screen tho I think I saw a fleeting nvidia logo, nothing else. Re-booted to runlevel 3, edited XF86Config to include the BusID line, change to init 5...and life seems to be good. Saw logo long enough to actually read it, went into X and appears good. While I seem not to have totally "learned my lesson" as my mother always said I would...I do have a couple of other questions: 1- I did not add the reference to "speedo" in the Module section. Is this important, what does it do?
Speedo is a font and this tells X to use it as an optional font, as is type1 and freetype. Your should really have a look at the XF86/Xorg site and browse they help files - though some is a bit hypertechnical, you'll definitively find much useful info on the workings of X and configs therein.
2- My Device section contains the option "rotate" "off". Any idea what that is? My monitor can be rotated, isn't, but wouldn't that be in the monitor section?
The Rotate function is more for LCD style displays the can be adjusted so instead of looking a 1024x768 monitor your rotate the physical monitor 90 degrees and then use the rotate function to make the screen imaging rotate the same 90 degrees (also good for notepad style displays on newer laptop, etc.). If your using a normal display then forget about it - you likely wont' ever use it.
3- I did not add to the Device section the option "NvAGP" "0". Should I? Again, what does it do, or not do?
Ah, this is where the real learning comes in. The wonderful thing about Linux and X (unlike Windblows) is that if you have a problem with X (init 5 gui level) you key into the console/terminal (ctrl-F! through F6, that's 6 console access points) and then issue command init 3, or telinit 3. Then as I do, command: pico /etc/X11/XF86Config. Make the changes back to a working config (or try a variation or other commands/options) then ctrl-o, crtl-x to write out the file and leave the pico editor, and then issue init 5 (or telinit 5) and see if it works. I also have a back up of the original "stable-working" X config (e.g. XF86Config-bkup). So if I really kludge my config to the point where it giving me fits then a just command cp /etc/X11/XF86Config-bkup /etc/X11/XF86Config. The X config is overwritten back to the original file and a restart X (e.g by using either "startx" [which as root will start the root gui vs logged in as user; or using init 5) and bada boom bada bing you should be back in gui land.
Thanks for your kind attention and detailed handholding. After several years of using linux I still feel I know just enough to be dangerous, but not quite enough to be effective. Richard
Attention to detail and end users is a hallmark of this list - no big deal, glad you got some answers. Cheers, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! In the Ocean it's called salvage, on land it's called grave robbing! "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." - -US Senator Orrin Hatch, (R) Utah (courtesy of Fred Miller). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFByYS+7CQBg4DqqCwRAt0dAJ4xmcpsYKDBGlkPIHFq3G0vbqz2SACgsFbQ FB004xKoENDUg4g0gqwDvLE= =MLkc -----END PGP SIGNATURE-----
On Wednesday 22 December 2004 6:29 am, Curtis Rey wrote: <snip>
Speedo is a font and this tells X to use it as an optional font, as is type1 and freetype. Your should really have a look at the XF86/Xorg site and browse they help files - though some is a bit hypertechnical, you'll definitively find much useful info on the workings of X and configs therein.
2- My Device section contains the option "rotate" "off". Any idea what that is? My monitor can be rotated, isn't, but wouldn't that be in the monitor section?
<snip> I do have one of these but was not aware I could use the rotate ability in linux. May have to set this to "on" sometime and see what happens, sometime when I am more daring and less shell-shocked than I am right now.
3- I did not add to the Device section the option "NvAGP" "0". Should I? Again, what does it do, or not do?
Ah, this is where the real learning comes in. The wonderful thing about Linux and X (unlike Windblows) is that if you have a problem with X (init 5 gui level) you key into the console/terminal (ctrl-F! through F6, that's 6 console access points) and then issue command init 3, or telinit 3. Then as I do, command:
<snip> Actually have been doing this, and using pico. I got used to it some time ago as it seemed somewhat to look like old DOS edlin and I had been comfortable with that. Problems last night would not even allow me into those consoles, but thanks for the advice/direction to the Xorg site. I will head there and set up camp in their help files. Richard
On Thursday 23 December 2004 05:52, Richard wrote:
3- I did not add to the Device section the option "NvAGP" "0". Should I? Again, what does it do, or not do?
This option is quite important, as it sets the type of AGP driver (if any) you will be using. As you have not set this option you will be using option 3, i.e; "NvAGP" "3" which is default. This option will try loading the AGPGART driver first and if that fails then the NVAGP driver. Note that using an AGP module with your nvidia display driver is only supported for certain chipsets. Use on unsupported chipsets can result in system instability. Full details can be found in the README.txt in /usr/share/doc/NVIDIA_GLX-1.0. Having played around with these settings on a previous nvdia card, it did affect system stability. So if you get crashing whilst using 3D graphics this might be something to look into. Cheers Allister -- Public Key to be found at www.keyserver.net. Search for tag@ukfsn
participants (3)
-
Curtis Rey
-
Lists
-
Richard