Video Screencast Help

Ghost WinPE Intel Driver

Created: 07 Nov 2012 • Updated: 21 Nov 2012 | 22 comments
This issue has been solved. See solution.

I have been trying to get a Ghost WinPE boot disc to work that encompasses all of our PCs. I have been having problems getting the Intel drivers to work properly. Multicast sessions always fail. I have tried different versions of the Intel drivers off of their web site, but multicast continues to fail.

 

Does anyone have some ideas for me to try out?

Comments 22 CommentsJump to latest comment

EdT's picture

Multicast failures after a couple of minutes are normally due to IGMP snooping not being enabled on the network switches. Search this forum on IGMP and look for postings by Nigel Bree, one of the former Ghost developers, who has posted many times on multicasting issues and IGMP.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

MHammett's picture

I saw references to that, but multicast works fine when other drivers are used. I haven't checked the IGMP, but observation would lend itself to the switch not being the problem.

EdT's picture

Which Intel chipset are you having trouble with?  If it happens to be the 82579 chipset then search this forum on 82579 as there are many users who have had problems finding working drivers for this chipset and have posted working links when the correct drivers were found.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Meckron's picture

And, in regards to some of the dealings I've dealt with in regards to NIC drivers, make sure the driver pack you're downloading includes support for the specific NIC you're dealing with.  I recently went out and had to download three sets of Intel 82579 drivers to find that only one of the three sets actually included the correct hardware identifier/PCI-TAG for the NIC I was needing.  Once I had that and verified the HW ID was in the Ghost manifests, I had no issues.

MHammett's picture

While I scour the Earth looking for functional 82579LM drivers, could someone look over these? Again, I think they're fine as multicast seems to work for other chipsets.

 

 

 

Global IGMP Snooping configuration:

-------------------------------------------

IGMP snooping                : Enabled

IGMPv3 snooping (minimal)    : Enabled

Report suppression           : Enabled

TCN solicit query            : Disabled

TCN flood query count        : 2

Robustness variable          : 2

Last member query count      : 2

Last member query interval   : 1000

 

 

 

 

Vlan 700:

--------

IGMP snooping                       : Enabled

IGMPv2 immediate leave              : Disabled

Multicast router learning mode      : pim-dvmrp

CGMP interoperability mode          : IGMP_ONLY

Robustness variable                 : 2

Last member query count             : 2

Last member query interval          : 1000

MHammett's picture

I would like to note that I have downloaded three different Intel drivers from this site, all of which were claimed to work and none did.

 

I'm considering recommending that we leave Ghost behind and move to something else that works.

EdT's picture

Since Ghost is not the issue here, by your own admission, I suspect you will encounter similar problems with any imaging product that uses WinPE, if the necessary drivers are not present in the driver library.

Have you checked things like bios settings and any other hardware related options that might have a bearing on your ability to use the NIC port when not running a full windows O/S ?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

MHammett's picture

I'm not sure what in the BIOS would allow me to get an IP address from DHCP, but then prevent me from participating in a multicast session.

 

Tracking which of the 4 machines I'm sending to hasn't shown a pattern in which machine ends up with the successful session.

MHammett's picture

Will this command tell me what driver WinPE is using or what driver the installed Windows would use?

 

x:\ghost\GhDplyAw32.exe /eval /target=c:\Windows /ddb=d:\windrivers

burndtjammer's picture

Assuming you are working in the correct directories, yes.  Record the device id's for Missing Critical Drivers. You will then want to open the inf files of the drivers you think should work. Once open, ctrl+f and search for the deviced id/PID for a match to your DeployAnywhere eval results.  There are companies that make products to do the driver imports and deployment for you but ive never seen one work well. I will stand by ghost and deployanywhere any day to these products.

MHammett's picture

Well, I haven't a desire to use DeployAnywhere, just using it to pull device and vendor IDs as another verification attempt on what drivers are needed.

 

Is there a way to tell in WinPE what driver was used?

burndtjammer's picture

Check the BIOS for any hints on what the deivce is,download a driver for it and load it in to the PE database.  Unfortunately, if you dont know what the device is you're working with this can become a guessing game.  Downloading the latest intel driver directly from Intel rather than Dell or HP should be backwards compatible with most intel NIC's.

MHammett's picture

It appears as though the problem was that the Intel driver doesn't like me removing the USB key during the process. I always waited until the machine was "Waiting for GhostCast session" and pulled the key, moving to a new computer.

 

I made a second key and two machines booted. I'm going to go back and try the stock driver to see what happens there.

SOLUTION
MHammett's picture

Actually, it is working fine with version 17.04 drivers directly off of the Intel web site...  now that I'm using one USB key for each computer and leaving it in there.

 

Don't have to do this with Broadcom drivers. Oh well.

burndtjammer's picture

From the dells and HPs we've purchased over the last 2 years they've all been intel NIC's with Intel Chipsets.  Its been a while since ive seen a broadcom.  Intels drivers may be a PITA but as long as you keep your ddb current you shouldnt have an issue.

EdT's picture

I posted an article at: https://www-secure.symantec.com/connect/articles/readyutility-assist-identifying-plug-and-play-drivers some time ago, which I wrote as a handy tool to capture all plug and play device ID's and associated INF and driver information, on any new machine that came into the company. This report then provided me with all the information I needed to locate suitable drivers when created a company operating system image.  You may find this useful if you work with new hardware on a regular basis.

It does seem odd that you cannot pull your USB stick once WinPE has booted. It would suggest that there is still some running process that needs to access the key, or the key removal changes drive mappings in some way. It would be an interesting exercise to see if booting off a CD rather than a USB stick would show up the same issues.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

burndtjammer's picture

I took a look at the article you linked to. Looks very useful. will this run in PE or just the factory installed OS that has the drivers preloaded?

EdT's picture

It is intended to run on any fully configured operating system as the intention is to retrieve not just all the device ID's but the related INF and driver information. This will not be present under WinPE unless you have integrated every single device driver appropriate to the hardware you have booted.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

MHammett's picture

Maybe it has something to do with how I have my drive setup. It took a lot of monkeying around to get the custom stuff onto the USB key in a location where I could get them to work. I'd follow some guides on how to load things onto it, but they'd almost never work.

EdT's picture

When WinPE loads into memory from any boot media, it generally mounts onto the X: drive. However, the source media, eg the USB stick, remains on the drive letter it was initially booted from.  If you are running operations from WinPE which need to access the USB stick, you need to have some code in there to look for the "footprint" of the USB stick and apply the right drive letter to any calls.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

MHammett's picture

It would be nice if the Ghost Boot Wizard would just put the additional files onto X: instead of on the USB itself. I haven't been successful with opening the WIM myself. Plus any time you make a driver change, the changes you made would be erased.

EdT's picture

Editing the WIM is quite straightforward. Have a look at this article: https://www-secure.symantec.com/connect/articles/readyadventures-winpe

This takes you through the process of building your own WinPE solution using the same version of WinPE as in Ghost. You should be able to mount, edit, commit and unmount a WIM using this methodology.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.