New Driver for Realtek RTL8111

[Mrengles]

What I need is the kernel log, nothing else. I want to find out if this strange behavior has anything to do with the driver or not.

 

Mieze

 

Hey Laura

 

I've got some good new! The ethernet bonding issues I was having with El Capitan (10.11.x) was not caused by your driver. I've managed to fix all my network problems by removing the DSM methods; I was injecting port locations into my DSDT at device RP05 and RP06 for the dual ethernet ports. It was just a cosmetic fix when it worked, but ended up causing the problem.

 

Sorry to waste you time. 

 

Your OS X Realtek Ethernet Driver is still kicking ass! 

 

I'm now back to sharing NetInstall images over my 2 Gbit/s (poor mans SAN) pipe.

 

Gratitude,

 

Robert aka Mrengles

[Vustom]

I have a Realtek 8111C network card in my HP Pavilion Elite m9180a, there's only been one kext that's worked for me since I started using Yosemite and that is RealtekR1000SL.kext. It's not very stable though and randomly disconnects however this does resolve itself after restarting my PC.

 

I'm using Clover and have my own DSDT and SSDT specific to my PC, although after adding RealtekRTL8111.kext to my Clover's 10.11 folder and deleting RealtekR1000SL.kext, the Ethernet connection in System Preferences just says Ethernet is not connected. I've tried removing the Ethernet profile from System Preferences prior to restarting my PC too - no luck yet.

 

Any ideas why I can't get this to work?

[euggie]

[uPDATE: The problem is solved]

I was mislead by System info in windows and the B75-D3V specs as well which gave me wrong direction... Actual network interface is Atheros AR81xx ! So the post is not really on topic, but anyway, it might be helpful

 

----

Thank you for your driver. It gives me a hope.

 

Actually, I had no success installing it.
Mobo is: Gig B75-D3V. Network interface is: Realtek RTL8168D/811D Family PCI-E Gigabit Ethernet. OS: Yosemite 10.10.4.

 

I followed these advices:
 

• Use the debug version to collect log data when trying to track down problems. The kernel log messages can be found in /var/log/system.log. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant.
  - no debug info at all, even from debug binary kext.
   
• Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver.
• - Network boot, UEFI Network Stack are disabled.
   
• Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly.
  - No realtek kexts, except the one for Asus USB-N13, that I removed too while experimenting.
   
• Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. 
  - No flags too

The weirdest thing is that there are no logs from the driver at all in the system.log. About this Mac / System info shows the driver in inactive state.
I tried old RealtekR1000SL with no success as well.

What did I miss and what i did wrong can you give me some hints please?

Edited November 5, 2015 by euggie

[Mieze]

@euggie: When there is absolutely no entry of the driver in the kernel logs, the solution is quite simple. The driver doesn't load because it's either not properly installed or it doesn't find the hardware because the NIC has been disabled in BIOS.

 

Mieze

[Wowfunhappy]

Hi! Despite my best efforts, I haven't been able to make this driver work on my Z170 PCMate, which uses a Realtek RTL8111H ethernet controller. I'm running 10.11.1 El Capitan with the Clover bootloader.

 

OS X can see that an ethernet cable is plugged in, but says "Ethernet has a self-assigned IP address and will not be able to connect to the internet."

 

Here is what I found in my kernel log:

Ethernet [RealtekRTL8111]: PCIe ASPM support disabled.
Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
Ethernet [RealtekRTL8111]: EEE support enabled.
Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Ethernet [RealtekRTL8111]: Version 2.0.0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com!
Ethernet [RealtekRTL8111]: Retry chip recognition.
Ethernet [RealtekRTL8111]: RTL8168B/8111B: (Chipset 0) at 0x<ptr>, d8:cb:8a:99:33:43
Ethernet [RealtekRTL8111]: MSI interrupt index: 1
Ethernet [RealtekRTL8111]: Already in power state 1.
Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
Ethernet [RealtekRTL8111]: Link up on en4, 100-Megabit, Full-duplex, flow-control

[drshader]

Wowfunhappy ++

Hi, Mieze. Same here on H170 (GA-H170-HD3 DDR3 (rev. 1.0)) with RTL8168 onboard. After installing your kext in L/E/ (and in clover/kexts/10.11/), I have en0 Ethernet visible in system profile.

While booting I can see proper MAC-address of my NIC (Ethernet [RealtekRTL8111]: RTL8168B/8111B: (Chipset 0) at 0x<ptr>, 40:8D:5C:4B:9E:9A).

But system prefs says "Ethernet has a self-assigned IP address and will not be able to connect to the internet." And shows me creepy IP.

Checked this thread for solutions with no luck...

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Disable PCIe ASPM.

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Version 2.0.0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com!

Nov  7 05:53:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: RTL8168B/8111B: (Chipset 0) at 0x<ptr>, 40:8d:5c:4b:9e:9a

[Mieze]

Currently the driver lacks support for the RTL8111H. I will update it as soon as possible to add support for this chip found on recent boards.

 

Mieze

[Wowfunhappy]

