New Driver for Realtek RTL8111

kjp4756 · January 24, 2014

I just started using this driver with my Asus p7p55d and so far it has been the best out of the ones I have tried (lnx2mac's was one). I am noticing one weird issue and I am not sure if it's a problem with the driver or maybe if it's something DSDT related. WOL worked for me after I first installed this driver. After I rebooted the machine, WOL will no longer work. I have to shut down the computer and unplug the power cable then plug it in and turn it on. After doing that WOL will function as it should until I reboot again.

Any idea on what is going on here?

BTW I'm running 10.9.1 and I compiled the kext myself.

FUT1L1TY · January 26, 2014

This is normal behavior for 10.7+. Add darkwake=0 to kernel boot arguments to disable.

Thank you for the pointer in the right direction. I wound up using darkwake=8 as suggested in this in-depth article and now everything is working as expected.

http://www.cnpbagwell.com/mac-os-x/bonjour-sleep-proxy

I'd also like to thank Mieze for his work on this awesome driver. It's nice to have WOL working on my machine again.

joe75 · January 26, 2014

I'd also like to thank Mieze for his work on this awesome driver. It's nice to have WOL working on my machine again.

her* work on this awesome driver..

shiecldk · January 28, 2014

Hi Mieze,

Two days ago, I had no ethernet connection (wrong IP, not 192.168.XXX.XXX) after my desktop strangely waked from automatic sleep itself.

(I don't even know why it waked up. According to the Console app, it appears to be RTC which waked up my system. However, I didn't setup any wake schedule in System Preferences>Energy Saver.)

Could this be the diver's issue?

I'm using 1.1.3 on RTL8111. Here is the log:

1/26/14 12:46:18.138 PM xpcproxy[643]: assertion failed: 13B42: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2
1/26/14 12:48:07.000 PM kernel[0]: PM notification timeout (pid 142, SRStreamerDaemon)
1/26/14 12:48:27.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x6400 ****
1/26/14 12:48:27.000 PM kernel[0]: Bluetooth -- LE is supported - Disable LE meta event
1/26/14 12:48:27.000 PM kernel[0]: REQUIRE_NO_ERR failure: 0x1 - file: /SourceCache/IOBluetoothFamily_kexts/IOBluetoothFamily-4200.4.6/Core/Family/HCI/Transports/USB/IOBluetoothHostControllerUSBTransport/IOBluetoothHostControllerUSBTransport.cpp:1937
1/26/14 12:48:27.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x6400 ****
1/26/14 12:48:29.000 PM kernel[0]: Wake reason: RTC (Alarm)
1/26/14 2:36:25.000 PM kernel[0]: RTC: Maintenance 2014/1/26 06:36:24, sleep 2014/1/26 04:48:40
1/26/14 2:36:25.000 PM kernel[0]: Previous Sleep Cause: 5
1/26/14 2:36:25.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- Error -- GetDeviceInformation() returned 0xE00002ED (kIOReturnNotResponding) -- counter = 1 ****
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- Error -- GetDeviceInformation() returned 0xE00002ED (kIOReturnNotResponding) -- counter = 2 ****
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- Error -- GetDeviceInformation() returned 0xE00002ED (kIOReturnNotResponding) -- counter = 3 ****
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- Error -- GetDeviceInformation() returned 0xE00002ED (kIOReturnNotResponding) -- counter = 4 ****
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- Error -- SuspendDevice () returned 0x0000 (kIOReturnSuccess), GetDeviceInformation() returned 0xE00002ED (kIOReturnNotResponding), attempting to continue...
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess), getDeviceInfoResult = 0xE00002ED (kIOReturnNotResponding) -- calling DoDeviceReset() -- 0xbd00 ****
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- success = FALSE -- 0x6400 ****
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0xE00002ED (kIOReturnNotResponding) -- 0x6400 ****
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][setPowerStateWL] -- PerformPowerStateChange() failed: 0xE00002BC (kIOReturnError) -- powerStateOrdinal = ON, mCurrentInternalPowerState = SLEEP -> mPendingInternalPowerState = ON -- 0x6400 ****
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][HubResetThreadEntry] -- 0x6400
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][HubReset] -- entering -- 0x6400 ****
1/26/14 2:36:26.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][HubReset] -- in our workloop -- 0x6400 ****
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][HubReset] -- no hub found!
1/26/14 2:36:26.000 PM kernel[0]: [IOBluetoothHostControllerUSBTransport][HubReset] -- exit; error = 0xE00002C0 (kIOReturnNoDevice)
1/26/14 2:36:28.000 PM kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control
1/26/14 2:36:28.091 PM configd[17]: LINKLOCAL en0: parent has no IP
1/26/14 2:36:28.094 PM configd[17]: network changed: v4(en0-:192.168.10.47) DNS- Proxy-
1/26/14 2:36:28.096 PM configd[17]: setting hostname to "user-iMac.local"
1/26/14 2:36:28.105 PM netbiosd[307]: network_reachability_changed : network is not reachable, netbiosd is shutting down
1/26/14 2:36:32.000 PM kernel[0]: com_driver_GxxxDriver::probe fails
1/26/14 2:36:32.000 PM kernel[0]: com_driver_GxxxDriver::probe fails
1/26/14 2:36:33.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x5c00 ****
1/26/14 2:36:33.000 PM kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0x5c00 ****
1/26/14 2:36:33.000 PM kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x5c00 
1/26/14 2:36:33.000 PM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
1/26/14 2:36:33.000 PM kernel[0]: **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x3c00 -- 0x3000 -- 0x5c00 ****
1/26/14 2:36:33.308 PM digest-service[650]: label: default
1/26/14 2:36:33.308 PM digest-service[650]: 	dbname: od:/Local/Default
1/26/14 2:36:33.308 PM digest-service[650]: 	mkey_file: /var/db/krb5kdc/m-key
1/26/14 2:36:33.308 PM digest-service[650]: 	acl_file: /var/db/krb5kdc/kadmind.acl
1/26/14 2:36:33.321 PM digest-service[650]: digest-request: uid=0
1/26/14 2:36:33.373 PM digest-service[650]: digest-request: netr probe 0
1/26/14 2:36:33.373 PM digest-service[650]: digest-request: init request
1/26/14 2:36:33.376 PM digest-service[650]: digest-request: init return domain: USER-IMAC server: USER-IMAC indomain was: <NULL>
1/26/14 2:36:33.429 PM digest-service[650]: digest-request: uid=0
1/26/14 2:36:33.429 PM digest-service[650]: digest-request: init request
1/26/14 2:36:33.431 PM digest-service[650]: digest-request: init return domain: USER-IMAC server: USER-IMAC indomain was: <NULL>
1/26/14 2:36:53.487 PM configd[17]: subnet_route: write routing socket failed, Network is unreachable
1/26/14 2:36:55.823 PM configd[17]: network changed: Proxy
1/26/14 2:37:11.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5c00 ****
1/26/14 2:37:16.000 PM kernel[0]: full wake (reason 1) 51333 ms
1/26/14 2:37:16.380 PM WindowServer[151]: CGXDisplayDidWakeNotification [4423360031651]: posting kCGSDisplayDidWake
1/26/14 2:37:16.380 PM WindowServer[151]: handle_will_sleep_auth_and_shield_windows: Deferring.
1/26/14 2:37:16.000 PM kernel[0]: Sound assertion in AppleHDAWidget at line 4240
1/26/14 2:37:16.000 PM kernel[0]: Sound assertion in AppleHDACodecGeneric at line 1374
1/26/14 2:37:16.000 PM kernel[0]: DSP Sound assertion in DspFuncManager at line 2047
1/26/14 2:37:16.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5c00 ****
1/26/14 2:37:39.616 PM Console[675]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
1/26/14 2:37:44.094 PM Google Chrome Helper[677]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:37:44.094 PM Google Chrome Helper[677]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:37:44.100 PM Google Chrome Helper[677]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
1/26/14 2:37:44.254 PM Google Chrome Helper[678]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:37:44.254 PM Google Chrome Helper[678]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:37:44.260 PM Google Chrome Helper[678]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
1/26/14 2:37:46.724 PM Google Chrome Helper[680]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:37:46.725 PM Google Chrome Helper[680]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:37:46.731 PM Google Chrome Helper[680]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
1/26/14 2:37:57.414 PM com.apple.InputMethodKit.UserDictionary[684]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](760): CoreData: Ubiquity:  user~XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX:UserDictionary
Using local storage: 1
1/26/14 2:37:57.700 PM com.apple.InputMethodKit.UserDictionary[684]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](760): CoreData: Ubiquity:  user~XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX:UserDictionary
Using local storage: 0
1/26/14 2:38:15.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5c00 ****
1/26/14 2:39:04.593 PM Google Chrome Helper[434]: CoreText CopyFontsForRequest received mig IPC error (FFFFFECC) from font server
1/26/14 2:39:04.593 PM Google Chrome Helper[434]: CoreText CopyFontsForRequest received mig IPC error (FFFFFECC) from font server
1/26/14 2:39:08.080 PM login[704]: USER_PROCESS: 704 ttys000
1/26/14 2:39:09.614 PM login[704]: DEAD_PROCESS: 704 ttys000
1/26/14 2:39:12.426 PM com.apple.preference.network.remoteservice[718]: assertion failed: 13B42: liblaunch.dylib + 25164 [XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX]: 0x25
1/26/14 2:39:12.434 PM com.apple.preference.network.remoteservice[718]: assertion failed: 13B42: liblaunch.dylib + 25164 [XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX]: 0x25
1/26/14 2:39:12.625 PM com.apple.preference.network.remoteservice[718]: Bogus event received by listener connection:
<error: 0x7fff72796b50> { count = 1, contents =
	"XPCErrorDescription" => <string: 0x7fff72796e60> { length = 18, contents = "Connection invalid" }
}
1/26/14 2:39:12.867 PM com.apple.preference.network.remoteservice[718]: Could not find image named 'InvalidDataIcon'.
1/26/14 2:39:12.901 PM com.apple.preference.network.remoteservice[718]: *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
1/26/14 2:39:12.902 PM com.apple.preference.network.remoteservice[718]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
1/26/14 2:39:17.468 PM Google Chrome Helper[721]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:39:17.468 PM Google Chrome Helper[721]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:39:17.474 PM Google Chrome Helper[721]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
1/26/14 2:39:17.647 PM Google Chrome Helper[722]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:39:17.647 PM Google Chrome Helper[722]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:39:17.653 PM Google Chrome Helper[722]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
1/26/14 2:39:18.545 PM Google Chrome Helper[723]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
1/26/14 2:39:18.545 PM Google Chrome Helper[723]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
1/26/14 2:39:18.551 PM Google Chrome Helper[723]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)

