On Fri, Dec 02, 2005 at 08:55:17PM +0100, Sven Luther wrote:
> 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, 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.
>
# cat /proc/fb
0 ATY Rage128
snippet from dmesg:
aty128fb: Found Open Firmware ROM Image
aty128fb: BIOS not located, guessing timing
aty128fb: Rage128 RE PCI [chip rev 0x02] 16M 128-bit SDR SGRAM (1:1)
Console: switching to colour frame buffer device 128x48
fb0: ATY Rage128 frame buffer device on Rage128 RE PCI
To summarize:
I did not yet discover a possibility to make the gtkk frontend work with
video=ofonly
using the standard aty128fb, the gtk frontend works if hardware
acceleration is disabled. There remains an endianess problem while
setting the colour palette, but this is only a cosmetical (nevertheless
nasty) problem.
HTH,
Wolfi
Attachment:
signature.asc
Description: Digital signature