LinuxQuestions.org
Visit the LQ Articles and Editorials section
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 11-25-2003, 05:01 PM   #1
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Rep: Reputation: 30
Unhappy Touble dualbooting different Linux os'


Ok, here's the prob;

i use slackware regulary, right?

but i'd like to dualboot to debian, cause i wanna check it out.

my lilo.conf's set up correctly and stuff.

but when i try to load debian, it loads the kernel from my slackware partition. (which is doomed). how can i make it load from its own root?
 
Old 11-25-2003, 05:06 PM   #2
kasperhans
Member
 
Registered: Oct 2003
Location: right behind the moon
Distribution: gentoo
Posts: 466

Rep: Reputation: 30
then your lilo is not setup right you have to specify the location of your debian kernel in lilo for dual booting read the lilo conf on that should work though
 
Old 11-25-2003, 05:07 PM   #3
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
yeah

image=/boot/vmlinuz
root=/dev/hdc5
 
Old 11-25-2003, 05:19 PM   #4
ringwraith
Senior Member
 
Registered: Sep 2003
Location: Indiana
Distribution: Slackware-current
Posts: 1,244

Rep: Reputation: 47
and you ran lilo after making the correct entry in lilo.conf?
 
Old 11-25-2003, 05:19 PM   #5
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
of cource
 
Old 11-25-2003, 05:29 PM   #6
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
you post your lilo.conf to me please, maybe i'll discover i did something wrong.
 
Old 11-25-2003, 05:30 PM   #7
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
(can't post mine, I'm in windows and I'm too lazy to reboot:P)
 
Old 11-25-2003, 06:16 PM   #8
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
here it comes;

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# 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
# DOS bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
 
Old 11-26-2003, 12:25 AM   #9
kasperhans
Member
 
Registered: Oct 2003
Location: right behind the moon
Distribution: gentoo
Posts: 466

Rep: Reputation: 30
try first root then image and also maybe just renaming the debian boot image if nothing else helps
 
Old 11-26-2003, 01:38 AM   #10
Locura
Member
 
Registered: May 2003
Distribution: Ubuntu 6.10 SE, Mac OS 10.4.8
Posts: 370

Rep: Reputation: 30
I had this problem once before when experimenting with multiple distros. The solution was to put a copy of the kernel image in the /boot/ directory of my slackware setup. I don't know why it worked, but it did.
 
Old 11-26-2003, 06:58 AM   #11
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
To be honest, i've allready tried that. and.. i guess it worked. but i find that as an cheap sulution. i want to really fix it. any one?
 
Old 11-26-2003, 07:26 AM   #12
a slacker
Member
 
Registered: Aug 2003
Distribution: Arch
Posts: 44

Rep: Reputation: 15
Try mounting your debian partition under slack (call it /mnt/debian). Then run:

mount /dev/hdc5 /mnt/debian

and it will mount your debian partition. Then change your lilo.conf to look like this:

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /mnt/debian/boot/vmlinuz
root = /dev/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Then run lilo again and reboot. It should then boot your debian kernel correctly
 
Old 11-26-2003, 07:27 AM   #13
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by kasperhans
try first root then image and also maybe just renaming the debian boot image if nothing else helps
dude, no. that didn't work either. lilo gave me some nasty error. that's not how it's supposed to be lined.
 
Old 11-26-2003, 07:48 AM   #14
Kjetil4455
Member
 
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by a slacker
Try mounting your debian partition under slack (call it /mnt/debian). Then run:

mount /dev/hdc5 /mnt/debian

and it will mount your debian partition. Then change your lilo.conf to look like this:

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /mnt/debian/boot/vmlinuz
root = /dev/hdc5
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Then run lilo again and reboot. It should then boot your debian kernel correctly
That wont work, because the Debian disk is mounted under bootup of slackware.
 
  


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
Problem with dualbooting win2k and linux eaglegst Linux - General 1 06-29-2004 06:50 PM
Problem dualbooting XP and Linux. Lilo isn't cutting it... Lepinski Linux - Newbie 5 04-05-2004 07:40 PM
Dualbooting Linux and Windows using lilo kLUMSY bOT LinuxQuestions.org Member Success Stories 1 02-11-2004 02:23 AM
touble installing linux 8.2, blank screen after pushing install doppelmord Linux - Software 1 12-26-2003 09:29 PM
Dualbooting WinXP/Linux and Lilo Comreak Slackware 18 06-29-2003 11:30 PM


All times are GMT -5. The time now is 07:19 PM.

Main Menu
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