Hello.

I made the test driver of Realtek.

One is making of the linux driver whom the Realtek Co. offers as the source.
r8101.o is version 1.020.00, r8168.o is version 8.020.00, and r8169.o is version 6.014.00.
However, r8168.o seems not to operate well in two or more network adaptors.

Another one corrected and made r8169.c of kernel version 2.6.36.4.
This driver is supporting r8101, r8169, and r8111D/r8168D, and externals seem to be steady.

It is not possible to test with all Realtek adaptors, and use it by way of experiment, please.

Moreover, 8139too driver operates perfectly by using the source of Mr. pigeonstriker.

Realtek oem.tgz.
10ec:8136 0000:0000 network r8101.o
10ec:8139 0000:0000 network 8139too.o
10ec:8167 0000:0000 network r8169.o
10ec:8168 0000:0000 network r8168.o
10ec:8169 0000:0000 network r8169.o

Kernel source oem.tgz.
10ec:8136 0000:0000 network r8169.o
10ec:8139 0000:0000 network 8139too.o
10ec:8167 0000:0000 network r8169.o
10ec:8168 0000:0000 network r8169.o
10ec:8169 0000:0000 network r8169.o

Thank you.

After my testing with ASUS P8H67-M Pro(Realtek 8111E)
1.Realtek oem.tgz.
It is unstable and same problem with others.

2.Kernel source oem.tgz.
It cann't find my NIC.

Confirmed working Realtek Oem (I didn't test connection speed yet):

ESXi 4.1.0 348481
LAN Card TP-Link TG-3269 chip RTL8169SC


Thank you very much!

Mr. kulunhuang and Mr. mud911

Thank you very much for the test the driver.
Mii.c was added because there was no kernel driver to use it well.
Perhaps, I think that I can use it by this.

However, the kernel driver's supporting 8111E/8168E in not having been built in kernel module yet becomes 8111D/8168D.
Being built in the source becomes the following driver.

RTL_GIGA_MAC_VER_01 = 0x01, // 8169
RTL_GIGA_MAC_VER_02 = 0x02, // 8169S
RTL_GIGA_MAC_VER_03 = 0x03, // 8110S
RTL_GIGA_MAC_VER_04 = 0x04, // 8169SB
RTL_GIGA_MAC_VER_05 = 0x05, // 8110SCd
RTL_GIGA_MAC_VER_06 = 0x06, // 8110SCe
RTL_GIGA_MAC_VER_07 = 0x07, // 8102e
RTL_GIGA_MAC_VER_08 = 0x08, // 8102e
RTL_GIGA_MAC_VER_09 = 0x09, // 8102e
RTL_GIGA_MAC_VER_10 = 0x0a, // 8101e
RTL_GIGA_MAC_VER_11 = 0x0b, // 8168Bb
RTL_GIGA_MAC_VER_12 = 0x0c, // 8168Be
RTL_GIGA_MAC_VER_13 = 0x0d, // 8101Eb
RTL_GIGA_MAC_VER_14 = 0x0e, // 8101 ?
RTL_GIGA_MAC_VER_15 = 0x0f, // 8101 ?
RTL_GIGA_MAC_VER_16 = 0x11, // 8101Ec
RTL_GIGA_MAC_VER_17 = 0x10, // 8168Bf
RTL_GIGA_MAC_VER_18 = 0x12, // 8168CP
RTL_GIGA_MAC_VER_19 = 0x13, // 8168C
RTL_GIGA_MAC_VER_20 = 0x14, // 8168C
RTL_GIGA_MAC_VER_21 = 0x15, // 8168C
RTL_GIGA_MAC_VER_22 = 0x16, // 8168C
RTL_GIGA_MAC_VER_23 = 0x17, // 8168CP
RTL_GIGA_MAC_VER_24 = 0x18, // 8168CP
RTL_GIGA_MAC_VER_25 = 0x19, // 8168D
RTL_GIGA_MAC_VER_26 = 0x1a, // 8168D
RTL_GIGA_MAC_VER_27 = 0x1b // 8168DP

Best regards.

Hello all,
I have a problem to install VMware-VMvisor-Installer-4.1.0.update1-348481.x86_64 with a new realtek 8169 adapter on my motherboard which is Asus P7P55D.

I downloaded the oem file (thanks for you hard work) and I created the ISO file.
Now, I have not nic error found anymore, but I have this error message:
"The installation operation has encountered a fatal error:
unable to find the system image to install.
this is due to the image not deing mounted correctly or the CR-ROM not being supported"
The strange thing is that on the other computer the installation works fine.

Please could you help me on this kind of problem?
Thanks so much,
Denis

A few options
1) if you're build the ISO using Varazir's script choose the kickstart script option.
2) try an external USB drive or install from a USB device
3) install ESXi 4.0 and then upgrade to 4.1

Hello Dave,
sorry for being in late, I was trying different ways to solve this kind of issue.
At first thanks for suggestions, in fact if I use the 3rd option (3 - USB boot) and it works fine, also with 2 nics.

But if I use 2nd option (2 - USB Installation) it is not able to install the vmware on hard disk and the message is always the same

I have tried to install the ESXi4.0 and then upgrade to 4.1, but I need the vCenter manager, right? I don't know how to use the scripts comand.

I would like at the end to have a HD of OS and another as datastore for virtual machine space.

Do you know if there is any problem of hard disk controller on matherboard?

Thank you very much,
Regards,
Denis

You can use vihostupdate from the vCLI or PowerCLI to update the host from 4.0 to 4.1.

The error you specify about is specific to 4.1.

Mr. ichi,

Thank-you for getting these drivers up and running.

The r8169 driver from the Kernel code worked for me "out-of-the-box" with my
Gigabyte Z68MA-D2H-B3 motherboard which has a RTL8111E onboard ethernet.

I know Francois didn't add any 8111E specific code to the linux driver until somewhere in the Linux 3.0.0-rc? kernel, however I can confirm that the driver you've posted does still work with RTL8111E chips.

I will be stress testing the driver this week, and will keep you posted as to how it goes.

Are you willing to post the modified source code for this driver? That would help others trying to port linux drivers to the ESX platform.

Thanks for your hard work!

Mr. themaninblack

Thank you for the report.
Kernel source was corrected to the one that mii.c is not used a little.
When it is this version, the output of ethtool seems to become it as well as linux, too.

Corrected oem.tgz starts appending the one of the first post. Source code is appended to this post.

The stability operation was done when my having tested.
It would be greatly appreciated when the operation situation can be taught.