Jump to content
Slice

RealtekR1000 v3

127 posts in this topic

Recommended Posts

Tried this driver on my ancient GA-EP45-DS3 and it seems to work a lot better than the lnx2mac driver I was using previously. :)

 

Actually my ethernet worked fine (out of the box) under 10.5 and 10.6. Installing 10.7 on a different disk required a driver and it also somehow killed the ethernet functionality on the SL partition, and I had to install lnx2mac driver on both.

 

Anyway thanks for this driver, it works great in a 32-bit kernel (some hardware I'm using limits me to 32-bit).

 

edit - I spoke too soon... the driver worked great until a reboot. Now the DHCP doesn't work properly (gets some random address) and although I can set things manually, it doesn't connect to the network.

 

The chip is a Realtek 8111C - it has 2 of them in fact, with identical results on both :(

 

So anyone know why this would work on install, but then stop working completely?

Share this post


Link to post
Share on other sites
Advertisement

this kext was working great on 10.10.0. But today after the upgrade to 10.10.1, the network just stops/hangs after awhile?. anyone else seeing this? any suggestions?

 

log messages - 

 

Nov 17 22:10:51 Toms-Hack.local configd[27]: network changed: v4(en0+:192.168.1.17) DNS+ Proxy+ SMB

Nov 17 22:11:41 Toms-Hack kernel[0]: en0: Tx_skbuff[902] is NULL

Nov 17 22:11:45 Toms-Hack kernel[0]: en0: Tx_skbuff[700] is NULL

Nov 17 22:15:51 Toms-Hack kernel[0]: en0: Tx_skbuff[1011] is NULL

Nov 17 22:15:52 Toms-Hack kernel[0]: en0: Tx_skbuff[888] is NULL

Nov 17 22:16:01 Toms-Hack kernel[0]: en0: Tx_skbuff[652] is NULL

Nov 17 22:16:05 Toms-Hack kernel[0]: en0: TX_RING_IS_FULL, stalling

Nov 17 22:30:11 Toms-Hack.local discoveryd[50]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en0, 65

Share this post


Link to post
Share on other sites

After discovered, Mieze kext works very well with 10.10.1 and samba copying too,
I decide to give this a second look.
 
RealtekR1000SL_src_[25.04.2013]
 
recompile this under Xcode 6.1.1 (3 warnings, 1=unused, 2,3=dead storage)
I have make no attempt to fix this,
 
first boot
2014-12-23 6:50:46.000 PM kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x4,00
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: Found chip reg=3f4000c0
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: Realtek RTL8168C/8111C (mcfg 19)
2014-12-23 6:50:46.000 PM kernel[0]: identified as RTL8168C/8111C
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: RTL8168CHwPhyConfig
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: 1000Mbps Full-duplex operation, TBI Link OK
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: Link Status: Linked
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: Link Speed: 100Mbps
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: Duplex mode: Full-Duplex
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: registerWithPolicyMaker
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: configureInterface
2014-12-23 6:50:46.000 PM kernel[0]: RTL8xxx@0xee00: attaching as en0
2014-12-23 6:50:46.000 PM kernel[0]: en0: start: returning '1'
2014-12-23 6:50:46.000 PM kernel[0]: en0: setPowerState(1)
 
Auto set speed to 100 Mbps (tested very stable, over 2.5Mbps on transmission dl, smb copy at 1Gbyte per minutes)
 
Set Speed manually to 1000Mbps in preference, 
 
2014-12-23 7:02:52.000 PM kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x4,00
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: Found chip reg=3f4000c0
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: Realtek RTL8168C/8111C (mcfg 19)
2014-12-23 7:02:52.000 PM kernel[0]: identified as RTL8168C/8111C
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: RTL8168CHwPhyConfig
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: 1000Mbps Full-duplex operation, TBI Link OK
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: Link Status: Linked
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: Link Speed: 1000Mbps
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: Duplex mode: Full-Duplex
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: registerWithPolicyMaker
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: configureInterface
2014-12-23 7:02:52.000 PM kernel[0]: RTL8xxx@0xee00: attaching as en0
 
Retest,  seem very stable,  samba copying at >4Gb  per min. [ to Version C (installed R1000SL) ; from Ver-G (Mieze Kext) ]
 
This R1000SL will not work on Version G.

 

google: 

RealtekR1000SL_src_[25.04.2013]

it from hackintoshOSX

Share this post


Link to post
Share on other sites

ReTest: Slice's:  RealtekR1000SL_src_20.12.2013

 

ReCompile with Xcode 6.1.1

7 warnings,  no attempt to fix it.

 

Test Smb copy at >5G per minutes

also stable.

and detect correct speed at 1000 Mbps

 

 

2014-12-23 9:04:27.000 PM kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x4,00
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: Found chip reg=3f4000c0
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: Realtek RTL8168C/8111C (mcfg 19)
2014-12-23 9:04:27.000 PM kernel[0]: identified as RTL8168C/8111C
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: RTL8168CHwPhyConfig
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: 1000Mbps Full-duplex operation, TBI Link OK
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: Link Status: Linked
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: Link Speed: 1000Mbps
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: Duplex mode: Full-Duplex
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: registerWithPolicyMaker
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: setPowerState(1)
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: configureInterface
2014-12-23 9:04:27.000 PM kernel[0]: RTL8xxx@0xee00: attaching as en0
2014-12-23 9:04:27.000 PM kernel[0]: en0: start: returning '1'

 


Conclusion:

 

tluck's problem may be  fixed:   by reCompile with Xcode 6.1.1

Share this post


Link to post
Share on other sites

error message comes from this code fragment:

int speed_opt = SPEED_100;

int duplex_opt = DUPLEX_FULL;

int autoneg_opt = AUTONEG_ENABLE;

int val = 0;

 

// FIXME -- WTF does this do?!

// if TBI is not endbled

if (!(ReadMMIO8(PHYstatus) & TBI_Enable))

{

val = ReadGMII16(PHY_AUTO_NEGO_REG);

val |= PHY_Cap_PAUSE | PHY_Cap_ASYM_PAUSE ;

 

R1000SetMedium(speed_opt, duplex_opt, autoneg_opt);

}// end of TBI is not enabled

else

{

IODelay(100);

DLog("1000Mbps Full-duplex operation, TBI Link %s\n", (ReadMMIO32(CSIDR) & TBILinkOK) ? "OK" : "Failed" );

}// end of TBI is not enabled

 
default set to 100mbps, and failed to set autoneg_opt.
 
did you try,  on system settings, network pref, advance and set settings manually.

the only other reference to TBI_Enabled is in the header.

Does  this means anything to you.

 

/*rtl8169_PHYstatus (MAC offset 0x6C)*/

TBI_Enable = 0x80, /* Not defined in RTL8168 not RTL8101 */

TxFlowCtrl = 0x40,

RxFlowCtrl = 0x20,

_1000Mbps = 0x10, /* Linux _1000bps */ /* Not in RTL8101 */

_100Mbps = 0x08, /* Linux _100bps */

_10Mbps = 0x04, /* Linux _10bps */

LinkStatus = 0x02,

FullDup = 0x01,

 

Share this post


Link to post
Share on other sites

darn. the RTL 8168E still has issues on 10.10.2 - compiled with Xcode 6.1.1 target 10.10

i plugged into a wifi router which is 100BT and still gets stuck after awhile.

 

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: Realtek RTL8168E-VL/8111E-VL (mcfg 35)

Jan  3 13:53:42 localhost kernel[0]: identified as RTL8168E-VL/8111E-VL

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: 1000Mbps Full-duplex operation, TBI Link Failed

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: Link Status: Not Linked

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: registerWithPolicyMaker

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: setPowerState(1)

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: configureInterface

Jan  3 13:53:42 localhost kernel[0]: RTL8xxx@0xee00: attaching as en0

Jan  3 13:53:42 localhost kernel[0]: en0: start: returning '1'

Jan  3 13:53:52 localhost kernel[0]: en0: enable

Jan  3 13:53:52 localhost kernel[0]: en0: setActivationLevel(2)

Jan  3 13:53:52 localhost kernel[0]: en0: Selected medium is NULL, forcing to autonegotiation

Jan  3 13:53:52 localhost kernel[0]: en0: selectMedium, index=6

Jan  3 13:53:52 localhost kernel[0]: en0: R1000SetMedium(0x3, 0x2, 0x1)

Jan  3 13:53:52 localhost kernel[0]: en0: PHYstatus=88, LinkStatus=2

Jan  3 13:53:52 localhost kernel[0]: en0: setLinkStatus but no PHYStatus

Jan  3 13:53:54 localhost kernel[0]: en0: Link up

Jan  3 14:13:44 Toms-Hack kernel[0]: en0: Tx_skbuff[596] is NULL

Jan  3 14:16:18 Toms-Hack kernel[0]: en0: Tx_skbuff[494] is NULL

Jan  3 14:18:09 Toms-Hack kernel[0]: en0: Tx_skbuff[642] is NULL

Share this post


Link to post
Share on other sites

RTL8168E-VL/8111E-VL

 

Is this detected correctly.

 

when using wifi, i have similar experience on network hang, 

fixed by manually change MTU to 1280. (pref-network-adv-hardware)

 

may be you can try this.


Also,

Andy Vandijck

just posted his version of RTL kext, you may try that too.

 

I will test that kext, sunday night, after the games.

 

(In the development section)

Share this post


Link to post
Share on other sites

one more thing.

 

Error messages is from this fragment:

 

//DLog("R1000TxInterrupt(%#04x)\n", intrStatus);

BUMP_ETHER_TX_COUNTER(interrupts);

 

// check Tx error status

if (intrStatus & TxErr)

{

DLog("R1000TxInterrupt: Tx abort\n");

BUMP_NET_COUNTER(outputErrors);

}

 

// clean up after sent buffers

ulong ldirty_tx = dirty_tx;

ulong tx_left = cur_tx - ldirty_tx;

//DLog("R1000TxInterrupt cur_tx %d, dirty_tx %d, tx_left %d\n", cur_tx, dirty_tx, tx_left);

 

tx_left = min(tx_left, max_interrupt_work);

while (tx_left > 0)

{

ulong entry = ldirty_tx % n_tx_desc;

if ((OSSwapLittleToHostInt32(TxDescArray[entry].status) & DescOwn) == 0)

{

if (Tx_skbuff[entry] != NULL)

{

/*

DLog("packet sent, packet size %u, phys addr %x%08x\n", 

mbuf_len(Tx_skbuff[entry]),

OSSwapLittleToHostInt32(TxDescArray[entry].buf_Haddr),

OSSwapLittleToHostInt32(TxDescArray[entry].buf_addr));

*/

// Clean up after this packet

freePacket(Tx_skbuff[entry]);

Tx_skbuff[entry] = NULL;

BUMP_NET_COUNTER(outputPackets);

}

else

{

// Queue slot was reserved but not used

// See outputPacket() for possible causes

DLog("Tx_skbuff[%d] is NULL\n", entry);

}

 

ldirty_tx++;

tx_left--;

}

else 

{

// DLog("Tx packet at index %d is pending\n", entry);

break;

}

}

 

 

looks like, interrupt and timing problem, it is beyond my ability to continue from this.

 

 

 

if your motherboard is very old,  LAN may share interrupt with printer or other devices.

you may try, in bios, disable printer device.

Share this post


Link to post
Share on other sites

in the meantime, I have gone back to an older kext pulled off the RealTek download site listed as v2.0.6 for Lion.

This one works well enough for what i need it do. And is just as fast as my USB3/Ethernet on 100BT. 

seems to chew up about 15% of my cpu if i SCP a large file to the box. but then again thats about all this box does as HTPC with Plex.

The USB ethernet chews up about 22% CPU.

 

Realtek 8168/8101E Gigabit Ethernet:

 

  Name: ethernet

  Type: Ethernet

  Bus: PCI

  Slot: Ethernet

  Vendor ID: 0x10ec

  Device ID: 0x8168

  Subsystem Vendor ID: 0x1458

  Subsystem ID: 0xe000

  Revision ID: 0x0006

  Link Width: x1

  BSD name: en0

  Kext name: AppleRTL8169Ethernet.kext

  Location: /System/Library/Extensions/AppleRTL8169Ethernet.kext

  Version: 1.1.4a5

Share this post


Link to post
Share on other sites

I have used the same kext from RealTek.

works fine, most of the time.

Until you try to use transmission to download.

It will be fine, if dl speed were slow,

you will kp when speed approach 200kps.

It happen on all the machine i tested. (GA-EP43, Rev-c,  Acer-605 Ver-G, AMD-Ver-C)

All i can say is good luck!


On ver-G, it shows in Pref-Network as connected, but not really.

 

Look at this forum, for user that has LAN  problem on 10.10.1, 

you will be find out, this is the norm, not the exception.


i think, i did wasted my time here.


Quote

I was merely reporting my observation because it kinnda surprised me.

UnQuote

 

Why not test Andy Vandijck, kext

or try disable Printer on BIOS..

 

 

Is this, A normal tester will do?

 

Share this post


Link to post
Share on other sites

@aww - yes i had read there are/were issues with that old kext. but i did not see any issues in my limited usage. Certainly i prefer to use a newer version. So i am testing andy v's RealTek8111.kext today.

so far so good. a smidge faster - was able to transfer a file 11.2 MiB/s (1000BT to wireless router ->wireless extender @450Mbps -> 100BT

and a few % less CPU. but again this not a true performance test. I just want a stable interface!

 

$ grep kernel /var/log/system.log|grep Realt

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: Initialized emulated MAC address = 7C:6D:F8:AC:9E:1F

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: Version 1.3.5 using interrupt mitigate value 0xcf58.

Jan  4 10:51:51 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: detected RTL8168E-VL/8111E-VL (Chipset 16) at 0xffffff8108766000

Jan  4 10:51:53 Toms-Hack kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Jan  4 10:54:24 Toms-Hack kernel[0]: considerRebuildOfPrelinkedKernel com.insanelymac.RealtekRTL8111 triggered rebuild

Share this post


Link to post
Share on other sites

Not working on RTL8110 (device-id:8167).
I added the device id to the info.plist and kext loads but no connection.

Could you please add support for this chip?!

 

EDIT: Sorry, this is a PCI card and won't work with a PCIe driver.

Share this post


Link to post
Share on other sites

Hi guys,

 

Is there any solution for the wake on lan feature on this device? I tired another "Mieze" driver for this card, but the upload speed is terrible, 1mbit/s.

 

Realtek 8168/8101E Gigabit Ethernet:

 

  Name: ethernet

  Type: Ethernet

  Bus: PCI

  Slot: Ethernet

  Vendor ID: 0x10ec

  Device ID: 0x8168

  Subsystem Vendor ID: 0x1043

  Subsystem ID: 0x8367

  Revision ID: 0x0002

  Link Width: x1

  BSD name: en0

  Kext name: RealtekR1000SL.kext

  Location: /System/Library/Extensions/RealtekR1000SL.kext

  Version: 3.1.2

Share this post


Link to post
Share on other sites

I want to present you updated RealtekR1000 driver. I added support for new chips according to linux's sources.

Now it supports RTL8168E,F/8111E,F.It works for me and works better then v2.0.6 from realtek.com.tw. Now I have no problems with sleep/wake. With native driver I sometimes lose LAN after wake.With this driver never.

 

I have a little problem. Network utility shows Link Speed = 0Can someone help me to resolve this Resolved!

Unplug cable

attachicon.gifScreen Shot 2013-03-11 at 21.05.46.png

Plug cable

attachicon.gifScreen Shot 2013-03-11 at 21.05.25.png

 

UPDATE. In this version I applied my own inventions so my driver differs from native.

 

 

25.04.2013

Corrected a mistake with warm boot after Windows. Thanks for Mieze, dmazar, rehabman.

Updated part for RTL 8105/RTL8136

This kext is compiled under SL, XCode 3.2.5. For use in ML I'll check little later. EDITED: I checked, it works in ML 10.8.3.

attachicon.gifRealtekR1000SL.kext-v304.zip

attachicon.gifRealtekR1000SL_src_25.04.2013.zip

 

15.12.2013

I made some changes according to official Realtek driver 8.037, newest for now. I can't say I take it as a whole. No, my driver is cropped and may not work for some chips.

Anyway it tested for me in Mavericks.

Change log:

- adopted for new chips RTL8168GU/8111GU, 8411B, RTL8168EP/8111EP . But not tested

- autolink to 1000Mb/s

- some functions for WOL, not tested.

 

17.12.2013

More changes from linux sources implemented

attachicon.gifRealtekR1000SL_src_17.12.2013.zip

attachicon.gifRealtekR1000SL.kext-311b-Snow.zip

 

20.12.2013

Implemented WoL as Mieze did.

attachicon.gifRealtekR1000SL_src_20.12.2013.zip

attachicon.gifRealtekR1000SL.kext-312.zip

 

24.12.2013

More codes for 8105E but not complete

attachicon.gifRealtekR1000SL_src_22.12.2013.zip

 

I can't download any file.

Share this post


Link to post
Share on other sites

Hi Slice I made an Automator Application very cool and fast Installer for your driver  :D


Thats working absolutely perfect inside OS Yosemite 10.10.3 


Thank you very mutch  :)


Ps;This will Remove the old Driver on S/L/E if you have one


and Install the new Driver on S / L / E 


 


This is the name


Realtek R1000SL Ethernet.app


 


intern11.png


The step 


017.png


 


0114.png


 


0211.png


 


 


The Result  :thumbsup_anim:


140.png


 


224.png


 


 


Updating the Driver


simply changing the kext inside Bundle / Contents / Resources  / RealtekR1 


319.png


Share this post


Link to post
Share on other sites

I can't download any file.

I forgot that the forum lose all attachments.

Now I updated the first post with latest driver v312 and its sources.

As usual sources are free and I am open to apply your patches to them.

 

chris1111

Thanks! I hope someone will use it.

Share this post


Link to post
Share on other sites

UPDATE. In this version I applied my own inventions so my driver differs from native.

05.05.2015

Sorry about broken links. There is new one. My latest sources

attachicon.gifRealtekR1000SL_src_20.02.2014.zip

attachicon.gifRealtekR1000SL.kext-v312.zip

 

Hello Slice,

Only a curiosity,

This is a mistake? Any problem?
post-1511929-0-48597300-1437785814_thumb.png
Note. I'm learning to program in XCode, I am Web developer, Windows and mobile devices.
Maybe one day I can contribute to the forum  :P
 
<--  -->
 
I compiled and am using the kext, much better than the previous
Thank You Slice!
Edited by #McFly

Share this post


Link to post
Share on other sites

Tried this driver today because Mieze's driver is not usable due to lost interrupts.

 

:no: Lost interrupts are nothing more than cosmetic issues.

 

Mieze

Share this post


Link to post
Share on other sites

System keeps the ethernet card awake in sleep and sends, constantly, requests to the router.

Device: Realtek 8111b  (RJ45)

Driver ver: 3

 

Update 1

 

In addition there's no wake on lan option in Energy saver.

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 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). 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 Yosemite. 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. 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 Mieze
      Driver for recent Intel onboard LAN controllers. 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
      I219LM I219V 200 and 300 Series
      I219LM I219V Please see the project's homepage at http://www.insanelymac.com/forum/topic/304235-intelmausiethernetkext-for-intel-onboard-lan/ for a detailed project description.
    • By liuhongxin1993
      ASUS x99-e-10G ws  
      X550-T2
      http://pci-ids.ucw.cz/read/PC/8086/1563
      https://downloadcenter.intel.com/download/14687/?product=88209
      Requesting Linux compilation of High Sierra 10.13.4

      ixgbe-5.3.6.tar.zip
    • By ITzTravelInTime
      This is a dedicated thread about the intel 8255X based ethernet cards which, although being old (but also very cheap and easy to find used online), they still works in the latest macOS releases today i tested mine with the 64 bit compiled AppleIntel8255X kext and works like a charm! stable and withou any issues with mine 100 mbit managed ethernet switch and also without suffering of problems like connection dieing under heavy load or sleep/wake issues, so just to report that i have create this dedicated thread about and also i leave the kext as an attachment, in this post, this may be usefoul to have cheap working ethernet for hackintosh machines running the latest macOS or just to reuse old hardware some one can have laying around.
      AppleIntel8255x.kext.zip
    • By ITzTravelInTime
      I have started this thread to discuss about old and very cheap ethernet cards working in the latest macOS releases, cards who just uses old ethernet controllers or are new and cheap cards with old ethernet controllers, this thread is just to discuss about such cards and also to have a list in the first post with reported working cards with drivers linked.
      To contribute you have to report which card of this kind is working for you and which driver or method you followed to get it wo work and also which issues you have, and then it will be added in the list.
      I start reporting cards which worked for me, yours will be added in the future:
      intel 8255X based cards:
                just works using the AppleIntel8255X kext (look in the attachments) and seems to be stable with no issues
       
      And also there are some cards i am curious to see if can work with mac, so i leave this part at the end of the post, do you know if it's possible to get realtek pci (not pci express) ethernet cards working in the latest mac os? i have a few of them and i have difficulties fining drivers for mac, having a driver for the latest mac wil help me in creating also a youtube video with the cheapest hackintosh compatible ethernet cards
       
      AppleIntel8255x.kext.zip
×