I did leave space and Aboot was installed. Although I may have an answer.
For BSD style disklabeling you have to create an empty partition that gets the
c label that encompasses the entire disk. If aboot were installed to this
whole disk partitions would it cause aboot to not be able to read/mount the
harddisk because it no longer contained a BSD-style disk label? I can boot
from my redhat floppy. I have no clue about the kernel overflow fault when
booting from the CD. The aboot problem seems to me to have something to do
with its ability to read the harddrive after the install? I didn't
repartition though.
Do you know how the installer installs aboot? I was surprised to have it do
it itself. This could give me more info to go on.
Thanks,
James
------------------------------------------------------------------------------
James Fowler
Graduate Student Political Science & Latin America
Arizona State University
[EMAIL PROTECTED] ICQ: 22088266
-----------------------------------------------------------------------------
On Fri, 14 Apr 2000, Pixel wrote:
> [EMAIL PROTECTED] writes:
>
> > I grabbed the ISO for Mandrake
> > 7.0 for Alpha and installed it last night. The easiest install I have ever
> > had on my Alpha. Plus, It actually worked! (the installer, that is). I have
> > run into a small problem - just curious to see if anyone else has experienced
> > this too. After the install, (PWS433a/au, Qlogic, SRM) when I go to boot,
> > aboot loads fine but cannot read from my harddrive. I didn't change my
> > partitioning and I had set up BSD disklabels using fdisk from Redhat 5.2
> > before I installed Mandrake. I did reformat my swap (sda4) and / (sda2)
> > partitions. Aboot cannot mount my harddrive.
>
> maybe aboot wasn't installed. Did you leave some free space at the beginning of
> the drive?
>
> > I tried to boot from the cdrom
> > (as they suggest) and I get a kernel stack overflow (overflow error=2)?
>
> sigh... known bug though. don't know how to fix this (and hard to test, needing
> burning each time)
>
>
