Re: request: boot floppies for AlphaServer 1000A (Noritake?)
>>> Yedidya Bar-david said:
>
> I am a debian user for ~1.5 years (linux ~4.5 years), currently
> running debian 1.3.1 for Intel. I will soon install 2.0. I would
> like to try to install debian for alpha on an AlphaServer 1000A
> I have access to at work. I believe its chipset is Noritake.
Correct; AS 1000A is NORITAKE; but note that it can have either EV4 CPU
(as in model 4/xxx), or EV5 CPU (model 5/xxx). You'll need the appropriate
kernel to handle the CPU (until we get generic kernels working in 2.1.xx :-).
> This machine usually runs Windows NT, but we had also Digital
> Unix and OpenVMS on it. I tried only once to boot linux on it
> (I believe it was from and old redhat 4.0), with no success.
> I also have access to an AlphaServer 4000 and an AlphaServer
> 2100, so I can try to boot things there (but not to install).
> If someone wants me to try something, please do, but I can only
> take these machines down on weekends.
Whoa! A real beta-test site... ;-}
All the above (AS 4000, aka RAWHIDE; AS 2100, aka SABLE), and NORITAKE,
*require* booting from SRM console. There are (currently) no MILOs for
any of them, AFAIK.
NORITAKE and SABLE are supported by the 2.0.xx kernels; RAWHIDE is only
supported under the 2.1.xx development tree. Both RAWHIDE and SABLE can be
SMP machines; again, 2.1.xx is going to be required for such (and that is
getting much more stable, finally; we hope to have full support in soon).
--Jay++
-------------------------------------------------------------------------------
American Non Sequitur Society: we don't make sense, but we do like pizza...
Jay A Estabrook Alpha Motherboards - LINUX Project
Digital Equipment Corp. (508) 841-3241 or (DTN) 237-3241
334 South Street, Shrewsbury, MA 01545 Jay.Estabrook@digital.com
-------------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: