Mailinglist Archive: opensuse-factory (507 mails)

[Greg KH <gregkh@xxxxxxx>]

On Thu, Jul 30, 2009 at 09:39:20AM +0200, Stephan Kulow wrote:
> Am Mittwoch 24 Juni 2009 schrieb Holger Macht:
> > On Sat, 2009-06-13 at 19:12 +0200, Stephan Kulow wrote:
> > > On Saturday 13 June 2009 09:40:16 Rastislav Krupanský wrote:
> > > > > Someone needs to do a test with both available solutions and then we
> > > > > need to judge.
> > > >
> > > > Can users/volunteers do it? What is needed to test and how?
> > >
> > > As I'm not aware of anyone working on it, I'm not aware of anything to
> > > test - other than testing how to replace bootsplash with splashy and/or
> > > plymouth.
> >
> > Johannes Engel (CC) already did some initial work and tests with splashy
> > in regard to regular booting. I remember him having problems with
> > parallel booting because the bootsplash interaction is hard coded in
> > /sbin/startpar. Attaching his /etc/rc.splash which worked (at that time)
> > with RUN_PARALLEL=no for reference if someone wants to pick up his work.
> OK, I looked into this yesterday and there are some problems:
>
> - plymouth is out as it requires DRM and while fedora has tons of drm patches
>   in their kernel I don't see us going there - perhaps 11.3 if everything
>   needed settled in Xorg and kernel.
> - bootsplash works, but is limiting the artists and is only used for booting,
>   not for suspend. And it has no support for e.g. error boxes and password
>   queries
> - splashy is from what my experiments easy to fix, it has support for not
>   so useful effects (you can emulate them in bootsplash using mng anims,
>   but you need a tool to create these), displaying errors in truetype fonts
>   and getting password queries. suspend & resume already use it, so we have
>   some experience with it - and a package ready.
>
> The problems I faced with splashy are: it flickers one more often than 
> bootsplash as the kernel will setup the framebuffer and detect hardware
> and _then_ splashy comes up to paint  over it. With bootsplash the kernel
> will display an initial graphic and _then_ the userspace will take over
> showing a progress bar. And I didn't yet experiment to see how we can
> go from initrd to booting, but that should be possible - splashy has
> chroot support.
>
> Now I wonder if we can leave the bootsplash kernel patch in and use it only
> to display the initial graphic. My experiments were with a vanilla kernel.
> Oppinions? Volunteers? :)

If that's all you want, they why not use what we are doing in the Moblin
images, which is no kernel patch, and just the framebuffer in userspace?
Much simpler and faster, and no kernel changes needed.

thanks,

greg k-h
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx