On Sun, 2001-12-09 at 18:09, Peter Surda wrote: > On Sun, Dec 09, 2001 at 04:24:00PM +0100, Michel Dänzer wrote: > > > Syslog still complains CONTINUOSLY though, but I think that isn't so important > > > now. > > While others have reported the same errors, I haven't seen them here. Do > > they always appear, or only under certain circumstances, e.g. running GL > > or Xv clients or whatever ? > Now I tested it and the ONLY way I can reproduce it (both syslog bitching and > display corruption) is: > - starting kdm > - logging in via kdm into kde aka KDE spash screen. > It looks like this > http://ten.panorama.sth.ac.at/pictures/sshot.png > The background should be blue, there should be a kde splash picture and > obviously the fonts shouldn't overlap. Again to repeat: disabling dri fixes > it.
Hmm, I can't reproduce it here, but then I don't use kdm. > Afterwards I simply use X for a little time and apparently correct data finds > its way into videoram then :-). I am unable to reproduce either display > corruption or syslog entries later. > > Perhaps there is another place where ModeInit is run AFTER some initialization > was done already? Shouldn't be hard to find out. :) But then I wouldn't expect it to work fine afterwards. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
