LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Blogs > mfduqued
User Name
Password

Notices

Rate this Entry

Problem with lilo.conf at Slackware 12.2

Posted 03-29-2009 at 04:21 PM by mfduqued

I try to make lilo.conf, as a table that it has two columns and one row, but lilo but lilo says:
Fatal: bmp-table: value out of range [2,11]
Why?, Can I can do this table?
My lilo.conf file is:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
lba32

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/handy_128.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 38,0,53,112,38,25
# 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 = 180p,315p,2,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 460p,335p,25,0,5

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# 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
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = Slackware
read-only
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda3
label = Windows
table = /dev/sda
# Windows bootable partition config ends
Posted in Uncategorized
Views 4385 Comments 2
« Prev     Main     Next »
Total Comments 2

Comments

  1. Old Comment

    I do not know what is wrong

    but did you try to allow for more colors? 256 colors may require special palette entries or something.
    Posted 03-31-2009 at 07:52 AM by AGer AGer is offline
  2. Old Comment
    If you have an External USB HD attached to the system during bootup, disconnect it. I was getting the same error, then by some fluke I rebooted with the device switched off. Problem went away.

    If anyone knows how to fix the issue so we can keep our External USB HD's connected during bootup and the Framebuffer won't freak out, that would be helpful. I hate having to remember to turn off my external before booting up.
    Posted 07-17-2009 at 01:37 PM by Fallhallen Fallhallen is offline
 

  



All times are GMT -5. The time now is 12:08 PM.

Main Menu
Advertisement

My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration