Re: Bug#341597: [ppc,d-i-gtk] installation report on b&w G3
On Fri, Dec 02, 2005 at 07:28:47PM +0100, Wolfram Quester wrote:
> Hi again!
>
> On Fri, Dec 02, 2005 at 06:44:04PM +0100, Sven Luther wrote:
> [...snip...]
> > > >
> > > > 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
> > >
> > > OK, I tried "video=radeonfb:800x600@60" but it looks like it is ignored.
> >
> > Well, obviously, as you have a rage128, not a radeon card, you would need
> > video=atyfb:800x600 or something such. But then, if you had to use ofonly, i
> > am not sure, but you could try video=ofonly:800x600@60, but as i said, i don't
> > think it will work.
> Nooo! I did not use video=ofonly! With video=ofonly I only get the crash
> reported at the beginning. Not the blue screen one, but the one where
> the graphical installer dies with sig 11, but leaving the sytem running.
> Changing any option did not change anything.
>
> video={aty,radeon}fb-parameters are ignored.
>
> So all the screenshots are created with "install DEBIAN_FRONTEND=newt"
> and then changing /etc/directfbrc.
Interesting. This will automatically load the fbdev driver which correspong to
your hardware. Can you go to console 2 and look at the dmesg output (pipe it
through more and look near the top of the file, 20 lines or so down i think),
to confirm which fbdev is used. We can then easily enough modify rootskel-gtk
to desactivate accel for it by adding the right line in /etc/directfbrc.
we can detect the fbdev driver by mapping the /proc/fb content, or somewhere
in /sys/class/graphics/fb0.
> > > > So, you will disable hardware acceleration in all cases ? What does it bring
> > > > you ?
> > >
> > > I think it doesn't hurt. The installer probably doesn't do anything
> > > where we gain much from hardware-acceleration and hardware-acceleration
> > > is more error prone.
> >
> > It should not, it will maybe show bugs, which needs to be fixed, but nothing
> > major should be different between accel and no accel.
>
> Yes, and since you don't get much you can work around all these bugs in
> a safe manner. Of course this doesn't change the neccessity to fix these
> bugs, but I think there are other bugs which should be tackled before.
Yep, best is to disable accel for now, but onlt for the fbdev drivers we know
have problems.
> > Ah, that would be helpful, thanks.
> Not today, perhaps over the weekend.
That would be soon enough :)
Friendly,
Sven Luther
Reply to: