LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 06-04-2008, 09:12 AM   #1
Unr3a164
Member
 
Registered: Apr 2007
Distribution: Slackware 13.1 + Ubuntu 9.04
Posts: 143

Rep: Reputation: 16
Chainloading Grub from Lilo


I am trying to dual boot my laptop between Slackware and Ubuntu. I was told to just use Grub to boot to the two OS's, so I had Ubuntu overrite the MBR with GRUB. This was able to successfully load Ubuntu, but it could not recognize Slackware, because I have an IDE based system. And Ubuntu, regardless of what type of hard drive you have, recognizes all drives on the system as SDA, not HDA. So Slackware wouldn't boot. So I am trying to configure Lilo to chainload to GRUB. How do I configure Lilo to chainload into Grub on /dev/hda2?
 
Old 06-04-2008, 09:25 AM   #2
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729
How Ubuntu recognizes drives is irrelevant. All you have to do is add an entry for Slackware to your GRUB menu.lst file. I infer that you have Slackware on hda1 and Ubuntu on hda2. So the Slackware entry would look somethink like this:
title Slackware
root (hd0,0)
kernel /boot/vmlinuz..... root=/dev/hda1 ro

(Assumes that there is no separate /boot partition.)

(Since you now have GRUB on the MBR, it's a lot easier to setup GRUB than to re-install LILO.)


More details in the "booting" link below.
 
Old 06-04-2008, 09:26 AM   #3
wadsworth
Member
 
Registered: Aug 2007
Distribution: Slackware64 13.37
Posts: 215

Rep: Reputation: 65
Code:
other=/dev/hda2
   label=Ubuntu
You must reinstall Ubuntu's grub to the boot sector of /dev/hda2,
and (of course) reinstall Slackware's lilo to the mbr.
 
Old 06-04-2008, 09:48 AM   #4
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,487

Rep: Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077
That will work - as will installing lilo to its own boot sector, and chainloading that from grub.
Only one can be setup to be in the MBR, not both.

Either way is easier than trying to directly reference the others kernel image - that would require a full path specification on the kernel and initrd.
 
Old 06-04-2008, 10:12 AM   #5
Unr3a164
Member
 
Registered: Apr 2007
Distribution: Slackware 13.1 + Ubuntu 9.04
Posts: 143

Original Poster
Rep: Reputation: 16
I had GRUB installed before and it could not load Slackware, because it would come up with an error saying that HDA did not exist. I asked what that meant in the Ubuntu IRC chat, and they said it was because Ubuntu and GRUB with Ubuntu, recognize the HDD as SDA, not HDA.
 
Old 06-04-2008, 11:35 AM   #6
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Originally Posted by Unr3a164
I had GRUB installed before and it could not load Slackware, because it would come up with an error saying that HDA did not exist. I asked what that meant in the Ubuntu IRC chat, and they said it was because Ubuntu and GRUB with Ubuntu, recognize the HDD as SDA, not HDA.
That's because Ubuntu users don't know what they're talking about. (Just kidding, of course)

The problem was most likely due to the change in inode size from 128 to 256 bytes in ext2/ext3 filesystems in Slackware.
Quote:
Originally Posted by extra/source/grub/grub.SlackBuild
# This is needed for the optional (but now default) increase in
# inode size from 128 to 256 bytes with ext2 and ext3:
zcat $CWD/grub_support_256byte_inode.patch.gz | patch -p1 --verbose || exit 1
During the installation, you have the option of choosing an inode size. The DEFAULT inode size for ext2/ext3 filesystems is now 256 bytes in Slackware instead of 128 bytes (which is likely what Ubuntu uses). Slackware's GRUB available from extra/ from CD number 4 (or the DVD, or your favourite mirror) is patched to handle the 256 byte filesystem. There are two options. You could either reinstall Slackware from scratch and choose a 128 byte inode size for your ext2/ext3 filesystem (the stupid way), chainload Ubuntu's GRUB from Slackware's LILO (see wadsworth's post) or install Slackware's patched GRUB and use it to boot both Slackware and Ubuntu (the smart way -- though you must edit the menu.lst to add Ubuntu as a boot option).

Last edited by T3slider; 06-04-2008 at 11:36 AM.
 
  


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
grub and lilo chainloading rienqunuser Linux - Newbie 5 02-13-2008 06:59 PM
Chainloading from grub to LILO AtomicAmish Slackware - Installation 2 08-24-2007 11:47 PM
GRUB & XP w/out Chainloading: Possible? Computer Guru Linux - Software 5 06-14-2006 01:23 PM
chainloading lilo mimithebrain Linux - Software 7 05-18-2005 06:31 PM


All times are GMT -5. The time now is 04:08 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration