Jump to content
Slice

RealtekR1000 v3

127 posts in this topic

Recommended Posts

Advertisement

This kext is way better than the older ones, no more lag or loose of signal during normal use.

Also sleep seems to work fine.

Thank you, this really completes my stable build using an otherwise already well supported GA-Z68X-UD3H board.

Share this post


Link to post
Share on other sites

THANKS!

 

I use (since 9 months) the Lnx2Mac Realtek RTL81xx driver for my LAN (EP-35 Board) - worked fine (also has sleep / speed fixes) , but i always try some new things.

 

http://lnx2mac.blogs...osx-driver.html (v0.0.90) Lnx2Mac's Realtek RTL81xx Driver... Due to the shortcomings of the current Realtek 81xx Hackintosh drivers (such as lack of or limited support of 8111E, 32/64-bit, sleep issues), I endeavored to port the Linux RTL81xx driver to Mac OS X.)

 

Problem with rtl8168 ( Hersteller-ID: 0x10ec, Geräte-ID: 0x8168, Subsystem-Hersteller-ID: 0x1458, Subsystem-ID: 0xe000, Versions-ID: 0x0001)

Your kext get loaded : org.chucko.driver.RealtekR1000 (3.0.0d1)

but no Ethernet available. OS X 10.8.3 dev D76, Gigabyte EP35

 

system.log (yours):

10.03.13 10:45:20,000 kernel[0]: RealtekR1000: init

10.03.13 10:45:20,000 kernel[0]: RealtekR1000: start

10.03.13 10:45:20,000 kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x4,00

10.03.13 10:45:20,000 kernel[0]: RTL8xxx@0xd000: Found chip reg=bb500700 // = val32 = ReadMMIO32(TxConfig);

10.03.13 10:45:20,000 kernel[0]: RTL8xxx@0xd000: Unknown device type, reg = 0xb8000000

// code section in voidRealtekR1000::R1000GetMacVersion(). mfg not set in case ...

bb500700 // u32 val32 = ReadMMIO32(TxConfig);

bb500700 & 0xFC800000 = 0xB8000000 // u32 reg = val32 & 0xFC800000; // was 0x7C800000

But there is no case for 0xB8000000 !

SOLUTION:

But if you would use // was 0x7C800000 vs 0xFC800000 for the & , then it would be in case as 0x38000000

0xbb500700 & 0x7C800000 = 0x38000000 (vs bb500700 & 0xFC800000 = 0xB8000000 ), and case 0x3800000, or change value the case to B8000000, it would work - side effects fpor others unknown of course.

 

void RealtekR1000::R1000GetMacVersion()
{
u32 val32 = ReadMMIO32(TxConfig);
u32 reg = val32 & 0xFC800000; // was 0x7C800000
u32 ICVerID = val32 & 0x00700000;
DLog("Found chip reg=%08x\n", val32);
switch (reg)
{
.......
case 0x38000000:
if(ICVerID == 0x00000000) {
mcfg = MCFG_8168B_2;
} else if(ICVerID == 0x00500000) {
mcfg = MCFG_8168B_3;
} else {
mcfg = MCFG_8168B_3;
}
break;
....
default:
mcfg = -1;
break;
}

if (mcfg < 0)
{
DLog("Unknown device type, reg = %#08x\n", reg);
}
else
{
...
}

 

10.03.13 10:45:20,000 kernel[0]: RTL8xxx@0xd000: R1000InitBoard: **** Ethernet chip unrecognized ****

10.03.13 10:45:20,000 kernel[0]: RTL8xxx@0xd000: start: Failed, R1000ProbeAndStartBoard returned false

10.03.13 10:45:20,000 kernel[0]: RTL8xxx@0xd000: start: returning '0'

 

 

system.log with working (v0.0.90) Lnx2Mac's Realtek RTL81xx Driver:

10.03.13 02:06:28,000 kernel[0]: [RealtekRTL81xx:init] RealtekRTL81xx.kext v0.0.90 ©2010-2011 by Lnx2Mac (lnx2mac@gmail.com)

10.03.13 02:06:28,000 kernel[0]: [RealtekRTL81xx:init] _logLevel is now 132 (0x0084)

10.03.13 02:06:28,000 kernel[0]: [RealtekRTL81xx:init] Using updated PHY config method

10.03.13 02:06:28,000 kernel[0]: [RealtekRTL81xx:init] init completed

10.03.13 02:06:28,000 kernel[0]: [RTL81xx@0xd000:rtl8168_init_board] NIC identified as RTL8168B/8111B mcfg=2

Share this post


Link to post
Share on other sites

OK, thank you for the note. Will correct.

lnx2mac driver doesn't work for me, I don't remember exactly what is the problem, like my chip 8111F is not supported.

Share this post


Link to post
Share on other sites

 

But if you would use // was 0x7C800000 vs 0xFC800000 for the & , then it would be in case as 0x38000000

0xbb500700 & 0x7C800000 = 0x38000000 (vs bb500700 & 0xFC800000 = 0xB8000000 ), and case 0x3800000, or change value the case to B8000000, it would work - side effects fpor others unknown of course.

 

The reason is an attempt to join with 8169

 case 0x98000000:
  mcfg = MCFG_8169SC_2;
  break;

I will add case 0xB8000000

Share this post


Link to post
Share on other sites

Slice,

 

I start to love this driver as it is first RTL driver which offers me working WOL on my GA-P35-DS4 under ML 10.8.2!

I just started to play with it and currently I see there is problem with idle sleep.

With LNX2MAC driver sleep works perfectly - so it looks my system is OK.

Also - when system is woken via WOL, wakeup reason is undefined:

 

 

Mar 10 21:28:27 Piotr-Desktop kernel[0]: en0: disable
Mar 10 21:28:27 Piotr-Desktop kernel[0]: en0: setActivationLevel(0)
Mar 10 21:28:27 Piotr-Desktop kernel[0]: en0: setPowerState(0)
Mar 10 21:28:27 Piotr-Desktop kernel[0]: en0: R1000Suspend
Mar 10 21:28:27 Piotr-Desktop kernel[0]: Wake reason: ?
Mar 10 21:28:56 Piotr-Desktop kernel[0]: Previous Sleep Cause: 5
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: setPowerState(1)
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: R1000Resume
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: R1000ResetTask
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: enable
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: setActivationLevel(2)
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: Selected medium index 5
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: selectMedium, index=5
Mar 10 21:28:56 Piotr-Desktop kernel[0]: en0: R1000SetMedium(0x3, 0x2, 0x2)
Mar 10 21:28:56 Piotr-Desktop.local configd[19]: network changed: v4(en0-:192.168.1.1) DNS- Proxy- SMB 

 

Maybe this explains why WOL wake system with monitor off for 15-20sec and next system returns to sleep.

Setting ttyspreventsleep not helps, but using caffeination -s allows to keep system ON.

 

Anyway - million thx for excellent work!

Share this post


Link to post
Share on other sites

Hi Slice,

Thanks for your efforts.

Tried to use your kext (3.0.1) for device 10ec:8136 in lenovo z560, but it won't work.

 

 

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: init

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: start

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x7,00

11.03.13 08:34:47,000 kernel[0]: com_chucko_RealtekR1000: Ethernet address XX:XX:XX:XX:XX:XX

11.03.13 08:34:47,000 kernel[0]: RTL8xxx@0x2000: attaching as en0

11.03.13 08:34:47,000 kernel[0]: en0: start: returning '1'

11.03.13 08:34:47,000 kernel[0]: en0: enable

11.03.13 08:34:47,000 kernel[0]: en0: setActivationLevel(2)

11.03.13 08:34:47,000 kernel[0]: en0: Selected medium is NULL, forcing to autonegotiation

11.03.13 08:34:47,000 kernel[0]: en0: selectMedium, index=6

11.03.13 08:34:47,000 kernel[0]: en0: R1000SetMedium(0x2, 0x2, 0x1)

11.03.13 08:34:47,000 kernel[0]: en0: RTLN8101NicReset

11.03.13 08:34:47,000 kernel[0]: en0: RTL8100DSM

11.03.13 08:34:47,000 kernel[0]: en0: RTL8100DisableEEE called on an unsupported chip.

 

Is this device supported? ID was in plist.

 

Regards

Share this post


Link to post
Share on other sites

Slice,

I don't know what things are improved in 3.0.2 but I decided give you just small update after going to 3.0.2:

-idle sleep is still not working

-WOL still gives "wake reason: ?" and turns-off PC after 15sec

-the same like previous version driver auto detects my GE network like 100Mb/s. Manual selection to 1GE works OK.

Share this post


Link to post
Share on other sites

I've been testing this version on my MSI Z77MA-G45 mobo and so far it works flawlessly! Latency seems down, downloads about 10% faster - sleep/wake is problem free. LNX2MAC has issues on my mobo when waking sometimes the network is dead and the OS needs to be rebooted to get the network going again. Nice job, thanks!

Share this post


Link to post
Share on other sites

Hi, Slice! Congratulations for your work! :D

 

Will your driver also work for the RTL8105E (10/100), which i think is a variation of the 8139? Or, better yet, can you add support for it in your driver (which i can personally confirm it works for the 8111).

 

Best regards!

Share this post


Link to post
Share on other sites

Hi Slice,

Thanks for your efforts.

Tried to use your kext (3.0.1) for device 10ec:8136 in lenovo z560, but it won't work.

 

 

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: init

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: start

11.03.13 08:34:47,000 kernel[0]: RealtekR1000: R1000InitBoard @ PCI 0x7,00

11.03.13 08:34:47,000 kernel[0]: com_chucko_RealtekR1000: Ethernet address XX:XX:XX:XX:XX:XX

11.03.13 08:34:47,000 kernel[0]: RTL8xxx@0x2000: attaching as en0

11.03.13 08:34:47,000 kernel[0]: en0: start: returning '1'

11.03.13 08:34:47,000 kernel[0]: en0: enable

11.03.13 08:34:47,000 kernel[0]: en0: setActivationLevel(2)

11.03.13 08:34:47,000 kernel[0]: en0: Selected medium is NULL, forcing to autonegotiation

11.03.13 08:34:47,000 kernel[0]: en0: selectMedium, index=6

11.03.13 08:34:47,000 kernel[0]: en0: R1000SetMedium(0x2, 0x2, 0x1)

11.03.13 08:34:47,000 kernel[0]: en0: RTLN8101NicReset

11.03.13 08:34:47,000 kernel[0]: en0: RTL8100DSM

11.03.13 08:34:47,000 kernel[0]: en0: RTL8100DisableEEE called on an unsupported chip.

 

Is this device supported? ID was in plist.

 

Regards

Hi, Slice! Congratulations for your work! :D

 

Will your driver also work for the RTL8105E (10/100), which i think is a variation of the 8139? Or, better yet, can you add support for it in your driver (which i can personally confirm it works for the 8111).

 

Best regards!

Sorry guys, I made no new support for 8105/8136 series cards although it is possible.

Just some work needed. If someone do this....

The new sources include a folder with recent linux driver for those.

RealtekR1000SL_12.03.2013-src-with8101.zip

Share this post


Link to post
Share on other sites

Thanks Slice!

 

Going to try with my P8H67-M Pro MB, seems that I have a Realtek 8111E. :)

 

I never had any problems with their driver (Realtek), but it is always nice to have a 'bug free' kext. :P

Share this post


Link to post
Share on other sites

Slice, with the latest version it gets an ip even though the cable is not even connected. The one before that worked great. It's a RTL8111E.

 

3.0.2d1:

12/03/13 19:58:52,000 kernel[0]: en0: setActivationLevel(2)
12/03/13 19:58:52,000 kernel[0]: en0: Selected medium index 6
12/03/13 19:58:52,000 kernel[0]: en0: selectMedium, index=6
12/03/13 19:58:52,000 kernel[0]: en0: R1000SetMedium(0x2, 0x2, 0x1)
12/03/13 19:58:52,000 kernel[0]: en0: setLinkStatus but no PHYStatus

 

 

Older (2.0.0d1?):

 

12/03/13 20:00:55,000 kernel[0]: en0: setActivationLevel(2)
12/03/13 20:00:55,000 kernel[0]: en0: Selected medium is NULL, forcing to autonegotiation
12/03/13 20:00:55,000 kernel[0]: en0: selectMedium, index=6
12/03/13 20:00:55,000 kernel[0]: en0: R1000SetMedium(0x2, 0x2, 0x1)

Share this post


Link to post
Share on other sites

Thank you, Slice! I'm going to see what can i do!

 

