Subject: Re: Pyxis chip on a 500a.
To: David Hopper <dhop@nwlink.com>
From: Jeff Roberson <nomad@nop.aliensystems.com>
List: port-alpha
Date: 12/29/1999 19:57:32
It hangs long before sysinst, before it even starts detecting devices on
my pci bus.  There is no panic, or explination of why it hung.  I'm
currently using the built in IDE interface, because I've had trouble
locating the appropriate qlogic card for the beast.  I'm also using an old
cirrus logic from a pc because graphics aren't supported yet.

Jeff

On Wed, 29 Dec 1999, David Hopper wrote:

> Date: Wed, 29 Dec 1999 18:48:45 -0800
> From: David Hopper <dhop@nwlink.com>
> To: Jeff Roberson <nomad@nop.aliensystems.com>, port-alpha@netbsd.org
> Subject: Re: Pyxis chip on a 500a.
> 
> FWIW, on my particular 500a I've managed to _install_ NetBSD-current fine (12/4
> snapshot); i.e. the INSTALL kernel works great for me, but the GENERIC kernel
> installed by the 12/4 snapshot falls down with a 'memory management' kernel-trap
> error upon initializing the Qlogic card I've got in it.  (I believe this was fixed
> after 12/4 by Matthew Jacob).
> 
> I'm currently in the process of compiling a new -current Miata-flavored kernel on
> another Alpha.  I'm confident I can get NetBSD happy on the thing.  I'll let you
> know the outcome, and send you a kernel once my little bastard is up.
> 
> This 500a of mine has a Trio-64 card in it (bottom PCI slot), and a DEC 21141 card.
> 
> Does your machine hang at the INSTALL kernel (i.e. before sysinst?)
> 
> dhop
> 
> Jeff Roberson wrote:
> 
> > I tried 1.4.1 and 1.4.2_ALPHA both of which exhibited the same symptoms.
> > I tried to break into the kernel debugger, but I assume it isn't enabled
> > this early in the game.  And yes, there was no other output after the cia0
> > warning.  I can test the debugging kernels later tonight if they are
> > available.
> >
> > Thanks,
> > Jeff
> >
> > >
> > > I.e. there was _NO_ other kernel output after the 'cia0: WARNING: ...'
> > > line?
> > >
> > > that's interesting, because it means that the machine crashed in a
> > > place where it shold be relatively easy to figure out what's going on.
> > >
> > >
> > > You didn't say if you were trying to run 1.4.x or -current on that
> > > box.  If -current, could you try to run a 1.4.x (e.g. 1.4.1) kernel?
> > > If that fails, i can try to compile you a few kernels with debugging
> > > printfs...  (I don't have -current on any of my alphas.)
> > >
> > >
> > >
> > > cgd
> > > --
> > > Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
> > > Disclaimer: Not speaking for NetBSD, just expressing my own opinion.
> > >
> 
>