Intel 82579LM and 82579V

peetz said:
Hi Telefragger,

please follow Chilly's instructions to find out the PCI ID of your NIC.
You can then use the "Advanced-edit"-mode of ESXi-Customizer to change the contents of the OEM.tgz file before it is applied to the ISO. Check the file /etc/vmware/simple.map to see whether it includes a mapping for your device ID. If not try to add it by copying and modifying an existing entry for the e1001e driver.

- Andreas
Click to expand...

Chilly said:
You downloaded *both* RAR files and extracted the OEM.tgz file out of the rar files properly correct? It is *possible* but unlikely that IBM has their own pci.id code. If they do, you'd have to add it to the pci.id of the oem.tgz

Do this for me please, boot up the system using the custom iso. Once you get to the install screen, press ALT-F1, that will get you into the console. By default the username is root and blank password. Once your logged in, run these commands in order and tell me what the output is for each.
Code: 
esxcfg-nics -l
Is anything listed here, if so what. After this command, run the next one;
Code: 
vmkload_mod e1001e
And then run this following command again, and let me know what, if anything is listed here, and what its PCI number is.
Code: 
esxcfg-nics -l

Once you try that, we can go from there :)
Click to expand...

for me..
first one had nothing..
second one brought up couldnt load module
third one nothing....
 
had to install xp on one so here is the ID

nic.jpg
 
The PCI ID 8086:1502 is already included in the simple.map file, but it looks like the driver does not work with this device.
What messages are logged in vmkernel.log when you try to load the module with "vmkload_mod e1001e. Press Alt-F12 on the console to switch to the logging screen. You can scroll up and down there with the cursor keys.
- Andreas
 
Chilly said:
You downloaded *both* RAR files and extracted the OEM.tgz file out of the rar files properly correct? It is *possible* but unlikely that IBM has their own pci.id code. If they do, you'd have to add it to the pci.id of the oem.tgz

Do this for me please, boot up the system using the custom iso. Once you get to the install screen, press ALT-F1, that will get you into the console. By default the username is root and blank password. Once your logged in, run these commands in order and tell me what the output is for each.
Code: 
esxcfg-nics -l
Is anything listed here, if so what. After this command, run the next one;
Code: 
vmkload_mod e1001e
And then run this following command again, and let me know what, if anything is listed here, and what its PCI number is.
Code: 
esxcfg-nics -l

Once you try that, we can go from there :)
Click to expand...

Yep of course I downloaded BOTH .RAR files as instructed!! :D

From what I've discovered... Windows XP (32-bit) is horrible at generating custom .ISO files from an OEM.tgz. Lesson learned.

After much frustration and reading--I present to you--ESXi 4.1U1:

~ # esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:00:19.00 e1000e Up 1000Mbps Full 44:37:e6:55:32:b0 1500 Intel 82579LM Gigabit Network Connection
~ #

I am a happy admin! :p
 
Just want to confirm Chilly and/or Peetz,
No one has successfully enabled these chips with 5.0 yet?
 
Hi Chilly,

I have a new system, HP rp5800, with an Intel 82579LM Gigabit Network adapter. I tried the ESXi-Customizer along with your 2 oem files..... and as I read in other posts that didn't work.

So, it will be nice when you have so graciously taken the time to create new ones. Thanks ahead of time!

- RickM :)
 
sloncek said:
I'm wondering if I could use this source code:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15817&ProdId=3299&lang=eng&OSVersion=Linux*&DownloadType=%0ADrivers%0A

and this VDDK:

http://downloads.vmware.com/d/details/vddk50_os_l/dHRAYnQlQGRiZHAlJQ==#drivers_tools

to compile a suitable driver. If so, can chilly or anyone else tell me how to do it so I can give it a shot?
Click to expand...

This is not the actual VDDK, the tar.gz just contains the open source archives VMWare uses and is required by the GPL or their licenses to provide downloads for.

I'm interested in getting a driver for the Intel 82579LM working on ESXi 5.0, preferably over PXE install.

I'm researching how to do this and can provide any help needed to Chilly/Petez. I have plenty of systems we can test on if needed.
 
All,

I think that it is not possible (or at least very difficult) to built an ESXi 5.0 compatible device driver without access to the open source code of the drivers that are shipped by VMware, and - more important - the modifications that were made to it by VMware
(Chilly: If you do not agree, and maybe have already made progress here, then please let us know).

As of today, VMware has not made the Open Source code of ESXi 5.0 available for public download. However, the GPL obliges them to provide access to the Open source code they used and the modifications they made to it.
Providing access does not necessarily mean making it available for public download ...

On the ESXi 5.0 install media there is a text file VMWARE-ESX-BASE-OSL.txt with instructions on how to get access to the source code (at the end of the text).
I have now followed these instructions and sent a request to [email protected].

I'm looking forward to the answer ... and will let you know how this works out.

- Andreas
 
It does contain ESXi 5.0 with all drivers that have been updated by VMware since the release of ESXi 5.0. These updated drivers are available as separate downloads here:
http://downloads.vmware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere/5_0#drivers_tools

And, no, there is no updated version of the e1000e driver in there ...

shortkud said:
Does anyone know what the vSphere Hypervisor ESXi 5.0 Driver Rollup 1 contains?

http://downloads.vmware.com/d/details/rollupiso_50_1/dHRAYnRoJSpiZHAlJQ==
Click to expand...
 
sloncek said:
VMware has finally released the source code:

https://download3.vmware.com/software/open-source/VMware-esx-public-source-5.0.0-434156.tar.gz

This thing contains the compile script as well. Does anyone know how to modify intel's source code, compile it and pack it into a .tgz?
Click to expand...

http://hardforum.com/showpost.php?p=1037937845&postcount=8

Your welcome to look into the code and do it yourself if you like. If you have any C programing skills I sure as hell won't refuse the help. :)

The only useful thing I can say is this, reverse engineer the code changes by comparing VMware's driver code to the "official" open source code of the same version its derived from. This advice applies for any driver people are looking to add support to.

In any case, I will post and update on my progress at the end of the weekend.
 
Hey Chilly-
Just following up to see if there was any new progress over the weekend.

Thanks for your work!
-David
 
First initial 82579LM custom driver compiled :D

Currently testing driver, no clue if it works or not yet. Might require further changes need to be made. I will update as progress is made.
 
Code: 
login as: root
Using keyboard-interactive authentication.
Password:
The time and date of this login have been sent to the system logs.

VMware offers supported, powerful system administration tools.  Please
see www.vmware.com/go/sysadmintools for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # vmware -v
VMware ESXi 5.0.0 build-469512
~ # vmware -l
VMware ESXi 5.0.0 GA
~ # vmkload_mod e1001e
Module e1001e loaded successfully
~ #

:cool:
 
Let us know if you need testers for this software! Been waiting for this one for a while as I want to get Win8 up on a VM. Hope you're doing swell!!
 
Any luck with the Intel 82579LM NIC drivers for ESXi 5.0?

I've been waiting for the oem.tgz drivers for the Intel 82579LM NIC as well. This is for a new system with no data so if you need a tester I'll be happy to help.
 
how much has the source code changed between VMware's version and intel's current one? Will is be sufficient to simply add the PCI ID of the 82579LM chip to the .map file?
 
sloncek said:
how much has the source code changed between VMware's version and intel's current one? Will is be sufficient to simply add the PCI ID of the 82579LM chip to the .map file?
Click to expand...

Not that simple, the inbox driver in ESXi does not support the 82579 PHY at all. VMware's driver is based off an older driver.

In any case, if my testing tonight goes well, I might be posting the first ESXi 5.0 version up tonight! :D
 
Chilly the oem.tgz that is linked in the OP should work with ESXi 4.1 and ESXi 4.1 Update 1 correct? Are there any instructions on how to use it with a PXE install?

I do the PXE install via NFS with a kickstart to customize.
 
Chilly said:
Not that simple, the inbox driver in ESXi does not support the 82579 PHY at all. VMware's driver is based off an older driver.

In any case, if my testing tonight goes well, I might be posting the first ESXi 5.0 version up tonight! :D
Click to expand...

Exciting! Thanks for all your hard work Chilly. Just in time for Thanksgiving break too :)
 
It will be up in 30 minutes or so, I'm just cleaning up the OEM.tgz file, and creating proper .map files.

Now, just a few hints ahead of time, the OEM.tgz which I will be uploading, should be used only with ESXi 5.0 and injected using the ESXi 5.0 Customizer by Peetz. My OEM.tgz for 5.0 designed around his method currently.
 
First release for ESXi 5.0, it may be buggy as hell, cause your system to crash, etc etc, so I provide it AS-IS, I take no responsibility for any damage, USE AT OWN RISK. This release is designed for use with Peetz ESXi Customizer ( http://esxi-customizer.v-front.de/ ).

Let me know if you have any issues, if your device isn't detected or whatever comments you want to throw my way. :)

Enjoy!
http://dl.dropbox.com/u/27246203/E1001E.tgz
 
You must log in or register to reply here.
Back
Top