View unanswered posts | View active topics It is currently Sun Sep 15, 2019 5:49 am



Reply to topic  [ 72 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6 ... 8  Next
 r8169 Driver "Works" 
Author Message

Joined: Thu May 14, 2009 12:23 am
Posts: 9
Reply with quote
Post Re: r8169 Driver "Works"
Driver works great with Asus P5B Realtek RTL8168B/8111B integrated NIC.

In attachment oem.tgz with r8169.o and modified simple.map:

Code:
10ec:8167 0000:0000 network r8169.o
10ec:8168 0000:0000 network r8169.o
10ec:8169 0000:0000 network r8169.o


Attachments:
oem.tgz [25.01 KiB]
Downloaded 1677 times
Mon Nov 23, 2009 4:36 am
Profile

Joined: Wed Nov 25, 2009 8:36 pm
Posts: 1
Reply with quote
Post Re: r8169 Driver "Works"
stefa.rossi wrote:
But I have no compatible NIC available...



I had the same issue and didn't fancy the idea of having to compile stuff.
This is how I solved it:

1) download oem.tgz attached to first post in this thread and put it on a USB stick.

2) download slax iso image from here and burn a CD.

3) boot slax CD in ESXi machine - HDD will auto mount, USB will automount.

4) copy (drag and drop) oem.tgz from USB stick into Hypervisor1 partition on HDD.

5) shutdown slax and reboot ESXi from HDD - it will automatically load the r8169.

Hope this helps.


Wed Nov 25, 2009 8:51 pm
Profile

Joined: Sun Dec 13, 2009 12:43 pm
Posts: 2
Reply with quote
Post Re: r8169 Driver "Works"
I tried this fix and am now getting the error "PANIC: Failed to find HD boot partition". lspci output indicates
Did a search and the resolution seems to be to install & boot ESXi from USB drive; or add a secondary HDD.


Sun Dec 13, 2009 6:11 pm
Profile

Joined: Sun Dec 13, 2009 12:43 pm
Posts: 2
Reply with quote
Post Re: r8169 Driver "Works"
Got it to work with this fix for realtek 8111c driver and the instructions here -http://davidwjones.wordpress.com/2009/06/17/vmware-esxi-3-5-on-dell-optiplex-745-no-hard-drive-resolution/


Sun Dec 13, 2009 6:45 pm
Profile

Joined: Mon Jan 18, 2010 2:09 am
Posts: 2
Reply with quote
Post Re: r8169 Driver "Works"
Hi evrybody,

I'm trying to install ESXi on my Asus M3M WS (2 * 8111C NIC). I have no more NIC compatible...
I want follow theses instructions :

helioz2000 wrote:
stefa.rossi wrote:
But I have no compatible NIC available...



I had the same issue and didn't fancy the idea of having to compile stuff.
This is how I solved it:

1) download oem.tgz attached to first post in this thread and put it on a USB stick.

2) download slax iso image from here and burn a CD.

3) boot slax CD in ESXi machine - HDD will auto mount, USB will automount.

4) copy (drag and drop) oem.tgz from USB stick into Hypervisor1 partition on HDD.

5) shutdown slax and reboot ESXi from HDD - it will automatically load the r8169.

Hope this helps.


But when i tried to install ESXi, installation freeze because i have no NIC compatible. :cry:

Further, it seems be impossible to add "oem.zip" file to the ESXi ISO.

Quote:
The oem.tgz I have provided does not work as a part of a bootable install, but only after an install.
As for the simple.map and pci.ids, it is my understanding that they are autogenerated.


