[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "no link beat found" on digital alpha-station 255



On Tue, Jan 17, 2006 at 11:35:39PM -0800, Steve Langasek wrote:
> On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
> > On Tue, Jan 17, 2006 at 01:21:38PM +0100, Cornelius Weiss wrote:
> 
> > > i managed to install a debian-base-system from the net-install image on 
> > > a digital alpha-station255.
> > > After the reboot of DI the installation couldn't be finished, as the 
> > > network isn't working.
> 
> > > On colsole it alwas says: "Wanrning: No link beat Found"
> 
> > > Is sombody aware of a solution for this problem?
> 
> > Many of the Alphas with builtin old/slow TULIPs give problems with
> > the current default driver ("de2104x"). I think it's NOT the driver's
> > fault, but some kinda quirky implementation on the mobos. Regardless,
> > it doesn't work successfully (and won't, until the quirkiness is
> > understood).
> 
> > If the other TULIP driver "de4x5" is built for your kernel, try that.
> 
> > By old/slow TULIPs, I mean 21040 and 21041 chipsets.
> 
> Are there any changes that should be made to the kernel's modules.pcimap for
> this?

If they become "generic", meaning affect ALL platforms, then no, I think
that'd be wrong, since the majority of machines don't have the builtins,
and don't exhibit the problem.

> > And the Alphas with those builtin are:
> 
> > AS200/AS250/AS255/AS300/AS500
> 
> > Those same old/slow TULIP chipsets, when on a PCI card (like the DE434
> > and DE435), do seem to work OK with the "de2104x" driver, IIRC.
> 
> Hrm.  Does that mean the PCI IDs match between the working and non-working
> cases?

I believe they match exactly, but I'll check...

 --Jay++

---------------------------------------------------------------
Jay A Estabrook                            HPTC - XC I & B
Hewlett-Packard Company - ZKO1-3/D-B.8     (603) 884-0301
110 Spit Brook Road, Nashua NH 03062       Jay.Estabrook@hp.com
---------------------------------------------------------------



Reply to: