RE: Multia Install problems
Hello there.
I am currently running a 166 Alpha Multia,
and not using SRM.
I'm using ARC and went through the aches and pains of that, instead.
If I understand Multias correctly (I'm a total newbie to Linux AND
Alphas)
I'd say that the Multia won't boot directly from an EXT2 partition,
period.
You have to create a FAT partition (the Multia can read directly from
FAT or from ISO9660 only),
and you have to point the firmware to the partition, where Milo and the
"noname" file live.
Once you get Milo to load into memory, which can read ext2, you can load
the root partition and the kernel,etc.
In ARC, it's annoying, because you have to create an entry in the
firmware that will tell the multia
where MILO is, and then enter a passthrough command to MILO which allows
the system to boot.
When I did my install, I gave up trying to install from CD altogether,
and did a net install using floppies
and the ethernet connector.
I got that part done without TOO much trouble and spent some painful
time getting "X" to work.
Take it easy, have fun.
Ted Letofsky
-----Original Message-----
From: Mark T. Valites [mailto:valites@geneseo.edu]
Sent: Monday, February 24, 2003 9:38 PM
To: debian-alpha@lists.debian.org
Subject: Re: Multia Install problems
On Mon, 24 Feb 2003, mcompengr@earthlink.net wrote:
>
> Did you try partition "a" to start at 2 (not 1)? BTW, that swap
> partition "b" looks rather huge. (Almost 4 Gig.? A size twice that
> of physical memory size should be enough.) Also, "a" probably wants
> to be ext2, too, and maybe bigger. And, "c" should maybe start at
> the end of (a much smaller) "b" plus 1. I don't think things will
> work with a filesystem's partition and the swap partition overlapping.
This scheme is what showed up whenever I createdthe full disk label & is
definetely not what I asked for - Looking back at it now in retrospec,
that layout looks plenty out of whack.
> > # start end size fstype [fsize bsize cpg]
> > a: 1 129 129 unused 0 0
> > b: 130 2033 1904 swap
> > c: 1 2033 2033 ext2
> > #
Regardless, by deleteing the a slice (thank you Richard Fillion
<rick@rhix.ods.org.), the aboot install at least appeared to have took.
I'm sure I'll redo it over serveral times till I've firgured it out, but
for the time being, I'd like to make sure the base install worked. I
didn't see any milo or aboot prompt on boot - am I missing something/
where do I head from here?
--
Mark T. Valites
Unix Systems Analyst
CIT - SUNY Geneseo
>--))> >--))>
--
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: