Slackware This Forum is for the discussion of Slackware Linux.
Notices
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
11-25-2003, 05:01 PM
#1
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Rep:
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?
11-25-2003, 05:06 PM
#2
Member
Registered: Oct 2003
Location: right behind the moon
Distribution: gentoo
Posts: 466
Rep:
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
11-25-2003, 05:07 PM
#3
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
yeah
image=/boot/vmlinuz
root=/dev/hdc5
11-25-2003, 05:19 PM
#4
Senior Member
Registered: Sep 2003
Location: Indiana
Distribution: Slackware 15.0
Posts: 1,272
Rep:
and you ran lilo after making the correct entry in lilo.conf?
11-25-2003, 05:19 PM
#5
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
of cource
11-25-2003, 05:29 PM
#6
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
you post your lilo.conf to me please, maybe i'll discover i did something wrong.
11-25-2003, 05:30 PM
#7
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
(can't post mine, I'm in windows and I'm too lazy to reboot:P)
11-25-2003, 06:16 PM
#8
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
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
11-26-2003, 12:25 AM
#9
Member
Registered: Oct 2003
Location: right behind the moon
Distribution: gentoo
Posts: 466
Rep:
try first root then image and also maybe just renaming the debian boot image if nothing else helps
11-26-2003, 01:38 AM
#10
Member
Registered: May 2003
Distribution: Ubuntu 6.10 SE, Mac OS 10.4.8
Posts: 370
Rep:
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.
11-26-2003, 06:58 AM
#11
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
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?
11-26-2003, 07:26 AM
#12
Member
Registered: Aug 2003
Distribution: Arch
Posts: 44
Rep:
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
11-26-2003, 07:27 AM
#13
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
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.
11-26-2003, 07:48 AM
#14
Member
Registered: Jul 2003
Location: Norway/Drammen
Distribution: Slackware~
Posts: 250
Original Poster
Rep:
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.
All times are GMT -5. The time now is 09:54 AM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News