Best regards!

 

EDIT: Slice, are you sure the new Linux drivers for the 8136/8105 are included with your sources? In Which folder are they? I only found 8101, 8102, 8103 and 8139: are these the drivers?

Share this post


Link to post
Share on other sites

Thank you, Slice! I'm going to see what can i do!

 

Best regards!

 

EDIT: Slice, are you sure the new Linux drivers for the 8136/8105 are included with your sources? In Which folder are they? I only found 8101, 8102, 8103 and 8139: are these the drivers?

As I see

static const struct {
const char *name;
u8 mcfg;
u32 RxConfigMask; /* Clears the bits supported by this chip */
} rtl_chip_info[] = {
_R("RTL8101E", CFG_METHOD_1, 0xff7e1880),
_R("RTL8101E", CFG_METHOD_2, 0xff7e1880),
_R("RTL8101E", CFG_METHOD_3, 0xff7e1880),
_R("RTL8102E", CFG_METHOD_4, 0xff7e1880),
_R("RTL8102E", CFG_METHOD_5, 0xff7e1880),
_R("RTL8103E", CFG_METHOD_6, 0xff7e1880),
_R("RTL8103E", CFG_METHOD_7, 0xff7e1880),
_R("RTL8103E", CFG_METHOD_8, 0xff7e1880),
_R("RTL8401E", CFG_METHOD_9, 0xff7e1880),
_R("RTL8105E", CFG_METHOD_10, 0xff7e1880),
_R("RTL8105E", CFG_METHOD_11, 0xff7e1880),
_R("RTL8105E", CFG_METHOD_12, 0xff7e1880),
_R("RTL8105E", CFG_METHOD_13, 0xff7e1880),
_R("RTL8402", CFG_METHOD_14, 0xff7e1880),
_R("RTL8106E", CFG_METHOD_15, 0xff7e1880),
_R("RTL8106E", CFG_METHOD_16, 0xff7e1880)
};

Share this post


Link to post
Share on other sites

My motherboard is a Gigabyte G31M-ES2C and the network is based on 8102E. Seems to get the ip but when I try to access a website no dice. Cable shows as connected as well...

Share this post


Link to post
Share on other sites

1 problem: I have 1GB Ethernet but it shows only 100MBit and it also acts like 100MBit. Any ideas?

 

EDIT: Found it in Networkconf. sorry :wallbash:, now its working 1GB/s

Share this post


Link to post
Share on other sites

Hi Slice,

 

I have tried your kext, everything works OK, but I need to set it to 1000BaseT manually.

 

Do you need any debug-info?

 

Thanks for your kext! :)

Share this post


Link to post
Share on other sites

Hi Slice,

 

I have tried your kext, everything works OK, but I need to set it to 1000BaseT manually.

 

Do you need any debug-info?

 

Thanks for your kext! :)

Yes, show me part of kernel.log (system.log) concerning R1000 and en0:

But I don't know why it is happen. May be the card is not ready for 1000Mbit at start? Heating?

 

There is last revision compiled as release. No debug messages but may be it will work faster. Check, please.

RealtekR1000SL.kext-v303.zip

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 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 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
×