Evrybody have a solution ? :roll:
Thanks a lot.
(Sorry for my english, i'm french)


Mon Jan 18, 2010 2:21 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: r8169 Driver "Works"
Take a look at this script - viewtopic.php?f=12&t=4 and when you download the file you'll want to save it as oem.tgz (not .zip).

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


Mon Jan 18, 2010 8:08 am
Profile

Joined: Tue Jan 19, 2010 8:11 am
Posts: 3
Reply with quote
Post Re: r8169 Driver "Works"
Hi all !

I'm trying to make work a D-Link DGE-528T card which appears to has a Realtek 8169S chipset on it.

I tried the driver but nothing seems to get working ...

All i get in the /var/log/vmkernel is that :
Code:
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.169 cpu0:4104)Loading module r8169 ...
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.169 cpu0:4104)Elf: 2320: <r8169> symbols tagged as <GPL>
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)module heap : Initial heap size : 102400, max heap size: 16777216
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)module heap r8169: creation succeeded. id = 0x4100bac00000
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)module skb heap : Initial heap size : 524288, max heap size: 23068672
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)module skb heap : creation succeeded
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: driver r8169 is looking for devices
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1d.0
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1d.1
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1d.2
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1d.3
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1d.7
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1f.1
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:00:1f.2
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:01:00.0
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: Trying 0000:04:00.0
Jan 19 17:04:01 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)PCI: driver r8169 claimed 0 device
Jan 19 17:04:02 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)Mod: 2892: Initialization for r8169 succeeded with module ID 59.
Jan 19 17:04:02 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)r8169 loaded successfully.
Jan 19 17:04:02 srv-esx1 vmkernel:
Jan 19 17:04:02 srv-esx1 vmkernel: 0:00:16:17.190 cpu1:4104)ALERT: Elf: 2518: Kernel module r8169 was loaded, but has no signature attached


It appears that the module loads fine even if it hasn't got any valid signature.

The main problem of my story is the fact that the card isn't recognized as a real "Realtek" card as of the Vendor/Device identifiers.
When i run a lspci, it looks like this :
Code:
0a:01.0 Ethernet controller: D-Link System Inc Unknown device 4300 (rev 10)

lspci -n :
Code:
0a:01.0 0200: 1186:4300 (rev 10)


So i'm wondering a thing : If, before compiling the module r8169, the vendor/device identifiers are joined in it, will the card(s) works ? (I have 3 of them and they are 1 Gigabit/s cards ...)

Thanks !

PS : I'm not as good as i can compile something :oops:


Tue Jan 19, 2010 8:18 am
Profile
Site Admin

Joined: Mon Mar 16, 2009 10:13 pm
Posts: 3880
Reply with quote
Post Re: r8169 Driver "Works"
lspci will be using data for /etc/vmwware/pci.ids but it doesn't matter if an entry is there as it is only used for display (in the console and vSphere client) purposes.

The driver will have a PCI id reference to the devices it can work with and if that's not there then the device will not claim a PCI device. I would start with looking at the driver file with a hex editor to see what is listed. Do you have a Linux sample of the driver that will work with the NICs mentioned plus your dlink model?

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


Tue Jan 19, 2010 12:11 pm
Profile

Joined: Mon Jan 18, 2010 2:09 am
Posts: 2
Reply with quote
Post Re: r8169 Driver "Works"
Dave.Mishchenko wrote:
Take a look at this script - viewtopic.php?f=12&t=4 and when you download the file you'll want to save it as oem.tgz (not .zip).


Tkanks a lot, my NIC's works great ! Now ESXi don't recognize my SATA HDD but i continue my research. ;)


Wed Jan 20, 2010 2:47 am
Profile

Joined: Tue Jan 19, 2010 8:11 am
Posts: 3
Reply with quote
Post Re: r8169 Driver "Works"
Dave.Mishchenko wrote:
lspci will be using data for /etc/vmwware/pci.ids but it doesn't matter if an entry is there as it is only used for display (in the console and vSphere client) purposes.

The driver will have a PCI id reference to the devices it can work with and if that's not there then the device will not claim a PCI device. I would start with looking at the driver file with a hex editor to see what is listed. Do you have a Linux sample of the driver that will work with the NICs mentioned plus your dlink model?


No I don't, it appears that the realtek driver supports x64 platforms but the D-Link DGE-528T isn't listed in the realtek driver. So i need someone to mod the original driver before compiling it for ESXi v4.0. I'll post my report here for you all to know !


Wed Jan 20, 2010 8:28 am
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 72 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6 ... 8  Next

Who is online

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