Jump to content
Mieze

New Driver for Realtek RTL8111

1,363 posts in this topic

Recommended Posts

Hi @Mieze

I have problems with RTL8111H on 10.13.4.

Kext bad working.

Errors in console

Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
Ethernet [RealtekRTL8111]: Tx stalled? Resetting chipset. ISR=0x80, IMR=0x803f.

What me do?

Share this post


Link to post
Share on other sites
Advertisement

Let me guess: ASPM? Take a look at the BIOS setup and make sure that ASPM is either disabled or that the OS has full control over ASPM. Also check that you are using the latest version of the driver.

 

Mieze

Share this post


Link to post
Share on other sites

Hello fellows.

I have a similar problem but i have 2 operating systems: first is Windows 10 on #1 SSD drive and second on #2 SSD drive macOS Sierra 10.12.6.

My lan card doesn't work when i first booting macOS via Clover.

When i first booting with Windows and then restart computer and back to Clover and choose macOS, Realtek starts working.

2018-05-02 16:36:44.291543+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: EEE support disabled.
2018-05-02 16:36:44.291549+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: RxPoll support enabled.
2018-05-02 16:36:44.291555+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
2018-05-02 16:36:44.291560+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
2018-05-02 16:36:44.291564+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
2018-05-02 16:36:44.291570+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Version 2.2.2 using interrupt mitigate value 0x5f51. Please don't support tonymacx86.com!
2018-05-02 16:36:44.291614+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
2018-05-02 16:36:44.306458+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: RTL8168H/8111H: (Chipset 29) at 0x<private>, 4c:cc:6a:06:fb:2a
2018-05-02 16:36:48.668473+0200 0x102      Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control
2018-05-02 16:38:58.233162+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: EEE support disabled.
2018-05-02 16:38:58.233168+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: RxPoll support enabled.
2018-05-02 16:38:58.233174+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
2018-05-02 16:38:58.233180+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
2018-05-02 16:38:58.233185+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
2018-05-02 16:38:58.233190+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Version 2.2.2 using interrupt mitigate value 0x5f51. Please don't support tonymacx86.com!
2018-05-02 16:38:58.233469+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
2018-05-02 16:38:58.247950+0200 0xd5       Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: RTL8168H/8111H: (Chipset 29) at 0x<private>, 4c:cc:6a:06:fb:2a
2018-05-02 16:39:03.820663+0200 0x102      Default     0x0                  0      kernel: (kernel) Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control

 

Share this post


Link to post
Share on other sites

Mieze,

low priority request for comments on flow control. Please.

 

As I see broadcom chips|drivers do flow control negotiation on startup, while realtek ones do not.

Share this post


Link to post
Share on other sites
1 minute ago, nms said:

Mieze,

low priority request for comments on flow control. Please.

 

As I see broadcom chips|drivers do flow control negotiation on startup, while realtek ones do not.

It's already implemented but it might be necessary to select the medium manually as auto-negotiation not always gives you the desired result.

 

Mieze

Share this post


Link to post
Share on other sites

Hi Mieze,

 

Recently encountered a KP. Please see the specific panic logs.

 

Any help from you greatly appreciated.

 

Thank you.

 

*** Panic Report ***
panic(cpu 3 caller 0xffffff800038776f): Kernel trap at 0xffffff7f80bf17d5, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff81f97b5008, CR3: 0x0000000014cb5000, CR4: 0x00000000003627e0
RAX: 0x0000000000000000, RBX: 0xffffff81ad838000, RCX: 0xffffff81fafebe88, RDX: 0x0000000000000100
RSP: 0xffffff81fafebcc0, RBP: 0xffffff81fafebd40, RSI: 0xffffff8030370000, RDI: 0xffffff81ad838000
R8:  0x0000000000000000, R9:  0x0000000000000001, R10: 0x0000086fc3a7c7ba, R11: 0xffffff8000bebc80
R12: 0xffffff81ad838000, R13: 0x0000000000000000, R14: 0xffffff81f97b5000, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7f80bf17d5, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff81f97b5008, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1

Backtrace (CPU 3), Frame : Return Address
0xffffff81fafeb790 : 0xffffff800026c1c6
0xffffff81fafeb7e0 : 0xffffff8000395274
0xffffff81fafeb820 : 0xffffff8000387544
0xffffff81fafeb890 : 0xffffff800021e1e0
0xffffff81fafeb8b0 : 0xffffff800026bc3c
0xffffff81fafeb9e0 : 0xffffff800026b9fc
0xffffff81fafeba40 : 0xffffff800038776f
0xffffff81fafebbb0 : 0xffffff800021e1e0
0xffffff81fafebbd0 : 0xffffff7f80bf17d5
0xffffff81fafebd40 : 0xffffff7f80bf218c
0xffffff81fafebd60 : 0xffffff7f80bc14ce
0xffffff81fafebd90 : 0xffffff800089ad68
0xffffff81fafebe00 : 0xffffff7f80bc1538
0xffffff81fafebe60 : 0xffffff7f80bc57ac
0xffffff81fafebee0 : 0xffffff800050a665
0xffffff81fafebfa0 : 0xffffff800021d557
      Kernel Extensions in backtrace:
         com.apple.iokit.IONetworkingFamily(3.4)[5A99D802-B477-3D83-9F76-304605479B9F]@0xffffff7f80bb7000->0xffffff7f80bedfff
         com.insanelymac.IntelMausiEthernet(2.4d0)[6FDD7FE8-3965-3DAC-8997-8F76D32D99E5]@0xffffff7f80bee000->0xffffff7f80c01fff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[5A99D802-B477-3D83-9F76-304605479B9F]@0xffffff7f80bb7000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f80a50000

 

Share this post


Link to post
Share on other sites
On 7/18/2018 at 4:24 AM, greythorne said:

Hi Mieze,

 

Recently encountered a KP. Please see the specific panic logs.

 

Any help from you greatly appreciated.

 

Thank you.

 


*** Panic Report ***
panic(cpu 3 caller 0xffffff800038776f): Kernel trap at 0xffffff7f80bf17d5, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff81f97b5008, CR3: 0x0000000014cb5000, CR4: 0x00000000003627e0
RAX: 0x0000000000000000, RBX: 0xffffff81ad838000, RCX: 0xffffff81fafebe88, RDX: 0x0000000000000100
RSP: 0xffffff81fafebcc0, RBP: 0xffffff81fafebd40, RSI: 0xffffff8030370000, RDI: 0xffffff81ad838000
R8:  0x0000000000000000, R9:  0x0000000000000001, R10: 0x0000086fc3a7c7ba, R11: 0xffffff8000bebc80
R12: 0xffffff81ad838000, R13: 0x0000000000000000, R14: 0xffffff81f97b5000, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7f80bf17d5, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff81f97b5008, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1

Backtrace (CPU 3), Frame : Return Address
0xffffff81fafeb790 : 0xffffff800026c1c6
0xffffff81fafeb7e0 : 0xffffff8000395274
0xffffff81fafeb820 : 0xffffff8000387544
0xffffff81fafeb890 : 0xffffff800021e1e0
0xffffff81fafeb8b0 : 0xffffff800026bc3c
0xffffff81fafeb9e0 : 0xffffff800026b9fc
0xffffff81fafeba40 : 0xffffff800038776f
0xffffff81fafebbb0 : 0xffffff800021e1e0
0xffffff81fafebbd0 : 0xffffff7f80bf17d5
0xffffff81fafebd40 : 0xffffff7f80bf218c
0xffffff81fafebd60 : 0xffffff7f80bc14ce
0xffffff81fafebd90 : 0xffffff800089ad68
0xffffff81fafebe00 : 0xffffff7f80bc1538
0xffffff81fafebe60 : 0xffffff7f80bc57ac
0xffffff81fafebee0 : 0xffffff800050a665
0xffffff81fafebfa0 : 0xffffff800021d557
      Kernel Extensions in backtrace:
         com.apple.iokit.IONetworkingFamily(3.4)[5A99D802-B477-3D83-9F76-304605479B9F]@0xffffff7f80bb7000->0xffffff7f80bedfff
         com.insanelymac.IntelMausiEthernet(2.4d0)[6FDD7FE8-3965-3DAC-8997-8F76D32D99E5]@0xffffff7f80bee000->0xffffff7f80c01fff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[5A99D802-B477-3D83-9F76-304605479B9F]@0xffffff7f80bb7000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[AEA4C7F5-CCB0-338B-B471-CF28A9792522]@0xffffff7f80a50000

 

Driver related kernel panics occur when a driver fails to communicate with the OS, which is definitely not the case for IntelMausiEthernet, or when there is something wrong the system, for example messed up system caches, a broken DSDT or a wrong BIOS setting which causes BIOS code to interfere with the driver. I explained this in detail a dozen times before in this thread. Anyway, fix your system to get rid of the KP! By the way, you posted in the wrong thread.

Mieze

Edited by Mieze

Share this post


Link to post
Share on other sites

Hi Mieze! 

Thanks for you work!

I have a problem with a TP-LINK TG-3269 PCI Ethernet Card. It has RTL8169SC Chipset which was supported by [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] till Yosemite and Apple till Snow Leopard. Now I try to install your driver and my ethernet card is not recognized by Mac OS. I tryied to install AppleRTL8169.kext but it doesnt work. 

Can you help me? 

 

Share this post


Link to post
Share on other sites

@andrea99: Sorry but this chip isn't supported because PCI devices are unable to perform 64bit DMA operations and require a completely different approach for a driver.

 

Mieze

Share this post


Link to post
Share on other sites

oh... i just bought it... 

Do you have a list of gigabit ethernet or wifi adapter for high sierra??

because i have only pci slots free... pci-e is free but graphics card take the space. 

 

Share this post


Link to post
Share on other sites

seem to be having some trouble with this on an asus chromebox cn60

detects fine, doesn't get a mac address, it can detect if a cable is being plugged in and unplugged, refuses to get a dhcp address from the router and ends up with a self-assigned ip instead

ethernet appears to work in ubuntu fine

 

kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: PCIe ASPM support disabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: EEE support disabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: RxPoll support enabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: Version 2.2.2 using interrupt mitigate value 0x5f51. Please don't support tonymacx86.com!
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0142.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: RTL8168G/8111G: (Chipset 20) at 0x<private>, 00:00:00:00:00:00
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: Device is WoL capable.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: MSI interrupt index: 1
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: Already in power state 1.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: pollIntervalTime: 1000us
kernel: (RealtekRTL8111) Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
lspci -nnn
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)

 

Edited by vindu

Share this post


Link to post
Share on other sites

Hello dears!

 

Help with solving the problem please!

I have RTL8111.

Kext from Rehab leads to panic.

Kext from Mieze works, but:

After the computer restarts, the adapter disappears from the system, is missing from the system information, and therefore there is no network.

That most strange! In Windows he, too, disappear! That is, in fact as if there is no network adapter.

But the link indicator is lit))

When i reset Bios to default and setting him again - the adapter appears again.

Any ideas friends Thanks in advance!

 

Hardware:

ACER Veriton Z4640G: Mac OS X 10.14; Clover; CPU: Intel Core i3-6100; GPU: Intel HD Graphics 530

438705_Snimok_ehkrana_2018-10-26_v_14.50.58.png

438706_Snimok_ehkrana_2018-10-26_v_14.51.39.png

438831_438765_myhackreg.zip

Share this post


Link to post
Share on other sites

kernel .Error (AppleSystemPolicy) Setting mach port for daemon

kernel .Error: (Sandbox) Sandbox: identityservices(292) System Policy: deny(1) system-privilege 12010

 

 kernel: (AppleCredentialManager) ACM: findCredentialSet: returning, err = -2.

Share this post


Link to post
Share on other sites
1 minute ago, jinbingmao said:

kernel .Error (AppleSystemPolicy) Setting mach port for daemon

kernel .Error: (Sandbox) Sandbox: identityservices(292) System Policy: deny(1) system-privilege 12010

 

 kernel: (AppleCredentialManager) ACM: findCredentialSet: returning, err = -2.

Sorry, but this is off-topic.

Share this post


Link to post
Share on other sites

Low priority question ahead (-;

 

What is -- mDNS_Keepalive?

 

Excepts from log are below

 

2018-12-23 11:03:30.289345+0300 0x2cd      Default     0x0                  0      0    kernel: (kernel) Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.
2018-12-23 11:03:32.515865+0300 0x117      Default     0x0                  0      0    kernel: (kernel) Ethernet [RealtekRTL8111]: pollIntervalTime: 170us
2018-12-23 11:03:32.526669+0300 0x117      Default     0x0                  0      0    kernel: (kernel) Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control
2018-12-23 11:03:33.143924+0300 0x458      Info        0x0                  208    0    mDNSResponder: [com.apple.mDNSResponder:AllINFO] CheckInterfaceSupport: Interface en0 service IOEthernetInterface parent RTL8111
2018-12-23 11:03:33.143933+0300 0x458      Info        0x0                  208    0    mDNSResponder: [com.apple.mDNSResponder:AllINFO] CheckInterfaceSupport: No mDNS_Keepalive for interface en0/IOEthernetInterface/RTL8111
2018-12-23 11:03:33.144238+0300 0x458      Info        0x0                  208    0    mDNSResponder: [com.apple.mDNSResponder:AllINFO] CheckInterfaceSupport: Interface en0 service IOEthernetInterface parent RTL8111
2018-12-23 11:03:33.144247+0300 0x458      Info        0x0                  208    0    mDNSResponder: [com.apple.mDNSResponder:AllINFO] CheckInterfaceSupport: No mDNS_Keepalive for interface en0/IOEthernetInterface/RTL8111
2018-12-23 11:03:33.207979+0300 0x458      Info        0x0                  208    0    mDNSResponder: [com.apple.mDNSResponder:AllINFO] CheckInterfaceSupport: Interface en0 service IOEthernetInterface parent RTL8111

 

Share this post


Link to post
Share on other sites

Hello Mieze, recently I purchased the following motherboard https://www.asrock.com/mb/Intel/Z390%20Phantom%20Gaming%20SLIac/index.asp#Specification

 

It comes with the Realtek LAN chip RTL8125AG (Dragon). Do you plan on supporting this chip in the future. I have been searching all over but no Realtek kexts work right now.

 

Thank you.

Share this post


Link to post
Share on other sites
8 hours ago, Luiz Saluti said:

It comes with the Realtek LAN chip RTL8125AG (Dragon). Do you plan on supporting this chip in the future. I have been searching all over but no Realtek kexts work right now.

Sure, I will add support for new devices as soon as Realtek releases Linux driver sources so that I can learn how to handle them.

 

Mieze :cat:

Share this post


Link to post
Share on other sites
2 hours ago, Mieze said:

Sure, I will add support for new devices as soon as Realtek releases Linux driver sources so that I can learn how to handle them.

 

Mieze :cat:

Great news! If you ever need any information regarding the chip, I can provide it to you.

Share this post


Link to post
Share on other sites
On 1/7/2019 at 5:25 PM, Mieze said:

Sure, I will add support for new devices as soon as Realtek releases Linux driver sources so that I can learn how to handle them.

 

Mieze :cat:

 

Hello Mieze,

 

I just tested Realtek drivers for the 8125 chip in a Ubuntu live USB (18.04 LTS). It worked fine and connection was great. I am attaching it here in case you have plans to support it in your future releases.

 

Here is the original link from the realtek website, if you wish to download it directly.

 

https://www.realtek.com/zh-tw/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

 

Cheers....

r8125-9.001.00.tar.zip

Share this post


Link to post
Share on other sites

Having problems with RTL8111H on High Sierra. Adapter appears, but only works a few times. Usually I have to restart 3 times the computer to get it working, the rest of times It doesn't works or It works too slowly. I can't find any ASPM option in my B350M Bazooka bios.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Mieze
      Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy.
       
      As of now the driver supports the following members the RTL810X Fast Ethernet family:
      RTL8101E RTL8102E RTL8103E RTL8401E RTL8105E RTL8402 RTL8106E RTL8106EUS RTL8107E   Here is a list of the driver's basic features:
      Supports Sierra (maybe El Capitan). 64 bit architecture only. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2. Built using Xcode 4.6.3.  
      Changelog Version 2.0.1 (2018-05-10): Fixes a problem with retrieval of the permanent MAC address on some chips. Version 2.0.0 (2017-04-04): Uses Apple's private driver interface introduced with 10.8. Adds support for the RTL8107E. Supports packet scheduling with QFQ. Adds support for flow control and EEE. Version 1.0.0 (2014-05-24): First offical release.     Installation   Before you install the driver you have to remove any installed driver for RTL810X. Goto /S/L/E and delete the old driver. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Install the new driver and recreate the kernel cache. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.   Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      Getting the driver
      There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/ The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100   Mieze
    • By Mieze
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V  
      Key Features of the Driver
      Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.  
      Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS.   Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.  
      FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
×