On Tue, 2006-05-16 at 17:52 +0200, Sven Luther wrote: > On Tue, May 16, 2006 at 05:33:24PM +0200, Sven Luther wrote: > > On Tue, May 16, 2006 at 12:16:38PM +0200, Michael Schmitz wrote: > > > > > $ more /proc/fb > > > > > 0 ATI Radeon Lf > > > > > > > > 0 OFfb ATY,264LTP > > > > 1 OFfb ATY,264LTP > > > > > > Might be the LCD is actually on the second one? > > > > This might be the reason it fails, if it is so. But i am not sure, since the > > dmesg output mentioned fb0. > > 17:37 < Corsac> but forcing DEBIAN_FRONTEND to gtk seems to run correctly, > until it crash with signal 11 > > So, the DEBIAN_FRONTEND is not correctly set to gtk, for whatever reason, > probably because of the image used, and the build setup not being adapted for > powerpc after the merge or something.
I don't really know. Maybe the "framebuffer.." error message is also due to framebuffer crashing. > > Still, it crashed with signal 11. > > Could you tell us more about this signal 11, and tell us when it happened. You can see logs of running debian-installer: http://heracles.corsac.net/~corsac/hydra/di3.log When I strace this, this is what I get: http://heracles.corsac.net/~corsac/hydra/strace.log > > It is possible that we did disable some stuff in the directfb code for radeon, > which needs disabling also for atyfb, or in general for powerpc. > > Some directfb accel i think it was. On advices got on #debian-boot I added on my /etc/directfbrc: debug no-hardware Regards, -- Yves-Alexis Perez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
