LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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!

Notices


Reply
  Search this Thread
Old 09-09-2009, 07:10 PM   #1
sokis
LQ Newbie
 
Registered: Sep 2009
Location: Athens
Distribution: Slackware
Posts: 8

Rep: Reputation: 0
Cant Boot to Slackware after fresh Install


I just made a fresh install of slackware. I have the following partitions
/dev/sda1 ntfs windows xp
/dev/sda2 swap
/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

Code:
# 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:
append=" vt.default_utf8=0"
prompt
timeout = 50
# VESA framebuffer console @ 640x480x256
vga = 769
# 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
# ramdisk = 0     # paranoia setting
# End LILO global section
#Linux bootable partition
image = /boot/vmlinuz-huge-smp-2.6.29.6-smp
  root = /dev/sda3
  labl = Linux
  read-only
#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...

My laptop is ACER 5930 with AHCI.

Last edited by sokis; 09-09-2009 at 07:12 PM.
 
Old 09-09-2009, 07:24 PM   #2
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,601
Blog Entries: 25

Rep: Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981
Hi,

Welcome to LQ & Slackware!

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);

Code:
~#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.
 
Old 09-10-2009, 04:41 AM   #3
sokis
LQ Newbie
 
Registered: Sep 2009
Location: Athens
Distribution: Slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Thanks for the reply!

After i did the test i got the following

Code:
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
calling map_insert_data
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
calling map_insert_file
Also my graphic card is ATI 3470 HD

Last edited by sokis; 09-10-2009 at 04:43 AM.
 
Old 09-10-2009, 07:35 AM   #4
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,453
Blog Entries: 55

Rep: Reputation: Disabled
You missed the e out of label:
Code:
#Linux bootable partition
image = /boot/vmlinuz-huge-smp-2.6.29.6-smp
  root = /dev/sda3
  labl = Linux
  read-only
#Linux bootable partition config ends
 
Old 09-10-2009, 08:43 AM   #5
sokis
LQ Newbie
 
Registered: Sep 2009
Location: Athens
Distribution: Slackware
Posts: 8

Original Poster
Rep: Reputation: 0
I wrote label but again nothing happened. Did the test again and same result
 
Old 09-10-2009, 08:52 AM   #6
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,453
Blog Entries: 55

Rep: Reputation: Disabled
Did you run lilo after editing lilo.conf?
 
Old 09-10-2009, 09:49 AM   #7
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,601
Blog Entries: 25

Rep: Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981
Hi,

The OP is testing the '/etc/lilo.conf' with 'lilo -v -t -b /dev/sda'.

OP, try setting your vga line too 'vga=normal' and add the 'lba32' to your global section. You should be able to create the lilo now without errors.

You can then find out why your video is not recognizing the 'vga=769' (VESA framebuffer console @ 640x480x256).
 
Old 09-10-2009, 10:01 AM   #8
sokis
LQ Newbie
 
Registered: Sep 2009
Location: Athens
Distribution: Slackware
Posts: 8

Original Poster
Rep: Reputation: 0
I just write lba32 anywhere in the global section??
 
Old 09-10-2009, 10:07 AM   #9
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,453
Blog Entries: 55

Rep: Reputation: Disabled
I usually put it just before all the VESA framebuffer options.
 
Old 09-10-2009, 10:18 AM   #10
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,601
Blog Entries: 25

Rep: Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981
Hi,

You can 'man lilo.conf' to get the full Monty;

Quote:
sample '/etc/lilo.conf';

lilo.conf - configuration file for lilo

DESCRIPTION
This file, by default /etc/lilo.conf, is read by the boot loader in-
staller 'lilo' (see lilo(8)).

It might look as follows:

# lilo.conf
#
# global options:
boot=/dev/hda
prompt
timeout=150
lba32
compact
vga=normal
root=/dev/hda1
read-only
menu-title=" John's Computer "
#
# bootable kernel images:
image=/boot/zImage-1.5.99
label=try
image=/boot/zImage-1.0.9
label=1.0.9
image=/tamu/vmlinuz
label=tamu
initrd=initramdisk.img
root=/dev/hdb2
vga=ask
#
# other operating systems:
other=/dev/hda3
label=dos
boot-as=0x80 # must be C:
other=/dev/hdb1
label=Win98
boot-as=0x80 # must be C:
other=/dev/hdb5
label=os2
loader=os2_d
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
documentation.)

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
options.)

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 ;

Quote:
default=<name>
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.
Very useful.
 
Old 09-10-2009, 10:37 AM   #11
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,953

Rep: Reputation: 267Reputation: 267Reputation: 267
what happens if liloconfig is ran in simple mode from the install disk.
 
Old 09-10-2009, 11:10 AM   #12
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,601
Blog Entries: 25

Rep: Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981
Hi,
Quote:
Originally Posted by colorpurple21859 View Post
what happens if liloconfig is ran in simple mode from the install disk.
If you are referring to the 'simple' mode option then it will walk you through with minimal user input. 'Expert' allows a more detailed query and control.
 
Old 09-10-2009, 11:36 AM   #13
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,953

Rep: Reputation: 267Reputation: 267Reputation: 267
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.
 
Old 09-10-2009, 04:15 PM   #14
sokis
LQ Newbie
 
Registered: Sep 2009
Location: Athens
Distribution: Slackware
Posts: 8

Original Poster
Rep: Reputation: 0
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).
 
Old 09-10-2009, 04:38 PM   #15
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,953

Rep: Reputation: 267Reputation: 267Reputation: 267
try simple install if you haven't tried that option yet,
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
slackware 12 fresh install - udev causing lockup on boot l33t_c0w Slackware 13 10-24-2007 02:56 PM
Slackware freezes during boot up after fresh install Dachy Linux - Laptop and Netbook 1 08-23-2004 09:18 AM
Getting 2.6.7 with slackware on a fresh install equilibrium Slackware 6 07-13-2004 05:41 PM
Fresh Slackware 9.1 installation requires boot disk to boot smithtodda Slackware - Installation 7 06-23-2004 10:06 PM
Can't boot after fresh install of Slackware Darvocet Linux - General 2 02-22-2003 11:00 PM


All times are GMT -5. The time now is 01:57 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration