Boot Splash.

cwizardone · 06-18-2016, 10:21 PM

In another thread I mentioned how I found the sign-on/splash screen used by Alien BOB for Slackware Live to be quite attractive. The largest font on the screen is, of course, "Slackware Linux," but what I really liked was what it says in the bottom right-hand corner, "When you get serious."
I tried converting it to a bitmap file and using it with -current, but it didn't work.
So, after searching around I found one I like even better and thought of "sharing" it with other Slackware64 users.
Since it is a bitmap file it won't attach, so here you go, a Slackware64 lilo boot splash screen,

http://kde-look.org/content/show.php...content=124827

Of course, to use this you need to copy it to your /boot directory, edit your lilo.conf file accordingly and re-run lilo.
Enjoy.

chrisretusn · 06-18-2016, 11:17 PM

Hey that is nice.

Ztcoracat · 06-18-2016, 11:27 PM

That's a much nicer splash screen thanks cwizardone.-

Like this guys?

Quote:

bitmap = /boot/124827-slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255

cwizardone · 06-19-2016, 12:42 AM

Quote:

Originally Posted by Ztcoracat

That's a much nicer splash screen thanks cwizardone.-

Like this guys?

I just looked at my lilo.conf and your second, third and fourth lines are already there, you just need to change the name of the image.

Qury · 06-19-2016, 06:44 AM

Now the only thing I miss is a working howto on how to implement plymouth or some other bootsplash to hide the kernel messages.
(there are a few desktop users in the wider family who do not care about those messages)

Alien Bob · 06-19-2016, 07:41 AM

OK cwizardone, I could not leave that unanswered...
I wrote a script that takes any image as input and writes a LILO bitmap file: http://www.slackware.com/~alien/tools/img2lilobmp.sh

After conversion, the script outputs the color palette of the generated image file, because it's the indices in this color palette that are used in the 'bmp-colors' and 'bmp-timer' entries of lilo.conf:

Code:

-- Converting 'liveslak/syslinux/swlogov.png' to './swlogov.bmp'
-- LILO's 'bmp-colors' and 'bmp-timer' need to use these palette indices:
         0: (  0,  0,  0) #000000 black
         1: ( 20, 24, 43) #14182B rgb(20,24,43)
         2: ( 27, 34, 59) #1B223B rgb(27,34,59)
         3: ( 31, 38, 67) #1F2643 rgb(31,38,67)
         4: ( 37, 46, 81) #252E51 rgb(37,46,81)
         5: ( 48, 58,103) #303A67 rgb(48,58,103)
         6: ( 55, 68,119) #374477 rgb(55,68,119)
         7: ( 61, 75,131) #3D4B83 rgb(61,75,131)
         8: ( 69, 85,149) #455595 rgb(69,85,149)
         9: ( 75, 93,164) #4B5DA4 rgb(75,93,164)
        10: ( 85,104,184) #5568B8 rgb(85,104,184)
        11: (  0,  0,  0) #000000 black
        12: (  0,  0,  0) #000000 black
        13: (  0,  0,  0) #000000 black
        14: (  0,  0,  0) #000000 black
        15: (  0,  0,  0) #000000 black

The following can be used together with the "When you get serious" bitmap, using only palette incices '0' (black) and '2' (dark purple). Using one of the palette indices 3 to 10 instead of 2 would give you a somewhat lighter color for the menu and the timer:

Code:

  bitmap = /boot/swlogov.bmp
  bmp-colors = 2,0,2,0,2,0
  bmp-table = 60,13,1,16
  bmp-timer = 65,27,0,2

elcore · 06-19-2016, 07:52 AM

Quote:

Originally Posted by Qury

Now the only thing I miss is a working howto on how to implement plymouth or some other bootsplash to hide the kernel messages.
(there are a few desktop users in the wider family who do not care about those messages)

What's the point having plymouth when booting into xdm takes 4 seconds, it will only extend boot time, plus it only makes sense with framebuffer enabled.
You can pass "quiet" to kernel command line to reduce messages if you don't want them, no?

cwizardone · 06-19-2016, 09:37 AM

Quote:

Originally Posted by Alien Bob

OK cwizardone, I could not leave that unanswered...
I wrote a script that takes any image as input and writes a LILO bitmap file......

Many Thanks. Once again your work is, "...above and beyond the call..."

Tonus · 06-19-2016, 04:14 PM

I always wonder what can be the specs of a machine booting in less than 10s...

Or I am really missing something.

montagdude · 06-19-2016, 04:55 PM

Quote:

Originally Posted by Tonus

I always wonder what can be the specs of a machine booting in less than 10s...

Or I am really missing something.

From reports I've read, an SSD + that which shall not be named will boot in ~5 seconds. Not that boot time really matters to me, as long as I can be using my computer to its full capacity within a couple minutes of powering on.

notKlaatu · 06-19-2016, 05:03 PM

With SSD, honestly, ANYTHING boots in about 5 seconds. I run Slack on SSD and there basically is no boot time.

montagdude · 06-19-2016, 05:06 PM

Quote:

Originally Posted by notKlaatu

With SSD, honestly, ANYTHING boots in about 5 seconds. I run Slack on SSD and there basically is no boot time.

I figured as much. It's just that the boot time war discussions I've seen have usually been by people on distros that use systemd (woops, I just named it).

kjhambrick · 06-19-2016, 07:19 PM

Hmmm ...

That whole boot-time discussion loses meaning when one factors in the POST time.

I am running SSDs and for sure, Linux boots PDQ.

OTOH I spend a relatively long time waiting for POST to hand over control to lilo.

Once lilo starts the actual boot, I am up in a few seconds.

Maybe if I was to go EFI boot, it might go faster but I imagine the POST time will still be the larger part of boot time.

-- kjh

drgibbon · 06-20-2016, 12:03 AM

My favourite Slackware background/splash is the one that comes with this SLiM theme (preview here). Nothing too fancy, just the Linux penguin with Dobbs pipe and "Slackware Linux" underneath. The image in the source archive doesn't have the login box, should be ok for LILO.

elcore · 06-20-2016, 12:07 AM

Quote:

Originally Posted by Tonus

I always wonder what can be the specs of a machine booting in less than 10s...

Or I am really missing something.

Well, my desktop is old BIOS machine with 14.1, static ethernet, dual core phenom with 4G DDR2@1600 and GT440. Got an SSD specially for root ext2fs however.
It's usable in 4 sec from grub > xdm. I guess it takes about 8-10 sec from cold boot into fluxbox.
From my experience, reading initrd & modules from regular HDD will cause a slight delay, but it all depends on the drive cache and sometimes network if nfs/ntp/dhcp is used.
And I'm sorry for derailing the thread. More artwork is always a good thing, except when it's plymouth, thing doesn't mix well with nvidia module and needs framebuffer to briefly display an image for couple of seconds before xdm displays another image.