Mailinglist Archive: opensuse (2731 mails)
| < Previous | Next > |
Re: [SLE] NVIDIA Upgrade
- From: Thom Nuzum <thom@xxxxxxxxxx>
- Date: Sun, 3 Aug 2003 13:33:37 -0400
- Message-id: <200308031333.37586.thom@xxxxxxxxxx>
Thanks for this.
Don't know if this was the best way. I just installed the default kernel and
removed the Athlon one. did the Nvidia-install, enabled 3d and all works.
Not sure if I should use the Athlon kernel or not though.
On Sunday 03 August 2003 15:09, Curtis Rey wrote:
> On Saturday 02 August 2003 06:29 pm, Zach Smith wrote:
> > Don't know if you want to hear this but I tried "upgrading" to the 5200
> > and it did the same thing. I never could get it resolved so I ended up
> > going back to the GeForce3 card. I hear the the 5900 has been used
> > successfully with Linux in general but don't take my word on it. Good
> > luck.
> >
> > Zach
> >
> > On Sat, 2003-08-02 at 17:53, thom@xxxxxxxxxx wrote:
> > > Hi,
> > >
> > > I just replaced old Geforce with a new Geforce FX 5200.
> > > I boot into a blank screen now. Starting in text mode I can start Yast
> > > and there all the NVIDIA options for my card cause a lock-up that
> > > Ctrl-Alt-Backspace can't get me out of.
> > > I've already tried the Nvidia forum and will look back.
> > > Is there a way in Yast to get the generic NViDIa drivers back and work
> > > from there? Not sure if going into xf86config will help either.
> > > Should I put the old card back in and try something there?
> > > Don't want to reinstall SuSe 8.2 (though i could back-up my docs and do
> > > this)
>
> OK, in the sax cdb (card data base) is a listing of all the cards sax
> recognizes. When on goes to the NVIDIA README and looks at the cards the
> drivers support then one finds the following:
>
> GeForce FX 5200 0x0322
> GeForce FX 5200 Ultra 0x0321
>
> And in Sax on finds:
>
> NVidia:0x0321 {
> 3DDriver = nvidia
> 3DProfile = nvidia
> Flag = 3D
> Extension = glx
> Driver = nv
> }
>
> NVidia:0x0322 {
> 3DDriver = nvidia
> 3DProfile = nvidia
> Flag = 3D
> Extension = glx
> Driver = nv
> }
>
>
> So it seems that your card is supported by sax. The questions are these
> however:
>
> A) are you chosing the right vid card module from sax? Given that this is
> not explicitly labelled GeForceFX 5200, might you have better success with
> chosing the card labelled "0x0322" or "0x0321"?
>
> B) is the listing in /var/lib/hardward/unique-keys causing a problem? This
> has been the case in the past with soundcards, and it may or may not be
> causing problems.
>
> C) One might manually edit the XF86Config to change the labelled
> identifiers to the video card as such
>
> #BoardName "GeForce3 Ti 200"
> BoardName "0x0322"
> Driver "nvidia"
> Identifier "Device[0]"
> Option "CursorShadowAlpha" "64"
> Option "CursorShadowXOffset" "4"
> Option "DigitalVibrance" "175"
> Option "CursorShadow" "1"
> Option "NvAGP" "3"
> Option "NoBandWidthTest" "1"
> Option "CursorShadowYOffset" "4"
> Option "NoLogo" "1"
> Screen 0
> Option "Rotate" "off"
> VendorName "NVidia"
>
> And is the module "GLX" designated in the XF86Config? as such:
>
> Section "Module"
> Load "type1"
> Load "glx" ***************************************
> Load "v4l"
> Load "freetype"
> Load "speedo"
> Load "dbe" ************ as well as this ***********
> Load "extmod ************ and this *****************
>
> There are other parameters that are in conjunction with the way the the
> Xserver, video card/drivers, and monitors interact. Sometimes these don't
> play nice with each others. This has been my experience with problems
> between video card and monitors. I have had to in the past add options
> such as:
>
> Option "UseEdidFreqs" "boolean"
> Option "IgnoreEDID" "boolean"
>
> And
>
> Option "NoDDC" "boolean"
>
> This is due to failings in the NVIDIA drivers while "probing" the monitors.
>
> There is also a no probe option, but it escapes me now. You might need to
> reconfig you monitor as well, lord knows I have had to do this before
> several times. Just as soon as the 3Ddiag and other checks indicate the
> drivers are installed and operating as they should it fails on the X start
> (similar to you problem) so I have to go back and config it all over making
> sure that the monitor is reconfiged as well.
>
> HTH, Curtis.
--
Thom Nuzum
(in DC)
Don't know if this was the best way. I just installed the default kernel and
removed the Athlon one. did the Nvidia-install, enabled 3d and all works.
Not sure if I should use the Athlon kernel or not though.
On Sunday 03 August 2003 15:09, Curtis Rey wrote:
> On Saturday 02 August 2003 06:29 pm, Zach Smith wrote:
> > Don't know if you want to hear this but I tried "upgrading" to the 5200
> > and it did the same thing. I never could get it resolved so I ended up
> > going back to the GeForce3 card. I hear the the 5900 has been used
> > successfully with Linux in general but don't take my word on it. Good
> > luck.
> >
> > Zach
> >
> > On Sat, 2003-08-02 at 17:53, thom@xxxxxxxxxx wrote:
> > > Hi,
> > >
> > > I just replaced old Geforce with a new Geforce FX 5200.
> > > I boot into a blank screen now. Starting in text mode I can start Yast
> > > and there all the NVIDIA options for my card cause a lock-up that
> > > Ctrl-Alt-Backspace can't get me out of.
> > > I've already tried the Nvidia forum and will look back.
> > > Is there a way in Yast to get the generic NViDIa drivers back and work
> > > from there? Not sure if going into xf86config will help either.
> > > Should I put the old card back in and try something there?
> > > Don't want to reinstall SuSe 8.2 (though i could back-up my docs and do
> > > this)
>
> OK, in the sax cdb (card data base) is a listing of all the cards sax
> recognizes. When on goes to the NVIDIA README and looks at the cards the
> drivers support then one finds the following:
>
> GeForce FX 5200 0x0322
> GeForce FX 5200 Ultra 0x0321
>
> And in Sax on finds:
>
> NVidia:0x0321 {
> 3DDriver = nvidia
> 3DProfile = nvidia
> Flag = 3D
> Extension = glx
> Driver = nv
> }
>
> NVidia:0x0322 {
> 3DDriver = nvidia
> 3DProfile = nvidia
> Flag = 3D
> Extension = glx
> Driver = nv
> }
>
>
> So it seems that your card is supported by sax. The questions are these
> however:
>
> A) are you chosing the right vid card module from sax? Given that this is
> not explicitly labelled GeForceFX 5200, might you have better success with
> chosing the card labelled "0x0322" or "0x0321"?
>
> B) is the listing in /var/lib/hardward/unique-keys causing a problem? This
> has been the case in the past with soundcards, and it may or may not be
> causing problems.
>
> C) One might manually edit the XF86Config to change the labelled
> identifiers to the video card as such
>
> #BoardName "GeForce3 Ti 200"
> BoardName "0x0322"
> Driver "nvidia"
> Identifier "Device[0]"
> Option "CursorShadowAlpha" "64"
> Option "CursorShadowXOffset" "4"
> Option "DigitalVibrance" "175"
> Option "CursorShadow" "1"
> Option "NvAGP" "3"
> Option "NoBandWidthTest" "1"
> Option "CursorShadowYOffset" "4"
> Option "NoLogo" "1"
> Screen 0
> Option "Rotate" "off"
> VendorName "NVidia"
>
> And is the module "GLX" designated in the XF86Config? as such:
>
> Section "Module"
> Load "type1"
> Load "glx" ***************************************
> Load "v4l"
> Load "freetype"
> Load "speedo"
> Load "dbe" ************ as well as this ***********
> Load "extmod ************ and this *****************
>
> There are other parameters that are in conjunction with the way the the
> Xserver, video card/drivers, and monitors interact. Sometimes these don't
> play nice with each others. This has been my experience with problems
> between video card and monitors. I have had to in the past add options
> such as:
>
> Option "UseEdidFreqs" "boolean"
> Option "IgnoreEDID" "boolean"
>
> And
>
> Option "NoDDC" "boolean"
>
> This is due to failings in the NVIDIA drivers while "probing" the monitors.
>
> There is also a no probe option, but it escapes me now. You might need to
> reconfig you monitor as well, lord knows I have had to do this before
> several times. Just as soon as the 3Ddiag and other checks indicate the
> drivers are installed and operating as they should it fails on the X start
> (similar to you problem) so I have to go back and config it all over making
> sure that the monitor is reconfiged as well.
>
> HTH, Curtis.
--
Thom Nuzum
(in DC)
| < Previous | Next > |