Re: 4.2: Boot -> reboot -> reboot -> ...

[Peter Wiemer-Hastings <Peter irvin psyc memphis edu>]

Thanks for the reply Stephen,

I didn't install any other hardware except for a bunch more ram.
Can't imagine that that would have an effect.
The new Quantum drive is on the same IDE cable as the original.

But what you wrote suggested that it could be a lilo problem.  Thought
I'd figured it out, but I might have got something wrong.
Here's what I got (I ran lilo from 4.1):

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
        label=linux
        root=/dev/hdb6
        read-only
image=/boot/vmlinuz
        label=lin41
        root=/dev/hda6
        read-only
other=/dev/hda1
        loader=/boot/chain.b
        label=win95
        alias=w
        table=/dev/hda

hda is the old small disk, and as I understand it, I'm booting off the
MBR on that disk.  The root for 4.2 is on hdb6, on the big drive.
But I'm not sure where it's getting the /boot files from.

Thanks again,
Peter

Stephen Smoogen writes:
 > 
 > Ok the problem you have listed below looks like it is linked to the fact
 > that you have a 4.1 initrd being loaded. The initial ramdisk gets loaded
 > when the kernel is looking for certain modules and the kernel that is
 > inside this ramdisk is the one that gets booted. Since you are having
 > problems with the 4.2 boot floppy (which would be my way of getting around
 > the problem..) I dont know exactly what could be happening. Do you know
 > what other hard-ware you added so that it could see a big hard-drive?
 > 
 > [Please reply to the list... email sent to me sometimes gets shuffled away
 > by procmail to someplace west :)]
 >