On Wed, Oct 13, 2004 at 03:37:41PM +0200, Jan-Benedict Glaw wrote: > On Wed, 2004-10-13 00:24:44 -0400, Michel Dänzer <daenzer@debian.org> > wrote in message <[🔎] 1097641484.4421.46.camel@admin.tel.thor.asgaard.local>: > > On Tue, 2004-10-12 at 15:43 +0200, Jan-Benedict Glaw wrote: > > > On Wed, 2004-09-01 04:55:17 -0500, Branden Robinson <branden@debian.org> > > > wrote in message <20040901095517.GO16490@redwald.deadbeast.net>: > > > I guess (but of course I'm not sure -- I'm not a X11 / XFree86 guru...) > > > this means that the used widget library contains a bug. I guess it's > > > responsible for providing the xwd dump data, but not the hardware > > > driver... > > > This is likely a driver bug; to most other components involved it > > matters little if at all which screen xclock is on. So, please provide > > the information about your setup that Branden asked for in his first > > followup. > > Here we are: Thanks for following up! I need a little more info, though: > VGA-compatible devices on PCI bus: > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) > 0000:02:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB [Mach64 GTB] (rev 9a) > 0000:02:0a.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB [Mach64 GTB] (rev 9a) Which of these video cards is driving the display that exhibits the bad behavior? Does it matter? I.e., does the middle screen always have this problem whether it's being driven by the RV280 or the 3D Rage II+ cards? -- G. Branden Robinson | I'm a firm believer in not drawing Debian GNU/Linux | trend lines before you have data branden@debian.org | points. http://people.debian.org/~branden/ | -- Tim Ottinger
Attachment:
signature.asc
Description: Digital signature