View unanswered posts | View active topics It is currently Thu Oct 17, 2019 7:46 am



Reply to topic  [ 17 posts ]  Go to page 1, 2  Next
 Intel 82578DM [Server Platform SR1630GP] custom oem.tgz 
Author Message

Joined: Mon Nov 30, 2009 6:06 pm
Posts: 4
Reply with quote
Post Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Hi,

I've modified oem.tgz so that Intel 82578DM is listed in lspci - I've edited simple.map and pci.ids. Unfotunately NIC is not seen by vSphere client and other VM tools. I suppose it's due to e1000e version used in ESXi (208167). Could anyone build/help me build newest e1000e drivers?

Here is my lspci:
00:00.00 Bridge: Intel Corporation
00:08.00 Generic system peripheral: Intel Corporation
00:08.01 Generic system peripheral: Intel Corporation
00:08.02 Generic system peripheral: Intel Corporation
00:08.03 Generic system peripheral: Intel Corporation
00:16.00 Generic system peripheral: Intel Corporation
00:16.01 Generic system peripheral: Intel Corporation
00:25.00 Network controller: Intel Corporation 82578DM Gigabit Network Connection vmnic1
00:26.00 Serial bus controller: Intel Corporation
00:28.00 Bridge: Intel Corporation
00:28.04 Bridge: Intel Corporation
00:28.06 Bridge: Intel Corporation
00:28.07 Bridge: Intel Corporation
00:29.00 Serial bus controller: Intel Corporation
00:30.00 Bridge: Intel Corporation 82801BA/CA/DB/EB PCI Bridge
00:31.00 Bridge: Intel Corporation
00:31.02 Mass storage controller: Intel Corporation Ibex Peak 6 port SATA AHCI Controller vmhba0
00:31.03 Serial bus controller: Intel Corporation
02:00.00 Network controller: Intel Corporation 82574L Gigabit Network Connection vmnic0
03:00.00 Display controller: Matrox Graphics, Inc. MGA G200e Pilot ServerEngines (SEP1)
255:00.00 Bridge: Intel Corporation
255:00.01 Bridge: Intel Corporation
255:02.00 Bridge: Intel Corporation
255:02.01 Bridge: Intel Corporation
255:03.00 Bridge: Intel Corporation
255:03.01 Bridge: Intel Corporation
255:03.02 Bridge: Intel Corporation
255:03.04 Bridge: Intel Corporation
255:04.00 Bridge: Intel Corporation
255:04.01 Bridge: Intel Corporation
255:04.02 Bridge: Intel Corporation
255:04.03 Bridge: Intel Corporation
255:05.00 Bridge: Intel Corporation
255:05.01 Bridge: Intel Corporation
255:05.02 Bridge: Intel Corporation
255:05.03 Bridge: Intel Corporation


Tue Dec 01, 2009 2:18 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Have you tried ESXi 4 Update 1?

_________________
Dave Mishchenko
VMware vExpert 2009-2013
Image
Now available - VMware ESXi: Planning, Implementation, and Security
Also available - vSphere Quick Start Guide


Tue Dec 01, 2009 8:59 pm
Profile

Joined: Mon Nov 30, 2009 6:06 pm
Posts: 4
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Yes, as I said, build 208167 is ESXi 4.0 U1.

Odd thing is i Can share it thanks to VT-d, I have not tried if it actually works, but I suppose, that the drivers would be on VM's side than, so it could. I use second NIC for Vyatta DSL modem so it's not very demanding on NIC, but it's some kind of solution. Also additional NIC is a no-go, since it's 1U server, and I was planning to put SAS/RAID card in PCI-E raiser.

Is there a SDK/DDK for ESX/ESXi, so i can bould drivers myself? Is it free? XenServer has DDK and SDK.


Wed Dec 02, 2009 12:27 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
What output do you get for lspci -p?

_________________
Dave Mishchenko
VMware vExpert 2009-2013
Image
Now available - VMware ESXi: Planning, Implementation, and Security
Also available - vSphere Quick Start Guide


Wed Dec 02, 2009 8:54 pm
Profile

Joined: Mon Nov 30, 2009 6:06 pm
Posts: 4
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
lspci -p:
Code:
Bus:Sl.F Vend:Dvid Subv:Subd ISA/irq/Vec P M Module       Name
                             Spawned bus
00:00.00 8086:d130 8086:0000               V
00:08.00 8086:d155 0000:0000               V
00:08.01 8086:d156 0000:0000               V
00:08.02 8086:d157 0000:0000               V
00:08.03 8086:d158 0000:0000               V
00:16.00 8086:d150 0000:0000               V
00:16.01 8086:d151 0086:00ec               V
00:25.00 8086:10ef 8086:34ec  9/  9/0x79 A V              vmnic1
00:26.00 8086:3b3c 0108:c000  5/  5/0x81 A V ehci-hcd
00:28.00 8086:3b42 0000:0000 10/ 10/0x89 A V
                                 001
00:28.04 8086:3b4a 0000:0000 10/ 10/0x89 B V
                                 002
00:28.06 8086:3b4e 0000:0000 11/ 11/0x91 C V
                                 003
00:28.07 8086:3b50 0000:0000 10/ 10/0x99 D V
                                 004
00:29.00 8086:3b34 9200:4790  9/  9/0xa1 A V ehci-hcd
00:30.00 8086:244e 0000:0000               V
                                 005
00:31.00 8086:3b14 8086:34ec               V
00:31.02 8086:3b22 8086:34ec 11/ 11/0x91 B V ahci         vmhba0
00:31.03 8086:3b30 8086:34ec 11/   /     B V
02:00.00 8086:10d3 8086:34ec 10/ 10/0x89 A V e1000e       vmnic0
03:00.00 102b:0522 8086:0101 11/ 11/0xa9 A V
255:00.00 8086:2c50 8086:8086               V
255:00.01 8086:2c81 8086:8086               V
255:02.00 8086:2c90 8086:8086               V
255:02.01 8086:2c91 8086:8086               V
255:03.00 8086:2c98 8086:8086               V
255:03.01 8086:2c99 8086:8086               V
255:03.02 8086:2c9a 8086:8086               V
255:03.04 8086:2c9c 8086:8086               V
255:04.00 8086:2ca0 8086:8086               V
255:04.01 8086:2ca1 8086:8086               V
255:04.02 8086:2ca2 8086:8086               V
255:04.03 8086:2ca3 8086:8086               V
255:05.00 8086:2ca8 8086:8086               V
255:05.01 8086:2ca9 8086:8086               V
255:05.02 8086:2caa 8086:8086               V
255:05.03 8086:2cab 8086:8086               V


there is vmnic1 up there, but:
Code:
~ # ethtool vmnic1
Cannot get control socket: No such file or directory


PS.
Building of new drivers for XenServer took me about 5min with DDK. I tried to play around with ESX-opensource to build the drivers and i got lot's of errors during compilation. The only success was e1000e.o which was about 9MB and when i put it in oem.tgz it wasnt loaded for some reason.

ESXi has e1000e drivers 0.4.xx, and I tried CentOS 5.4 with 1.0.4, as I recall. CentOS was OK out of box.


Thu Dec 03, 2009 1:47 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
If you try to load the driver manually with vmkload_mod do you get any errors in /var/log/messages?

_________________
Dave Mishchenko
VMware vExpert 2009-2013
Image
Now available - VMware ESXi: Planning, Implementation, and Security
Also available - vSphere Quick Start Guide


Tue Dec 08, 2009 12:38 am
Profile

Joined: Mon Nov 30, 2009 6:06 pm
Posts: 4
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
The odd thing is that it shows still old version.
Code:
Dec  8 08:56:03 vmkernel: 0:09:16:34.042 cpu0:120517)Loading module e1000e ...
Dec  8 08:56:03 vmkernel: 0:09:16:34.042 cpu0:120517)Elf: 2320: <e1000e> symbols tagged as <GPL>
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)module heap : Initial heap size : 102400, max heap size: 4194304
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)module heap e1000e: creation succeeded. id = 0x4100ba800000
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)module skb heap : Initial heap size : 524288, max heap size: 23068672
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)module skb heap : creation succeeded
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)<6>e1000e: Intel(R) PRO/1000 Network Driver - 0.4.1.7-NAPI
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)<6>e1000e: Copyright (c) 1999-2008 Intel Corporation.
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: driver e1000e is looking for devices
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1a.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1c.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:00:1c.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1c.4
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:00:1c.4
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1c.6
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:00:1c.6
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1c.7
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:00:1c.7
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1d.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1f.2
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:00:1f.3
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:00:1f.3
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Trying 0000:02:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)PCI: Announcing 0000:02:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.056 cpu0:120517)socket buffer cache creation succeeded for vmnic%d
Dec  8 08:56:03 vmkernel: 0:09:16:34.057 cpu0:120517)IntrVector: 279: 0xb9
Dec  8 08:56:03 vmkernel: 0:09:16:34.057 cpu0:120517)IntrVector: 279: 0xc1
Dec  8 08:56:03 vmkernel: 0:09:16:34.057 cpu0:120517)VMK_PCI: 1103: device 002:00.0 allocated 2 vectors (intrType 3)
Dec  8 08:56:03 vmkernel: 0:09:16:34.057 cpu0:120517)VMK_PCI: 739: device 002:00.0 capType 16 capIndex 224
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)<6>0000:02:00.0: vmnic0: (PCI Express:2.5GB/s:Width x1) 00:15:17:ad:f1:cc
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)<6>0000:02:00.0: vmnic0: Intel(R) PRO/1000 Network Connection
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)<6>0000:02:00.0: vmnic0: MAC: 4, PHY: 8, PBA No: 1010ff-0ff
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)PCI: driver e1000e claimed device 0000:02:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)PCI: Registering network device 0000:02:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)VMK_PCI: 638: Device 002:00.0 name: vmnic0
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)LinPCI: LinuxPCI_DeviceClaimed: Device 2:0 claimed.
Dec  8 08:56:03 vmkernel:
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)PCI: Trying 0000:03:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)PCI: Announcing 0000:03:00.0
Dec  8 08:56:03 vmkernel: 0:09:16:34.232 cpu0:120517)PCI: driver e1000e claimed 1 device
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)IDT: 939: 0xb9 <vmnic0-Q0> exclusive (entropy source), flags 0x10
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)VMK_VECTOR: 137: Added handler for  vector 185, flags 0x10
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)IDT: 1035: 0xb9 for vmkernel
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)VMK_VECTOR: 225: vector 185 enabled
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)IDT: 939: 0xc1 <vmnic0> exclusive (entropy source), flags 0x10
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)VMK_VECTOR: 137: Added handler for  vector 193, flags 0x10
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)IDT: 1035: 0xc1 for vmkernel
Dec  8 08:56:04 vmkernel: 0:09:16:34.257 cpu3:4134)VMK_VECTOR: 225: vector 193 enabled
Dec  8 08:56:04 vmkernel: 0:09:16:34.319 cpu0:120517)Mod: 2986: Initialization for e1000e succeeded with module ID 54.
Dec  8 08:56:04 vmkernel: 0:09:16:34.319 cpu0:120517)e1000e loaded successfully.


PS
As a temporary solution I made use from my VD-d capability and passed one NIC to my Vyatta VM. Everything seams to be working. Also with grate success I managed to build drivers for XenServer.


Tue Dec 08, 2009 1:00 am
Profile

Joined: Thu Apr 01, 2010 1:48 am
Posts: 6
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Hi,

has anyone gotten ESXi to install with this Intel 82578DM network card?

Would be very grateful to any advice.

Cheers
Jack...


Thu Apr 01, 2010 1:51 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Besides compiling a new driver you could try to edit the existing driver with a hex editor and update it to recognize the PCI id for this NIC.

_________________
Dave Mishchenko
VMware vExpert 2009-2013
Image
Now available - VMware ESXi: Planning, Implementation, and Security
Also available - vSphere Quick Start Guide


Thu Apr 01, 2010 7:26 pm
Profile

Joined: Thu Apr 01, 2010 1:48 am
Posts: 6
Reply with quote
Post Re: Intel 82578DM [Server Platform SR1630GP] custom oem.tgz
Hi Dave,

any advice for how to compile a new driver, or what changes and where I'd need to make in the file with a hex editor?

I've tried changing the oem.tgz file and including different versions of the e1000e and e1000 drivers but none of them seem to be recognised during the install process.

Cheers
Jack...


Wed Apr 14, 2010 11:47 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 17 posts ]  Go to page 1, 2  Next

Who is online

Users browsing this forum: No registered users and 3 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.