Lilo Dual boot

rudi · 2004-02-23 14:37:40

Hi,

I'm experimenting with Arch, and still runs Slackware as my main OS. I've installed Arch on my second HD and Slackware next to Windoze on my first.
Because Slackware is my main OS i configure lilo from there. After installing Arch i did not installed Lilo because i didn't want to let it overwrite my old one.

Now so far for the introduction, Slackware uses hda1, hda2, hdb1 etc. but Arch uses /disc0/part2.
I've added Arch to lilo from Slackware as root=/dev/hdb2
Now ArchLinux will boot, but halfway it suddenly stops and reboot. Can someone tell me what's going one? I doubt if it has something to do with the nomenclature of both systems, but hey, i'm the n00b around here

*Edit
During boot just before rebooting i get the following message:
"unable t open initial console"
/Edit

Greets, Rudi

martinaramirez · 2004-02-24 14:12:22

Did you run Lilo after you updated lilo.conf? This will update any changes you make in lilo.conf and write them to the MBR. Are you loading windows from your lilo? One setup that I use default boots the windows loader which in turn will boot either xp or 98 and the other lilo choice is arch. I hope this helps! I'm still a NooB myself, but I'm getting the hang of it. One other quick question for you, is it shutting down booting to the command line or to a GUI (KDE, etc)?

rudi · 2004-02-24 19:49:02

Hi,

Yes i did run LILO after editting lilo.conf from Slackware. Currently i have three OS-es Windoze XP, Slackware Linux and Arch. The problem lies in the two versions of Linux. If i run lilo from Arch, Arch works like a charm, and Slackware doesn't function well (though it does finish booting). If i maintain Slackware as my main OS, and use Lilo from there Arch won't boot. Because i want to learn Arch i've chosen to use lilo from there (i still would like to know how to solve this though!!!!).

As for your question: you mean that if you boot your PC it'll boot directly into KDE or to a command prompt first?
You could change your etc/inittab default runlevel to 5

#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)       Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

id:5:initdefault:

Rudi

afu · 2004-02-24 22:01:39

I've never tried this, but maybe you could set lilo for Slackware in the MBR like you normaly would. Then point it to Arch on the second drive. Is it possible to then have Arch run it's Lilo, so as to match the devfs entries?

Clueless here but curious.
-Shawn

Xentac · 2004-02-24 23:45:24

rudi, are you using a custom kernel for archlinux? If so you forgot to compile in an option or two. I can't remember the options off hte top of my head, but searching for your error message wil probably find it.

rudi · 2004-02-25 12:37:36

Hi,

I do not have a custom kernel, just the standard IDE kernel. I've compared both the etc/devfs files and i believe they are identical. I really think is has something to do with the fact that Arch uses /disc0 etc and Slack the /hda1. If i boot Slack the screen output looks like a combination of Arch and Slackware... :shock:

I really am lost there. Arch does function well though..

Xentac · 2004-02-25 16:21:04

I bet you're booting with slack's kernel instead of arch's.

rudi · 2004-02-25 19:52:34

Xentac wrote:

I bet you're booting with slack's kernel instead of arch's.

Just the other way around, just figured it out this morning...
Sorry guys :?, can't believe i missed that :oops: (to hasty)

Here is my lilo.conf. Is it still posible to fix this? Perhaps use Grub?

boot=/dev/discs/disc0/disc

default=ArchLinux
timeout=50
lba32
prompt

image=/boot/vmlinuz
        label=ArchLinux
        root=/dev/discs/disc1/part2
        read-only

image=/boot/vmlinuz
        label=Slackware
        root=/dev/discs/disc0/part3
        read-only

other=/dev/discs/disc0/part1
        label=Windows

Xentac · 2004-02-26 06:13:49

One of two ways. You can boot your arch boot partition (or root, if you don't have a seperate boot partition) in slackware, then point to that one in your lilo.conf i.e. image=/mnt/arch/boot/vmlinuz.

The other way to do it would be to install an arch bootloader on the arch root partition and chain load it (like you do with windows). This way you don't have to boot into slackware every time you want to upgrade your kernel in arch. Running two linuxes is just generally difficult.

rudi · 2004-02-26 06:40:23

Thanx Xentac.
I didn't thought that running two linuxes was so difficult. I'll repartition the whole lot and install Arch as i'm using it 99.9% of the time now. Thanx for your help.

jimdaworm · 2004-02-29 15:25:56

Hey guys I have Exactly the same setup and Exactly the same problem... is there any easier way to set things up without chain loading the lilos?? I don´t fully understand how I should do it.

I have Win XP Slackware and Arch... here is my Slackware lilo.conf... incase it helps!

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdd=ide-scsi"
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# 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
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Slack
read-only # Non-UMSDOS filesystems should be mounted read-only for checking

image = /boot/vmlinuz.old
root = /dev/hda2
label = SlackOK
read-only

# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Arch
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = Window
table = /dev/hda
# DOS bootable partition config ends

Thanks
Adam

jimdaworm · 2004-03-02 17:59:36

I sussed it ... installed grub and that made everything work

Adam

Arch Linux

#1 2004-02-23 14:37:40

Lilo Dual boot

#2 2004-02-24 14:12:22

Re: Lilo Dual boot

#3 2004-02-24 19:49:02

Re: Lilo Dual boot

#4 2004-02-24 22:01:39

Re: Lilo Dual boot

#5 2004-02-24 23:45:24

Re: Lilo Dual boot

#6 2004-02-25 12:37:36

Re: Lilo Dual boot

#7 2004-02-25 16:21:04

Re: Lilo Dual boot

#8 2004-02-25 19:52:34

Re: Lilo Dual boot

#9 2004-02-26 06:13:49

Re: Lilo Dual boot

#10 2004-02-26 06:40:23

Re: Lilo Dual boot

#11 2004-02-29 15:25:56

Re: Lilo Dual boot

#12 2004-03-02 17:59:36

Re: Lilo Dual boot

Board footer