Jump to content
singh_dd93

Kernel Panic on Using RealtekRTL8111 kext

9 posts in this topic

Recommended Posts

Hi Guys,

Thanks a lot devs for making hackintosh possible on AMD.

 

I just updated to 10.10.5 from 10.10.3 and I get Kernel Panic until I remove the RealtekRTL8111.kext from S/L/E

 

My Config:

 

FX 8120

GA 970A DS3 (Non UEFI)

24GB DDR3

320GB HDD

 

I am using Chameleon as bootloader.

 

Everything was working fine in 10.10.3 I updated and used the kernel and other files in Zip in AMD Development Section. Everything else is working fine. It boots all fine If I remove the kext and clear the cache. I have tried both v 1.2.3 and 2.0

It doesnt boot into Safe Mode with the kext.

 

Kindly Help finding a solution. I mainly use this for iOS development. I have a Mac book Air but its too small for long time work.

 

post-1261854-0-51904300-1443138589_thumb.jpg

post-1261854-0-51904300-1443138589_thumb.jpg

Share this post


Link to post
Share on other sites
Advertisement

use these newer drivers from Mieze and rehabman for your LAN: Realtek RTL8168 / 8111

http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/

I am already using those kexts. 

 

I have found one more thing.

If I load the kext using Kext Wizard after login, ethernet works fine. This is using the same kext which causes the above error

 

Edit: The above process also causes a shutdown/reboot problem. The screen goes off but the Fan etc keep running. i.e. PC doesnt shutdown completely.

Share this post


Link to post
Share on other sites

Do you use a custom DSDT?

I will contact you back this afternoon, when I come home from work, then we can try to resolve the issue.

Share this post


Link to post
Share on other sites

Do you use a custom DSDT?

I will contact you back this afternoon, when I come home from work, then we can try to resolve the issue.

No, Never even tried DSDT thing.

 

Thanks a lot. :)

Share this post


Link to post
Share on other sites

install the contents of the folder in the appendix in your /Extra/Extensions/ repair the permissions and renew the kernel cache with Kext Wizzard. then use the AMD.DMG of rampagedev, there should be included files for your board. if should not be the case, then Install maciasl or dsdt editor and export a raw dsdt and upload it here


Edit:

 

If you have any questions, ask your questions here: http://www.insanelymac.com/forum/topic/285760-help-topic-further-help-in-chatosx86hulegacykernel-irc/page-128

extra_Extensions.zip

Share this post


Link to post
Share on other sites

Xcode 7 wasnt working properly and I was trying something and system went bad. 

Now I am thinking of clean install 10.10.5 and not use a distro. (I was using one from Hackintosh.zone)

 

Can you guide me to a proper tutorial

 

Thanks a lot guys

Share this post


Link to post
Share on other sites

create an USB installer using by Disk Utility, install Enoch bootloader (current version), then use the contents, see package, what I have uploaded in to --> Extra/Extensions/ ... then Download my latest AMD kernel, see above under download, install the kernel in your USB Installer to  /S/L/kernel/

Then prepare the BIOS Settings for OS X, then boot from USB Installer and install yosemite....then install the AMD kernel in your partition to /S/L/kernels/  .... that's it!

 

Edit:

