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? |
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
|
yeah
image=/boot/vmlinuz root=/dev/hdc5 |
and you ran lilo after making the correct entry in lilo.conf?
|
of cource
|
you post your lilo.conf to me please, maybe i'll discover i did something wrong.
|
(can't post mine, I'm in windows and I'm too lazy to reboot:P)
|
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 |
try first root then image and also maybe just renaming the debian boot image if nothing else helps
|
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.
|
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?
|
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 |
Quote:
|
Quote:
|
All times are GMT -5. The time now is 10:40 AM. |