Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Jazkal

HP DL585-G2 and WinPE v2.0

Recommended Posts

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

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

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".

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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:

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.

Share this post


Link to post
Share on other sites

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

makeiso.cmd:

@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.

Edited by chrislynch

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

@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.

:-(

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...