Has anyone been able to get network / SAS drivers for an HP DL160 G6 to work with Bart PE? I'm trying to build a network boot disk for this system.
So far I have tried putting ALL of the drivers from the HP Easy Set-up CD into both the C:\pebuilder310\drivers\Net and SCSIAdapter folders.
I've tried downloading all the mass storage drivers and the Network Drivers (Windows 2003 Server) from HP's website and adding them to the corresponding C:\pebuilder310\drivers\ directory.
I'v downloaded and copied Driver Packs from DriverPacks.net without any luck either.
I also tried downloading drivers from Intel's website.
Every time I boot form the BartPE disk I am unable to see the local drives and I get an "unable to install driver" error message.
The Network driver that my 2008Server installation sees is the following:
W2k8 driver cp010296
NC-Series Intel N1QDriver for Windows Server 2008 x64 editions
In "properties" menu it is listed as:
HP NC362i Integrated DP Gigabit Server Adapter
If any one can help me out with this issue I would appreciate it!
Thank You
Full Version: Bart PE Drivers for an HP DL 160 G6
Have you run infCacheBuild or looked at the posting Adding drivers to BartPE?
Thread moved to the Bart PE forums.
Thread moved to the Bart PE forums.
QUOTE (Ed_P @ Nov 3 2009, 12:34 AM) 
Have you run infCacheBuild or looked at the posting Adding drivers to BartPE?
Thread moved to the Bart PE forums.
Thread moved to the Bart PE forums.
Sorry it took me so long to respond! I checked my post for a while saw that there weren't any replies and I assumed my post turned stale! A friend of mine lent me a bartpe disk he had built and it turns out it a ProLiant DL160 G6 will boot to this disk as long as I don't have RAID enabled in the system BIOS. I have to configure the BIOS to use "compatibility" mode otherwise the system will blue screen.
That said I am stil trying to get a boot disk to work with the system even when it is in RAID mode. I copied all the (what I think are necessary) drivers from the HP "Easy Set-up CD" to the corresponding "Net" and "SCSIAdapter" folders. I then ran the "infCacheBuild" you were talking about. I made an ISO, burnt a disk, was excited to see my system successfully boot without blue screening, and then I find out my network drivers didn't load, and I can't see any local drives :-(
Hi mwheat
you have not said whether you are building with source files = Win XP or Win 2003 and what service pack level
I think driver pack net drivers are mainly for XP not 2003
you need to find the F6 floppy drivers for your server (if no floppy drive exists) they go in drivers\SCSIAdapter\xxx
(Or on a floppy disk, if the floppy drive exists)
even if you find the correct drivers, if they support both 32 & 64 bit OS & drivers the inf file may need to be edited before pebuilder can process them correctly
(sorry I cant be more specific but if you post the first 20 or so lines an expert can show you the changes needed)
you are probably going to need to use Win 2003 OS & drivers for RAID & NIC
(unless Win 2000 server drivers are available and they may work with XP)
regards
Mike Barnes
you have not said whether you are building with source files = Win XP or Win 2003 and what service pack level
I think driver pack net drivers are mainly for XP not 2003
you need to find the F6 floppy drivers for your server (if no floppy drive exists) they go in drivers\SCSIAdapter\xxx
(Or on a floppy disk, if the floppy drive exists)
even if you find the correct drivers, if they support both 32 & 64 bit OS & drivers the inf file may need to be edited before pebuilder can process them correctly
(sorry I cant be more specific but if you post the first 20 or so lines an expert can show you the changes needed)
you are probably going to need to use Win 2003 OS & drivers for RAID & NIC
(unless Win 2000 server drivers are available and they may work with XP)
regards
Mike Barnes
As mbarns already said first witch os source you use? For BartPE it will be XP or Win Server 2003. I guess you use last one.
For HP ProLiant DL160 G6 Server series & M$ Win Server 2003 here is dl. you need. Here is appropriate SATA RAID Controller Driver (cp010928.exe).
In drivers\SCSIAdapter create folder (for ex. HP_DL_160_G6, open cp010928.exe with WinRAR and expand it in new created folder.
If you use core BartPE next important step is to add / use post processing infCacheBuild routine. Make test build and try access your raid array.
If you're still have problems with access to the data see whether there is a "HpAHCIsr" service was launched and working. If not, make a plugin in which will only be one inf file with reg keys related to the mentioned service. You need to expand data from reall working os (M$ Win Server 2003). Just for example here is part of Avira AVP8 inf file (AVP8 plugin) where you can see the settings and start for the AVGIO service:
For network controller first you need to determine witch one you have, on support page is 9 possible options. The solution is similar to the previous case just put necessary files in drivers\Net\xxx folder.
I hope this will help you.
For HP ProLiant DL160 G6 Server series & M$ Win Server 2003 here is dl. you need. Here is appropriate SATA RAID Controller Driver (cp010928.exe).
In drivers\SCSIAdapter create folder (for ex. HP_DL_160_G6, open cp010928.exe with WinRAR and expand it in new created folder.
If you use core BartPE next important step is to add / use post processing infCacheBuild routine. Make test build and try access your raid array.
If you're still have problems with access to the data see whether there is a "HpAHCIsr" service was launched and working. If not, make a plugin in which will only be one inf file with reg keys related to the mentioned service. You need to expand data from reall working os (M$ Win Server 2003). Just for example here is part of Avira AVP8 inf file (AVP8 plugin) where you can see the settings and start for the AVGIO service:
CODE
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO","NextInstance", 0x00000001
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Service","avgio"
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Legacy", 0x00000001
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","ConfigFlags", 0x00000000
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Class","LegacyDriver"
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","ClassGUID","{8ECC055D-047F-11D1-A537-0000F8753ED1}"
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","DeviceDesc","avgio"
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Capabilities", 0x00000000
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000\Control","*NewlyCreated*", 0x00000000
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000\Control","ActiveService","avgio"
0x4, "ControlSet001\Services\avgio","Type", 0x00000001
0x4, "ControlSet001\Services\avgio","Start", 0x00000003
0x4, "ControlSet001\Services\avgio","ErrorControl", 0x00000001
0x2, "ControlSet001\Services\avgio","ImagePath","\??\B:\Programs\AVP8\avgio.sys"
0x1, "ControlSet001\Services\avgio","DisplayName","avgio"
0x7, "ControlSet001\Services\avgio","DependOnService","FltMgr"
0x7, "ControlSet001\Services\avgio","DependOnGroup"
0x1, "ControlSet001\Services\avgio\Enum","0","Root\LEGACY_AVGIO\0000"
0x4, "ControlSet001\Services\avgio\Enum","Count", 0x00000001
0x4, "ControlSet001\Services\avgio\Enum","NextInstance", 0x00000001
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Service","avgio"
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Legacy", 0x00000001
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","ConfigFlags", 0x00000000
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Class","LegacyDriver"
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","ClassGUID","{8ECC055D-047F-11D1-A537-0000F8753ED1}"
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","DeviceDesc","avgio"
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000","Capabilities", 0x00000000
0x4, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000\Control","*NewlyCreated*", 0x00000000
0x1, "ControlSet001\Enum\Root\LEGACY_AVGIO\0000\Control","ActiveService","avgio"
0x4, "ControlSet001\Services\avgio","Type", 0x00000001
0x4, "ControlSet001\Services\avgio","Start", 0x00000003
0x4, "ControlSet001\Services\avgio","ErrorControl", 0x00000001
0x2, "ControlSet001\Services\avgio","ImagePath","\??\B:\Programs\AVP8\avgio.sys"
0x1, "ControlSet001\Services\avgio","DisplayName","avgio"
0x7, "ControlSet001\Services\avgio","DependOnService","FltMgr"
0x7, "ControlSet001\Services\avgio","DependOnGroup"
0x1, "ControlSet001\Services\avgio\Enum","0","Root\LEGACY_AVGIO\0000"
0x4, "ControlSet001\Services\avgio\Enum","Count", 0x00000001
0x4, "ControlSet001\Services\avgio\Enum","NextInstance", 0x00000001
For network controller first you need to determine witch one you have, on support page is 9 possible options. The solution is similar to the previous case just put necessary files in drivers\Net\xxx folder.
I hope this will help you.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.