Re: Bug#341597: [ppc,d-i-gtk] installation report on b&w G3

[Attilio Fiandrotti <fiandro@tiscalinet.it>]

Sven Luther wrote:
> On Thu, Dec 01, 2005 at 04:59:59PM +0100, Wolfram Quester wrote:
>
> > Package: installation-reports
> >
> > Boot method: miniiso with graphical installer daily build from Sven Luther
> > Image version: http://people.debian.org/~luther/d-i/gtkdi/images/2005-12-01/powerpc/gtk-miniiso/mini.iso
> > Date: 2005-12-01 
> >
> > Machine: Apple PowerMac G3 (Blue&White)
> > Processor: G3, 400 MHz
> > Memory: 192 MB
> > Partitions: <df -Tl will do; the raw partition table is preferred>
> >
> >
> > Output of cat /proc/cpuinfo:
> > processor	: 0
> > cpu		: 740/750
> > temperature 	: 32-37 C (uncalibrated)
> > clock		: 400MHz
> > revision	: 2.2 (pvr 0008 0202)
> > bogomips	: 794.62
> > machine		: PowerMac1,1
> > motherboard	: PowerMac1,1 MacRISC Power Macintosh
> > detected as	: 66 (Blue&White G3)
> > pmac flags	: 00000000
> > L2 cache	: 1024K unified
> > memory		: 192MB
> > pmac-generation	: NewWorld
> >
> > Output of lspci
> > 0000:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
> > 0000:00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02)
> > 0000:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG
>
>
> Mmm, this is a rage 128, not sure if it will have enough memory, or if the
> corresponding fbdev is broken or something.
>
> Attilio, do you perhaps have some program linked with the .deb libraries, that
> the user could run to test under normal circunstances ? This would make
> debugging somewhat easier maybe.

this is what i got on directfb-dev from andi@fischlustig.de (thanks!) 
after forwarding wolfram's post

---------------------
I recommend to disable hw acceleration on ppc systems. At least for now.

It is best to pass

--with-gfxdrivers=none

to configure on ppc.

Judging from your cursor you are experiencing the "bi-endian system" 
problem. (ram: big-endian, vram: little-endian). This should not  result 
in a crash, but shows me that you are using a gfxdriver, which  in 
addidion may cause your segfault.
---------------------

i know HW acceleration can disabled at runtime bi adding "no-hardware" 
option to /etc/directfb (see 
http://www.directfb.org/docs/directfbrc.5.html).
Since this seems to be a DFB upstream bug, shouldn't better the 
discussion take place at directfb-dev@directfb.org? here we could get 
more specialistic help.
To make simple tests you could compile and run the "simple" app from 
http://www.directfb.org/downloads/Extras/DFBTutorials-0.5.0.tar.gz
.

ciao

attilio