Re: Bug#341597: [ppc,d-i-gtk] installation report on b&w G3
On Fri, Dec 02, 2005 at 03:14:40PM +0100, Attilio Fiandrotti wrote:
> Wolfram Quester wrote:
> >Hi alltogether,
> >
> >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
> >>>>>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.
> >>>
> >>>
> >>>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
> >>export DEBIAN_FRONTEND=gtk
> >>debian-installer
> >>
> >>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.
>
> Super-cool! :)
> It seems here you're still running into bug
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338191
> and that the initial vesa mode was set to 1024x768 instead of 800x600.
Mmm, he does see the logo endianness problem, but not the cursor problem, is
that right Wolfram ?
> -PowerPC specific: the kernel must get passed "video=ofonly vga=788"
> (wolfram, could you please test with this additional kernel parameter too?)
Well, this is only needed for powermacs who have no radeon graphics, which
would include all oldworld and maybe nvidia based pmacs. The vga= parameter
has no chance of working at all on anything but x86. to pass size paramters,
you specify it with something like :
video=radeonfb:1024x768@60
Not sure if ofonly allows this, i believe it cannot switch modes, and you are
saddled with the mode which was set up withing the firmware, but it is
possible to change it from the firmware probably, i am no expert here.
I would thus recomend the following. Somewhere in rootskel-gtk, before the
directfb and stuff is called, do :
1) check if we are on powerpc.
2) if so, check wether the graphic card needs extra handling. This should be
ok for radeonfb, but may cause problems with other graphic cards.
3) In the rage128 case, we write noaccel to /etc/directfbrc.
4) parse /etc/cmdline, for a noaccel option, or use the normal preseed
mechanism, and have a a couple of cdebconf values to seed /etc/directfbrc.
> -Achitecture indipendent: The following lines should be added to
> /etc/directfb for compability sake and to allow to taking screenshots
>
> no-hardware
So, you will disable hardware acceleration in all cases ? What does it bring
you ?
> screenshot-dir=/
>
> 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
> /etc/directfbrc options?
See above for a detail about the kernel parameters, i have no time to test the
options though.
> 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).
Indeed.
Friendly,
Sven Luther
Reply to: