Latitude E6400 NIC Driver
Hi all,
I've downloaded what appears to be the latest NIC Driver (Intel 825xx Gigabit Platform LAN Network Device Driver, OEM Version 9.50.14.2, Version A00) but when i try to add this to my Win PE 2.1 automtation environment, it doesn't appear to recognise the NIC Driver. Instead, when i try to boot the Laptop into PXE Mode, i receive the following error messages:
Initializing Windows PE
Starting The network
Trying to install ms_mstcpip
done
Trying to install ms_netbios
.
done
The DHCP Client Service is starting
The DHCP Client Service service was started successfully
The TCP/IP netbios Helper service services starting
The TCP/IP netbios Service services was started successfully
Establishing network connections
Validating IP Address
Restarting DHCP client service retry 1
Restarting DHCP client service retry 2
Restarting DHCP client service retry 3
Restarting DHCP client service retry 4
Restarting DHCP client service retry 5
The computer continues to loop on Restarting DHCP client service retry after Validating IP Address.
After 19 attempts, system error 1231 has occurred.
Article ID 29615 (https://kb.altiris.com/display...=&catURL=&r=0.5223505) on the Altiris Website mentions this error & the fact that this is caused by an unsupported Network card, in this case, was the DELL Optiplex 755 but an updated driver is provided for this.
Has anyone come across a similar updated driver for the Dell Latitude E6400?
Download the NIC driver from Intel instead of Dell. That was how I got the E6400 and E6500 deployment job working.
What's is the model for the E6400 card?
Intel has so many different models in there?
Can you send me the link to intel drivers that you used on the E6400.
Thanks,
I downloaded the Intel suite of drivers. Where you add additional drivers to the Boot disk, you then select the appropriate one from the list. I think it was the 82567LM Giga adapter.... But please double check. The link to the driver suite is as follows:
http://downloadcenter.intel.co...ss-apac+dc_netw_driver
Thanks, i was able to figure out too. Thanks again.
Has anyone found what storage driver to use? I can get the e6400 to see the network but not the disk.
ok, this is driving me crazy today. We got our first E6400. I can't get it to work with WinPE. I added the driver from Intel but it still won't work. Was there any trick that you guys used to get it working?
Hi Anthony.
Is it the storage driver or the network driver that isn't working?
If it's the network driver, are you using the Vista driver (WinPe 2.x use Vista, not Xp drivers).
Duh! I should have known that. I was using the XP driver. Thanks jahmar!
ok, I must be missing something or I'm just stupid. I can't get it to add the driver for this card to my boot disk in 6.8 SP1 with the XP driver or 6.9 SP1 with the Vista driver. It looks like its adding it but it never shows up. I've tried the Dell driver and the Intel driver.
I just tried Linux and that seems to be working. Wish I knew what I was doing wrong with WinPE and DOS.
I can't say that I ever got it to work in DOS. It just forced me to scrap DOS (actually a good thing as Linux is faster). Never really had any desire to make WinPE work as it takes too long for it to load via PXE.
I've never had a problem with WinPE before. Its always imaged faster than Linux for me. The drivers for this laptop just refused to be added to WinPE.
Is the nic driver in the WinPe image?
If you boot with WinPe, stop the script (ctrl+c) when "Restarting DHCP client service retry 1" appear.
Do this (replace X: with your boot drive)
-----
X:
cd X:\windows\system32\drivers
dir e1y*.sys
-----
Is "e1y6032.sys" listed?
The problem seems to be that the driver isn't being added to the WinPE boot disk. It doesn't give an error and seems like its adding it but when I go back and look the driver isn't on the list.
Do the extracted files look something like this?
e1000msg.dll
E1y6032.CAT
e1y6032.din
E1y6032.inf
e1y6032.sys
NicCo26.dll
NicInE6.dll
I use this driver:
HP 6930p Nic
Try it. It's the same nic that Dell use. Just run the exe-file, select the folder where you want to extract the files and add them to Boot Disk Creator.
Nope. Still didn't work. The driver never gets added to the boot disk. Its very strange.
Anthony, is this issue happening on the 6.9 SP1 server, the 6.8 SP1 server, or both?
If it's happening in 6.9 SP1, have you applied the hotfix which resolves the issue of adding NIC and MSD drivers to WinPE? Here's a link to the kb article on the issue and hotfix:
https://kb.altiris.com/article...?article=44108&p=1
Hopefully this helps.
Its 6.9 SP1. Thanks for the link. I'll try it right now.
That did it. The driver added. Thanks Nick!
No problem. Glad I could help.
I racked my brain over the same issue for about four days before stumbling on that article.
I'm having a similar problem with the E6400. I downloaded the drivers from Intel (PRO2KXP_v13_4.exe), manually extracted them and added the e1y5132.inf (and all corresponding files) to a WinPE package. The drivers seemed to add fine, but when I run the EBW, it won't get past the "BOOTING PRODUCTION PARTITION" statement. According to Altiris Support, the correct driver should be VEN_8086&DEV_10F5, however this doesn't come as a part of the Intel bundle for the "Intel (R) 82567LM Gigabit Network" adapter. I have checked Dell's support site and Intel's support site and have not been able to find the correct driver to download. Anybody run into this?
BTW, I'm running DS 6.8 SP1 w/ WinPE 1.6. Thanks!
I'm also experiencing the
I'm also experiencing the same issues. We are running 6.9 SP1 and I cant find the download for 6.9 SP2.
Update: Called support, SP2 should be released soon, mean time use the patch on Altiris FTP for me.
I'm having difficulties with
I'm having difficulties with this also. I've follow Altiris KB 45286 and added the e1000e.ko and the ahci.ko drivers to the boot disk (moving the hard drive in the bios to AHCI). I also get a different message right after the pxelinux.cfg runs (Starting x86 Altiris Pre-boot Automation Enviroment...). The message says 0000:00:19:0: Failted to initialize MSI interrupts. Falling back to legacy interrupts.
It will then continue as normal and then sit at the /# prompt. Then after a minute or so it will reboot. This time it won't even start the PXE boot (menu prompt for PXE booting).
Would you like to reply?
Login or Register to post your comment.