Mieze Posted March 12, 2016 Author Share Posted March 12, 2016 Thanks. I dl it from the DOWNLOAD tab insanely Mac. Q: Normally the Debug builds are bigger in file size than Release builds. In the 2.2.1 build , it´s the first build where the debug build is smaller size than Release build. Is the build in the Release really the the release build or perhaps copy mistake the debug build? Thanks I also realized the fact that the release build is bigger than the debug build but I have no explanation for it. I checked things several times and found nothing. I used Xcode 7.2.1 for the builds. Maybe it's a strange behavior of the compiler optimizing for speed instead of size. Mieze Link to comment Share on other sites More sharing options...
MacKonsti Posted March 12, 2016 Share Posted March 12, 2016 Hi dear Mieze, first of all many thanks again for your continuing support of this driver!I am sorry to report that latest version released v2.2.1-d4 does not work under Mavericks 10.9.5. I hadn't visited the thread for days and just found out your v2.2.xxx releases after the single v2.1.0-d1 release, so I thought to give it a try. Previous version 2.0.0 works well, despite low transfer speeds between hackintoshes on a Gigabit home LAN (other is Gigabyte GA-H67N-USB3). On my main Gigabyte GA-P55M-UD4 the driver doesn't kick in. I re-did the caches with Kext Utility, to no avail. Although you are not compelled or obliged to keep supporting 10.9.5 after your v2.0.0 release (I will upgrade to 10.10.x soon, promise!) please can you inform us if the latest v2.2.1-xxx dropped support for Mavericks? I keep leaving it at 10.9.5 as it remains a good working system... Just to confirm you official upload here on InsanelyMac... I assume this has to do with the never-ending Xcode versions and most likely the one you used? Many thanks! 13/3/16 01:23:56,258 sudo[1526]: Konsti : TTY=ttys001 ; PWD=/Users/Konsti/Desktop ; USER=root ; COMMAND=/usr/sbin/chown -R 0:0 RealtekRTL8111.kext 13/3/16 01:25:50,167 sudo[1564]: Konsti : TTY=ttys000 ; PWD=/System/Library/Extensions ; USER=root ; COMMAND=/bin/mv RealtekRTL8111.kext /Users/Konsti/Downloads/ 13/3/16 01:25:55,639 sudo[1568]: Konsti : TTY=ttys000 ; PWD=/System/Library/Extensions ; USER=root ; COMMAND=/bin/mv /Users/Konsti/Desktop/RealtekRTL8111.kext . 13/3/16 01:26:04,416 com.apple.kextcache[1570]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/RealtekRTL8111.kext" 13/3/16 01:26:15,203 com.apple.kextcache[1570]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: 13/3/16 01:26:15,203 com.apple.kextcache[1570]: kxld[com.insanelymac.RealtekRTL8111]: IOPCIDevice::setASPMState(IOService*, unsigned int) 13/3/16 01:26:15,205 com.apple.kextcache[1570]: Prelink failed for com.insanelymac.RealtekRTL8111; omitting from prelinked kernel. 13/3/16 01:31:29,919 com.apple.kextd[14]: kext com.insanelymac.RealtekRTL8111 202011004 is in exception list, allowing to load 13/3/16 01:31:30,000 kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: 13/3/16 01:31:30,000 kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: __ZN11IOPCIDevice12setASPMStateEP9IOServicej 13/3/16 01:31:30,000 kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed. 13/3/16 01:31:30,000 kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111. 13/3/16 01:31:30,000 kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016). 13/3/16 01:31:30,180 com.apple.kextd[14]: Failed to load /System/Library/Extensions/RealtekRTL8111.kext - (libkern/kext) link error. 13/3/16 01:31:30,182 com.apple.kextd[14]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel. 13/3/16 01:31:56,839 sudo[366]: Konsti : TTY=ttys000 ; PWD=/System/Library/Extensions ; USER=root ; COMMAND=/bin/rm -R RealtekRTL8111.kext 13/3/16 01:32:03,282 sudo[373]: Konsti : TTY=ttys000 ; PWD=/System/Library/Extensions ; USER=root ; COMMAND=/bin/mv /Users/Konsti/Downloads/RealtekRTL8111.kext . 13/3/16 01:32:56,364 com.apple.kextd[14]: kext com.insanelymac.RealtekRTL8111 200009000 is in exception list, allowing to load 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled. 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled. 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled. 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled. 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: Version 2.0.0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! 13/3/16 01:32:56,000 kernel[0]: Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0xffffff810950d000, 0:24:1d:da:e9:51 13/3/16 01:32:57,773 com.apple.kextcache[406]: kext com.insanelymac.RealtekRTL8111 200009000 is in exception list, allowing to load 13/3/16 01:32:58,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled. 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled. 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled. 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled. 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: Version 2.0.0 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! 13/3/16 01:33:56,000 kernel[0]: Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0xffffff8109586000, 0:24:1d:da:e9:51 13/3/16 01:33:59,000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control Link to comment Share on other sites More sharing options...
Mieze Posted March 12, 2016 Author Share Posted March 12, 2016 (edited) I am sorry to report that latest version released v2.2.1-d4 does not work under Mavericks 10.9.5 It's not a bug, version 2.2.1 requires El Capitan and there is no way to make it work on Mavericks. I should have mentioned this in the post. Sorry! Mieze Edited March 12, 2016 by Mieze 2 Link to comment Share on other sites More sharing options...
mitch_de Posted March 13, 2016 Share Posted March 13, 2016 I also realized the fact that the release build is bigger than the debug build but I have no explanation for it. I checked things several times and found nothing. I used Xcode 7.2.1 for the builds. Maybe it's a strange behavior of the compiler optimizing for speed instead of size. Mieze Yep, maybe some speed optimizations in release vs debug version. Doesn't matter! I only want to be sure to use not the debug version. THANKS! Link to comment Share on other sites More sharing options...
MacKonsti Posted March 13, 2016 Share Posted March 13, 2016 Hi dear Mieze, thanks for your El Capitano confirmation. So v2.2.x not even supported on Yosemite... I downloaded from earlier posts v2.1.0-d1 (that included the Xcode project, somehow) and compiled it on my Mac with Xcode 6.2 and it seems to work with 10.9.5 (but was debug version, in your zip). Can I please ask you to share the latest v2.1.0 available (from your repository, perhaps, Mieze?) so we can make it the last, official release for Mavericks? Just to be sure if you've introduced any fixes or improvements to 2.1.0-d1 before moving on to 2.2.x You had only posted v2.1.0-d1 once, before posting v2.2.x-dxx builds... just for us running behind on OS X ;-) Unless v2.1.0 was experimental and you advise us to keep v2.0.0... even for Yosemite? Many thanks again for your support! Link to comment Share on other sites More sharing options...
Mieze Posted March 13, 2016 Author Share Posted March 13, 2016 Hi dear Mieze, thanks for your El Capitano confirmation. So v2.2.x not even supported on Yosemite... I downloaded from earlier posts v2.1.0-d1 (that included the Xcode project, somehow) and compiled it on my Mac with Xcode 6.2 and it seems to work with 10.9.5 (but was debug version, in your zip). Can I please ask you to share the latest v2.1.0 available (from your repository, perhaps, Mieze?) so we can make it the last, official release for Mavericks? Just to be sure if you've introduced any fixes or improvements to 2.1.0-d1 before moving on to 2.2.x You had only posted v2.1.0-d1 once, before posting v2.2.x-dxx builds... just for us running behind on OS X ;-) Unless v2.1.0 was experimental and you advise us to keep v2.0.0... even for Yosemite? Many thanks again for your support! Version 2.0.0 was made for Yosemite and there is no need to upgrade on 10.10 but in case you are desperately trying to get the latest version you might try 2.2.1d3 (the release build posted) because I added the call to setASPMState() which makes the driver fail under Mavericks in 2.2.1d4. Besides that, you can roll back to any commit I made in the past using git's checkout command. Google should give you a link to a git tutorial. commit 0f6d8784eae9d07de45e3fb627912693811787a1 Author: Laura Müller <laura@Lucy.no-ip.info> Date: Wed Mar 9 21:29:49 2016 +0100 Version 2.2.1d3 - Reduced the poll interval for gigabit speed to 170us in order to optimize SMB throughput. Mieze 1 Link to comment Share on other sites More sharing options...
MacKonsti Posted March 13, 2016 Share Posted March 13, 2016 Thank you, Mieze! The reason I'd like to run a newer driver (even on 10.9.5) is that I saw transfer improvement of 2.1.0 earlier (over 2.0.0) so I expect 2.2.1-d3 to be equally great and stable. Even on my chip... Although I am not a skillful Xcode user, I managed to get back to your 2.2.1-d3 version via SourceTree client that I am using, and compiled it with Xcode 6.2 (latest on 10.9.5 available) using target 10.10 system. The 'Release' compiled without errors, and the build works fine and as expected on my 10.9.5. and 10.10.5 on another hackintosh! (Gigabyte P55M-UD4 and MSI-Z97i-AC). Many thanks for pointing me to this. Vielen Dank! 1 Link to comment Share on other sites More sharing options...
LockDown Posted March 14, 2016 Share Posted March 14, 2016 Mieze What's the difference between "flow-control" and "No flow-control"? I have 2 diffrent realtek and both showing different from the other one. if it has effect, which one is better? Link to comment Share on other sites More sharing options...
Mieze Posted March 14, 2016 Author Share Posted March 14, 2016 What's the difference between "flow-control" and "No flow-control"? I have 2 diffrent realtek and both showing different from the other one. if it has effect, which one is better? For an in-detail description of flow control please see: https://en.wikipedia.org/wiki/Ethernet_flow_control Mieze Link to comment Share on other sites More sharing options...
Moorre Posted March 15, 2016 Share Posted March 15, 2016 Hi, Mieze! I have a small question. Seems to be incorrect information about the address of chipset. With 2.1.0d1 was Ethernet [RealtekRTL8111]: Version 2.1.0d1 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0xffffff82d7519000, With 2.1.0 here we go: Ethernet [RealtekRTL8111]: Version 2.2.1 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0x<ptr>, Link to comment Share on other sites More sharing options...
LockDown Posted March 15, 2016 Share Posted March 15, 2016 For an in-detail description of flow control please see: https://en.wikipedia.org/wiki/Ethernet_flow_control Mieze Thats too much for me.. in simplest form? Link to comment Share on other sites More sharing options...
Mieze Posted March 15, 2016 Author Share Posted March 15, 2016 Hi, Mieze! I have a small question. Seems to be incorrect information about the address of chipset. With 2.1.0d1 was Ethernet [RealtekRTL8111]: Version 2.1.0d1 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0xffffff82d7519000, With 2.1.0 here we go: Ethernet [RealtekRTL8111]: Version 2.2.1 using interrupt mitigate value 0xcf58. Please don't support tonymacx86.com! Ethernet [RealtekRTL8111]: RTL8168D/8111D: (Chipset 9) at 0x<ptr>, That's a peculiarity of El Capitan which refuses to print addresses in log entries. Probably a security feature. Thats too much for me.. in simplest form? If you don't experience any problems leave it to the auto-configured setting, in particular when you don't know what you are doing. Mieze 1 Link to comment Share on other sites More sharing options...
pp888 Posted March 16, 2016 Share Posted March 16, 2016 Hi, Mieze: Thanks for the great work. Got a question on my newly El Capitan - the link stays on 100-Megabit (and I found it while copy big files in a local LAN to a NAS machine). My MB is a MSI Z77MA-G45 with i5-2400 CPU. I've switch between your RTL1111 kext and another Hackintosh which used Asus Z77-M MB and got 1Giga networks speed on its RTL1111.kext, this MSI one loads OK, but the line speed always stay at 100-M. Mar 16 19:40:32 iMac-2 distnoted[478]: # distnote server agent absolute time: 71.862453060 civil time: Wed Mar 16 19:40:32 2016 pid: 478 uid: 89 root: no Mar 16 19:40:33 iMac-2 networkd[172]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID Mar 16 19:40:33 --- last message repeated 1 time --- Mar 16 19:40:33 iMac-2 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control Mar 16 19:40:33 iMac-2 mDNSResponder[92]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:8E89:A5FF:FEDB:039B) Mar 16 19:40:34 iMac-2 networkd[172]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID Mar 16 19:40:36 --- last message repeated 3 times --- any parameters I can tweak and try to make this line goes faster ? ... my local network environment all use Gigabit hub now, and this machine when boot to Windows7 it's sending files faster in Gigabit speed, only I can't get that speed when boot into El Capitan. Thanks in advance ! PP Link to comment Share on other sites More sharing options...
Mieze Posted March 16, 2016 Author Share Posted March 16, 2016 Hi, Mieze: Thanks for the great work. Got a question on my newly El Capitan - the link stays on 100-Megabit (and I found it while copy big files in a local LAN to a NAS machine). My MB is a MSI Z77MA-G45 with i5-2400 CPU. I've switch between your RTL1111 kext and another Hackintosh which used Asus Z77-M MB and got 1Giga networks speed on its RTL1111.kext, this MSI one loads OK, but the line speed always stay at 100-M. Mar 16 19:40:32 iMac-2 distnoted[478]: # distnote server agent absolute time: 71.862453060 civil time: Wed Mar 16 19:40:32 2016 pid: 478 uid: 89 root: no Mar 16 19:40:33 iMac-2 networkd[172]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID Mar 16 19:40:33 --- last message repeated 1 time --- Mar 16 19:40:33 iMac-2 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 100-Megabit, Full-duplex, flow-control Mar 16 19:40:33 iMac-2 mDNSResponder[92]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:8E89:A5FF:FEDB:039B) Mar 16 19:40:34 iMac-2 networkd[172]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID Mar 16 19:40:36 --- last message repeated 3 times --- any parameters I can tweak and try to make this line goes faster ? ... my local network environment all use Gigabit hub now, and this machine when boot to Windows7 it's sending files faster in Gigabit speed, only I can't get that speed when boot into El Capitan. Thanks in advance ! PP Try to select the line speed manually. Auto-negotiation doesn't always result in the desired speed. Mieze Link to comment Share on other sites More sharing options...
LockDown Posted March 16, 2016 Share Posted March 16, 2016 Where to select line speed manually? Link to comment Share on other sites More sharing options...
pp888 Posted March 16, 2016 Share Posted March 16, 2016 Hi, Mieze: Thanks, tried to manual select the speed in System Preference, Network menu then select the ethernet, Hardware tab. Tried set it to 1000BaseT, full duplex with 1500MTU. The log still says it's 100-Magabit after I apply the changes .... could it be this MB specifically ? ... my other Asus Z77 works just fine with Gigabit speed - I can tell the difference when copy a 6GB file. Thanks again ! PP Link to comment Share on other sites More sharing options...
Mieze Posted March 16, 2016 Author Share Posted March 16, 2016 Hi, Mieze: Thanks, tried to manual select the speed in System Preference, Network menu then select the ethernet, Hardware tab. Tried set it to 1000BaseT, full duplex with 1500MTU. The log still says it's 100-Magabit after I apply the changes .... could it be this MB specifically ? ... my other Asus Z77 works just fine with Gigabit speed - I can tell the difference when copy a 6GB file. As far as I know the MSI Z77MA-G45 is equipped with an RTL8111E-VL (chipset 16) which is the same as I use for testing. In case you are stuck with 100MBit there are three possible reasons: A hardware issue (bad cable, dust on the connectors, defective NIC, compatibility issue, etc.) A messed up system (-> reinstall) A firmware issue (blame Realtek) or an incorrect BIOS setting (network boot and the UEFI network stack should be disabled). Mieze 1 Link to comment Share on other sites More sharing options...
pp888 Posted March 16, 2016 Share Posted March 16, 2016 Got it, I'll check them accordingly, just don't wanna miss if anything else I should/can set as parameter anywhere. Thanks again ! UPDATE: Finally found the problem, it's the wire !! .... it's a Cat 5 cable. I should've check this 3 days ago and will save me lots of time and the post. Thanks to Mieze again ! 1 Link to comment Share on other sites More sharing options...
LockDown Posted March 17, 2016 Share Posted March 17, 2016 Mieze What's the difference between "flow-control" and "No flow-control"? I have 2 diffrent realtek and both showing different from the other one. if it has effect, which one is better? Allow me to rephrase what i said earlier... Chipset 20 v2.0.0 = flow-control v2.2.1 = No flow-control Something went wrong? Link to comment Share on other sites More sharing options...
Mieze Posted March 17, 2016 Author Share Posted March 17, 2016 Allow me to rephrase what i said earlier... Chipset 20 v2.0.0 = flow-control v2.2.1 = No flow-control Something went wrong? Flow control has it's pros and cons as the Wikipedia entry described but in most situations you won't notice any difference wether it's enabled or disabled. Version 2.2.1 uses different firmware than version 2.0.0 and provides the ability to control flow control manually whereas 2.0.0 left the decision to a routine provided by Realtek. Mieze 3 Link to comment Share on other sites More sharing options...
xenophon Posted March 22, 2016 Share Posted March 22, 2016 Thank you for your beautiful work! Just so that you know, the new version resolved the following issue relating to AFP file sharing: v1.2.3 - AFP shares were visible from other Macs on the network v2.0.0 - AFP shares were NOT visible ("There was a problem connecting to the server"). v2.2.1 - all OK Once again, thanks. With greetings from Athens, Xen Link to comment Share on other sites More sharing options...
Dewdman42 Posted March 23, 2016 Share Posted March 23, 2016 This driver is sweet! Definitely the fastest one I have tried on GA-P35-DS4 mobo with Mavericks. One quick question, I installed this initially with one of the post install utilities which shall not me mentioned by name here, and basically whenever I delete the Kext cache to start over clean, I get a complaint from OSX about this driver not being made by Apple or something of this nature. I am taking this to mean its not signed or something. Is there any way to tweak something so that I will not get this warning message any more in the future, or a particular way of installing it which will avoid that? That utility only installs v 1.2.2 also, I'm about to try your latest build... Link to comment Share on other sites More sharing options...
Mieze Posted March 23, 2016 Author Share Posted March 23, 2016 This driver is sweet! Definitely the fastest one I have tried on GA-P35-DS4 mobo with Mavericks. One quick question, I installed this with #####, and basically whenever I delete the Kext cache to start over clean, I get a complaint from OSX about this driver not being made by Apple or something of this nature. I am taking this to mean its not signed or something. Is there any way to tweak something so that I will not get this warning message any more in the future, or a particular way of installing it which will avoid that? ##### only installs v 1.2.2 also, I'm about to try your latest build... Sorry, but I can't sign the kext in order to avoid the warning because when you request a developer ID for kext signing you have to provide the intended use and a request for hackintosh driver development will most likely be rejected. Mieze 1 Link to comment Share on other sites More sharing options...
Dewdman42 Posted March 23, 2016 Share Posted March 23, 2016 Is that the reason for the warning and no other way to avoid that warning dialog huh? Its not that big of a deal I guess, it only comes into play if and when I run Onyx or something and clean house...just kind of an annoyance. Strangely though, I have a number of Kext's install related to hackintoshery...and none of them give this error message...just your Realtek one. And previously I was using the Lynx2mac one, which is not as performant as yours...but that one did not give any warning message either. Link to comment Share on other sites More sharing options...
Dewdman42 Posted March 23, 2016 Share Posted March 23, 2016 So version 1.2.2 of this driver works pretty darn great. For kicks I tried to install the latest 2.2.1 version. It doesn't load. Maybe you can help me figure out how, here are the errors reported in /var/log/system.log when using debug version: Mar 23 17:34:57 hackman com.apple.kextd[12]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/RealtekRTL8111.kext" Mar 23 17:34:57 hackman kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: Mar 23 17:34:57 hackman kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: __ZN11IOPCIDevice12setASPMStateEP9IOServicej Mar 23 17:34:57 hackman kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed. Mar 23 17:34:57 hackman kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111. Mar 23 17:34:57 hackman kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016). Mar 23 17:34:57 hackman kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016). Mar 23 17:34:57 hackman com.apple.kextd[12]: Failed to load /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/RealtekRTL8111.kext - (libkern/kext) link error. Mar 23 17:34:57 hackman com.apple.kextd[12]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel. Link to comment Share on other sites More sharing options...
Recommended Posts