LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   It takes about 7 sec for lilo menu to appear after bios check.. (http://www.linuxquestions.org/questions/slackware-14/it-takes-about-7-sec-for-lilo-menu-to-appear-after-bios-check-4175459457/)

Kristian2 04-24-2013 12:29 PM

It takes about 7 sec for lilo menu to appear after bios check..
 
I find this unusually long, and in the past it didn't take that long. When I used older version of Slack/Lilo (and on older hardware as well) the lilo menu appeared quite fast after the bios check, now the prompt blinks around 7 sec.
Is there any reason (hardware issue) for this delay?

Thanks.

Bazzaah 04-24-2013 12:33 PM

you need to add

compact

at the top of your lilo.conf, like this

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
compact
lba32

Then run the command 'lilo' (without inverted commas) as root.

Kristian2 04-24-2013 12:46 PM

Is that the problem, thanks. I've never noticed that.

Kristian2 04-25-2013 05:07 AM

After adding (and rerunning lilo).. it makes no difference. My hardware is nothing outdated and better than years before, nor is lilo any more complicated with just two boot sections. Perhaps lilo is doing a check or waiting on something I am not aware of.

mrclisdue 04-25-2013 05:10 AM

Can you post your lilo.conf, please? It may reveal nothing, but it's a start....

cheers,

guanx 04-25-2013 07:04 AM

Quote:

Originally Posted by Kristian2 (Post 4938101)
I find this unusually long, and in the past it didn't take that long. When I used older version of Slack/Lilo (and on older hardware as well) the lilo menu appeared quite fast after the bios check, now the prompt blinks around 7 sec.
Is there any reason (hardware issue) for this delay?

Thanks.

I got the same problem (forgot how many seconds, but longer than I could stand) four years ago with a relatively recent notebook computer. Had to use syslinux as the boot loader instead of lilo to "solve" the problem.

Possibly this is some hardware compatibility issue. Just my guess.

kikinovak 04-25-2013 08:34 AM

KISS approach: take a sip of coffee (ETA 7.00 seconds).

Kristian2 04-25-2013 10:32 AM

Here's my lilo.conf

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
#append=" vt.default_utf8=0"
boot = /dev/sda
compact
lba32

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255


prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
vga=791
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
  label = Windows
  table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda9
  label = Linux
  read-only
# Linux bootable partition config ends


Feanor 04-25-2013 02:22 PM

I suddenly started experiencing this behaviour on my old P4 slack 12.2 installation at a similar time to date/time resets in my BIOS. Most likely due to motherboard battery dying. Might be related, might not.


All times are GMT -5. The time now is 08:19 AM.