DragonFlyBSD

On 16.04.2006, at 12:33, Thomas Schlesinger wrote:

The problem was already reported a year ago
(http://leaf.dragonflybsd.org/mailarchive/bugs/2004-04/msg00138.html),
but
obviously with no solution, so take this as a reminder ;-)

yes, it's broken, but nobody ever tried really hard to get it working
again. actually i don't consider it neeed in any way.

cheers
simon

Am Sonntag, 16. April 2006 15:55 schrieb Simon 'corecode' Schubert:

On 16.04.2006, at 12:33, Thomas Schlesinger wrote:

The problem was already reported a year ago
(http://leaf.dragonflybsd.org/mailarchive/bugs/2004-04/msg00138.html),
but
obviously with no solution, so take this as a reminder ;-)

yes, it's broken, but nobody ever tried really hard to get it working
again. actually i don't consider it neeed in any way.

cheers
simon

Sure, it's not really needed, but nevertheless it's at least for me a
nice-to-have ;-)

Thomas

On 16.04.2006, at 16:26, Thomas Schlesinger wrote:

The problem was already reported a year ago
(http://leaf.dragonflybsd.org/mailarchive/bugs/2004-04/
msg00138.html),
but
obviously with no solution, so take this as a reminder ;-)

yes, it's broken, but nobody ever tried really hard to get it working
again. actually i don't consider it neeed in any way.

Sure, it's not really needed, but nevertheless it's at least for me a
nice-to-have ;-)

happy bug hunting then (maybe the bug is colored and shaped like an
egg?)

if you go this route, you can be sure to learn a lot about boot and
internals of the dragonfly kernel :)

cheers
simon

Alternatively, you might consider using Lilo or Grub, both of which
support boot graphics. I use Lilo and posted a thread on the topic
here: http://www.linuxquestions.org/questions/showthread.php?t=418094

Simon 'corecode' Schubert wrote:

On 16.04.2006, at 16:26, Thomas Schlesinger wrote:

The problem was already reported a year ago
(http://leaf.dragonflybsd.org/mailarchive/bugs/2004-04/ msg00138.html),
but
obviously with no solution, so take this as a reminder ;-)

yes, it's broken, but nobody ever tried really hard to get it working
again. actually i don't consider it neeed in any way.

Sure, it's not really needed, but nevertheless it's at least for me a
nice-to-have ;-)

happy bug hunting then (maybe the bug is colored and shaped like an egg?)

if you go this route, you can be sure to learn a lot about boot and
internals of the dragonfly kernel :)

cheers
simon

Am Sonntag, 23. April 2006 12:18 schrieb user@domain.invalid:

Alternatively, you might consider using Lilo or Grub, both of which
support boot graphics. I use Lilo and posted a thread on the topic
here: http://www.linuxquestions.org/questions/showthread.php?t=418094

I use grub since a long time and the also grub's ability to show a bootsplash
(splashimage= in grub.conf). The bootsplash disappears after starting the
boot process of an OS, so I wouldn't get a bootsplash while loading
DragonFly.

Nevertheless is it a good idea to install grub to get rid of the boring
Dragonfly bootloader ;-)

It appears to me, that DragonFly switches for a split of a second into
graphic mode (a ultra-short flickering on the screen), but then switches back
to text output.

Thomas

Thomas Schlesinger wrote:

It appears to me, that DragonFly switches for a split of a second into
graphic mode (a ultra-short flickering on the screen), but then switches back
to text output.

No, the flickering is probably due to VESA initialization or the VGA
adapter loading a font.

I think the problem with the splash is that the decoders for the splash
image (splash_{bmp,pcx}.ko) are not yet initialized when the splash is
supposed to open. The splash is supposed to open when scinit() is called
the first time from init386() (machdep.c) via cninit(). The
splash_init() call in scinit() (syscons.c) then fails because the
splash_{bmp,pcx}.ko hasn't been initialized yet.

Someone (I think it was Emiel Kollof) told me that the splash stopped
working when the loader from FreeBSD 5 was imported.

I've looked into this several times and always ended up being frustrated.

Sascha