View unanswered posts | View active topics It is currently Wed Aug 23, 2017 1:27 pm



Reply to topic  [ 197 posts ]  Go to page Previous  1 ... 7, 8, 9, 10, 11, 12, 13 ... 20  Next
 Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC) 
Author Message

Joined: Fri Apr 22, 2011 4:59 am
Posts: 30
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Code:
Apr 24 01:42:40 vmkernel: 0:00:00:15.084 cpu5:4819)Loading module e1001e ...
Apr 24 01:42:40 vmkernel: 0:00:00:15.085 cpu5:4819)Elf: 2187: <e1001e> provides name-space <esx:nover>
Apr 24 01:42:40 vmkernel: 0:00:00:15.085 cpu5:4819)Elf: 1612: <e1001e> : R_X86_64_32 relocation(s) ignored
Apr 24 01:42:40 vmkernel: 0:00:00:15.086 cpu5:4819)module heap : Initial heap size : 102400, max heap size: 5750784
Apr 24 01:42:40 vmkernel: 0:00:00:15.086 cpu5:4819)module heap vmklnx_e1000e: creation succeeded. id = 0x4100b4000000
Apr 24 01:42:40 vmkernel: 0:00:00:15.086 cpu5:4819)module skb heap : Initial heap size : 524288, max heap size: 23068672
Apr 24 01:42:40 vmkernel: 0:00:00:15.086 cpu5:4819)module skb heap : creation succeeded
Apr 24 01:42:40 vmkernel: 0:00:00:15.086 cpu5:4819)<6>Intel(R) PRO/1000 Network Driver - 1.3.10a-NAPI
<snip>
Apr 24 01:42:41 vmkernel: 0:00:00:15.955 cpu1:4819)Mod: 4163: Initialization of e1001e succeeded with module ID 30.
Apr 24 01:42:41 vmkernel: 0:00:00:15.955 cpu1:4819)e1001e loaded successfully.
Attachment:
Capture1.PNG
Capture1.PNG [ 5.7 KiB | Viewed 56581 times ]


BOO-YAH!

I had to make a few code changes to get it to load completely. I worked around the problem, rather then fixing it directly. I would love to get a proper fix in, so a fresh set of eyes are welcome(source code without workaround provided above).

In the end, I had to regress 6 lines of code(vmalloc_node, I went back to using an older method of vmalloc used in 1.1.19), and remove 8 lines(_kc_print_hex_dump, its used when an adapter is reset to dump the buffer for debugging purposes, so for most people, I felt safe to get rid of it). Other than that and the required esxi/vmkernel centric changes required, its 1.3.10a goodness.

Having said that, its HOT off the presses, it may be buggy as hell, cause your system to crash, etc etc, so I provide it AS-IS.I tried to put in as many pci.id's, but might of missed a few. Anything 1.3.10a supports, this driver should work with as well. All that might need to done is to modify/create your own simple.map/pci.id.

Let me know if you have any issues, if your device isn't detected or whatever comments you want to throw my way. OEM.tgz file is provided in a spilt rar file below.

Enjoy! :D

[EDIT]Fixed simple.map to include 8086:1503 Intel 82579V - No other changes - No need to re-download unless you don't know how to edit simple.map yourself and need the 82579V support.

[EDIT-2]Updated simple.map and pci.ids using latest versions from 4.1u1

[EDIT-3]Updated simple.map and pci.ids with additional data(8086:0000 sub-vendor for 82579V)


Attachments:
oem.part1.rar [1.95 MiB]
Downloaded 16018 times
oem.part2.rar [911.7 KiB]
Downloaded 14283 times


Last edited by Chilly on Thu Apr 28, 2011 1:45 am, edited 3 times in total.

Sat Apr 23, 2011 10:33 pm
Profile

Joined: Fri Apr 10, 2009 3:34 pm
Posts: 39
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
pfff, trying to get this working. But allready made my ESXi installation unbootable!

Using a Q67 motherboard, so I use 4.1u1 which has support for it's AHCI storage controller natively.

But I have never used the oem.tgz method. So just replaced it. Bad bad bad. ;)

Have used the .vib installer files. But I guess it isn't possible to provide it in that format? Can't seem to find a good guide how to edit your oem.tgz file when ESXi is installed already. Using remote connections so booting a graphical linux environment isn't working either... Damn!!


Sun Apr 24, 2011 4:48 pm
Profile

Joined: Wed Apr 20, 2011 1:08 pm
Posts: 3
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Awesome - thank you Chilly. Worked great for my Intel DP67BA - added 8086:1503 to simple.map for 82579V
Putting a few VMs on it now to see how it fares... thanks again.

EDIT:
Whitebox specs here
Big thanks to Chilly for the driver and HUGE thanks to Dave (and the mods) for an awesome resource here at vm-help.com


Sun Apr 24, 2011 6:44 pm
Profile

Joined: Fri Apr 22, 2011 4:59 am
Posts: 30
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Quindor wrote:
But I have never used the oem.tgz method. So just replaced it. Bad bad bad. ;)

Have used the .vib installer files. But I guess it isn't possible to provide it in that format? Can't seem to find a good guide how to edit your oem.tgz file when ESXi is installed already. Using remote connections so booting a graphical linux environment isn't working either... Damn!!
Don't know how to create vib files, as far as I can tell it requires the DDK, which I don't have access to.

As for using the oem.tgz file on an already installed instance, upload and replace the oem.tgz somehow to the /bootbank and /bootbankalt folders in the esxi install. If you plug the esxi system drive directly into a Linux machine, these folders will show up as partitions "hypervisor1" and hypervisior2". Thats what I did actually while dev testing the driver(plug usb key into linux machine and replaced the oem.tgz file in hypervisor1 and 2 paritions).

Otherwise, the instructions at http://www.vm-help.com/esx40i/customize_oem_tgz.php should work for new installs.

[EDIT] If you enable SSH temporaly, you should be able to connect via SCP (using something like WinSCP) and upload the file(oem.tgz to bootbank and bootbankalt) that way! I just tried it myself and it worked!


Last edited by Chilly on Sun Apr 24, 2011 11:34 pm, edited 1 time in total.



Sun Apr 24, 2011 11:10 pm
Profile

Joined: Fri Apr 22, 2011 4:59 am
Posts: 30
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
wildblue wrote:
Awesome - thank you Chilly. Worked great for my Intel DP67BA - added 8086:1503 to simple.map for 82579V
Putting a few VMs on it now to see how it fares... thanks again.

EDIT:
Whitebox specs here
Big thanks to Chilly for the driver and HUGE thanks to Dave (and the mods) for an awesome resource here at vm-help.com

Whoops, I added it to pci.id, but made a typo in the simple.map file. :oops:

I'll fix it and upload a new copy with fixed simple.map file so others don't need to fix it manually.

[EDIT] Fixed! Uploaded new oem.tgz file with the fixed simple.map, check my original post!


Last edited by Chilly on Mon Apr 25, 2011 10:55 am, edited 2 times in total.



Sun Apr 24, 2011 11:21 pm
Profile

Joined: Fri Apr 10, 2009 3:34 pm
Posts: 39
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Wooohoo, after several hours of figuring this out. I have manged to get it to work!

What I did is boot ESXi with normal oem.tgz. Then copy simple.map and pci.ids to a separate folder in /bootbank

Then, boot a linux distro live CD. Copy the oem.tgz into the separate folder and make the necessary changes in there. Using the simple.map and pci.ids which you got and copied during the ESXi boot. Adding the .o file, etc.

After that, reboot into ESXi again. And replace the stock oem.tgz with the edited one from the separate directory and reboot again. After this, everything should work as intended.

Since I run from USB, I can use a seperate system to edit. All the scripts and other guides would NOT work for me with 4.1u1! No clue why. Also the default oem.tgz does not have a simple.map or pci.ids in there! You need to fetch it from a running system first.


Mon Apr 25, 2011 10:42 am
Profile

Joined: Wed Mar 18, 2009 1:32 pm
Posts: 455
Location: Sweden
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Quindor wrote:
Also the default oem.tgz does not have a simple.map or pci.ids in there! You need to fetch it from a running system first.


Yes it's empty, you need a oem file from this or some other site or copy the files from a running system

_________________
Dovie'andi se tovya sagain,



Mon Apr 25, 2011 10:48 am
Profile WWW

Joined: Fri Apr 22, 2011 4:59 am
Posts: 30
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Quindor wrote:
Wooohoo, after several hours of figuring this out. I have manged to get it to work!

What I did is boot ESXi with normal oem.tgz. Then copy simple.map and pci.ids to a separate folder in /bootbank

Then, boot a linux distro live CD. Copy the oem.tgz into the separate folder and make the necessary changes in there. Using the simple.map and pci.ids which you got and copied during the ESXi boot. Adding the .o file, etc.

After that, reboot into ESXi again. And replace the stock oem.tgz with the edited one from the separate directory and reboot again. After this, everything should work as intended.

Since I run from USB, I can use a seperate system to edit. All the scripts and other guides would NOT work for me with 4.1u1! No clue why. Also the default oem.tgz does not have a simple.map or pci.ids in there! You need to fetch it from a running system first.

Awesome! So you used my simple.map and pci.id from my oem.tgz file then? If you didn't, did you make sure to modify it to include the pci ids of your nic into them? This is important, otherwise esxi won't load the driver automatically since it won't detect the NIC!

Let me know if your esxi install detects the NIC, your post was a little confusing, and if so... Glad to hear you've got it working! :D


Mon Apr 25, 2011 10:52 am
Profile

Joined: Fri Apr 10, 2009 3:34 pm
Posts: 39
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Ah, no. Using your oem.tgz resultated in my system losing my AHCI storage controller. I figure this is because you are not running 4.1u1 or your simple.map file is from a different/older version.

So I had to install a "virgin" system en get the original files and I editted those.

I did not need to add it to the pci.ids because the NIC is listed in there. Probably because of the recent version! So only simple.map and .o file, .xml file and .mf file.

As promised I did some iperf tests!

Server Windows 2k8 R2 vmxnet3 (using e1001 with 82579LM)
Client Windows 7 intel 82567V-2

Code:
D:\Users\Quindor\Downloads>iperf -c quinftp.quindorian.lan -w 256KB
------------------------------------------------------------
Client connecting to quinftp.quindorian.lan, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[316] local 10.10.128.6 port 56284 connected with 10.10.128.254 port 5001
[ ID] Interval       Transfer     Bandwidth
[316]  0.0-10.0 sec  1.10 GBytes   940 Mbits/sec

So, as you can see this performs very well. Using 64KB blocks still gives you maximum bandwidth. Go lower then that and the bandwidth starts to drop a bit, but that isn't unusual.


Code:
D:\Users\Quindor\Downloads>iperf -c quinftp.quindorian.lan -w 256KB -d
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
------------------------------------------------------------
Client connecting to quinftp.quindorian.lan, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[376] local 10.10.128.6 port 56276 connected with 10.10.128.254 port 5001
[392] local 10.10.128.6 port 5001 connected with 10.10.128.254 port 49286
[ ID] Interval       Transfer     Bandwidth
[392]  0.0-10.0 sec  1.03 GBytes   883 Mbits/sec
[376]  0.0-10.0 sec  1.06 GBytes   906 Mbits/sec

This was a full-duplex test. It needs more then 64KB blocks to get the full bandwidth, but again, that is not unusual either.

So all is well according to these simple tests. I have started to use the NIC as the main NIC to see how well it behaves. If there is any trouble, I will let you know.

Thank you VERY much for this driver and all the help! :D


Mon Apr 25, 2011 12:02 pm
Profile

Joined: Fri Apr 22, 2011 4:59 am
Posts: 30
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Quindor wrote:
Ah, no. Using your oem.tgz resulted in my system losing my AHCI storage controller. I figure this is because you are not running 4.1u1 or your simple.map file is from a different/older version.

Ahhh, I'm actually using 4.1u1 as well actually, but you are correct, the simple.map file I'm using is from an earlier version. Information like this is great! Its not related to my driver, but I shall go and update the simple.map once again, ensuring that I use the 4.1u1 version, so that others don't encounter the same issue as you did.

Quindor wrote:
As promised I did some iperf tests!

Server Windows 2k8 R2 vmxnet3 (using e1001 with 82579LM)
Client Windows 7 intel 82567V-2

Code:
D:\Users\Quindor\Downloads>iperf -c quinftp.quindorian.lan -w 256KB
------------------------------------------------------------
Client connecting to quinftp.quindorian.lan, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[316] local 10.10.128.6 port 56284 connected with 10.10.128.254 port 5001
[ ID] Interval       Transfer     Bandwidth
[316]  0.0-10.0 sec  1.10 GBytes   940 Mbits/sec

So, as you can see this performs very well. Using 64KB blocks still gives you maximum bandwidth. Go lower then that and the bandwidth starts to drop a bit, but that isn't unusual.


Code:
D:\Users\Quindor\Downloads>iperf -c quinftp.quindorian.lan -w 256KB -d
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
------------------------------------------------------------
Client connecting to quinftp.quindorian.lan, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[376] local 10.10.128.6 port 56276 connected with 10.10.128.254 port 5001
[392] local 10.10.128.6 port 5001 connected with 10.10.128.254 port 49286
[ ID] Interval       Transfer     Bandwidth
[392]  0.0-10.0 sec  1.03 GBytes   883 Mbits/sec
[376]  0.0-10.0 sec  1.06 GBytes   906 Mbits/sec

This was a full-duplex test. It needs more then 64KB blocks to get the full bandwidth, but again, that is not unusual either.

Good to hear the drivers working well! Thank you for these tests!

Quindor wrote:
So all is well according to these simple tests. I have started to use the NIC as the main NIC to see how well it behaves. If there is any trouble, I will let you know.

Thank you VERY much for this driver and all the help! :D

You are most welcome! I'm going to go update the simple.map file(again :lol: ) now and re-upload the oem.tgz to my original post.

[EDIT] Updated! Uploaded new oem.tgz file with the updated simple.map, check my original post!


Mon Apr 25, 2011 1:38 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 197 posts ]  Go to page Previous  1 ... 7, 8, 9, 10, 11, 12, 13 ... 20  Next

Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.