topic Dialogic board (D/4PCI-U) in DL380 G3 in ProLiant Servers (ML,DL,SL)

Dialogic board (D/4PCI-U) in DL380 G3

Jeff Mathews — Mon, 08 Sep 2003 15:06:15 GMT

Hi Guys/Gals, I know this is a bit of a specialty request, but I'm hoping someone has got this working.

We have a new D/4PCI-U Dialogic card from Intel that we are trying to get working in a DL380 G3. This card is 5v Universal so it should work fine in the DL 380's 3.3v PCI slots. The problem I'm having is:

When I boot the server, the server recognizes new hardware fine, but the dialogic configuration utility can't see the card.

I need to get this working so I can phase out an old Netfinity server that uses an old Dialogic card. I don't want to be forced to maintain this old stuff 'cause I can't get it working on a new server.

TIA,

Jeff

Re: Dialogic board (D/4PCI-U) in DL380 G3

Thilo Knoch — Wed, 24 Sep 2003 05:45:56 GMT

May be you have already solved it.
There is an application note from intel:
PCI Boards Are Not Detected
Problem Description:
After installing an IntelÂ® DialogicÂ® PCI board into a computer system with IntelÂ® DialogicÂ® System Release 5.1.1, the configuration manager (DCM.EXE) is not able to detect the board. The same board may or may not be detected in other PCI slots in the same system.
.
.
This problem was corrected with a software update and is available in System Release 5.1.1 Build 30 and later software releases. Note that System Release 5.1.1 Build 30 is the production build and this is available for download from our website.

http://resource.intel.com/telecom/support/tnotes/gentnote/dl_hard/tn2

Re: Dialogic board (D/4PCI-U) in DL380 G3

Jeff Mathews — Thu, 25 Sep 2003 09:10:29 GMT

Thanks for your reply to this one. We actually have been able to get it working. It was a bit tricky, but we installed the system 5.1.1 like you suggested. Unfortunatly nothing would work if we installed the patches you mentioned. We had to use just the base 5.1.1 and then install Feature Pack 1 (if the patches were there with the feature pack - no go). This seemed to be the only way to get this to work for us....

Jeff