Bug #145

Bootsplash doesn't work

Added by schlesinger over 8 years ago. Updated 10 months ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi,

I've tried to enable a bootsplash with 1.5.2 and 1.5.3, following
http://leaf.dragonflybsd.org/cgi/web-man?command=splash&section=4, but it
didn't work.

This is an excerpt of my /boot/defaults/loader.conf:

[..]
splash_bmp_load="YES"
splash_pcx_load="NO"
vesa_load="YES"
bitmap_load="YES"
bitmap_name="splash.bmp"
bitmap_type="splash_image_data"
[..]
module_path="/;/boot;/modules"
[..]

The bootsplash bitmap is in place, too:

-rw-r--r--  1 root  wheel  481078 Apr 14 16:07 /boot/splash.bmp

 When I boot, I didn't get a bootsplash. I get, as expected, the selection
menu for DFly's boot options (e. g. with acpi, without acpi, ...) and after
selecting one, I get the usual boot messages on screen. The necessary modules
are loaded at boot time:

Id Refs Address    Size     Name
 1    8 0xc0100000 400a08   kernel
 2    1 0xc0501000 3068     splash_bmp.ko
 3    1 0xc0505000 55b8     vesa.ko
 4    1 0xc0580000 5ed0     snd_ich.ko
 5    2 0xc0586000 1d884    snd_pcm.ko
 6    1 0xc05a4000 c2c8     if_iwi.ko
 7    1 0xc05b1000 59064    acpi.ko

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 ;-)

Thomas

History

#1 Updated by corecode over 8 years ago

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

#2 Updated by schlesinger over 8 years ago

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

#3 Updated by corecode over 8 years ago

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

#4 Updated by user over 8 years ago

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
>

#5 Updated by schlesinger over 8 years ago

Am Sonntag, 23. April 2006 12:18 schrieb :
> 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

#6 Updated by swildner over 8 years ago

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

#7 Updated by robgar 10 months ago

  • Description updated (diff)
  • Status changed from New to Closed
  • Assignee deleted (0)

Also available in: Atom PDF