Mieze · January 28, 2014

Hello shiecldk,

well, your problem doesn't look like a driver issue because according to the logs the link gets established. Anything beyond is outside the scope of the driver and in case the NIC hangs the driver detects this situation and issues a chip reset after 3 seconds but there is no reset in your log file.

Mieze

Mieze · January 29, 2014

I just started using this driver with my Asus p7p55d and so far it has been the best out of the ones I have tried (lnx2mac's was one). I am noticing one weird issue and I am not sure if it's a problem with the driver or maybe if it's something DSDT related. WOL worked for me after I first installed this driver. After I rebooted the machine, WOL will no longer work. I have to shut down the computer and unplug the power cable then plug it in and turn it on. After doing that WOL will function as it should until I reboot again.

Any idea on what is going on here?

Frankly no, but WoL seems to be a difficult topic because of it's complexity. The driver, OS X and the BIOS have to cooperate in order for WoL to work. The driver's part is to put the NIC into a state so that it can generate wakeup events on reception of a magic packet and the BIOS has to process the wakeup event, power on the hardware and hand over control back to the operating system.

WoL is working fine for me and a lot of users have confirmed it too, while other reported that it doesn't work at all on their machines. Yes, it might be a DSDT problem or a BIOS related issue. Did you disable network boot and the PXE expansion ROM in BIOS?

Do multiple WoL cycles work after a cold boot? With restart you mean restart from OS X to OS X? In order to get some additional data you could try the debug version of the driver and take a look at the kernel logs.

Mieze

kjp4756 · January 29, 2014

Frankly no, but WoL seems to be a difficult topic because of it's complexity. The driver, OS X and the BIOS have to cooperate in order for WoL to work. The driver's part is to put the NIC into a state so that it can generate wakeup events on reception of a magic packet and the BIOS has to process the wakeup event, power on the hardware and hand over control back to the operating system.

WoL is working fine for me and a lot of users have confirmed it too, while other reported that it doesn't work at all on their machines. Yes, it might be a DSDT problem or a BIOS related issue. Did you disable network boot and the PXE expansion ROM in BIOS?

Do multiple WoL cycles work after a cold boot? With restart you mean restart from OS X to OS X? In order to get some additional data you could try the debug version of the driver and take a look at the kernel logs.

Mieze

Network boot is enabled. I will disable it. I used to use it when I had it set up on my home server.

Multiple WOL cycles work after a cold boot. WOL works as long as I don't reboot. Reboot OS X. I'll take a look at the debug version once I get some time. For now I'll be OK as long as I don't reboot.

Thanks for the reply.

polkaholga · January 30, 2014

Hello Mieze,

your driver's working great ! I would be interested to get this working for Snow Leopard aswell but i'm not a coder and to be honest have no idea

about the necessary patches.

I've built an "iMac12.2" ( see specs in my sig ) for a friend of mine who's a music producer working with Logic, 10.6.8 and some RME firewire soundcards ( in regular PCI slots ).

These soundcards are a bit old fashioned but he swears that these are the best one can have. Unfortunately their drivers only work in 32Bit mode

so he can't get his equipment connected under a 64Bit environment. We were asking for support at RME for 64Bit drivers but they refuse to make them

work at 64 ( they want to sell newer cards :blush: ).

Any chance we can compile your driver for 32 bit. What could i do, besides testing, to achieve this ?

kind regards

RehabMan · January 30, 2014

Hello Mieze,

your driver's working great ! I would be interested to get this working for Snow Leopard aswell but i'm not a coder and to be honest have no idea

about the necessary patches.

I've built an "iMac12.2" ( see specs in my sig ) for a friend of mine who's a music producer working with Logic, 10.6.8 and some RME firewire soundcards ( in regular PCI slots ).

These soundcards are a bit old fashioned but he swears that these are the best one can have. Unfortunately their drivers only work in 32Bit mode

so he can't get his equipment connected under a 64Bit environment. We were asking for support at RME for 64Bit drivers but they refuse to make them

work at 64 ( they want to sell newer cards ).

Any chance we can compile your driver for 32 bit. What could i do, besides testing, to achieve this ?

kind regards

My fork can be used on SL. You'll need to build the 32-bit version yourself, however, my builds are only 64-bit.

See: https://github.com/RehabMan/OS-X-Realtek-Network

polkaholga · January 31, 2014

My fork can be used on SL. You'll need to build the 32-bit version yourself, however, my builds are only 64-bit.

See: https://github.com/RehabMan/OS-X-Realtek-Network

Thank you, I'll try to wrap my head around it.

Mieze · February 2, 2014

As already announced a few weeks ago here is the first development release of version 1.2.0 which is now based on version 8.037.00 of Realtek's r8168 driver. Unfortunately there have been a lot of changes in the linux driver since 8.035.00, which earlier versions of my driver are based on, so that it has been quite challenging to update the code and took much more time than expected.

New features:

Support for RTL8411B and RTL8111EP

Please keep in mind that this is work in progress which has undergone only minimal testing. It might be unstable or might not work at all on certain chipsets. When giving feedback please take a look at your kernel logs and tell me which chipset number (0-26) you are using because the model name, for example 8111E, is useless for me as there are several chipsets which share the same model name.

The attached file contains prebuilt debug and release versions for ML as well as the source code.

Good luck!

Mieze

P. S.: For the latest code please see http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/page-24?do=findComment&comment=1991840

Edited February 6, 2014 by Mieze

Onixs · February 3, 2014

Hi Mieze

I tried compiling the source of V1.20 in Xcode 4.6.3 for a universal binary, but getting this error

Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1

Mieze · February 3, 2014

Hi Mieze

I tried compiling the source of V1.20 in Xcode 4.6.3 for a universal binary, but getting this error
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1

Please send me more of the logs because this could be anything. What do you mean with universal binary because there is only one architecture supported?

Mieze

Edited February 3, 2014 by Mieze

RehabMan · February 3, 2014

I have a new laptop (Lenovo U430, chipset 24) here with one of the newer chips. There is progress with this driver, but it is not working. The previous version would not even pick up the MAC address. This one does that, so something is working.

Unable to get an IP address via DHCP, end up with self-assigned IP. Setting the IP manually results in no connectivity (ping to router fails).

Here is the log with the debug kext installed:

Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: RTL8168GU/8111GU: (Chipset 24) at 0xffffff808f06d000,  xx:xx:xx:xx:xx:xx
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
Feb  3 00:10:20 localhost kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
Feb  3 00:10:23 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
Feb  3 00:14:04 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 00:15:49 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 00:15:51 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 00:16:04 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 00:16:06 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 10-Megabit, Full-duplex, No flow-control
Feb  3 00:17:59 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 00:18:01 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
Feb  3 00:19:52 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 00:19:54 ideapad-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Network config is Ethernet to router configured as Client Bridge (dd-wrt), 100mbit connection at "router"...

This driver does still work with the ProBook (chipset 14) in the same scenario:

Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00073c11, link control: 0x0143.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: RTL8168E/8111E: (Chipset 14) at 0xffffff80e8085000, xx:xx:xx:xx:xx:xx
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
Feb  3 08:26:58 localhost kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
Feb  3 08:26:59 localhost kernel[0]: Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
Feb  3 08:27:01 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 08:28:48 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 08:29:12 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 08:29:13 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 08:29:15 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 08:31:41 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 08:33:49 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
Feb  3 08:36:00 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0
Feb  3 08:36:48 ProBook-mavs kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Let me know if I can run additional tests or provide additional debug info. Thanks!

Skvo · February 3, 2014

Acer V5-572G, RTL8411B, Chipset 25.

Unable to get an IP address via DHCP, end up with self-assigned IP.

log:

03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: 8411B: (Chipset 25) at 0xffffff810060e000,  8:9e: 1:b6:ed:xx
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
03.02.14 22:58:47,000 kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: 8411B: (Chipset 25) at 0xffffff810072d000,  8:9e: 1:b6:ed:6e
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
03.02.14 23:03:02,000 kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
03.02.14 23:06:38,761 com.apple.kextcache[431]: kext com.insanelymac.RealtekRTL8111  102009000 is in exception list, allowing to load
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: Warning: PCIe ASPM enabled.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: Using interrupt mitigate value 0xcf68.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: 8411B: (Chipset 25) at 0xffffff810060e000,  8:9e: 1:b6:ed:6e
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
03.02.14 23:07:53,000 kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
03.02.14 23:09:42,000 kernel[0]: Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
03.02.14 23:09:44,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control
03.02.14 23:11:11,000 kernel[0]: Ethernet [RealtekRTL8111]: Link down on en0

Mieze · February 3, 2014

Hello RehabMan,

thanks for the debug data. Please repeat the tests for chipset 24 with a gigabit connection. Also take a look at network statistics (rx/tx packets). At first glance it looks like there are no packets going in or out.

@Skvo: What about the network statistics?

Mieze

RehabMan · February 3, 2014

Hello RehabMan,

thanks for the debug data. Please repeat the tests for chipset 24 with a gigabit connection. Also take a look at network statistics (rx/tx packets). At first glance it looks like there are no packets going in or out.

According to Network Utility, only packets going out. I don't have a gigE connection ATM, so this will need to wait until later (about a week). When I am closer to my normal network config, I'll update here.

Thanks!

Mieze · February 3, 2014

According to Network Utility, only packets going out. I don't have a gigE connection ATM, so this will need to wait until later (about a week). When I am closer to my normal network config, I'll update here.

Thanks!

Looks like the link change patch code is not ok. I almost expected that to happen because in the underlying linux driver they reinitialize the NIC completely after the link comes up. As this makes things more complex and the r8169 driver doesn't follow that scheme either, I decided to try without a complete reinitialization. Maybe I have to rethink my decision in case I won't find out what is missing.

By the way, you can connect directly to the other machine in order to get a gigabit connection.

In case you can send me a dump of the chip's PCI config space that would also help because for the latest models they poke at registers 0x99 and 0x180 and they don't want us to understand what they are doing (take a look at the source).

Mieze

Edited February 3, 2014 by Mieze

Skvo · February 3, 2014

@Skvo: What about the network statistics?

everything looks the same as in RehabMan:

Setting the IP manually:

P.S.

1 Gbit link - also not working

P.P.S.

Datasheets can help? Here there

https://sandbox.mediafire.com/folder/2fkqxyb4v76u8/Datasheet

RehabMan · February 3, 2014

By the way, you can connect directly to the other machine in order to get a gigabit connection.

Of course... (too focused on having Internet access from this laptop).

Tried it and the results are the same.

In case you can send me a dump of the chip's PCI config space that would also help because for the latest models they poke at registers 0x99 and 0x180 and they don't want us to understand what they are doing (take a look at the source).

I've dealt with some PCI config stuff recently in fixing IGPU (Intel HD Graphics) LCD backlight control... Is it like that, where with RW-Everything in Windows, I find a BAR address in PCI_config then look there at that SystemMemory? If you have specifics of what you want, I'll be glad to...

Mieze · February 3, 2014

I've dealt with some PCI config stuff recently in fixing IGPU (Intel HD Graphics) LCD backlight control... Is it like that, where with RW-Everything in Windows, I find a BAR address in PCI_config then look there at that SystemMemory? If you have specifics of what you want, I'll be glad to...

Yes, a config space dump from Windows would be perfect. There are several tools for that purpose. I guess RW-everything will work too. Maybe I can find out what these mysterious registers are for with the help of the capability registers.

Mieze

RehabMan · February 3, 2014

Yes, a config space dump from Windows would be perfect. There are several tools for that purpose. I guess RW-everything will work too. Maybe I can find out what these mysterious registers are for with the help of the capability registers.

Mieze

From which base(BAR)? There is BAR1=0x00004001 (io-space?), BAR3=0xB2504004, BAR5=B2500004, the others (BAR2,BAR4,BAR6) are zero.

If you have another tool in mind, let me know... RW-Everything is a bit more manual and there really isn't a "dump everything" function.

Mieze · February 3, 2014

From which base(BAR)? There is BAR1=0x00004001 (io-space?), BAR3=0xB2504004, BAR5=B2500004, the others (BAR2,BAR4,BAR6) are zero.

If you have another tool in mind, let me know... RW-Everything is a bit more manual and there really isn't a "dump everything" function.

No, I don't need the memory or IO space of the NIC, only the complete config space itself.

Mieze

PS: For the latest code please see http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/page-24?do=findComment&comment=1991840

Edited February 6, 2014 by Mieze

RehabMan · February 3, 2014

...

PS: Please try the attached version (sources only)!

Same result.

-------

Attached is PCI_config dump from Windows of Realtek device.

P010000.zip

Mieze · February 3, 2014

Thanks for the config space dump. Ok, next try. It might have been a wrong rx config. Please try the attached version.

Mieze

P. S.: For the latest code please see http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/?p=1991311

New Driver for Realtek RTL8111

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites