View unanswered posts | View active topics It is currently Tue Sep 25, 2018 10:51 pm



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

Joined: Thu Jun 02, 2011 11:43 am
Posts: 3
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Great news, i got my NIC working with your oem file :D . The problem was that i tried to load the drivers for 82578DM(i followed the specs. from INTEL site(MB S1200BTL) which are wrong and it turned out that i have 82579LM for a second NIC on my mb).
Thx a lot Chilly.


Sat Jun 04, 2011 4:40 am
Profile

Joined: Thu Apr 21, 2011 11:09 am
Posts: 2
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
I need to support a QM67 chipset based 82579 and I have a couple of dumb questions. First, this chipset includes two 82579 NIC. In one system I have, the bios loads a pci id of 8086:10D3 which convinces VMware its a 82574, which has standard support as a e1000e.o. That system ID's the second NIC as a 8086:1502 which is the standard id for a 82579, which isn't supported. On a different system, it appears to use the same id set, but it looks like the vendor has decided to only connect the second nic. I can see this because on install, vmare only complains later when it says the nic isn't connected.

So, my dumb questions are as follows: is all i need in my oem.tgz a modified simple.map with the added entry?; I noticed you had an e1000e.o in your oem.tgz and discussed it, since the register set is the same, why is a new driver needed?; do I simply place the oem.tgz in the root of my install usb or do I need additional incantations?; finally since on the second system, i8257 it may already be seeing the first nic, is simply changing the --device= to point to vmnic1 or is more required?

thanks


Sat Jun 25, 2011 6:29 pm
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
akreitman wrote:
I need to support a QM67 chipset based 82579 and I have a couple of dumb questions. First, this chipset includes two 82579 NIC. In one system I have, the bios loads a pci id of 8086:10D3 which convinces VMware its a 82574, which has standard support as a e1000e.o. That system ID's the second NIC as a 8086:1502 which is the standard id for a 82579, which isn't supported. On a different system, it appears to use the same id set, but it looks like the vendor has decided to only connect the second nic. I can see this because on install, vmare only complains later when it says the nic isn't connected.

So, my dumb questions are as follows: is all i need in my oem.tgz a modified simple.map with the added entry?; I noticed you had an e1000e.o in your oem.tgz and discussed it, since the register set is the same, why is a new driver needed?; do I simply place the oem.tgz in the root of my install usb or do I need additional incantations?; finally since on the second system, i8257 it may already be seeing the first nic, is simply changing the --device= to point to vmnic1 or is more required?

thanks

Simple.map tells ESXi which drivers to load, but it doesn't gaurantee that a driver will work. If you have two devices that use the e1000e driver, you only need a single entry in simple.map. When the driver loads it will load at all the PCI devices in the system and figure out which it can work with. Given that in your case it appears to only work with one of the NICs, then an updated driver may be required.

When you look at /var/log/messages after the host boots you should see a section in the log for each driver. Does it even recognize the 2nd NIC?

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


Sat Jun 25, 2011 10:43 pm
Profile

