On Fre, 2002-10-04 at 06:41, Miles Lane wrote: > > I am running XFree86 HEAD on a Titanium PowerBook III/800 > with a 2.4.20-pre7-ben0 kernel built from Benjamin Herrenschmidt's > rsync tree. For the last couple of days, when I build from cvs HEAD, > starting X has locked up my display (I cannot switch away from > the locked tty7). My kernel is still running, because the CAPSLOCK > light still toggles.
So it did when my machine didn't power on and I had to send it in for repair... I usually try to ping it to determine if the kernel is up. > Anyhow, I have had only minor problems with the ati driver for the > last couple of months. I am running radeonfb in the kernel and > have the following settings in XF86Config: > > Section "Module" > Load "GLcore" > Load "bitmap" > Load "dbe" > Load "ddc" > # Load "dri" > Load "extmod" > Load "freetype" > Load "glx" > Load "int10" > Load "pex5" > Load "record" > Load "speedo" > Load "type1" > Load "vbe" > Load "xie" > EndSection That's a bit excessive, have you tried removing at least int10 and vbe? > The problem I have had with the ati driver prior to hitting this > display lockup problem was that sometimes when I would switch > between a VT window and the X display (or vice versa), the display > would show a sequence of three scanlines all starting at > different points. So, line 1, 4, 7, 10, ... would start at the > right edge of the screen, lines 2, 5, 8, 11, ... would be indented > about 1/8 of the screen and lines 3, 6, 12, 13, ... would be > indented 1/4 of the screen. Switching back and forth between a VT > and the X display would usually clean up the problem. > Very occaisionally the machine would lock up and need a cold boot. > There was also a scrolling effect, where unsynced lines would seem > to be scrolliny up slowly up. [...] > It is worth noting that the fbdev driver is working pretty well, > though it exhibits the same problem that the ati driver used to > have. That is, sometimes when switching between a VT and the > X display (or vice versa), the display is munged with unsynced > scanlines. That's a radeonfb glitch. The one to find and fix it gets the prize. :) > (EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument That's also a radeonfb bug, I sent a fix to Ben and Ani and Ben is merging it into his tree right now. The second log you posted was still from the fbdev driver BTW. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
