Mrengles Posted April 21, 2014 Share Posted April 21, 2014 Hello Laura, I finally got around to testing version 1.2.0 RC-2 with my Gigabyte GA-Z77N-WiFi motherboard. The driver allowed me to set up ethernet bonding (802.3ad) for the two onboard Realtek ethernet ports. Throughput and reliability of the link appear to be consistent after 72 hours of continuous uptime so far. I won't really know until the end of this week how everything works with a heavy load, since half of Europe is closed today and has been this past weekend. The one anomaly that has occurred and seems to be consistent is link failure after a restart on one of the ports. The Bond stays active in system preferences but only one of the ports will be active showing the green light. The other port is missing and unable to link up like the other. As long as I don't restart the server this problem does not reoccur. Shutting down the server and then manually starting up the system does not produce the same anomaly as a restarts would. As a matter of fact shutting down the system for 10-15 seconds will actually fix the restart problem. Thanks again for the great driver Laura, keep the updates coming you're doing a fantastic job and a great service to the hackintosh community! Gratitude, Robert aka Mrengles http://mrengles.com 1 Link to comment Share on other sites More sharing options...
Mieze Posted April 21, 2014 Author Share Posted April 21, 2014 The one anomaly that has occurred and seems to be consistent is link failure after a restart on one of the ports. The Bond stays active in system preferences but only one of the ports will be active showing the green light. The other port is missing and unable to link up like the other. As long as I don't restart the server this problem does not reoccur. Shutting down the server and then manually starting up the system does not produce the same anomaly as a restarts would. As a matter of fact shutting down the system for 10-15 seconds will actually fix the restart problem. Hello Robert, thank you for the status report. During a reset/warm boot the NIC doesn't drop the physical connections but falls back to 10MBit and it looks like the second NIC on your board has trouble renegotiating the connection speed after the reboot. As Link Aggregation needs a gigabit connection, I assume that this is the reason why the second link doesn't come back after a reboot. As a workaround you might try to connect the second NIC to another port of your switch or try to set its connection speed manually to 1GBit/s in System Preferences. Good luck! Laura / Mieze Link to comment Share on other sites More sharing options...
Mrengles Posted April 21, 2014 Share Posted April 21, 2014 Hello Robert, thank you for the status report. During a reset/warm boot the NIC doesn't drop the physical connections but falls back to 10MBit and it looks like the second NIC on your board has trouble renegotiating the connection speed after the reboot. As Link Aggregation needs a gigabit connection, I assume that this is the reason why the second link doesn't come back after a reboot. As a workaround you might try to connect the second NIC to another port of your switch or try to set its connection speed manually to 1GBit/s in System Preferences. Good luck! Laura / Mieze Mieze I'll give this a try on the next restart. Being a server this machine very rarely is restarted or shut down for obvious reasons. Amazing uptime's during hurricane season thanks to a natural gas generator . The only problem Link Aggregation users will have with your workaround will be changing the connection speed manually. System Preferences won't allow Advanced > Hardware Settings to be changed while using Ethernet Bonding. All the settings are grayed out. On another note you mentioned a couple posts back about DSDT settings from an Xserve... Here are the DSDT ETH0 and ETH1 Devices from the new 2013 MacPro6,1. Will your driver have issues injecting only the "location" for each port like below? I thought this might help my restart issues, but haven't tested yet. ETH0 & ETH1 Snippet from MacPro6,1 DSDT: Scope (\_SB.PCI0.RP02) { OperationRegion (A1E0, PCI_Config, 0x00, 0x60) Field (A1E0, ByteAcc, NoLock, Preserve) { Offset (0x04), BMIE, 3, Offset (0x19), SECB, 8, SBBN, 8, Offset (0x1E), , 13, MABT, 1, Offset (0x4A), , 5, TPEN, 1, Offset (0x50), , 4, LDIS, 1, , 24, LACT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Device (ETH0) { Name (_ADR, 0x00) // _ADR: Address OperationRegion (ARE0, PCI_Config, 0x00, 0x04) Field (ARE0, ByteAcc, NoLock, Preserve) { AVND, 16 } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "location", Buffer (0x02) { "1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { If (OSDW ()) { Return (Package (0x02) { 0x09, 0x04 }) } Else { Return (Package (0x02) { 0x09, 0x04 }) } } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (0x00) } Method (_PSW, 1, NotSerialized) // _PSW: Power State Wake { If (Arg0) { Store (0x01, GP41) } Else { Store (0x00, GP41) } } } } Scope (\_SB.PCI0.RP01) { OperationRegion (A1E0, PCI_Config, 0x00, 0x60) Field (A1E0, ByteAcc, NoLock, Preserve) { Offset (0x04), BMIE, 3, Offset (0x19), SECB, 8, SBBN, 8, Offset (0x1E), , 13, MABT, 1, Offset (0x4A), , 5, TPEN, 1, Offset (0x50), , 4, LDIS, 1, , 24, LACT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Device (ETH1) { Name (_ADR, 0x00) // _ADR: Address OperationRegion (ARE0, PCI_Config, 0x00, 0x04) Field (ARE0, ByteAcc, NoLock, Preserve) { AVND, 16 } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "location", Buffer (0x02) { "2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { If (OSDW ()) { Return (Package (0x02) { 0x09, 0x04 }) } Else { Return (Package (0x02) { 0x09, 0x04 }) } } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (0x00) } Method (_PSW, 1, NotSerialized) // _PSW: Power State Wake { If (Arg0) { Store (0x01, GP40) } Else { Store (0x00, GP40) } } } } Gratitude, Robert aka Mrengles Link to comment Share on other sites More sharing options...
Mieze Posted April 21, 2014 Author Share Posted April 21, 2014 Hello Robert, the driver itself doesn't care about the location properties. They affect only OS X and System Configuration. Laura / Mieze Link to comment Share on other sites More sharing options...
Mrengles Posted April 22, 2014 Share Posted April 22, 2014 Laura I have some semi good news to my Gigabyte GA-Z77N-WiFi Link Aggregation (802.3ad) after manual restart problem. I made some very minor changes to my DSDT, and started injecting BSD locations for both ethernet ports. I still have the problem with one of my ports not coming up after a system restart, but it happens less often now. About 50% of the time, apposed to every time. Both ports stay active and bonded like they should. The server now at least stands a chance after a complete power failure. Here the ACPI code I'm using for this motherboard. Device (RP05) { Name (_ADR, 0x001C0004) // _ADR: Address Name (_HPP, Package (0x04) // _HPP: Hot Plug Parameters { 0x08, 0x40, One, Zero }) OperationRegion (PXCS, PCI_Config, 0x40, 0xC0) Field (PXCS, AnyAcc, NoLock, Preserve) { Offset (0x10), L0SE, 1, Offset (0x11), Offset (0x12), , 13, LASX, 1, Offset (0x14), , 6, HPCE, 1, Offset (0x1A), ABPX, 1, , 2, PDCX, 1, , 2, PDSX, 1, Offset (0x1B), Offset (0x20), Offset (0x22), PSPX, 1, Offset (0x98), , 30, HPEX, 1, PMEX, 1 } Field (PXCS, AnyAcc, NoLock, WriteAsZeros) { Offset (0x94), , 1, EIFD, 1, Offset (0x95), Offset (0x9C), , 30, HPSX, 1, PMSX, 1 } Device (ETH1) // Built-in Realtek GbE Ethernet (Port 1) { Name (_ADR, Zero) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x09, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "location", Buffer (0x02) { "1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Method (HPME, 0, Serialized) { If (PMSX) { Store (0xC8, Local0) While (Local0) { Store (One, PMSX) If (PMSX) { Decrement (Local0) } Else { Store (Zero, Local0) } } Notify (ETH1, 0x02) } } Method (_PRT, 0, NotSerialized) // _PRT: PCI Routing Table { If (PICM) { Return (AR08 ()) } Return (PR08 ()) } } Device (RP06) { Name (_ADR, 0x001C0005) // _ADR: Address Name (_HPP, Package (0x04) // _HPP: Hot Plug Parameters { 0x08, 0x40, One, Zero }) OperationRegion (PXCS, PCI_Config, 0x40, 0xC0) Field (PXCS, AnyAcc, NoLock, Preserve) { Offset (0x10), L0SE, 1, Offset (0x11), Offset (0x12), , 13, LASX, 1, Offset (0x14), , 6, HPCE, 1, Offset (0x1A), ABPX, 1, , 2, PDCX, 1, , 2, PDSX, 1, Offset (0x1B), Offset (0x20), Offset (0x22), PSPX, 1, Offset (0x98), , 30, HPEX, 1, PMEX, 1 } Field (PXCS, AnyAcc, NoLock, WriteAsZeros) { Offset (0x94), , 1, EIFD, 1, Offset (0x95), Offset (0x9C), , 30, HPSX, 1, PMSX, 1 } Device (ETH2) // Built-in Realtek GbE Ethernet (Port 2) { Name (_ADR, Zero) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x09, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "location", Buffer (0x02) { "2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Method (HPME, 0, Serialized) { If (PMSX) { Store (0xC8, Local0) While (Local0) { Store (One, PMSX) If (PMSX) { Decrement (Local0) } Else { Store (Zero, Local0) } } Notify (ETH2, 0x02) } } Method (_PRT, 0, NotSerialized) // _PRT: PCI Routing Table { If (PICM) { Return (AR09 ()) } Return (PR09 ()) } } The changes are very simple. 1. Renamed device PXSX under RP05 and RP06 to ETH1 and ETH2. 2. Inject location with Device Specific Method (_DSM) into devices ETH1 and ETH2. 3. You will need to make sure your DSDT has Method DTGP for the injections to work otherwise error on compile. Thanks again Mieze for this amazing driver! Gratitude, Robert aka Mrengles Link to comment Share on other sites More sharing options...
Mieze Posted April 25, 2014 Author Share Posted April 25, 2014 Yesterday I pushed version 1.2.0 of the driver, which is identical to the last release candidate, to GitHub and a few minutes ago I also updated the prebuilt binary for Lion, Mountain Lion and Mavericks in the download area of this site. Yes, it's no mistake: a binary for Lion which was built with SDK 10.7 is included too. Although I haven't got a Lion system to test it, I'm quite sure that it works. In case you encounter problem with 10.7, please drop me a line. Good luck! Mieze 4 Link to comment Share on other sites More sharing options...
Henry2010 Posted April 25, 2014 Share Posted April 25, 2014 Thanks very much for the update. Having been waiting for 1.2.0 for a long time. Works smoothly on 10.9.2 Link to comment Share on other sites More sharing options...
NapalmCandy Posted April 26, 2014 Share Posted April 26, 2014 Hi. I click on the link for the driver, but in the Github.com site I don't know exactly what it is the kext file.In the install ReadMe, say "install driver", ok, I want to install the driver, but HOW? Link to comment Share on other sites More sharing options...
RehabMan Posted April 26, 2014 Share Posted April 26, 2014 Hi. I click on the link for the driver, but in the Github.com site I don't know exactly what it is the kext file. In the install ReadMe, say "install driver", ok, I want to install the driver, but HOW? Post #1, "Getting the driver" section. Link to comment Share on other sites More sharing options...
NapalmCandy Posted April 26, 2014 Share Posted April 26, 2014 Thanks, I installed, and work fine, better than the older driver I had. Thank you very much for your time! Link to comment Share on other sites More sharing options...
EDigital Posted April 28, 2014 Share Posted April 28, 2014 Thanks for this driver ! I followed the instructions and it worked very well. Still I have a few questions : 1) When I reboot from Windows, OSX crash on startup. I use the latest realtek driver for windows and V1.2 RC2 from here for OSX. I can make a photo of the crash... It is an onboard chip on a asus p6t motherboard. 2) I need to have another Gigabit port on my setup, so I tried to install a D-Link DGE-528T with (unfortunately) a realtek 8139 driver. It was advertised to work with osx 10.4 and newer with included driver. However this is not the case, installing the driver and the card in my setup just collapsed the whole network setup. I reinstall your driver and it looks like my rtl8111 is working back,now. However I've read my only way to get the DLink working is to install the lnx2mac driver, which is supposed to be conflicting with your very nice driver. Should I try anyway ? Is there an order or is there something I can do to have both driver working independently ? I can give more info tommorow when I'll be back at my office. Didn't understood the quizz thing to be able to post here sonner in the day ... Thanks for any help ED Link to comment Share on other sites More sharing options...
Mieze Posted April 29, 2014 Author Share Posted April 29, 2014 @EDigital: Please send me a photo of the kernel panic. It is crucial to have only one driver installed because the results are unpredictable when more than one driver is installed. Add-on cards with Realtek RTL8168 chips are dirt cheap and should work flawlessly with my driver. I would prefer a card with a newer revision (RTL8168E for example) because it supports more offload features and has less bugs than the old RTL8168B chips. Some vendors like Edimax explicitly mention the chip used on their cards. Mieze Link to comment Share on other sites More sharing options...
EDigital Posted April 29, 2014 Share Posted April 29, 2014 There is the Kernel Panic photo joined to this post. It seems I have more problems now .. I reinstalled my mac OSX system to have a clear picture (Though I still used a dsdt.aml with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] since I'm not sure how to do otherwise). I avoid installing another driver before installing the driver of this thread. The driver seems to work OK I can see in the more info dialog that it is using the correct kext (v1.2) for the ethernet card. But now the mac adress of the device is ff:ff:ff:ff:ff:ff. And it doesn't work in windows anymore. However If I change the mac adress with " sudo en0 ether xx:xx:xx:xx:x::", I can connect to the internet from my osx. The strange thing is, if I reboot to windows, my card is working with the mac adress I configured in OSX ! If i shutdown the computer,the mac adress is back to ff:ff:ff:ff:ff:ff, internet doesn't work, and the card don't work in windows. I don't know how to get back my real mac adress... Did I corrupt my ROM ? Link to comment Share on other sites More sharing options...
Mieze Posted April 29, 2014 Author Share Posted April 29, 2014 (edited) There is the Kernel Panic photo joined to this post. It seems I have more problems now .. I reinstalled my mac OSX system to have a clear picture (Though I still used a dsdt.aml with ##### since I'm not sure how to do otherwise). I avoid installing another driver before installing the driver of this thread. The driver seems to work OK I can see in the more info dialog that it is using the correct kext (v1.2) for the ethernet card. But now the mac adress of the device is ff:ff:ff:ff:ff:ff. And it doesn't work in windows anymore. However If I change the mac adress with " sudo en0 ether xx:xx:xx:xx:x::", I can connect to the internet from my osx. The strange thing is, if I reboot to windows, my card is working with the mac adress I configured in OSX ! If i shutdown the computer,the mac adress is back to ff:ff:ff:ff:ff:ff, internet doesn't work, and the card don't work in windows. I don't know how to get back my real mac adress... Did I corrupt my ROM ? Remove npci=0x3000 from the kernel flags. It's causing the kernel panic and is not needed on most systems. You might be right with regard to the EEPROM. It seems that your NIC'sEEPROM has been erased somehow. Maybe it's a result of the failure to remove the other Realtek driver first? Please send me your kernel logs as it could help me to find out what happened and which configurations are affected of this strange behavior. EDIT: There is a DOS program available for download on Realtek's website. It's some kind of diagnostic utility named RSET8168. Although I haven't checked myself but it might have some function to write a new MAC address to the NIC's EEPROM. Please see: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false Mieze Edited April 29, 2014 by Mieze 1 Link to comment Share on other sites More sharing options...
EDigital Posted April 30, 2014 Share Posted April 30, 2014 Remove npci=0x3000 from the kernel flags. It's causing the kernel panic and is not needed on most systems. You might be right with regard to the EEPROM. It seems that your NIC'sEEPROM has been erased somehow. Maybe it's a result of the failure to remove the other Realtek driver first? Please send me your kernel logs as it could help me to find out what happened and which configurations are affected of this strange behavior. EDIT: There is a DOS program available for download on Realtek's website. It's some kind of diagnostic utility named RSET8168. Although I haven't checked myself but it might have some function to write a new MAC address to the NIC's EEPROM. Please see: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false Mieze Hello Mieze, Thank you for your help. 1) Indeed, it did fix the kernel panik on windows to osx reboot. Nice. 2) I tried the RSET8168 tool, it doesn't allow to write a new MAC adress. When I check the mac adress, it is still the one I configured in OSX till I keep my computer running. Do you know if the other tools might work (PXE and RPL ROM code) 3) I join a log to this post, not sure though if it's the one you are looking for. Thanks for your help Link to comment Share on other sites More sharing options...
Mieze Posted April 30, 2014 Author Share Posted April 30, 2014 @EDigital: Google for PG8168.exe. This tool should be able to rewrite the MAC address and is for Realtek's gigabit NICs. You might also take a look at http://www.insanelymac.com/forum/topic/296190-driver-for-realteks-rtl810x-fast-ethernet-series/?p=2016142. This information does not apply directly to you because he has got a FE NIC but his story is almost identical to yours. Good luck! Mieze Link to comment Share on other sites More sharing options...
DanielFo Posted May 5, 2014 Share Posted May 5, 2014 GA-H87TN with 10ec:8168, driver version 1.2.0 Connection drops every few seconds... 05.05.14 22:31:26,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control 05.05.14 22:31:28,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:31:29,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx stalled? Resetting chipset. ISR=0x80, IMR=0x803f. 05.05.14 22:31:31,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control 05.05.14 22:35:07,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:10,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:13,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:20,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:27,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:33,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:40,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:46,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:35:53,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:36:00,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:36:01,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx stalled? Resetting chipset. ISR=0x885, IMR=0x0. 05.05.14 22:36:02,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control 05.05.14 22:38:28,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx timeout. Lost interrupt? 05.05.14 22:38:29,000 kernel[0]: Ethernet [RealtekRTL8111]: Tx stalled? Resetting chipset. ISR=0x895, IMR=0x803f. 05.05.14 22:38:30,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control I checked my BIOS settings and there aren't any other Realtek kexts installed. Anything else i could do? Link to comment Share on other sites More sharing options...
Mieze Posted May 5, 2014 Author Share Posted May 5, 2014 @DanielFo: Try to disable EEE in the driver's Info.plist. 1 Link to comment Share on other sites More sharing options...
DanielFo Posted May 5, 2014 Share Posted May 5, 2014 @DanielFo: Try to disable EEE in the driver's Info.plist. Thanks, no drops so far... Link to comment Share on other sites More sharing options...
EDigital Posted May 9, 2014 Share Posted May 9, 2014 @EDigital: Google for PG8168.exe. This tool should be able to rewrite the MAC address and is for Realtek's gigabit NICs. You might also take a look at http://www.insanelymac.com/forum/topic/296190-driver-for-realteks-rtl810x-fast-ethernet-series/?p=2016142. This information does not apply directly to you because he has got a FE NIC but his story is almost identical to yours. Good luck! Mieze I've used PG8168, and managed to write a new mac adress. But the chip still doesn't work anymore .... Nevermind I found a Intel Dual Port for 15 euros on ebay. It works nicely. Also I installed your driver on another hackintosh, and it's working flawlessly. Thanks for your help... Link to comment Share on other sites More sharing options...
genzai Posted May 16, 2014 Share Posted May 16, 2014 Hello Mieze, Today i ordered a 4-port nic with RTL8111DL chipsets. I plan to use it in conjunction with your excellent driver for link aggregation on my OS X based SAS NAS. I will let you know how it goes! Thanks, g\ 1 Link to comment Share on other sites More sharing options...
betonmoewe Posted May 21, 2014 Share Posted May 21, 2014 Hello Mieze, first of all, thanks for your work with this driver ! I have a new builded hackintosh based on a GA-Z87-D3HP Board. Because of a lot of problems with the internal NIC with Intel Chip (I tried different intelE1000e kexts but got lost connections and no working WoL), Because of this, I installed a second NIC (TG-3468 v2) and your driver v1.2. Network looks ok, but WoL only works, if I use the "sleep" option (card still active with 10MBit connect to router). When I shutdown my system, all WoL packets are ignored (and the Card itself is without light). With W7, everything works fine. Is there any config option to set in the info.plist to let the card active when osx does a shutdown? Thanks Frank Link to comment Share on other sites More sharing options...
The Real Deal Posted May 23, 2014 Share Posted May 23, 2014 Hi, Is there a 10.6.8 compliant version floating around ? Many thanks Link to comment Share on other sites More sharing options...
RehabMan Posted May 23, 2014 Share Posted May 23, 2014 Hi, Is there a 10.6.8 compliant version floating around ? Many thanks My version is built for 10.6.8 or newer: https://github.com/RehabMan/OS-X-Realtek-Network 1 Link to comment Share on other sites More sharing options...
The Real Deal Posted May 23, 2014 Share Posted May 23, 2014 Glad to see some people are still rockin with the good old Snow Leopard. I am currently installing it. If you need any feedback, or whatever, just ask Thank you. mm, problem apparently : May 23 22:46:49 localhost kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: May 23 22:46:49 localhost kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: _OSKextGetCurrentIdentifier May 23 22:46:49 localhost kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: _OSKextGetCurrentLoadTag May 23 22:46:49 localhost kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: _OSKextGetCurrentVersionString May 23 22:46:49 localhost kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed. May 23 22:46:49 localhost kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111. May 23 22:46:49 localhost kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016). May 23 22:46:49 localhost kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016). Link to comment Share on other sites More sharing options...
Recommended Posts