Joined: Thu Apr 21, 2011 11:09 am
Posts: 2
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Dave.Mishchenko wrote:
[Simple.map tells ESXi which drivers to load, but it doesn't gaurantee that a driver will work. If you have two devices that use the e1000e driver, you only need a single entry in simple.map. When the driver loads it will load at all the PCI devices in the system and figure out which it can work with. Given that in your case it appears to only work with one of the NICs, then an updated driver may be required.

When you look at /var/log/messages after the host boots you should see a section in the log for each driver. Does it even recognize the 2nd NIC?



Thamks, I'll check the log but I don't think it can see the second nic since its id isn't in simple.map. It should work because as far as I can see the motherboard contains two register set identical nics that differ only by the device id that the bios loads as part of post. When you include a simple.map in the oem.tgz, does it replace the standard one or does it just add additional ids? When install finds an id in a simple.map that's in and oem.tgz, does it assume the driver is somewhere in the oem.tgz or does it also look in the core installation. I also noticed that the drivers entries in the core installation don't include a .o suffix, but the they do in the oem.tgz simple.map, why is that?


Sun Jun 26, 2011 1:47 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
akreitman wrote:
Thamks, I'll check the log but I don't think it can see the second nic since its id isn't in simple.map. It should work because as far as I can see the motherboard contains two register set identical nics that differ only by the device id that the bios loads as part of post. When you include a simple.map in the oem.tgz, does it replace the standard one or does it just add additional ids? When install finds an id in a simple.map that's in and oem.tgz, does it assume the driver is somewhere in the oem.tgz or does it also look in the core installation. I also noticed that the drivers entries in the core installation don't include a .o suffix, but the they do in the oem.tgz simple.map, why is that?

If the driver is loaded then you don't need an entry in simple.map. Each driver has a list of PCI ids that it can work with (look at the driver with a hex editor or at the source code).

Including a file in oem.tgz overwrites any existing file that has been extracted from the other vgz and tgz packages.

I'm not sure why they opted to exclude .o from simple.map. Probably just ease of readability.

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


Sun Jun 26, 2011 6:31 pm
Profile

Joined: Thu Jul 07, 2011 10:54 pm
Posts: 1
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Problem fixed, I forgot to modify the ks.cfg with the network config & password and interface was not up.
----------

First of all, thanks for Chilly great effort on the oem.tgz. I have tried to use it with the latest version. However I still received the following error message when I install ESXi to my box.

2011-7-11 Updated error message during isntallation
<Please see the attachmentes>

Here is my box specification.
MB: DQ67SW (Ref: http://www.intel.com/products/desktop/m ... erview.htm)
RAM: 4 x 4G RAM
CPU: i7 2600
NIC: Intel 82579LM
HDD: WD 2TB HDD

I used the script mkesxiaio_4.3.1.sh provided by Varazir to create a bootable USB with VMware-VMvisor-Installer-4.1.0.update1-348481.x86_64.iso. Everything is alright when I combined the oem.tgz to the iso. But I still cannot start the installation at last. As I am new to the driver customization on ESXi, any help would be highly appreciate. Many thanks.

Jacky


Attachments:
DQ67SW_2.JPG
DQ67SW_2.JPG [ 244.43 KiB | Viewed 5863 times ]
DQ67SW_1.JPG
DQ67SW_1.JPG [ 318.93 KiB | Viewed 5863 times ]
Sun Jul 10, 2011 6:20 pm
Profile

Joined: Mon Jul 25, 2011 11:23 am
Posts: 4
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Quote:
[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)


Chilly,
Thanks for your work. It appears from this thread that you have also provided a oem.tgz fix for the 82579V. However, there are two attachments listed on your original post, oem.part1.rar and oem.part2.rar. I downloaded each one and looked through them. I'm not sure which one I should use as they both seem to have the same files (although they aren't the same size). Additionally, neither version seems to have the pcitable entries for the 82579V in the e1001e.xml file. So basically (being a newbie) I have the following questions:

1. Which rar file should I use?

2. Shouldn't the e1001e.xml file contain code for the 82579V for this to work? (It only has an entry for the 82579LM with a <device id>=1502 which won't match the 82579V which is <device id>=1503.)

Thanks.


Mon Jul 25, 2011 1:42 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)
Hey gbeauq!

The file is in split into both rar files. You need both rar files(in the same folder/location) to extract it(otherwise the extraction will fail/resulting file will be corrupted), but it doesn't matter which file you extract it from as the file will be the same.

As for the xml file, its not really used in ESXi 4.1. I only included it for completeness sake.

Hope that helps, if you have any questions, feel free to ask! :)


Tue Jul 26, 2011 9:22 am
Profile

Joined: Mon Jul 25, 2011 11:23 am
Posts: 4
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Chilly wrote:
Hey gbeauq!

The file is in split into both rar files. You need both rar files(in the same folder/location) to extract it(otherwise the extraction will fail/resulting file will be corrupted), but it doesn't matter which file you extract it from as the file will be the same.


Ah. Must be some sort of split .rar file technique that I'm not aware of. It just so happens I downloaded both to the Desktop and then opened one of them so it all worked fine. (Sometimes it's better to be lucky than good!) Again, thanks.

I've built a custom .iso using the oem.tgz you supplied. Will be trying it out on a couple of Intel MBs: DP55WB and DH67CL. The DP55WB has the 82578DC Gigabit Ethernet Controller and the DH67CL has the 82579V Gigabit Ethernet Controller. I think your oem.tgz should work on both. [Fingers Crossed]

Thanks.

GBeauW


Tue Jul 26, 2011 2:58 pm
Profile

Joined: Mon Jul 25, 2011 11:23 am
Posts: 4
Reply with quote
Post Re: Intel 82578DC 8086:10f0 (on Intel motherboard DH55TC)
Chilly, et al,

Good news! :D

I am happy to report that the oem.tgz file that you provided in this thread DOES work with the Intel DP55WB MB as it uses the 82578DC. (I suspect that all Intel DH55xx Series MB's work with that oem.tgz file but that's just a guess.)

Now to build up the other machine using the new Intel DH67CL MB and the 82579V and see if that works.


Thu Jul 28, 2011 6:58 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 197 posts ]  Go to page Previous  1 ... 9, 10, 11, 12, 13, 14, 15 ... 20  Next

Who is online

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