in the package (see my Post #7) is a Chipset Driver, so should your system run better

 

Edit 2:

these Problematic drivers should remove from USB Installer and later from your finished installed Yosemite partiton from S/L/Extensions/  "AppleGraphicsControl.kext, AppleTyMCEDriver.kext, AppleUpstreamUserClient.kext"

 

 

as boot flags you can test with: -v -f kext-dev-mode=1 npci=0x3000 usekernelcache=no  GraphicsEnabler=NO nvda_drv=1

 

..... and do not use so called super-tony-tools that promise much and cause only problems in the long term. make every possible installation manually !

 

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 k.panic
      Hi to all!

      I've installed Yosemite on:
      - i5 4690
      - ASRock H87M Pro4 (with intel ethernet I219-V) (IntelMausiEthernet, AppleIntelE1000 and RehabMan for I219V kexts)
      - 8gb ddr3 RAM
      - 1tb hard disk
       
      If I disable I219-V from BIOS, when I shutdown it, don't reboots (tested with all kexts)
      If I enable I219-V from BIOS, when I shutdown it, the system reboots.
       
      How can I fix this? Thanks!
    • By Coddyx
      Hi,
       
      I followed the AMD OSX Vanilla Guide and managed to successfully build my first hackingtosh.
      Everything works great EXCEPT for my MSI - Radeon RX 580 8 GB GAMING X.
      I ran some benchmarks (and tried World of Warcraft) and I am getting ~50% of the performance I am usually getting in Windows 10.
      Unigine Heaven reports ~950 vs 1750 in Windows and World of Warcraft runs @ 30 fps lowest settings vs 60 fps ultra settings in Windows.
       
      Here are the kexts I am using:
      AppleALC Lilu NullCPUPowerManagement RealtekRTL811 VirtualSMC WhateverGreen  
      I should mention that this is an AMD hackingtosh running on Ryzen 5 1600 3.2 GHz 6-Core Processor.
       
      I read and I completely understand that I should not expect 100% performance. But I believe a 50% drop is out of the ordinary.
       
      If anyone has ideas on what I could try to up the performance it would be greatly appreciated.
       
      Thank you!
       
       
    • By vlgngrbrdmn
      Hey all,
       
      This is my first time posting to this forum.
       
      Here is my problem: My main issue is random freezing of my display (i.e. cannot move my mouse) and nothing being displayed after my monitors go to sleep (i.e. lock my screen, wait a few minutes, try to move mouse/type on keyboard. My displays wake up but display "no signal"). I have to reboot in order to use my Hackintosh again.

      Another issue that I am experiencing is that, every time I reboot my system and login initially, my right and left vertical displays do not display correctly until I turn one of them off and back on again. It is kind of hard to describe what is wrong, but basically the dimensions of the display and the orientation (horizontal vs. vertical) is wrong, and my mouse does not display in the correct place on the screen.

      Either way, after some research it looks like this all may be due to my Framebuffer being incorrect. However, I am having a hard time trying to determine whether that is the case and, if so, how to fix it.

      I did manually try to add a Framebuffer ("Kamarang") into my config.plist below, however that did not seem to make a difference.

      Any help with this would be much appreciated! Also, please let me know if I should upload anymore information.

      Currently, My setup consists of 1 Dell U3415w and 2 Dell 2415 monitors in an "H" configuration (both 2415s setup vertically on either side of the U3415W).

      This is all being powered by a SAPPHIRE Radeon RX Vega 64 (https://www.newegg.com/Product/Product.aspx?Item=N82E16814202326) with each monitor plugged via a DisplayPort.

      I am currently running the latest version of macOS Mojave, 10.14.4.

      I am also using the latest version of the Clover boot loader (4920) with the following kexts located in kexts\Other:
      AppleALC.kext AtherosE2200Ethernet.kext Lilu.kext USBInjectAll.kext VegaTab_64.kext VirtualSMC.kext WhateverGreen.kext My config.plist file contains the following:
      ?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>#DisableDrivers</key> <array> <string>CsmVideoDxe</string> <string>VBoxExt4</string> </array> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Fixes</key> <dict> <key>FixHPET</key> <true/> <key>FixIPIC</key> <true/> <key>FixRTC</key> <true/> <key>FixShutdown</key> <true/> <key>FixTMR</key> <true/> </dict> <key>Patches</key> <array> <dict> <key>Comment</key> <string>change XHCI to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDSQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change XHC1 to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDMQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change SAT0 to SATA</string> <key>Disabled</key> <false/> <key>Find</key> <data> U0FUMA== </data> <key>Replace</key> <data> U0FUQQ== </data> </dict> </array> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>MATS</string> </dict> </array> <key>FixHeaders</key> <true/> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>PluginType</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>keepsyms=1 dart=0 debug=0x100 shikigva=40</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Timeout</key> <integer>5</integer> </dict> <key>BootGraphics</key> <dict> <key>#DefaultBackgroundColor</key> <string>0xF0F0F0</string> <key>EFILoginHiDPI</key> <integer>1</integer> <key>UIScale</key> <integer>1</integer> </dict> <key>CPU</key> <dict> <key>#BusSpeedkHz</key> <integer>133330</integer> <key>#FrequencyMHz</key> <integer>3140</integer> <key>#HWPEnable</key> <true/> <key>#HWPValue</key> <string>0x30002a01</string> <key>#QPI</key> <integer>4800</integer> <key>#SavingMode</key> <integer>7</integer> <key>#TDP</key> <integer>95</integer> <key>#TurboDisable</key> <true/> <key>#Type</key> <string>0x0201</string> <key>#UseARTFrequency</key> <true/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> AAASGQ== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> </dict> </dict> <key>USB</key> <dict> <key>FixOwnership</key> <true/> </dict> </dict> <key>GUI</key> <dict> <key>Hide</key> <array> <string>PREBOOT</string> </array> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Linux</key> <true/> <key>Tool</key> <true/> </dict> </dict> <key>Graphics</key> <dict> <key>FBName</key> <string>Kamarang</string> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>RadeonDeInit</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Port limit increase</string> <key>Disabled</key> <false/> <key>Find</key> <data> g710////EA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.12.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g710////Gw== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (RehabMan)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g32IDw+DpwQAAA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.13.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g32ID5CQkJCQkA== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (PMHeart)</string> <key>Disabled</key> <true/> <key>Find</key> <data> g/sPD4MDBQAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.0</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (Ricky)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g/sPD4OPBAAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>External Icons Patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>C02601270QXGPF7FB</string> <key>ROM</key> <string>UseMacAddr0</string> </dict> <key>SMBIOS</key> <dict> <key>BoardSerialNumber</key> <string>C02601270QXGPF7FB</string> <key>ProductName</key> <string>iMac17,1</string> <key>SerialNumber</key> <string>C02R2HZDGG7L</string> <key>SmUUID</key> <string>91E0E343-A938-4117-BBC7-234EA3ED265E</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> Also, for what it is worth, sleep is disabled on my system:

      Again, thank you all for taking time out of your day to help a fellow hackintosher out!
    • 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 THE M
      Hi,Everyone
      i've struggled to install Mac High Sierra from three days ago  with an strange error then my pc restart ......
      My PC specifications is
      Cpu amd Athlon 620 II x2
      Ram 8g
      Graphic Ati 5670 DDR3 2g
      Motharboard msi 970 amd

×