Hi: I apologize in advance if this is the wrong place to report this.
I just checked out XDirectFB and DirectFB from CVS this morning, rebuilt both, and fired up XDirectFB. I'm getting what looks like corrupted video memory about 90% of the time. The other 10% of the time, I get an X display, but the keyboard and mouse input soon become unresponsive. The video card is a Matrox G400 32mb, dual-head capable. The machine is alive at the kernel level (I can ssh in, etc), but all of the virtual consoles, keyboard, and mouse are locked up, even when XDirectFB terminates on SIGTERM. All of the DirectFB demos work great on this (uniprocessor) box, so I'm pretty confident it's not a configuration issue. I've tried kernels 2.4.17 - 2.4.19-ac3, both with and without rml's preempt patches. Also tried memory tests and the X mga server; both of these work great also. Unless I'm really doing something boneheaded, it looks to me like I'm managing to trigger a race during the initialization of the framebuffer. I'm at a loss as to what to try next, so I thought I'd see if anyone has any debugging hints (or can reproduce this behavior). I'm more than willing to freeze up this machine a few more times, send configuration information, strace output, etc. Thanks in advance, - Dave [EMAIL PROTECTED]
msg00553/pgp00000.pgp
Description: PGP signature
