I've been hockintoshing for a long while, since Leopard to be exact and last week I replaced my Nvidia 9600GT with a brand new 1050 Ti...
I have a Lion and El Capitan both were running fine before the 1050 Ti arrived, I read that my new Geforce needs new drivers that are readily supported by Sierra and High sierra.
So I deleted Capitano and installed High Sierra 10.13 using Niresh distro. All went well and smooth and all my hardware was recognized the only problem left is this:
My Nvidia driver "WebDriver-318.104.22.168.15.121" installs well with SIP enabled (aka 0x0 with clover) and after reboot the system is perfect with Nvidia web driver running fine
However after rebooting the Default slow OSX graphics driver is loaded and stays that way until I resinstall the web driver....
It's very annoying, I just can't make it work, I've been reading posts and tutorials for more that a week, nothing works, help is needed
Things I've tried already:
1. Boot using different clover revisions as old as 3911 and as new as 3509 (the latest)
2. Tried with clover in the EFI partion and/or Boot partition
3. Tried using different combos of nvda_drv,, nvidia webdriver, inject stuff (all possible combos in boot and graphics settings)
4. Tried all available kext (Lilu, Nvidia fixup, Nvidiaegpusupport, NVlibvalfix..) single and combos - in clover kext folder and L/E folder
5. Tried all different NVram recommendation - problem persisted even when nvram.plist is present or not
6. Tried running the postscripts from the driver installer pkg
7. Tried installing the driver via webdriver.sh
8. Fixing permissions and what not
And maybe other stuff that I forgot
Things to note:
When the graphics web driver loads fine KCPM kext utility works fine too but when the default driver is loaded KPCM warns that B0 and B1 SIP options are not enabled even though they are when I test csrutil status
So I'm somehow thinking of a bug in Clover not applying the SIP restrictions correctly
I don't know what happens when the driver is reinstalled that makes it work after reboot for 1 time only (I've went through all the pre post scripts in the installer and didn't find anything magical)
It seems nothings works except reinstalling the driver - nothing else matters
I'm almost pulling my hair - haven't faced such a problem since a very long time
Any advice is greatly appreciated
How to make AppleHDAController load on Ryzen boards?
Rename(/add) your audio controller to your DSDT/SSDT as HDEF
Add a _DSM method to your HDEF device with layout id 1
Patch the AppleHDAController binary, because it has a static table containing the supported PCI Vendor/DeviceID pairs and it also checks the VendorID against known values. As an example I provide a dif file and patched 10.13.3 binary, but if you want to I can patch the binary for other versions.
After AppleHDAController loads to actually get sound working you need to patch AppleHDA.kext for the codec on your board. First I tried to use Lilu+AppleALC for this task, but for some reason it refused to work. (I might look into it later why) But for the time being it was easier to use toleda's cloverALC script for that, but to make it work I had to change(/remove) the specified location of the HDEF device from the script. And for some reason it also required me to mount the EFI partition manually.
if [[ $(cat /tmp/HDEF.txt | grep -c "HDEF@1") != 0 ]]; then
if [[ $(cat /tmp/HDEF.txt | grep -c "HDEF") != 0 ]]; then
Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy.
As of now the driver supports the following members the RTL810X Fast Ethernet family:
Here is a list of the driver's basic features:
Supports Sierra (maybe El Capitan).
64 bit architecture only.
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).
TCP segmentation offload under IPv4.
Support for TCP/IPv6 and UDP/IPv6 checksum offload.
Supports Wake on LAN.
Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES.
The driver is published under GPLv2.
Built using Xcode 4.6.3.
Version 2.0.1 (2018-05-10):
Fixes a problem with retrieval of the permanent MAC address on some chips.
Version 2.0.0 (2017-04-04):
Uses Apple's private driver interface introduced with 10.8.
Adds support for the RTL8107E.
Supports packet scheduling with QFQ.
Adds support for flow control and EEE.
Version 1.0.0 (2014-05-24):
First offical release.
Before you install the driver you have to remove any installed driver for RTL810X.
Goto /S/L/E and delete the old driver.
Recreate the kernel cache.
Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later.
Install the new driver and recreate the kernel cache.
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.
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 other Realtek kext from your system because they could prevent the driver from working properly.
Delete the following files:
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.
Getting the driver
There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/
The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100
I am new, I hope I am posting in the correct forum.
My specs: Processor: Core i5 6500 Skylake 3.2ghz
Mobo: Gigabyte h170-d3h
M2SSD: WD Black 256gb PCIe (Mac OSx)
SSD: Samsung 860 Evo (WIndows 10)
HDD: WD Blue 1TB
GPU: Radeon RX 480
Monitor: BenQ RL2460 24"
I was able to install High Sierra on a new m2 drive, that I added to the above configuration with windows 10 already installed.
I had a few issues during install, including the monitor turning off at boot screen.
Unfortunately, this persists even now. It turns off at about 60% of the progress bar, and to turn it on again I have to unplug/plug back my hdmi.
Additionally, while all of the usb ports worked during install and while running it out of the clover I had on the usb stick, only the rear ones appear to work now.
The audio doesn't work either, though I added the correct patch according to my mobo
Lastly, my other drives are not recognized in the bios anymore. They run fine from boot override but they don't show up in the boot priority (while multiple entries of mac OS do, and they seem to increase in number at every reboot)