Re: [SLE] Video corrution problem in SUSE10.1
You probably have Option "HWCursor" "off" or Option "SWCursor" "on"
in your configuration file. In that case these effects happen for XVideo and OpenGL surfaces. Nothing that can be done about that.
Note that with hardware cursors the cursor flickers on pointer bitmap updates (e.g. with the wait pointer in firefox) with the current driver. Nvidia is aware of that issue.
That was it. Commented out the HWCursor line, and restarted X... all is well again with the world :-) Thanks. C. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Jun 17, 06 12:02:18 +0200, Clayton wrote:
You probably have Option "HWCursor" "off"
in your configuration file. In that case these effects happen for XVideo and OpenGL surfaces. Nothing that can be done about that.
That was it. Commented out the HWCursor line, and restarted X... all is well again with the world :-) Thanks.
The only remaining thing is - how did that line ever come into your
configuration? :-]
Matthias
--
Matthias Hopf
You probably have Option "HWCursor" "off"
in your configuration file. In that case these effects happen for XVideo and OpenGL surfaces. Nothing that can be done about that.
That was it. Commented out the HWCursor line, and restarted X... all is well again with the world :-) Thanks.
The only remaining thing is - how did that line ever come into your configuration? :-]
I have no idea. I'm using the xorg.conf as configured/provided by SAX. I didn't use the initial xorg file provided when I installed 10.1.. I had an old one that I used because I was still using dual head, and had some special config options set that are basically impossible to set with SAX. I've since removed the second monitor and dropped back to just using one monitor. I removed my custom xorg and started sax2 from init 3. SAX did it's thing and made a huge mess of my system configuration. And I do mean a me. My mouse no longer worked, my video was set up wrong, my monitor was being pushed out of range.. the works. I was able to reset things once at a time using sax2 -l and selecting a mouse, telling it was a 3 button mouse and so on - all with the SAX tools... no hand config. So, somewhere in that SAX disaster I must have accidently set the HWCursor option. C. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Jun 19, 06 19:13:29 +0200, Clayton wrote:
The only remaining thing is - how did that line ever come into your configuration? :-]
I have no idea. I'm using the xorg.conf as configured/provided by
;)
dropped back to just using one monitor. I removed my custom xorg and started sax2 from init 3. SAX did it's thing and made a huge mess of my system configuration. And I do mean a me. My mouse no longer worked, my video was set up wrong, my monitor was being pushed out of range.. the works. I was able to reset things once at a time using
Maybe (if you want to) try "sax2 -r" - that -r is important, because it
starts from scratch. If some Meta-options aren't available, sax may
misbehave and break things otherwise.
But remember to save your config first ;)
CU
Matthias
--
Matthias Hopf
participants (2)
-
Clayton -
Matthias Hopf