LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 01-07-2006, 02:44 PM   #1
sr_25
Member
 
Registered: Nov 2005
Location: Colorado
Posts: 122

Rep: Reputation: 15
Boot loader help.


Okay, first off I consider myself a complete Linux newbie, so any help is appreciated.
I used to use ntldr to boot my various Os'es but have been unable to get it working for my current configuration.

I currently have a Primary fat 16 partition. and 1 large extended partition. I have both Win2k and WinXP and they reside on /dev/hda5, /dev/hda6 respectively. I also have Arch linux on /dev/hda9 and Slack on /dev/hda10.

Now, if I use a boot disk created from Slack I can boot into it no problem. To boot into Arch Linux I use SBootMgr(I should point out that the only OS I can't boot this way is Slack). Windows boots no problem from the hard drive using Ntldr.

I have finally decided to try Lilo, or Grub again, but when I run Control Center Boot Manager(Lilo) in Slack it says:

configuration is NOT ok. LILO said:
LILO version 22.5.9 (test mode), ...
Development beyond...
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.
Reading boot sector from /dev/hda
Using MENU secondary loader
Calling Map_insert_data
Boot image: /boot/vmlinuz
Added vmlinuz*
Boot image: /boot/vmlinux-ide-2.4.31
Added 2.4.31
Skipping /usr/src/linux/arch/i386/boot/bzImage
Boot other:/dev/hda1, on /dev/hda, loader CHAIN
Added NT
Boot other:/dev/hda5, loader CHAIN
Pseudo partition start: 449883
Fatal: Duplicate label "NT"

So I really have no idea what is wrong with this config. could you Guru's help me out? Sorry, if I included to much or the wrong information!

P.S.
Also, I really wanted to try Grub but am not clear on how to install it either.

Last edited by sr_25; 01-07-2006 at 02:45 PM.
 
Old 01-07-2006, 02:52 PM   #2
Akabaka
LQ Newbie
 
Registered: Oct 2005
Location: United States
Distribution: Ubuntu
Posts: 17

Rep: Reputation: 0
Attach your "/etc/lilo.conf" please.
 
Old 01-07-2006, 02:53 PM   #3
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
I'd choose 1 and stick with it until you understand how it works, then if you later decide it doesn't give you everything you want, try the other.

Since Lilo is default on Slack (and easier for me to use ) I'll try to help with that one.

You should post up what your /etc/lilo.conf looks like so we can give exact points of reference.

But generally speaking, if you open your /etc/lilo.conf file (while booted into Slackware) you will probably see 2 entries that say:
other = /dev/hda5
label = NT
table = /dev/hda

And
other = /dev/hda6
label = NT
table = /dev/hda

The other and table line are just for completeness, your install might say something slightly different, but that should be close. Basically, it's the "label' line that needs SOMETHING altered. I'd probably change both, one to say "Win2k" and the other to say "WinXP" so you know what's what. After the changes, re-run lilo to see what new error pops out, and post it up along with your lilo.conf

Cool
 
Old 01-07-2006, 03:16 PM   #4
sr_25
Member
 
Registered: Nov 2005
Location: Colorado
Posts: 122

Original Poster
Rep: Reputation: 15
Some more background, I installed my boot loader to the root partition of my Arch install(At the time I was thinking of still using ntldr). So do I need to remove it?

Okay, under Slack I don't have a lilo.conf!

I just booted Arch, (once again I think this is actually installed at hda9) using nano this is what I have:
#
# /etc/lilo.conf
#

boot=/dev/hda
#This line ofter fixes L40 ERRORS...
# disk=/dev/hda bios=0x80

default=arch
timeout=50
lba32
prompt

image=/boot/vmlinuz26
label=arch
root=/dev/hda9
read-only

#other=/dev/hda1
# label=dos
 
Old 01-07-2006, 03:25 PM   #5
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
Ok, that's probably a good place to start then. It's pretty basic, so let's go with it.

Let me give you some general info, and then try to use it in an example:

Whatever partition /boot is on is important. If it's on the same partition as everything else 'arch' (/dev/hda9) that's fine, just remember that when you compile and copy new kernels to your 'boot' directory. For multiple distro booting I tend to desire a seperate partition JUST for kernels (/boot). This way, when I boot any distro I can just mount /boot seperately and have every kernel there just as it would be an any other distro I boot.

Regardless, you need ALL kernels in a single directory (there are ways around this, but take this at face value for now). So, copy your slackware kernel to your arch's /boot directory. Once this is done, you'll need boot entries for these kernels. For ease of explaination I'll just call your kernels by your distro's name, you can name then WHATEVER you want, even pedro-1 and pedro-2 if that seems appropriate.

So, now we have these kernels in /boot in arch:
ls -lh /boot:
slackware-kernel
arch-kernel

And we might also have initrd's:
slackware-initrd
arch-initrd
These ARE NOT necessary, and if they aren't there, no sweat, just move on.

Now, edit /etc/lilo.conf within ARCH to have some entries that look similar to this (append to the existing LILO so you don't have to make any changes, just additions):
Code:
image = /boot/slackware-kernel
initrd = /boot/slackware-initrd #remember this doesn't have to exist, leave it out if it doesn't
root = /dev/hda7
read-only

other = /dev/hda5
label = WinXP
table = /dev/hda

other = /dev/hda6
label = Win2k
table = /dev/hda
This is just generic info, tailor the /dev's to your situation.

HTH

Cool
 
Old 01-07-2006, 10:02 PM   #6
sr_25
Member
 
Registered: Nov 2005
Location: Colorado
Posts: 122

Original Poster
Rep: Reputation: 15
Thank you so much for taking the time to explain this to me. I am sure for you Guru's this does get rather monotonous.
The next time I reformat I'll try using a seperate partition for kernels that makes good sense. I got it up and running and figured I might as well try grub, just for fun. I think I prefer grub it only took me about 10 minutes and everything is bootable!

I can't say how much I appreciate your help.

Jon B.
 
  


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
wireless Keyboard not working to select boot options (Grub boot loader) psrini_vasan Fedora 7 12-16-2009 06:45 PM
To load/boot Red Hat Enterprise Linux 4 WS from Microsoft's Boot Loader (NTLDR) dhawal Linux - Newbie 15 10-21-2005 11:29 AM
To load/boot Red Hat Enterprise Linux 4 WS from Microsoft's Boot Loader (NTLDR) dhawal Linux - General 1 09-25-2005 08:07 AM
Grub boot loader menu shows two linux boot options pramos Linux - Newbie 3 09-13-2004 12:40 AM
How to add a boot record which used to startup windows under my Grub boot loader? yunxiang Linux - Newbie 6 02-01-2003 03:22 AM


All times are GMT -5. The time now is 06:04 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