Nvidia Graphic card driver problems
in [Suse]
|
Prev: Conexant Falcon II Help
Next: Firefox over ssh
From: Martin on 9 Jun 2010 08:10 On 09/06/10 13:50, BlindBaby wrote: > On Thu, 03 Jun 2010 10:22:45 +0200, Martin <martin(a)invalid.invalid> > wrote: > >> >> I suspect the problem I have is caused by Nvidia providing one driver to >> support too many legacy cards. > > Bullshit. It is a driver PACKAGE. It KNOWS which card you have and > drops in or compiles that card's drivers upon installation. You are right. I meant the x-11... file. > > NVidia has been doing it better than the rest this whole time. It did it better with Open Suse Linux 11.0
From: Archimedes' Lever on 9 Jun 2010 22:51 On Wed, 09 Jun 2010 14:08:35 +0200, Martin <martin(a)invalid.invalid> wrote: >On 09/06/10 13:44, Archimedes' Lever wrote: >> On Tue, 01 Jun 2010 11:50:45 +0200, Martin <martin(a)invalid.invalid> >> wrote: >> >>> On 01/06/10 11:30, Martin wrote: >>>> On 01/06/10 09:33, graham wrote: >>>>> On Mon, 31 May 2010 17:39:25 +0200, Martin wrote: >>>>> >>>>>> On 31/05/10 17:23, Darklight wrote: >>>>> >>>>>>> make sure you use the one click legacy driver for geforce4 from >>>>>>> opensuse. >>>>>> >>>>>> I have and did. :o) >>>>> >>>>> I had a similar problem. >>>>> When I looked in yast I noted four pairs of nvidia drivers. >>>>> I removed those not related to my card and everything worked. >>>>> ( the pairs being the glx and kernel modeules. ) >>>> >>>> If only it was so easy :o) >>>> >>>> I only have the two that are required for my card installed, namely >>>> x11-video-nvidia and nvidia-gfx-kmp-default >>>> >>>> Incidentally using Open Suse Linux 11.0 I had no problems with the >>>> graphics board. >>> >>> In desperation I removed the GeForce 4 drivers and replaced them with >>> the GeforceFx drivers. The normal boot failed but rebooting from the >>> fail safe option, worked. I now have proper windowing. Very strange! >> >> That indicates a grub boot line error. Examine the differences between >> the safe boot line, and the normal boot line, and look for graphics calls >> in the normal one. >> >> It could be that the boot up mode that is being fed in is messing with >> the x mode startup. >> >> If all you need is windowing, you could simply go with frame buffer >> modes too. > >I was hoping to get windowing and the performance of the graphics cars >and a resoluton and refresh rate that matches the monitor I am using. Do you really need more than 60 Hz? And if your display is at 23" or more 60Hz is all that you likely have available to you. The frame buffer modes all do 60Hz. With the 3D acell off, you x performance is not much different than frame buffered mode. Cards can toggle their frame buffers pretty quickly. Anyway, it must have something to do with an x configuration file. Try booting up a live disc from a distro of your liking (the new suse and ubuntu releases are nice) and then investigate the screen mode it auto-selects as it takes you into x. or run sax2 from that live session and see what it puts in the file, and how that compares with your file. ***!!!###$$$ << alert indicator. :-) See below... There you go. Boot the live session, and chroot over to your install, and run sax2 and have it update your install's file from the active, working session.
From: Archimedes' Lever on 9 Jun 2010 22:54 On Wed, 09 Jun 2010 14:10:31 +0200, Martin <martin(a)invalid.invalid> wrote: > >It did it better with Open Suse Linux 11.0 We always get to poke and prod at the new releases if they have bugs. Then, we start talking about how the next release has them everywhere as the current release's crop gets 'ironed out'. I think maybe I did it better in a past life, or that maybe I will do better in the next, but I do not always feel the greatest about what I have gotten done (or not) in this life. I should do stand up.
From: Martin on 10 Jun 2010 05:53 On 10/06/10 04:51, Archimedes' Lever wrote: > On Wed, 09 Jun 2010 14:08:35 +0200, Martin <martin(a)invalid.invalid> > wrote: > >> On 09/06/10 13:44, Archimedes' Lever wrote: >>> On Tue, 01 Jun 2010 11:50:45 +0200, Martin <martin(a)invalid.invalid> >>> wrote: >>> >>>> On 01/06/10 11:30, Martin wrote: >>>>> On 01/06/10 09:33, graham wrote: >>>>>> On Mon, 31 May 2010 17:39:25 +0200, Martin wrote: >>>>>> >>>>>>> On 31/05/10 17:23, Darklight wrote: >>>>>> >>>>>>>> make sure you use the one click legacy driver for geforce4 from >>>>>>>> opensuse. >>>>>>> >>>>>>> I have and did. :o) >>>>>> >>>>>> I had a similar problem. >>>>>> When I looked in yast I noted four pairs of nvidia drivers. >>>>>> I removed those not related to my card and everything worked. >>>>>> ( the pairs being the glx and kernel modeules. ) >>>>> >>>>> If only it was so easy :o) >>>>> >>>>> I only have the two that are required for my card installed, namely >>>>> x11-video-nvidia and nvidia-gfx-kmp-default >>>>> >>>>> Incidentally using Open Suse Linux 11.0 I had no problems with the >>>>> graphics board. >>>> >>>> In desperation I removed the GeForce 4 drivers and replaced them with >>>> the GeforceFx drivers. The normal boot failed but rebooting from the >>>> fail safe option, worked. I now have proper windowing. Very strange! >>> >>> That indicates a grub boot line error. Examine the differences between >>> the safe boot line, and the normal boot line, and look for graphics calls >>> in the normal one. >>> >>> It could be that the boot up mode that is being fed in is messing with >>> the x mode startup. >>> >>> If all you need is windowing, you could simply go with frame buffer >>> modes too. >> >> I was hoping to get windowing and the performance of the graphics cars >> and a resoluton and refresh rate that matches the monitor I am using. > > Do you really need more than 60 Hz? No. The default is giving me 70Hz > > And if your display is at 23" or more 60Hz is all that you likely have > available to you. It is 22". I agree with you. > > The frame buffer modes all do 60Hz. With the 3D acell off, you x > performance is not much different than frame buffered mode. Cards can > toggle their frame buffers pretty quickly. > > Anyway, it must have something to do with an x configuration file. > > Try booting up a live disc from a distro of your liking (the new suse > and ubuntu releases Open Suse 11.2? > are nice) and then investigate the screen mode it > auto-selects as it takes you into x. or run sax2 from that live session > and see what it puts in the file, and how that compares with your file. > > ***!!!###$$$ << alert indicator. :-) See below... > > There you go. Boot the live session, and chroot over to your install, > and run sax2 and have it update your install's file from the active, > working session. I did all that already. :o(
From: Martin on 10 Jun 2010 05:57
On 10/06/10 04:54, Archimedes' Lever wrote: > On Wed, 09 Jun 2010 14:10:31 +0200, Martin <martin(a)invalid.invalid> > wrote: > >> >> It did it better with Open Suse Linux 11.0 > > We always get to poke and prod at the new releases if they have bugs. > > Then, we start talking about how the next release has them everywhere > as the current release's crop gets 'ironed out'. Part of the problem is support for legacy cards. One reason for switching to Linux is cost. I'm not the sort that bins adequate boards. In the words of the song "Fings aint wot they used to be" > > I think maybe I did it better in a past life, or that maybe I will do > better in the next, but I do not always feel the greatest about what I > have gotten done (or not) in this life. > > I should do stand up. I go along with that LOL |