Update:  for those who might find this later...  I was able to get this to work, thanks for the tip -- last time I tried using stock drivers (for the 6400 and 6410), I failed, so I didn't really think to try that this time.

For this system, you can grab Intel_825xx-Gigabit-Platform_A00_R291627.exe, extract it, and copy the contents of the subfolder XP-x86 to pebuilder\drivers\Net\.  I have several other drivers in there as well as the latest LAN DP.

Hopefully this helps somebody.

-Matt-

I love Dell...  With every single new product, even within the same family (eg, 6420 instead of 6410), they have to completely change out the ethernet chipset...  What a PIA...

Here we go again...

PCI\VEN_8086&DEV_1502&SUBSYS_04931028&REV_04


Trying to use BartPE.  Tried DP_LAN_wnt5_x86-32_1101.7z -- no such luck.  Any idea where I might find the drivers to suppor this adaptor?

-Matt-

3

(48 replies, posted in DriverPack LAN)

I still haven't had any luck with the Driverpacks on this, although I haven't tried the 10.07...  I added the Intel XP driver in in pebuilder\drivers\net -- and then went back to the prior 10.05 (current at the time, vs. the pre-release from @mr_smartepants listed above).  It works on the Latitude E6410 (Intel 82577LM), but I'm at a loss to explain how or why (and I was *sure* I tested it this way before, when i was was working on the Precision M4500, also an Intel 82577LM, which prompted my initial post).

Give that a try and see if it works...

-Matt-

4

(48 replies, posted in DriverPack LAN)

Still doesn't work, "Unable to install network adaptors".

Hopefully this chip will be better supported by Intel in the near future...  In the meantime, I guess my only option is disabling the on-board NIC and trying a PC-Card NIC -- I tried USB previously, and can't get that to work with BartPE either...  WI-FI works, but BartPE doesn't have wifi management, it doesn't seem like...  Failing that, its back to pulling the drive and imaging it from another machine.

Thanks very much for trying...

-Matt-

5

(48 replies, posted in DriverPack LAN)

I sto...  Borrowed a Latitude E6410 (from a company exec, no less), which has exactly the same Intel 82577LM ethernet chip (same exact hardware ID's from the device manager, all 4 lines, as the Precision M4500 that I don't have in front of me but which prompted me to start this thread).

It doesn't work with BartPE, same error, "Unable to install network adaptors".

I'm guessing Intel simply hasn't released an update that provides the WinPE drivers for this chip?  Why exactly does PE use different drivers anyway, that makes no sense to me, a linux guy...  :-p

6

(48 replies, posted in DriverPack LAN)

I'm pulling this down now...  The M4500 in question is on asignment at the moment, and won't be back to me until Thursday, I'll test it out then.

Thank you very much...

7

(48 replies, posted in DriverPack LAN)

Interestingly, the Precision M6500, which is in the same family as the M4500, has a Broadcom 57xx ethernet chip, which works great using the current LAN DP, whereas the M4500 that I'm having problems with (and a number of other newly released notebooks) has the Intel 82577LM that I haven't been able to make work...

Just thought I'd share...

8

(48 replies, posted in DriverPack LAN)

@mr_smartepants -- Thanks anyway, I'll stay sub'd to this thread in case something else comes up or there's an update...

Hi cdob -- where would those file(s) be in BartPE?

I was going to try turning off the DP plugin, and extracting the newest Intel drivers in drivers\Net -- I know I did that before, and it didn't help.

At this point I have to pull the drive and image it from another system, I can't wait any longer, d'oh...

9

(48 replies, posted in DriverPack LAN)

I noticed that a new LAN pack was released, so I tried using that (stock)...  No change.

extracted DP_LAN_wnt5_x86-32_10051.7z to a temporary folder.  I copied the .inf from <tempfolder>\D\L\I\RIS\e1k5132.zip\e1k5132.inf (NOTE change in path, you said RIS_INF but all I found was RIS) to <tempfolder>\D\L\I\e1k5132.inf, overwriting the one that was there before.  Created new DP_LAN_wnt5_x86-32_100601.7z containing the modified D\ and DriverPack_LAN_wnt5_x86-32.ini, and moved that into place alongside the old.  DPs_BASE UpdateChecker says "Where did you get that?" (hahah, nice touch).  slipstream'd, and re-built BartPE, no errors reported.

No love, BartPE reports "Unable to install network adaptors".

-Matt-

10

(48 replies, posted in DriverPack LAN)

I extracted the .inf from the ZIP you specified, I'm not sure what to do with it...  Can you provide more specific instructions?  I don't normally consider myself a NOOB, but when it comes to Win-PE, I don't have a lot of experience, I just click and giggle.  :-)

11

(48 replies, posted in DriverPack LAN)

Yes, correct, affirmative...  I'm not trying to use WLAN (although the WLAN pack does support the on-board controller, its just that bartpe seems to lack the ability to manage it).  I'm trying to get the gig-E ethernet working, which is the 82577LM controller.

12

(48 replies, posted in DriverPack LAN)

Not to be a pest, but any update to this?

13

(48 replies, posted in DriverPack LAN)

I have the most recent driverpacks, LAN 10.05, no dice.  It does see the Intel wi-fi card, but BartPE doesn't let me set wireless params such as SSID, WPA auth, etc, so that doesn't help.  Any diag info I can send you?

As far as the INF, I found the one to extract, but, being a noob, don't know where to copy it as the 'standard INF'.  Can you provide a bit more info?

14

(48 replies, posted in DriverPack LAN)

(post no longer relavant in this part of the thread)

15

(48 replies, posted in DriverPack LAN)

Newest batch of Dell laptops (Latitude E6500, Precision M4500 specifically) utilize this new Intel chip.  Specifically I want to get this working in BartPE / WinPE-32, but follows the hardware ID information from a Win-7 box using the same chip:

PCI\VEN_8086&DEV_10EA&SUBSYS_040C1028&REV_05
PCI\VEN_8086&DEV_10EA&SUBSYS_040C1028
PCI\VEN_8086&DEV_10EA&CC_020000
PCI\VEN_8086&DEV_10EA&CC_0200

Any workarounds would be much appreciated, hitting a brick-wall trying to get this going...

-Matt-