SlackwareThis 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.
Hi
i just installed arch to test it but i can't make dual boot work with lilo
i got installed slsackware in hda2 (sda2 in arch) and arch in hdc3 (sdb3 in arch)
i tried monting arch linux partition to /mnt/arch then i added and to lilo.conf this:
I tried dual booting Slack with Arch a few months ago, and the only way I could get this to work was to use grub to boot. I though about upgrading to the newest kernel on the slack side, which would probably have fixed the hda/sda naming problem with lilo, but never actually did this.
In the end, I experience too many frustrations with Arch (mainly around their required dependencies and compile-time options) to want to continue with it. My old laptop is back to a slack only machine
I dual-boot Slackware and Arch. But my harddrive is /dev/sda on both systems. I use lilo from Slackware with no problems at all. What version of Slackware are you running?
PS Ib any case, have you tried setting root=/dev/sdb3 for arch in your lilo.conf?
Last edited by Uncle_Theodore; 01-07-2008 at 11:32 PM.
I didn't like the "sda thing" so when installing arch, i used the 'ide-legacy' option (or something like that) Check it a boot time, and check if you need to type ide-legacy or 'ide-legacy' i don't remember atm
No need to use grub (imo)
good luck
to lstamm
thanks for you advice, i will try to make it work with lilo but if i can't i will use grub
to Uncle_Theodore
i'm using slackware 12 with kernel 2.6.23.12, i tried with /dev/sdb3 but doesn't work, i got this error "Fatal: Illegal 'root=' specification: /dev/sdb3"
to mannyslack
do you know any way to change sd* to hd* without install arch again??
to lstammto mannyslack
do you know any way to change sd* to hd* without install arch again??
No, sorry i don't. Not sure if it can be done safely. Just guessing:
umount arch partition(s) edit all /etc/fstab (including arch's) and change to hdX. Remount partitions again (mount -a) and edit /etc/lilo.conf Then /sbin/lilo and hope it works. Please let us know if it does. Also helpfull to ask in arch forums or irc, but let us know how i was solved please
gl
There's another thing to try... You can install arch's lilo on the superblock of the arch's root partition. And then, in you Slackware lilo.conf set something like you'd done for Windows
other=/dev/hdc3
label=Arch
table=/dev/hdc
Then, in Arch's lilo.conf you could set root to be /dev/sdb3
You'll get a two-stage booting of Arch, but hopefully, it will work.
you aren't going to believe this the second hard disk was disabled in the bios (with is kinda weird i don't remember to disable it, and i can read/write without problem in linux) so i enabled and that fixed the 0x01 error in lilo. But still arch doesn't work so i made some research in google and fixed the problem adding this to lilo.conf:
Note to myself:
Always double-check error suggestion (even if i am sure the problem is not there)
Code:
0x01: Illegal Command
This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. Definitely check to see if the disk is seen by the BIOS first (and that the BIOS detail is complete).
Using a console in Slackware
1.- mount /dev/sda9 /mnt/arch
2.- cd /mnt/arch/boot && cp kernel26.img vmlinuz26 /boot
3.- Add to /etc/lilo.conf
image = /boot/vmlinuz26
root = /dev/sda9
label = arch
read-only
initrd = /boot/kernel26.img
4.- run, lilo
5.- Reboot and select arch, work fine
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.