-----Original Message-----
> > On Wed, 29 Oct 2003, Buchan Milne wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Andrey Borzenkov wrote: > > > Apparently this progress bar is displayed not by kernel but by some > > external program? > > > > No, it seems just to work by placing "show $num" in /proc/splash where > > $num is a 16bit integer (see /sbin/splash.sh and the rc_splash function > > in /etc/rc.d/). > > sorry, but I can't have /proc/splash on a kernel without bootsplash patch. Still I have progress bar. Oh never mind, that's definitely not the first priority thing. just realized it could well be LILO progress bar as it appears before kernel output. Does it have one? In this case it smells like a bug. > > > On 2.4.23-pre8 it is too short while on 2.6 it extends over the right > > side - apparently > > > it depends on relative kernel version number :) > > > > Does framebuffer work on 2.6? yes. As has been mentioned on lkml many times - you can't compile several FB drivers in your kernel. Select one and it will work. It has always been working here since I started using 2.5. I guess I am useing vesa framebuffer driver, have to check @home. For other drivers YMMV as usual. Sure it is PITA for distributions kernels. I hoped new roofs/initramfs would allow dynamic loading of framebuffer drivers during boot but apparently it is initialized too late. I vaguelly remember someone mentioned on lkml possibility to load fb driver after system boots - i.e. out of initrd but I never had time to recompile kernel just to test it. Besides it is a bit too late, you still have some time window with plain text output. -andrey
