Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just made a fresh install of slackware. I have the following partitions
/dev/sda1 ntfs windows xp
/dev/sda3 ext4 slackware
/dev/sda4 ntfs temp
After installing Slackware 13 i installed the LILO in expert mode the lilo.config file is like this
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
# 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
# Append any additional kernel parameters:
timeout = 50
# VESA framebuffer console @ 640x480x256
vga = 769
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
#Linux bootable partition
image = /boot/vmlinuz-huge-smp-188.8.131.52-smp
root = /dev/sda3
labl = Linux
#Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
label = win
# map-drive = 0x80
# to = 0x81
# map-drive = 0x81
# to = 0x80
table = /dev/sda
# Windows bootable partition config ends
But now i can boot only to windows no label for Linux...
Before that i had GRUB with ubuntu in the partition and in the MBR.
LILO is in the MBR. I formated the partitions with Gparted and i think they were formated in the slackware Setup (blue screens).
What happens now?? I am trying to configure lilo boot file from Ubuntu Live CD but nothing happens...
You are sure that your bootloader was written to the 'MBR'?
You can use the Slackware install cd1/dvd to boot the system.
After you get to the login then from the cli (command line);
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #the device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write to your boot device
You can 'man commands' in the above example to get a full understanding of the commands and options.
If you have any errors/major warnings for the 'lilo -v -t -b /dev/your_device' then you should correct these before writing the MBR. Some people forget the 'lba32' which is a minor warning which can be solved by including 'lba32' in the global section.
If everything is joy then just reboot. Post any errors or helpful information to aid us in diagnosinng the problem.
Warning: Ignoring entry 'boot'
Warning: LBA32 addresing assumed
Reading boot sector from /dev/sda3
Warning: Unable to determine video adapter in use in the present system
using BITMAP secondary loader
Mapping bitmap file /boot.slack.bmp
Warning: video adapter does not support VESA BIOS extensions needed for display of 256 colors.
Boot loader will fall back to TEXT only operation
This file, by default /etc/lilo.conf, is read by the boot loader in-
staller 'lilo' (see lilo(8)).
It might look as follows:
# global options:
menu-title=" John's Computer "
# bootable kernel images:
# other operating systems:
boot-as=0x80 # must be C:
boot-as=0x80 # must be C:
table=E: # os2 sees as E:
This configuration file specifies that lilo uses the Master Boot Record
on /dev/hda. (For a discussion of the various ways to use lilo, and the
interaction with other operating systems, see user.tex from the lilo
When booting, the boot loader will issue its boot: prompt and wait for
you to enter the label of the kernel (and any options) which you wish
to boot. At any time you may hit [Tab] to see a list of kernel/other
labels. Alternately, if the menu boot loader is installed, a menu of
boot options will be presented for your selection. The title of this
menu is overridden with the menu title specification in this configura-
tion file. If you enter nothing, then the default kernel image, the
first mentioned, (/boot/zImage-1.5.99) will be booted after a timeout
of 15 seconds (150 deciseconds). There may be at least 16 images men-
tioned in lilo.conf. (The exact number depends upon compilation
As can be seen above, a configuration file starts with a number of
global options (the top 9 lines in the example), followed by descrip-
tions of the options for the various images. An option in an image
description will override a global option.
Comment lines may appear anywhere, and begin with the "#" character....
Don't forget the use of ;
Uses the specified image as the default boot image. If `default'
is omitted, the image appearing first in the configuration file
is used. See also, vmdefault below.
I know what it does, I was just wondering if he installed lilo in simple mode, will it work then he can go back later and edit lilo.conf, I just didn'nt see where he has tried simple mode, maybe there is something about the setup we are not seeing that the simple mode will catch.
Last edited by colorpurple21859; 09-10-2009 at 11:40 AM.
Again nothing... If saw my first post everything is written as sda (/boot/sda1 etc/) But in the example we have hda. The curious is that windows boot just fine the problem is that in the boot loader theres no Linux. Should i try to install Lilo throught simple install ?? Also the slack is definetely ok because i can get to it if i boot from the DVD (also i put sda there).