LinuxQuestions.org - Slackware 10, custom 2.6.7 kernel, lilo, loads kernel very slowly

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware 10, custom 2.6.7 kernel, lilo, loads kernel very slowly (https://www.linuxquestions.org/questions/slackware-14/slackware-10-custom-2-6-7-kernel-lilo-loads-kernel-very-slowly-219883/)

Slackware 10, custom 2.6.7 kernel, lilo, loads kernel very slowly

Very Newb, doing my best not to ask questions that have already been asked, but I haven't found anything about this yet...

I'm running a 2.6.7 kernel(from kernel.org) I compiled on Slackware 10 (full install). When I select what-to-boot from lilo, slackware's kernel(bzImage) seems to load extremely slowly (5 sec or so) when compared with some other distros I have tried (Mandrake & Redhat(not custom)... about a second, max).

The part that's slow is right after lilo goes away, and its saying "Loading Slackware............................................" (during the periods part).

I'm assuming that's when its loading the kernel into memory. ...it happens with either the kernel I compiled OR the 2.4.26 bare.i. I'm guessing that means its not the kernel, but rather lilo. I've checked lilo.conf and lilo docs for some indication of what would be causing it, but I've found no evidence anyone else has even experienced a similar issue. maybe I'm just not searching with the right words? in any case, I would appreciate any advise or assistance anyone can offer. (other than this little setback, it flies)

The short answer is you might try adding "compact" to your lilo.conf. Then run lilo as root to set it up.

http://www.linuxquestions.org/questi...t=lilo+compact

EDIT: Would not have found it either if I had not already known what to look for.

here is my lilo.conf as an example

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/hda

message = /boot/boot_message.txt

prompt

timeout = 120

compact

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# Normal VGA console

vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# End LILO global section

# Windows bootable partition config begins

other = /dev/hda1

  label = Windows

  table = /dev/hda

# Windows bootable partition config ends

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/hda3

  label = Linux

  read-only

# Linux bootable partition config ends

image = /boot/vmlinuz.old

  root = /dev/hda3

  label = LinuxOld 

  read-only

OH SUPERFLY!!!!! success, thanks!

<code>
boot = /dev/hda
compact # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga=773

install=/boot/boot-bmp.b # means you will use grafical version
bitmap=/boot/handy_128.bmp # background path
bmp-colors=38,0,53,112,38,25 # text color
bmp-table=114p,347p,2,7 # label position on the screen p=pixel
bmp-timer=470p,336p,25,0,11 # timer position on the screen p=pixel

image=/boot/bzImage
root = /dev/hda6
label = Slackware
read-only

#image = /boot/vmlinuz
# root = /dev/hda6
# label = Slack_2.4.26
# read-only # Non-UMSDOS filesystems should be mounted read-only for checking

other = /dev/hda1
label = Win2k
table = /dev/hda
</code>

btw, if you're curious, my lilo img: http://www.kde-look.org/content/show.php?content=11098

Quote:

Originally posted by entropyv

btw, if you're curious, my lilo img: http://www.kde-look.org/content/show.php?content=11098

Very cool!! That actually tempts me to change from my staunch "graphics are for wussies" lilo.