Mieze Posted January 23, 2018 Author Share Posted January 23, 2018 @Mieze Im trying to compile my own and noticed it has a v2. Which one should i compile? Thanks Always V2! V1 is outdated and will be removed soon. Mieze Link to comment Share on other sites More sharing options...
LockDown Posted January 23, 2018 Share Posted January 23, 2018 I got it working on 10.11. I though your release and my own compile was only for Sierra+ Thanks Mieze Link to comment Share on other sites More sharing options...
Funky frank Posted January 23, 2018 Share Posted January 23, 2018 Hi, if you let the macos settings on "manual" in the hardware tab of the ethernet device driven by this driver, it won't select 1000baseT, if it is available. So you have to switch to 1000baseT manually, else it stays in 100baseX mode. Using a CAT5e cable. Link to comment Share on other sites More sharing options...
Mieze Posted January 23, 2018 Author Share Posted January 23, 2018 Hi, if you let the macos settings on "manual" in the hardware tab of the ethernet device driven by this driver, it won't select 1000baseT, if it is available. So you have to switch to 1000baseT manually, else it stays in 100baseX mode. Using a CAT5e cable. "Manual" means manual configuration. So, what is the point? Mieze Link to comment Share on other sites More sharing options...
Funky frank Posted January 23, 2018 Share Posted January 23, 2018 Mieze, I actually meant "automatically" I switched my LAN from 100 to 1000, but in auto-mode, the driver does not seem to detect the 1000 mbit. Shouldn't it detect it automatically? EDIT: Hm, nvm. I checked now in another LAN, there it works. Seems to be a wrong CAT5e cable? Link to comment Share on other sites More sharing options...
Mieze Posted January 23, 2018 Author Share Posted January 23, 2018 Mieze, I actually meant "automatically" I switched my LAN from 100 to 1000, but in auto-mode, the driver does not seem to detect the 1000 mbit. Shouldn't it detect it automatically? Auto-configuration is a complex process in which both link partners negotiate the link parameters but the result isn't always the expected one and that's the reason why one might want to switch to manual mode. Mieze 3 Link to comment Share on other sites More sharing options...
kikiwora Posted February 11, 2018 Share Posted February 11, 2018 Hey there.My Ethernet doesn't work after sleep, but kext itself does - I can see a self-assigned IP address in my network settings.Is that normal for this driver? Or how can I fix it if it's not? Link to comment Share on other sites More sharing options...
Mieze Posted February 11, 2018 Author Share Posted February 11, 2018 Hey there. My Ethernet doesn't work after sleep, but kext itself does - I can see a self-assigned IP address in my network settings. Is that normal for this driver? Or how can I fix it if it's not? No, it's not normal and you should check other things like DHCP first as I haven't heard of any sleep/wake related problems for quite a long lime. In case you think that's a driver related problem, you should send me some kernel logs showing the problem. Mieze Link to comment Share on other sites More sharing options...
ctich Posted February 11, 2018 Share Posted February 11, 2018 Hello Mieze, can you delete these messages from the log? Thank you. 2018-02-11 21:21:41.107117+0200 0x39e Default 0x0 0 kernel: (kernel) setOffset79() ===> 2018-02-11 21:21:41.110350+0200 0x39e Default 0x0 0 kernel: (kernel) setOffset79() <=== 2018-02-11 21:21:41.135446+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() ===> 2018-02-11 21:21:41.135888+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() <=== 2018-02-11 21:21:41.161713+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() ===> 2018-02-11 21:21:41.167093+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() <=== 2018-02-11 21:21:41.230920+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.236896+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.254538+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.260332+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.283636+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.289017+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.294344+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.299477+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== /// 2018-02-11 21:21:44.841041+0200 0x104 Default 0x0 0 kernel: (kernel) getFeatures() ===> 2018-02-11 21:21:44.851499+0200 0x104 Default 0x0 0 kernel: (kernel) getFeatures() <=== 2018-02-11 21:21:41.242840+0200 0x39e Default 0x0 0 kernel: (kernel) getPacketFilters() ===> 2018-02-11 21:21:41.248731+0200 0x39e Default 0x0 0 kernel: (kernel) getPacketFilters() <=== 2018-02-11 21:21:41.265920+0200 0x1bf Default 0x0 0 kernel: (kernel) getPacketFilters() ===> 2018-02-11 21:21:41.271323+0200 0x1bf Default 0x0 0 kernel: (kernel) getPacketFilters() <=== Link to comment Share on other sites More sharing options...
Mieze Posted February 11, 2018 Author Share Posted February 11, 2018 Hello Mieze, can you delete these messages from the log? Thank you. 2018-02-11 21:21:41.107117+0200 0x39e Default 0x0 0 kernel: (kernel) setOffset79() ===> 2018-02-11 21:21:41.110350+0200 0x39e Default 0x0 0 kernel: (kernel) setOffset79() <=== 2018-02-11 21:21:41.135446+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() ===> 2018-02-11 21:21:41.135888+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() <=== 2018-02-11 21:21:41.161713+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() ===> 2018-02-11 21:21:41.167093+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastMode() <=== 2018-02-11 21:21:41.230920+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.236896+0200 0x39e Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.254538+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.260332+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.283636+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.289017+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== 2018-02-11 21:21:41.294344+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() ===> 2018-02-11 21:21:41.299477+0200 0x2d1 Default 0x0 0 kernel: (kernel) setMulticastList() <=== /// 2018-02-11 21:21:44.841041+0200 0x104 Default 0x0 0 kernel: (kernel) getFeatures() ===> 2018-02-11 21:21:44.851499+0200 0x104 Default 0x0 0 kernel: (kernel) getFeatures() <=== 2018-02-11 21:21:41.242840+0200 0x39e Default 0x0 0 kernel: (kernel) getPacketFilters() ===> 2018-02-11 21:21:41.248731+0200 0x39e Default 0x0 0 kernel: (kernel) getPacketFilters() <=== 2018-02-11 21:21:41.265920+0200 0x1bf Default 0x0 0 kernel: (kernel) getPacketFilters() ===> 2018-02-11 21:21:41.271323+0200 0x1bf Default 0x0 0 kernel: (kernel) getPacketFilters() <=== Why? These are debug messages output by the debug version of the driver, which is for debugging only. Production systems should use the release version of the driver which doesn't output these lines. Mieze 1 Link to comment Share on other sites More sharing options...
ctich Posted February 11, 2018 Share Posted February 11, 2018 Why? These are debug messages output by the debug version of the driver, which is for debugging only. Production systems should use the release version of the driver which doesn't output these lines. Mieze I'm sorry, I have a debug version installed. Link to comment Share on other sites More sharing options...
arsradu Posted March 11, 2018 Share Posted March 11, 2018 (edited) I can't believe there have been almost 5 YEARS since this thread started... 5 years! I think I've been using this kext since 3 years ago. Never had an issue. Not even once. It's been incredibly reliable for me. So I just wanted to extend my gratitude to the developer. Congrats! And thank you very, very much for you work. Edited March 12, 2018 by arsradu 1 Link to comment Share on other sites More sharing options...
X-Tropic Posted March 19, 2018 Share Posted March 19, 2018 On 01.05.2017 at 2:39 AM, FFForever said: panic(cpu 0 caller 0xffffff80004011bd): Kernel trap at 0xffffff7f838951a2, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff81ec657000, CR3: 0x0000000009b62000, CR4: 0x00000000001627e0 RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff81ec657000, RDX: 0xffffff81c2469088 RSP: 0xffffff81ed40be40, RBP: 0xffffff81ed40be50, RSI: 0x0000000000000000, RDI: 0xffffff81a1b97000 R8: 0x00000591bb32903c, R9: 0xffffff80296b6d98, R10: 0x0000000000000000, R11: 0xffffff8000a8a810 R12: 0x00000591ba46549d, R13: 0x000000008df5a1c1, R14: 0xffffff81a1b97000, R15: 0xffffff81a1b972a0 RFL: 0x0000000000010246, RIP: 0xffffff7f838951a2, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff81ec657000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffff81ed40bad0 : 0xffffff80002ec3ec 0xffffff81ed40bb50 : 0xffffff80004011bd 0xffffff81ed40bd30 : 0xffffff800029d543 0xffffff81ed40bd50 : 0xffffff7f838951a2 0xffffff81ed40be50 : 0xffffff7f83896e39 0xffffff81ed40be70 : 0xffffff7f838967ea 0xffffff81ed40bea0 : 0xffffff7f8389609f 0xffffff81ed40bee0 : 0xffffff80008bcfaf 0xffffff81ed40bf30 : 0xffffff80008bb811 0xffffff81ed40bf80 : 0xffffff80008badf6 0xffffff81ed40bfb0 : 0xffffff800029a8f7 Kernel Extensions in backtrace: com.insanelymac.RealtekRTL8111(2.2.1)[8BA5E6A6-5DCA-3102-B71B-CE613147F452]@0xffffff7f83835000->0xffffff7f8389bfff dependency: com.apple.iokit.IONetworkingFamily(3.2)[6326DB88-5330-3F0C-91F6-D478AB5E7503]@0xffffff7f812fd000 dependency: com.apple.iokit.IOPCIFamily(2.9)[C6E3195E-A0D7-3B71-B5F4-9EE9E182D4FC]@0xffffff7f80b32000 Hi! I often have same panic on version 2.2.2 when i try to go to sleep. My LAN - RTL8168G. OS X Sierra 10.12.6. I disable ASPM, Network boot etc... Besides, if i fall asleep, then after waking up, the network speed drops to a minimum. At the moment I returned to version 2.2.1 and there are no such problems. Maybe you need to fix something in the new version? Link to comment Share on other sites More sharing options...
Mieze Posted March 19, 2018 Author Share Posted March 19, 2018 3 minutes ago, X-Tropic said: Hi! I often have same panic on version 2.2.2 when i try to go to sleep. My LAN - RTL8168G. OS X Sierra 10.12.6. I disable ASPM, Network boot etc... Besides, if i fall asleep, then after waking up, the network speed drops to a minimum. At the moment I returned to version 2.2.1 and there are no such problems. Maybe you need to fix something in the new version? The driver is working fine, there is no indication for a driver problem in 2.2.2 in particular no reason for a kernel panic. It's your system which is broken (DSDT, system caches, etc.). Please fix your system in order to resolve the problem. Mieze 1 Link to comment Share on other sites More sharing options...
kendok Posted March 20, 2018 Share Posted March 20, 2018 is this really a bug or somthing in high sierra an sierra when using the kext file the internet works fine after a reboot an then after a few mins it stops an says self assign ip an internet dont work until i reboot the laptop Link to comment Share on other sites More sharing options...
Mieze Posted March 20, 2018 Author Share Posted March 20, 2018 4 minutes ago, kendok said: is this really a bug or somthing in high sierra an sierra when using the kext file the internet works fine after a reboot an then after a few mins it stops an says self assign ip an internet dont work until i reboot the laptop It could be almost anything (DHCP issue, hardware problem, BIOS setting, etc.) but there is one thing I can almost certainly rule out: a driver bug! Fix your system in order get it working. 1 Link to comment Share on other sites More sharing options...
kendok Posted March 21, 2018 Share Posted March 21, 2018 such as reinstalling the OS X High Sierra cause i tried it in the installer it does the same thing when downloading the installer for High Sierra in Mac Os Utilites dhcp has no issue cause it works fine on my windows bios an hardware works fine Link to comment Share on other sites More sharing options...
Mieze Posted March 21, 2018 Author Share Posted March 21, 2018 7 minutes ago, kendok said: such as reinstalling the OS X High Sierra cause i tried it in the installer it does the same thing when downloading the installer for High Sierra in Mac Os Utilites dhcp has no issue cause it works fine on my windows bios an hardware works fine The fact that it works under Windows rules out a hardware issue but it doesn't rule out a DHCP related problem. Frankly I have no idea what went wrong on your system. Have you checked the BIOS settings? Is the the UEFI network stack and network boot disabled? Mieze Link to comment Share on other sites More sharing options...
wawa Posted March 21, 2018 Share Posted March 21, 2018 Not sure I have a dell inspiron 15 3567 also looking for WiFi next for qca 9565 I install the is this week soo... Don't blame me Link to comment Share on other sites More sharing options...
Badruzeus Posted March 21, 2018 Share Posted March 21, 2018 RTL8111 v2.2.2 is working fine under 10.11.6 && 10.13.4 Beta here.. Thanks @Mieze Link to comment Share on other sites More sharing options...
zy94 Posted April 4, 2018 Share Posted April 4, 2018 Is there any chance that "Realtek 8822BE Wirelss LAN 802.11ac PCI-E NIC" will work? Thanks. Link to comment Share on other sites More sharing options...
Mieze Posted April 4, 2018 Author Share Posted April 4, 2018 4 minutes ago, zy94 said: Is there any chance that "Realtek 8822BE Wirelss LAN 802.11ac PCI-E NIC" will work? Thanks. No! Please check Realtek's website for a macOS driver. Mieze Link to comment Share on other sites More sharing options...
baddles Posted April 7, 2018 Share Posted April 7, 2018 Hi, I'm running OS X 10.9.5 on my 1st gen Intel laptop. Currently I'm having this issue, which causes the kext not to load, any fix for this? Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: __ZN11IOPCIDevice12setASPMStateEP9IOServicej Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed. Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111. Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016). Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016). Apr 7 07:14:46 Baddless-MacBook-Pro.local com.apple.kextd[12]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel. Link to comment Share on other sites More sharing options...
Mieze Posted April 7, 2018 Author Share Posted April 7, 2018 50 minutes ago, baddles said: Hi, I'm running OS X 10.9.5 on my 1st gen Intel laptop. Currently I'm having this issue, which causes the kext not to load, any fix for this? Hide contents Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext: Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: __ZN11IOPCIDevice12setASPMStateEP9IOServicej Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed. Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111. Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016). Apr 7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016). Apr 7 07:14:46 Baddless-MacBook-Pro.local com.apple.kextd[12]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel. The lastest binary requires Sierra or newer. For 10.9.5 try an older version, preferably one which was released while 10.9 was the most recent version of macOS. Mieze Link to comment Share on other sites More sharing options...
baddles Posted April 7, 2018 Share Posted April 7, 2018 1 hour ago, Mieze said: The lastest binary requires Sierra or newer. For 10.9.5 try an older version, preferably one which was released while 10.9 was the most recent version of macOS. Mieze Ah I see, I'll try it when my computer can be turned on. (I think it died on me 15 mins ago as of this post....) Link to comment Share on other sites More sharing options...
Recommended Posts