It would appear that on Nov 21, please try again did say:
> jtwdyp;2505416 Wrote:
> >
> > It didn’t surprise me much with nouveau, as my builtin nvidia hasn’t
> > yet worked properly with nouveau on any of the dozen or so distro’s I’ve
> > had installed installed in it since I got to salvage my brother in laws
> > former winbox…
> >
> > But this is the first time installing an actual nvidia driver from the
> > distribution’s repo didn’t solve it…
> >
> > But it occurs to me that maybe I missed a step.
> >
>
> No. You are perfectly right. Installing the nvidia driver usually
> solves this kind of problem… But the Geforce 6150 has a lot of
> problems - and we should be “thankful” (?!) that it is still supported
> by the driver.
Yeah, I’ve noticed that… Still I wouldn’t want to disparage the gift my
Brother in law gave me when he upgraded from his old win xp box {on which he
thought his video card worked well for the games he liked to play on it…}
> jtwdyp;2505416 Wrote:
> > So is it likely that I just need to manually run mkinitrd???
>
> For sure, the GeForce 6150 doesn’t like KMS. But if you installed the
> nvidia driver correctly, it did already rebuilt initrd without KMS. You
> can not use KMS with nouveau either with this gfx card (you need to boot
> with nomodeset).
Is using yast2’s “software repositories” module to add the repo, then using
it’s “software management” module to update about 200 packages, including the
nvidia driver which had been marked for automatic installation, be the correct
process? Is there no other step I should have done?
And please tell me that the automatic rebuilding of the initrd would include
any needed changes to grub legacy’s menu.lst? {I despise grub2 too much to let
opensuse install it. (I’d go back to lilo first)}
-
-
-
-
-
-
-
- -< s n i p >- - - - - - - - - -
It would appear that on Nov 21, dd did say:
> On 11/21/2012 06:06 AM, please try again wrote:
> > Yes, I got this problem yesterday on GeForce 6150 and the latest nvidia
> > driver from repo.
>
> so, maybe you two should conspire to write a bug to the the nVidia driver
> folks…
>
> or should it enter the system in our bugzilla? http://tinyurl.com/nzhq7j
When I’m a little more sure what the problem is, I’d be more than willing to
to conspire & collaborate on such a thing… 
-
-
-
-
-
-
-
- -< s n i p >- - - - - - - - - -
It would appear that on Nov 21, Knurpht did say:
> martin_helm;2505427 Wrote:
> > Am 21.11.2012 11:46, schrieb please try again:
> > > Nobody cares about GeForce 6150 anymore. However I should not
> > > complain about these old mainboards. They’re still running fine,
> > > even in dual monitor setup.
> > >
> > While this card is a 6xxx has someone of you tried if the legacy G01
> > driver works better with it than the G02?
> ah, some confirmation that a friend is not crazy. He stated that his
> 6xxx card does work with the G01 driver, only partly with the G02.
> Haven’t been able to check this, when he told me we did not have acces.
> IIRC he found this on the NVIDIA forums
To which it seems that on Nov 21, Martin Helm did add:
>+ A friend of mine has a 6150 in an older machine and I think to remember
>+ that I used the older G01 driver with it when I installed 12.2 on his
>+ machine due to some reason I forgot in the meantime.
All righty then, maybe I want this “G01” driver… It might even resolve the
other display issues described in my “want HUGE font” thread…
Do I simply tell yast to install it, and let it automatically remove the G02?
And how would I prevent future updates from “upgrading” me back to G02" And do
I need to take any additional steps to keep “G01” safe from “zypper up” ???
Actually though, maybe, once/if I get a nvidia driver working well enough for
me, (don’t much care about the 3d stuff {My idea of gaming is Shisen-Sho &
KBreakOut} I just want stable 2d graphics…) would I be well advised to
simply disable the nvidia repo???
-
-
-
-
-
-
-
- -< s n i p >- - - - - - - - - -
It would appear that on Nov 21, Tyler K did say:
> * FWIW, I encounter a disappearing mouse cursor like you describe, on non
> nvidia hardware (to add another data pt), on a some what frequent basis
> (maybe every couple of days). However, unlike yourself, I’ve not been
> required to reboot to bring the cursor back to the foreground/visible
> … I can bring it back by exaggerated movements on/off the screen
> and/or across windows, and with mouse clicks (in particularly on
> clickable items, such as menus in an application window). For me, its
> an annoying behaviour but relatively benign. I can’t discern an actual
> trigger for it, though, I notice that its occurrence seems to be more
> prevalent with some things such as video playback (with smplayer for
> instance). I’ve seen (slash/ been afflicted by) it for several
> releases. I’ve also seen others complain about it too (both here and
> abroad).
Heck, in my case the trigger could be as simple as <ctrl>+<alt>+<F2> to open a
real root login session. Then changing my mind in favor of “su -” on a Konsole
where it’s easier to copy & paste stuff from an existing google search in
Firefox, And switching back with <alt>+<F7> {without even having logged in to
tty2…} Then, of course, I gotta use keyboard methods to save any changes
and reboot…
Even that, wouldn’t be so bad if the problem wasn’t triggered by so many things
that on average I’ve begun to feel lucky if the mouse pointer is still visible
half an hour after booting. But I’m hoping that with my hardware the fix will
turn out to be that G01 driver… Time will tell.
Thanks to all of you!
–
JtWdyP
