SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I was using Slackware 12.2 for quite a long time, dualbooting with XP (where slack and XP were on separate harddisks sda and sdb) using the following lilo.conf
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
# Append any additional kernel parameters:
boot = /dev/sda
map = /boot/map
#message = /boot/message
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
# bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
# 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
# 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):
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 50
# Override dangerous defaults that rewrite the partition table:
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# VESA framebuffer console @ 1024x768x32k
# VESA framebuffer console @ 1024x768x256
# VESA framebuffer console @ 800x600x64k
# VESA framebuffer console @ 800x600x32k
# VESA framebuffer console @ 800x600x256
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = "Linux"
# Linux bootable partition config ends
other = /dev/sdb1
label = "Windows"
table = /dev/sdb
It worked perfectly as both XP and slack were separated from each other, making it easier to manage the XP. But after I replaced Slackware 12.2 on sda with 13.0 I can't use this dualboot configuration. If I select XP in the boot menu there is a message "loading windows" but then it stops. Why the lilo.conf from 12.2 doesn't work for dualboot in 13.0 ??? Were there any significant chnages in LILo which may cause this problem ?
Note again that XP and Slackware are on two separate HDs and the map-drive commands are used to fool XP so that it thinks it's the master (all worked fine with 12.2)
Also note that XP is not corrupted because when I change my BIOS settings so that XP boots first, it works fine.
The problem is solved now. I'd had to disconnect SATA cable of my XP HD before the whole thing was reinstalled (disabling HD in BIOS is not enough)
So I installed LILO with only linux disk connected, then connected XP disk again and updated lilo.conf so that it looked like in my first post and it works fine.
I have to say that although slackware setup program is certainly great and flexible, the installation of LILO is the weakest part of it in my opinion. Sometimes the installation fails without any error message box (this occasionaly happens in both simple and expert mode) and then it's hard find out what happened.
Anyway, I'm looking forward to using Slackware 13.0,
thanks to all.