Re: Bug#341597: [ppc,d-i-gtk] installation report on b&w G3
Wolfram Quester wrote:
On Fri, Dec 02, 2005 at 10:18:40AM +0100, Attilio Fiandrotti wrote:
Sven Luther wrote:
On Thu, Dec 01, 2005 at 09:46:50PM +0100, Attilio Fiandrotti wrote:
Mmm, this is a rage 128, not sure if it will have enough memory, or if
corresponding fbdev is broken or something.
Attilio, do you perhaps have some program linked with the .deb
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 firstname.lastname@example.org (thanks!)
after forwarding wolfram's post
I recommend to disable hw acceleration on ppc systems. At least for now.
Oh well, we should fix it instead, whatever it is :)
Wolfram, could you please try again to boot with newt fontend and, after
switching to VT2, do
echo 'debug' >>/etc/directfbrc
echo 'no-hardware' >/etc/directfbrc
echo 'screenshot-dir=/' >>/etc/directfbrc
this should let us know if the bug goes away if hw aceleration is
disabled, and you can also take screenshots by pressing "stamp" key.
I booted "install DEBIAN_FRONTEND=newt" and did as recommended above.
And it worked! Well, there seems to be an endianess bug in the coloring,
which you can see in the attached screenshot. I did not try to finish
the installation today, perhaps I'll try next week.
It seems here you're still running into bug
and that the initial vesa mode was set to 1024x768 instead of 800x600.
So far, we ve stated that
-PowerPC specific: the kernel must get passed "video=ofonly vga=788"
(wolfram, could you please test with this additional kernel parameter too?)
-Achitecture indipendent: The following lines should be added to
/etc/directfb for compability sake and to allow to taking screenshots
If some other PPC user has time for some testing, could he confirm the
g-i still works on their computers using new kernel parameters and
I would also know from DFB experts if there is a /etc/directfb option
that prevents multibyte-colour PNGs from being trashes as seen in
Wolfram's screenshot (this seems to be an endianess-related issue).