Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used
Package: cdebconf-gtk-udeb
Severity: normal
DirectFrameBuffer by default enables hardware acceleration whenever
possible, this resulted in a DFB crash on many PPC systems [1] .
DFB's HW acceleration should be disabled at runtime for those fb drivers
that are known to be actually broken.
Detection of used framebuffer module can be done after boot by checking
kernel's output, while DFB's HW acceleration can be turned off by adding
"no-hardware" to runtime configuration file "/etc/directfbrc" [2].
The user should always be able to force HW accelaration off at boot time
with an ad-hoc parameter.
As a temporary workaround for bugs like [1] this has proven to
occasionally work
-Boot the graphical-installer with
install video=ofonly DEBIAN_FRONTEND=newt
-Let the NEWT frontend appear, switch to VT2 and type
echo 'no-hardware' >>/etc/directfbrc
echo 'screenshot-dir=/' >>/etc/directfbrc
export DEBIAN_FRONTEND=gtk
debian-installer
if everything goes as expected the graphical installer should start
using DFB's unaccelerated video driver and you should be able to use the
"Stamp" key to take screenshots
Attilio Fiandrotti
[1] http://lists.debian.org/debian-boot/2005/12/msg00011.html
[2] http://www.directfb.org/docs/directfbrc.5.html
Reply to: