MSFN Forums > HP DL585-G2 and WinPE v2.0

Jazkal

Mar 19 2007, 02:22 PM

Anyone have a HP DL585-G2 working with WinPE v2.0? I can't seem to get the NIC's working.

MTNMN51

Mar 19 2007, 04:11 PM

I believe that model has the Broadcom NetXtreme II card and that you probably need to use the monolithic drivers provided by Broadcom.

http://www.broadcom.com/support/ethernet_nic/netxtremeii.php
http://www.broadcom.com/docs/driver_downlo...eadme-2.6.2.txt

I haven't played with WinPE 2.0 yet, so don't know whether is supports the "virtual bus device" architecture. But I suspect it doesn't. If it doesn't, then I believe these drivers should work for you.

Jazkal

Mar 20 2007, 07:38 AM

Thank you for the input. I should have given more details about the problem I'm having.

I am using those drivers currently, and they are working on other systems that use those same broadcom nics. (ie. Dell 2950, and HP DL 385 G2).

The problem I'm having is that WinPE v2 isn't even seeing the NICs at all. I think they are sitting behind another device that I don't have the drivers for, therefore everything behind that device isn't showing up.

I have two devcon scans I'm posting below, one is from WinPE v1.6 (Windows 2005 SP1), and the other is from WinPE v2.0 (Vista PE).

Both versions of WinPE have the same drivers installed.

WinPE v1.6 devcon list

CODE

PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&21887AE&0&2048: Base System Device
PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&21887AE&0&2248: Base System Device
PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&21887AE&0&1848: Video Controller (VGA Compatible)
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C0: PCI HOST Bridge
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C8: PCI HOST Bridge
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&D0: PCI HOST Bridge
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&D8: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C1: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C9: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&D1: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&D9: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&C2: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&CA: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&D2: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&DA: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&C3: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&CB: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&D3: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&DB: PCI HOST Bridge
PCI\VEN_1022&DEV_7458&SUBSYS_00000000&REV_12\3&33B859B7&0&80: PCI to PCI Bridge
PCI\VEN_1022&DEV_7458&SUBSYS_00000000&REV_12\3&33B859B7&0&88: PCI to PCI Bridge
PCI\VEN_1022&DEV_7459&SUBSYS_74591022&REV_12\3&33B859B7&0&81: System Interrupt Controller
PCI\VEN_1022&DEV_7459&SUBSYS_74591022&REV_12\3&33B859B7&0&89: System Interrupt Controller
PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&22FEBB0D&0&0060: RAID Controller
PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&21887AE&0&2448: Universal Serial Bus (USB) Controller
PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&21887AE&0&2648: PCI Device
PCI\VEN_10DE&DEV_0051&SUBSYS_00000000&REV_B1\3&20FEA912&0&08: PCI to ISA Bridge
PCI\VEN_10DE&DEV_0053&SUBSYS_31F8103C&REV_A3\3&20FEA912&0&30: IDE Controller
PCI\VEN_10DE&DEV_005A&SUBSYS_31F8103C&REV_A2\3&20FEA912&0&10: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005B&SUBSYS_31F8103C&REV_A4\3&20FEA912&0&11: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&20FEA912&0&48: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&60: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&68: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&70: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&58: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&60: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&68: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&70: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&20FEA912&0&00: PCI Memory Controller
PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&33B859B7&0&00: PCI Memory Controller
PCI\VEN_10DE&DEV_00D3&SUBSYS_CB8410DE&REV_B1\3&33B859B7&0&08: PCI Memory Controller
PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&0880: Broadcom BCM5706C NetXtreme II GigE
PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&1080: Broadcom BCM5706C NetXtreme II GigE #2
43 matching device(s) found.

WinPE v2.0 devcon list

CODE

PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&21887AE&0&2048: Base System Device
PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&21887AE&0&2248: Base System Device
PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&21887AE&0&1848: Video Controller (VGA Compatible)
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C0: PCI HOST Bridge
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C8: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C1: PCI HOST Bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C9: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&C2: PCI HOST Bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&CA: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&C3: PCI HOST Bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&CB: PCI HOST Bridge
PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&22FEBB0D&0&0060: RAID Controller
PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&21887AE&0&2448: Universal Serial Bus (USB) Controller
PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&21887AE&0&2648: IPMI Interface
PCI\VEN_10DE&DEV_0051&SUBSYS_CB8410DE&REV_B1\3&20FEA912&0&08: PCI to ISA Bridge
PCI\VEN_10DE&DEV_0053&SUBSYS_31F8103C&REV_A3\3&20FEA912&0&30: IDE Controller
PCI\VEN_10DE&DEV_005A&SUBSYS_31F8103C&REV_A2\3&20FEA912&0&10: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005B&SUBSYS_31F8103C&REV_A4\3&20FEA912&0&11: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&20FEA912&0&48: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&60: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&68: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&70: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&58: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&60: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&68: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&70: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&20FEA912&0&00: PCI Memory Controller
PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&33B859B7&0&00: PCI Memory Controller
PCI\VEN_10DE&DEV_00D3&SUBSYS_CB8410DE&REV_B1\3&33B859B7&0&08: PCI Memory Controller
29 matching device(s) found.

As you can see, there is a big difference in how many devices the two versions actually "see".

MTNMN51

Mar 20 2007, 11:29 AM

I'm not sure if it works for WinPE 2.0, but I use the HP SmartStart Scripting Toolkit Win32 Edition driver update utility to keep my WinPe 2005 image up to date with the latest drivers. The version that I have has all the drivers from PSP 7.70, so is very current. The nice thing is that once you run the utility to update your WinPE image, you're covered for all the HP hardware. I hope that helps.

chrislynch

Mar 21 2007, 12:50 AM

We have released a beta version of the Proliant Support Pack (PSP) v7.65. You can read more on it here

For the 32-bit beta PSP 7.65:
ftp://ftp.compaq.com/pub/softlib2/softwar....65.lh.i386.exe

For the 64-bit beta PSP 7.65:
ftp://ftp.compaq.com/pub/softlib2/softwar...7.65.lh.x64.exe

You will need the following packages:

cp006277.exe
cp006284.exe
cp006316.exe
cp006913.exe
cp006924.exe
cp006926.exe
cp007054.exe
cp006258.exe

Extract the packages to c:\psp7.65, make sure that your winpe image is mounted, and then run the following commands:

peimg /inf="C:\psp7.65\cp006284\cpqasm2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006913\lsi_scsi.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006924\lsi_sas.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006926\hpcissx2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp007054\cpqcisss.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp007054\hpcisss.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006277\CpqCiDrv.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006258\hpqilo2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006316\bxvbd.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006316\bxnd.inf" c:\winpe_x86\mount\Windows

Now, you would only really need the cp006316 package, as it contains the necessary drivers you need to get networking to work. I would suggest the other packages (especially cp006284, cp006258 and cp006277) if you are going to use Altiris Deployment Solutions or HP RDP 3.50, or you want the ability to use hponconfig to configure the iLO2 management processor.

Jazkal

Mar 21 2007, 10:03 AM

First, I just want to say that I'm very impressed that HP would see this post and give an answer. Thanks chrislynch.

After trying what you posted, however, it still doesn't detect the NIC's.

You said the important one was cp006316, and inside that are two INF's: bxvbd.inf and bxnd.inf

If you look in those INF's, you'll see that none of the device ID's are listed in the Devcon output from WinPE v2.0 (see above).

I installed the INF's from all those packages that you listed, didn't want you to think I had only done this one package.

I have verified that we are running the most current BIOS.

Anything else you can think of?

NOTE: your x86 link wasn't working, but I browsed through the FTP site, and used this one:
ftp://ftp.compaq.com/pub/softlib2/softwar....65.lh.i386.exe

chrislynch

Mar 21 2007, 11:00 AM

I was doing some research on a particular WinPE 2.0 error I was experiencing, and came across this forum.

I haven't tested my WinPE package yet, as I'm preparing to test with RDP 3.50 and our newest generation of systems.

What happens if you simply add a new folder in our mount directory that contains the extracted components of cp006316, and run drvload within WinPE? You can then use devcon to list the loaded drivers (I'm assuming here as you could use devcon in WinPE 1.6.) I have seen reports that peimg doesn't properly embed some drivers properly.

I'll be testing my image the remainder of the week with our BL465's and BL480's that I have in a lab.

chrislynch

Mar 21 2007, 03:09 PM

I'm wondering if you can boot into your PE image and locate the bxvbdx.sys in \Windows\System32\drivers. If not, then there is an error in the build process (the same that I'm running into.) It appears that when the image boots, it actually boots the boot.wim file located in the \ISO\Sources directory within the WinPE build location on your PC. I'm working to see if indeed this is the case.

Jazkal

Mar 21 2007, 03:18 PM

QUOTE (chrislynch @ Mar 21 2007, 04:09 PM)

I'm wondering if you can boot into your PE image and locate the bxvbdx.sys in \Windows\System32\drivers. If not, then there is an error in the build process (the same that I'm running into.) It appears that when the image boots, it actually boots the boot.wim file located in the \ISO\Sources directory within the WinPE build location on your PC. I'm working to see if indeed this is the case.

Yes, I can find that file. We are booting our WinPE images over PXE, using the BCD/WIM option, as I believe ISO booting over PXE is no longer an option.

When I tried to load the drivers from within WinPE itself, I recieved this message for both INF's:

CODE

DrvLoad: Successfully loaded bxvbd.inf

After doing another devcon, nothing had changed.

The NIC's aren't seen by WinPE, so the drivers aren't loaded, and NIC's don't work.

chrislynch

Mar 21 2007, 03:20 PM

I got networking to initialize (although within a VM.) Here is the batch file I use to create the ISO:

makeiso.cmd:

CODE

@ECHO OFF
SET WINPE2SOURCE == "c:\winpe2_x86"
cd %WINPE2SOURCE%
ECHO.Moving winpe.wim to ISO\ folder
move winpe.wim ISO\sources\boot.wim
ECHO.
ECHO.Creating ISO image...
oscdimg -n -bc:\winpe2_x86\etfsboot.com c:\winpe2_x86\ISO c:\winpe2_x86\winpe2_x86.iso
ECHO.
Echo.Moving winpe.wim back to original location
move ISO\sources\boot.wim .\winpe.wim

The problem was that in the \ISO\Sources directory, a boot.wim file already existed. However, it was the original PE image that comes with WAIK (which bootmgr is looking for boot.wim in the Sources folder in the ISO image.) My script will move the modified winpe.wim image to \ISO\Sources, compile the ISO, then move it back. I was able to bring up the network and access hosts.

Jazkal

Mar 23 2007, 06:20 AM

I ended up having to open a ticket up with HP on the issue, I'll update here once I get a solution.

chrislynch

Mar 23 2007, 02:29 PM

I was able to get WinPE2 booting on a DL585 G1 and DL380G4 without incident. Did you follow the steps I outlined above? I do not believe tech support will assist you, as we do not officially support WinPE 2.0 until we release RDP with WinPE 2 support.

Feel free to PM me and I'll reply with my email address and we can converse via email.

Jazkal

Mar 23 2007, 02:50 PM

I sent you a PM.

I have WinPE v2.0 working on the following HP servers:

DL380-G5 (32 and 64 bit)
DL580-G5 (32 bit only, issues with 64 bit)
DL385-G1 (32 and 64 bit)
DL585-G1 (32 and 64 bit)
DL385-G2 (only tested 32 bit so far, works)
DL585-G2 (only tested 32 bit so far, doesn't work)

p4ntb0y

Mar 24 2007, 12:26 PM

@Jazkal

have you got the health driver loading with the DL380 G5?
I am trying to use winpe 2 for DL360 G5, ML350 G5 and the above but I can't get the HP tools to run properly ie conrep, and the acubin.

I had to go back to the winpe 2005 with wims but to use winpe 2 would be nice.

I was told that HP would not bother with winpe 2.0 until longhorn comes out, which is silly as its obvious that m$ are pushing for winpe 2.
:-(

Jazkal

Mar 24 2007, 12:55 PM

No, I have not tried the tools yet in WinPE2. I have a long list of Projects that I'm working on, and the HP tools aren't anywhere near the top of my long list.

But if you have success, I would like to hear about it, because I will end up having to reproduce what you find.

I hope HP at least has Beta drivers/software (that mostly work) by the time Longhorn launches, because we have to support it 100% on launch day.

chrislynch

Mar 24 2007, 07:32 PM

@p4ntb0y:

"I was told that HP would not bother with winpe 2.0 until longhorn comes out, which is silly as its obvious that m$ are pushing for winpe 2.
:-("

Once Longhorn has officially released, we should have the PSP, Insight Manager Agents, and tools for our SmartStart Scripting Toolkit. I haven't asked around, but I would not imagine official WinPE 2.0 support until we have a version of the SSSTK that supports WinPE 2. Keep in mind that Longhorn is just now coming out as an RC build, and not every vendor supports Longhorn on their servers. Our support for Longhorn, and quite frankly WinPE 2.0, is in Beta. WinPE 2 is bundled in the WAIK for Vista (and Longhorn when released) distribution.

For now, we only officially support WinPE 1.6 (WinPE 2005) with our SSSTK and Rapid Deployment Pack (RDP) solutions.

p4ntb0y

Mar 25 2007, 12:56 PM

@Jazkal

I keep you informed on what works and doesn't on the HP toolkit and winpe 2.0

I creating an offline dvd like the BDD SMS version so I test it with that.

I have not been able to make "sysmgmt service" run so I can't use the tools as it requires this service to run (But not 100% sure)

@chrislynch
Who ever did the documetation for the SSSTK needs a bit of a slap it allways seamed 90% complete saying that it works fine. I ve nearly solved the stupid restart after the diskpart section.

Is there any chance where I can test betas etc? I am part of a large IT Org.

Thanks for the response

mjviola

Apr 30 2007, 12:58 PM

Jazkal...

As you noticed already, v2.0 does not see the same devices as v1.6.

One of the biggest omissions that I see is the PCI to PCI Bridge (among others), which is most likely why you are not able to see the Broadcom NIC (or anything else on the PCI Bridge)...I'm working a case currently where we are not able to see the NIC or a fiber card...

You are correct; the issue seems to not be with the actual NIC driver, but with another device "up the chain". I am able to load WinPE 2.0 without any issues on the ML570 G4, which uses the same NC371i NIC as the DL585 G2.

I am currently working this issue and performing test in my lab...I will let you know what I find.

Cheers....
MJV

Jazkal

Apr 30 2007, 01:07 PM

That would be great, we are down to 2 final issues before we can roll out WinPE2 to our production systems. This issue is one, and the other is WinPE2 x64 not working right on the HP boxes.

mjviola

May 2 2007, 01:59 PM

Please give this workaround a try and let me know how it works.

1 - Open an elevated command prompt
2 - Type

bcdedit /set CONFIGACCESSPOLICY DISALLOWMMCONFIG

3 - Reboot

The NIC should now be seen by WinPE 2.0

Type this command to change back to normal settings (if needed):

bcdedit /set CONFIGACCESSPOLICY default

actionj

May 6 2007, 07:48 AM

hi guys,

i am in the same unfortunate situation..i can load the NIC drivers for the DL380G5 (NC373i) using broadcom's RIS drivers for the netxtreme II card. but, like in the post, winpe 2.0 cannot even see the embedded NC371i's. Has anyone succeeded yet ?

Jazkal

May 10 2007, 10:30 AM

No, I'm waiting for a fix from HP

Jazkal

Jun 5 2007, 06:52 AM

It looks like HP finally figured out what was wrong with the 585 G2.

http://h18004.www1.hp.com/products/servers...=reg_R1002_USEN

The firmware fix (beta) listed, does work on my tests with WinPE v2.0

p4ntb0y

Jun 5 2007, 05:13 PM

Hopefully they will release a new scripting toolkit for these.

However I better test to see if the toolkit can work ok with these drivers.

GCoop

Jun 14 2007, 09:44 AM

QUOTE (p4ntb0y @ Jun 5 2007, 07:13 PM)

Hopefully they will release a new scripting toolkit for these.

However I better test to see if the toolkit can work ok with these drivers.

Any luck getting the tools to work? I can boot to pe and load all the hardware drivers but cant get the tools to work.

My results so far:
The new HPDiscovery from the SSTK 1.7 gives some dll -1 info but appears to run and create the hardware file.

Have not trie ifhw to parse the discovery xml file.

v2.3 of statemgr included with SSTK 1.7 gives an error but outputs the saved variable state however when trying to read that variable it always returns a null value.

These are really the only tools i use so I have not tried to use any of the others. Any way to run exe's from PE 2.0 in compatability mode?

aaron818

Jun 14 2007, 03:01 PM

Do you have any documentation on what you did to get these models to work? I have not been able to get my DL385-G2 to work with network support.

QUOTE (Jazkal @ Mar 23 2007, 01:50 PM)

I sent you a PM.

I have WinPE v2.0 working on the following HP servers:

DL380-G5 (32 and 64 bit)
DL580-G5 (32 bit only, issues with 64 bit)
DL385-G1 (32 and 64 bit)
DL585-G1 (32 and 64 bit)
DL385-G2 (only tested 32 bit so far, works)
DL585-G2 (only tested 32 bit so far, doesn't work)

zorphnog

Jul 9 2007, 01:31 PM

@Jazkal: What did you do to get the DL380-G5 network support to work?

I've tried "peimg /inf=bxnd.inf mount\Windows". I've tried adding bxnd.inf to the windows\inf folder and the sys files to the windows\system32\drivers folder. Tried renaming the inf to netbxnd.inf. No luck what so ever.

Jazkal

Jul 9 2007, 01:45 PM

Are you using the Broadcom NetXtreme II - RIS drivers?

Just off the top of my head, that was the way to get Network working on my NetXtreme NIC's

zorphnog

Jul 9 2007, 02:02 PM

Nope. The cards show up as HP NC373i which are supposed to be covered in the beta drivers on that ftp site. I'll look into the NetExtreme II drivers though, who knows...

Jazkal

Jul 9 2007, 02:06 PM

Here is the devcon output on my devices for the DL380-G5

QUOTE

PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&2014205D&0&20F0: Base System Device
PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&2014205D&0&22F0: Base System Device
PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&2014205D&0&18F0: Video Controller (VGA Compatible)
PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&3028BA6E&0&0018: RAID Controller
PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&2014205D&0&24F0: Universal Serial Bus (USB) Controller
PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&2014205D&0&26F0: PCI Device
PCI\VEN_1166&DEV_0103&SUBSYS_00000000&REV_C2\4&110C88BD&0&00E1: PCI to PCI Bridge
PCI\VEN_1166&DEV_0103&SUBSYS_00000000&REV_C2\4&187919FE&0&00E0: PCI to PCI Bridge
PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_11\5&2EADD4B0&0&0000E0: Broadcom BCM5708C NetXtreme II GigE
PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_11\5&DE7916A&0&0000E1: Broadcom BCM5708C NetXtreme II GigE #2
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_D9\3&61AAA01&0&F0 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25D8&SUBSYS_00000000&REV_93\3&61AAA01&0&00 : PCI HOST Bridge
PCI\VEN_8086&DEV_25E2&SUBSYS_00000000&REV_93\3&61AAA01&0&10 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25E3&SUBSYS_00000000&REV_93\3&61AAA01&0&18 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25E5&SUBSYS_00000000&REV_93\3&61AAA01&0&28 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25E7&SUBSYS_00000000&REV_93\3&61AAA01&0&38 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&80 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&81 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&82 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F1&SUBSYS_00000000&REV_93\3&61AAA01&0&88 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F3&SUBSYS_00000000&REV_93\3&61AAA01&0&98 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F5&SUBSYS_00000000&REV_93\3&61AAA01&0&A8 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F6&SUBSYS_00000000&REV_93\3&61AAA01&0&B0 : PCI HOST Bridge
PCI\VEN_8086&DEV_25F8&SUBSYS_00000000&REV_93\3&61AAA01&0&20 : PCI to PCI Bridge
PCI\VEN_8086&DEV_25F9&SUBSYS_00000000&REV_93\3&61AAA01&0&30 : PCI to PCI Bridge
PCI\VEN_8086&DEV_2670&SUBSYS_00000000&REV_09\3&61AAA01&0&F8 : PCI to ISA Bridge
PCI\VEN_8086&DEV_2688&SUBSYS_31FE103C&REV_09\3&61AAA01&0&E8 : Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2689&SUBSYS_31FE103C&REV_09\3&61AAA01&0&E9 : Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_268A&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EA : Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_268B&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EB : Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_268C&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EF : Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2690&SUBSYS_00000000&REV_09\3&61AAA01&0&E0 : PCI to PCI Bridge
PCI\VEN_8086&DEV_2692&SUBSYS_00000000&REV_09\3&61AAA01&0&E1 : PCI to PCI Bridge
PCI\VEN_8086&DEV_269E&SUBSYS_31FE103C&REV_09\3&61AAA01&0&F9 : IDE Controller
PCI\VEN_8086&DEV_3500&SUBSYS_00000000&REV_01\4&276E5639&0&0010: PCI to PCI Bridge
PCI\VEN_8086&DEV_350C&SUBSYS_00000000&REV_01\4&276E5639&0&0310: PCI to PCI Bridge
PCI\VEN_8086&DEV_3510&SUBSYS_00000000&REV_01\5&36FA8587&0&000010: PCI to PCI Bridge
PCI\VEN_8086&DEV_3514&SUBSYS_00000000&REV_01\5&36FA8587&0&080010: PCI to PCI Bridge
PCI\VEN_8086&DEV_3518&SUBSYS_00000000&REV_01\5&36FA8587&0&100010: PCI to PCI Bridge
39 matching device(s) found.

This was pulled off WinPE 1.6, but it douldn't matter where the devcon scan was run.

p4ntb0y

Jul 9 2007, 03:12 PM

Just to confirm that I have used the Broadcom RIS driver and this works on a DL380 G5

Windows 2008 is just down the road so more support will be out soon been to my MS Partners windows 2008 comf

I spoke to the MVP there and he reckons that you be able to create your own winpe boot wim and there be more support nearer Nov time when it Windows 2008 ships...

So hopefully HP will jump on the wagon and sort the smart start scripting toolkit for winpe 2.0 which I reckon will actually work! depending on the not so good hp CHM'S/DOCS

Windows 2008 Core is so looking good but thats another topic.

zorphnog

Jul 10 2007, 06:52 AM

Yep. The Windows 2003 RIS drivers worked! I was looking and the only difference in the hwid is that mine was REV_12 instead of REV_11 which for some reason shows up as just "Ethernet Controller" as the descriptor. Thanks for the help.