Hello again Michel, One more bit of information for you. When in the dual monitor mode with the crazy messed up colours, I've observed that uninterrupted blocks of solid colour are drawn correctly.
For example, I use the Gnome desktop background (Nautilus in my case). If I set the solid background colour to be what should be blue (but is displayed black in the colour selector as I've previously stated), it is drawn correctly as blue on the background. If I click and drag an icon around, it leaves a black trail. (An image background is rendered incorrectly as everything else). Could this be related to the difference in hardware and software rendering? I'm assuming the solid colour is hardware filled, but as I drag icons it's done in software. The hardware rendered fill is drawn correctly but the software is wrong as described. Unfortunately I can't run Quake2 to see an entirely hardware drawn screen as direct rendering is disabled in dual monitor mode, but I'd expect it was drawn with the correct colour palette. Any other suggestions? I hope I'm not way off the tracks here and the information is useful to you (or somebody). John. On Wed, 2003-05-28 at 14:51, John Leach wrote: > Hi Michel, > > sorry for the delay, but this has taken me quite a while to put > together. > > On Tue, 2003-05-27 at 23:48, Michel Dänzer wrote: > > > Sure, NoAccel is never a solution but merely a means to help find out > > what's going on. > > Ok, my testing shows no change toggling the NoAccel option (for both > displays at the same time) other than a performance hit..... -- GPG KEY: B89C D450 5B2C 74D8 58FB A360 9B06 B5C2 26F0 3047 HTTP: http://www.johnleach.co.uk
signature.asc
Description: This is a digitally signed message part
