Intel,Altiris Group

 Hey all,


We have been using the Altiris boot disk (WinPE) method of imaging computers.  It's been pretty flawless up until recently.  For some reason we are having a very difficult time getting the "Intel(R) 82567LM Gigabit Network Connection" driver to load properly.  


We keep getting the "Retrying DHCP" error over and over, as it seems it's just not recognizing the card.  I've located the driver, and have installed it during the Boot Disk Creation process, but still it just keeps failing on DHCP.

Has anyone else run into this?  Is there some additional information I can provide that would make troubleshooting this issue easier?  I've tried downloading directly from Intel, but that hasn't helped either.  


We have two different models of computers that use this driver.  Dell's E6400s, and Toshiba's M750, so this is definately putting a hurt to us.

Thanks in advance for any information you can provide.

Jay

I have the same issue with a Broadcom driver. no matter what I do it won't load the driver. I boot into WinPE and get the DHCP restarting services. If I cancel out of this and browse the drivers folder it can see the B57w32.inf but I believe that the code for my model of NIC is missing from the inf file. yours may be the same. Run Devcon on the machine in windows to get the vendor class ID and see if it matches the .inf file for your driver.

Not sure if this will help, but based in past experience drivers for WinPE 2.1 could be from 3 different sources.
1. Vista Drivers
2. WIndows 2008 Drivers
3. Manufacturer creates a RIS driver for WIndows 2008

So play with it and hopefully it will work for u.

nelo

I had the same issue and got mine resolved, here's how.

Go to the intel website located here: http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=3003&OSFullName=&lang=eng&strOSs=156&submit=Go!

Select the driver download, it should be called "PROVISTA32_v14_0.exe".

Extract the executable using Winzip or WinRAR so you have the 5 folders and 3 other files that come out of the executable that we downloaded. The folder we are interested in is called "PRO1000".

Get your WinPE 2.1 image opened up in PXE Config, and choose to edit it.

Hit the back button and go to Step #2 of 12 in the Boot Disc Creator process.

Hit "Have Disk", Then hit Browse and select the PRO1000 folder we extracted earlier.

This should list 5 .INF files, select "e1y6032.inf" and hit open.

It might ask you to click ok to confirm the addition of "unsupported" drivers go ahead and OK this.

You should now see a list of devices that this driver will cover, at the very top my Intel (R) 82567LM Gig adapter is listed.

You can then hit OK and refresh to refresh the drivers list, it should increase by approx. 4 drivers.

In the driver list you can click on "device" heading to arrange the Device ID's in alphabetical order, you can scroll down and verify that the device 10F5 is listed, this is the one we need.

If you can't scroll through the drivers list, uncheck "auto detect drivers" but be sure you check it back and then just continue on through the rest of the 12 steps, this should fix your problem with restarting DHCP service or the 1060 service not installed errors.

For your information I think the Intel drivers package "PRO2KXP_v14_0.exe" from Intel seems bug for this card using Bootdiskcreator...
When you use WinPE 1.6 (or load XP drivers) => we just missing the P&P enumeration for PCI\VEN_8086&DEV_10F5.
It is OK with VISTA...

When want to "add drivers" , devices 10CC, 10CD, 10CE, 10E5 loading correctly using those Xp drivers for WinPE 1.6, but not for 10F5... :-(

And when booting, network failed "cycle requesting dhcp"

It is really curious because if I use "DS6.9/Tool/DeployAnyWhere to add the same drivers, the manifest seems OK:

{
"Intel82567LM" = {
class = network,
drivers = ({
path = "Intel82567LM\\e1y5132.inf",
devices = {
0x8086 = {
0x10bf = (0x11179 0x10bf8086),
0x10cb = (0x11179 0x10cb8086),
0x10cc = (0x10cc8086 0x10cc8086 0x10cc8086),
0x10cd = (0x10cd8086 0x10cd8086 0x10cd8086),
0x10ce = (0x10ce8086 0x10ce8086 0x10ce8086),
0x10e5 = (),
0x10f5 = (0x11179 0x10f58086)
}
},
os = ("XP" "X64_XP" "X64_2003" "X64_VISTA" "X64_2008")
}),
internal = 0,
selected = 0
}
}

Yes: I am last updated SP2 DS 6.9...  ;-)