[Splashy-users] splashy and Graphics Card's native fb driver

[Kushal Koolwal]

>On Mon, 2006-08-14 at 16:51 -0700, Kushal Koolwal wrote:
> > Mind you this only works if I boot pass the parameter for my fbdriver
> > as video=gxfb:640x480-24 at 60 i.e. the boot splash will show if I boot
> > my fb
> > driver with 640X480 resoluton. If I boot with
> > video=gxfb:1024x768-24 at 60 it
> > does not even starts.
> >
>
>It seems that this driver is not well supported by directfb, the main
>framebuffer library that splashy uses.

I always thought that the newer vesion of splashy (for sarge) does not use 
libdirecfb package any more. Even when I installed the splashy version 
splashy_0.1.8-0sarge40_i386.deb it did not asked for any other package 
dependencies and it intalled smoothly. Am I missing something here?
>
> > According to the splashy wiki
> > http://splashy.alioth.debian.org/wiki/doku.php?id=faq It seems I can
> > make
> > splashy program to use my own Graphics Card's framebuffer driver. But
> > it my
> > case I am not able to do it as explained above.
>
>Yep it's true. But the problem seems to be at lower level: the library
>has problem dealing with your framebuffer driver IMHO
> >
> > Also, if I boot my kernel with vga=791 everything works fine, but then
> > this
> > kernel does not my Graphics Card's fb driver which I really want to
> > use.
>
>You said that vesa didn't work. Is it working now? Did you use a custom
>kernel before?
Yeah the Vesa works fine with splashy, but my Graphics Cards is having some 
problem with the Vesa Frame buffer driver (like switching from X to console 
mode, the screen goes blank) and therefore I am using the native Graphics 
Card's Fb driver(gxfb).

Update: I just used the older splashy version splashy_0.1.5.svn28_i386.deb 
and it asked for libdirectfb package and I installed it and it is working 
fine with my fb driver. But I would like to use the newer version of splashy 
since it has many new features and less bugs.

Thanks for looking into this.

Kushal