Ah, that explains why it wasn't working! Great to hear, thanks!

[grml4d]

thank you , works well with hp touchsmart 600-11xx

[Mieze]

I just wanted to let you know that I started work on version 2.1.0 which is based on Realtek's driver source 8.040.000 and will add support for the latest members of the RTL8111 family including the RTL8111H.

 

Mieze

[Mieze]

Here is a first development release of version 2.1.0 of the driver which adds support for the RTL8111EP and the RTL8111H. I'm publishing it for testing purposes only as it's still far away from a final release.

 

Good luck!

 

Mieze

 

EDIT: Please use version 2.1.0d1 instead of this one!

[drshader]

Thank you, Mieze.

But still getting "Ethernet has a self-assigned IP..."

Here's log

Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe ASPM support disabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Nov 13 10:35:09 localhost com.apple.xpc.launchd[1] (com.apple.airplaydiagnostics.server): Unrecognized MachService property: ResetAtClose
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Version 2.1.0d0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com!
Nov 13 10:35:10 localhost kernel[0]: *IOAHCIBlockStorageDriver::DetermineDeviceFeatures - !!!!! WARNING !!!!! - Force Data Set Management is set
Nov 13 10:35:10 --- last message repeated 2 times ---
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: RTL8168H/8111H: (Chipset 29) at 0x<ptr>, 40:8d:5c:4b:9e:9a
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Device is WoL capable.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1

And my ioreg attached (maybe this helps)

H170_i5-6500.zip

[Mieze]

Thank you, Mieze.

But still getting "Ethernet has a self-assigned IP..."

Here's log

Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe ASPM support disabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Nov 13 10:35:09 localhost com.apple.xpc.launchd[1] (com.apple.airplaydiagnostics.server): Unrecognized MachService property: ResetAtClose
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Version 2.1.0d0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com!
Nov 13 10:35:10 localhost kernel[0]: *IOAHCIBlockStorageDriver::DetermineDeviceFeatures - !!!!! WARNING !!!!! - Force Data Set Management is set
Nov 13 10:35:10 --- last message repeated 2 times ---
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: RTL8168H/8111H: (Chipset 29) at 0x<ptr>, 40:8d:5c:4b:9e:9a
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: Device is WoL capable.
Nov 13 10:35:10 localhost kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1

And my ioreg attached (maybe this helps)

 

Doesn't look like a driver problem but more like a configuration issue of the interface. Try to configure it properly in System Preferences.

 

Mieze

[drshader]

What exactly means "properly"? I can only use two principal options - automatic DHCP, or DHCP with manual IP.

First gives me "Ethernet has a self-assigned IP..." and yellow-lighted Ethernet interface.

Second (when I set my IP assigned from router) gives me green-lighted Ethernet interface - and it looks like it working, but no "real connection" happens.

Same behavior was with version 2.0 of the driver too.

When I installed v2.1.0d0, I also deleted NetworkInterfaces.plist in prefs. Driver is installed in L/E/.

[Mieze]

@drshader: According to the logs you posted the driver has initialized the chip successfully. There is no indication for an error but the network stack doesn't try to enable the interface which indicates a problem in the configuration.

 

Mieze

[Kr3m1in]

I can report a similar issue; DHCP isn't connecting and is using the wrong subnet mask for whatever reason.

 

I've removed and re-added the ethernet interface in sys prefs, tried DHCP with manual address and tried configuring everything manually.

 

I'll be on all weekend if you need somebody to test stuff - though you'll have to bear with me, I'm new to the Hackintosh scene and I've nearly forgot all the stuff I learned in my CISCO courses in High School.

[Mieze]

I need the complete kernel logs in order to find out what is going on.

 

Mieze

[drshader]

my complete one-time-boot systemlog

systemlog.zip

[Mieze]

my complete one-time-boot systemlog

 

The log entries are ok, no errors, the interface detects the link. Everything looks fine. In order to find out why DHCP isn't working use netstat -I en0 in Terminal to check if the numbers of received and transmitted packets are increasing in time and report back.

 

Mieze

[Kr3m1in]

Here you go, Mieze.

 

Included is my system log as well as screenshots of the networking pane in System Preferences and the output of netstat -I en0.

System Log & Screenshots.zip

[drshader]

Screenshots with auto DHCP and assigned IP. Not too much info...

 

 

[Mieze]

Strange, the numbers are increasing. Please configure IP address, subnet mask, etc. manually. Try to ping a machine in your network, for example the router. Does the ping succeed?

 

Mieze

[Kr3m1in]

Strange, the numbers are increasing. Please configure IP address, subnet mask, etc. manually. Try to ping a machine in your network, for example the router. Does the ping succeed?

 

Mieze

I'll try it again, but last time I did I couldn't ping anything on the LAN.

Edit: Nada.

[drshader]

my ping results

[Mieze]

Hmm, As I'm quite sure that packets are going out (the statistics are based on hardware packet counters), the problem might be located in the receiver's configuration. I will check the source code again. Maybe I'll find something...

 

Mieze