Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 May 2000 15:05:28 -0500
From:      "Shawn Barnhart" <swb@grasslake.net>
To:        "DINKEY,GENE (Non-HP-Loveland,ex1)" <charles_dinkey@non.hp.com>, "questions@freebsd.org" <questions@FreeBSD.ORG>
Subject:   Re: Netserver LX Pro Install Hang
Message-ID:  <001001bfb471$c5345ab0$b8209fc0@marlowe>
References:  <F341E03C8ED6D311805E00902761278C531347@xfc04.fc.hp.com>

next in thread | previous in thread | raw e-mail | index | archive | help

----- Original Message -----
From: "DINKEY,GENE (Non-HP-Loveland,ex1)" <charles_dinkey@non.hp.com>
To: "questions@freebsd.org" <questions@FreeBSD.ORG>
Sent: Tuesday, May 02, 2000 10:39
Subject: RE: Netserver LX Pro Install Hang


| The AIC chip is on the PCI bus, and your right, by this time EISA was only
| kept to apease customers who did not wish to upgrade.  Leave the remote
| assistant card out, it will cause nothing but trouble.

What kind of problems?  I have two of those EISA monsters, and have never
had any problems with them -- AND they've saved me from making a 20 mile
round trip in bad weather more than once.

| I recently moved divisions and got rid of all my Netserver documentation
but
| I will try to find out what slots share IRQ's with the integrated SCSI.
| This is a big issue in the Netservers, there was no smart IRQ routing
| algorithim at the time the LX Pro was released so some slots are forced to
| share IRQ lines...

That'd be nice.

As it stands right now, the problem seems to be a defective memory
controller on the main board.  I built a custom kernel for the install
floppy, disabling just about everything and I was _still_ getting hangs.  I
yanked the memory board and memory out and replaced it with the memory board
+ memory from an LX Pro 200 and now I'm getting a 0304 fatal POST error.
Removing half of the memory from the memory board gets me booting again, but
I still get hangs when booting FreeBSD.  The other memory board works fine
in the LX Pro 200, so I don't think the board or RAM is bad (although the
database guy will be pissed if he knows he's down 128MB!).  I even swapped
CPUs to no avail.

So, "Mark" from HP is on his way out with a new system board. Which will
hopefully fix my problems.

Strangely, the 166's CPU board is slightly different than the 200's is --
it's got jumpers that the 200 doesn't.  When the tech gets here with my new
system board, I'm going to see if he'll tell me what the jumpers are for and
if I can run 200Mhz CPUs on it.

The good news from all of this is that my HPDA controller is elgible for
BIOS upgrade chips from Mylex.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001001bfb471$c5345ab0$b8209fc0>