Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About Andycore

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  1. Checking back in, with some good news -- did a fresh install of El Capitan 10.11, and using Mausi kext 2.0.2d3 -- everything works as expected. My previous issues with the kext not detecting the interface are no longer present. Seems as though a format and install did the trick, for me. I would suggest others having issues switching from the E1000e kext to this kext try that themselves as you never know what has been messed up in your system over time. Thanks for your hard work Mieze!
  2. I'll have to continue troubleshooting on my end, though things don't look good. It is quite probably something I did initially setting up the machine, there have been several hardware changes since I initially installed OS X. Thank you for taking the time to check out the logs and offer your advice. I'll try again when I do a fresh install.
  3. Sorry! Forgot to mention. It's an ASRock Z87 Fatal1ty Professional.
  4. Hey Mieze, excellent work on this! Glad to see an extension with improved performance over the sometimes shaky E1000e kext/s in existence. Unfortunately haven't had much luck getting it to work -- booting gets to the point where the GUI should appear, and then my system reboots without error or warning. My board has both I211AT and I217V based controllers on board, so the first boot with your kext didn't seem to initialise any hardware at all (there is a boot log of the first boot here, if you would like to see it). I have since disabled the 211 controller (it isn't used anyway), along with network boot options and WoL options from within my UEFI settings... Now I can see that the 217 is being detected correctly, however the issue remains. Just as soon as the boot process should be presenting the GUI, my system reboots. The most recent boot log is posted for you here, though to my inexperienced eye it doesn't seem like there is any issue with the driver loading or anything that would seem to show a problem resulting in a reboot. Your knowledge is greater than mine, so I thought it best to post to ask. I'm running 10.10.5, and while I use Clover as a boot loader I have your kext in S/L/E manually (as this is just easier for me). I also don't have a DSDT. It's entirely possible that this is a local conflict with some other kext or application, and I do plan on doing a complete rebuild of my workstation when El Capitan launches and is stable enough for hackintoshing... It would just be great to get some improved networking happening in the mean time. FWIW, the I217V on my mainboard does work with an E1000e kext with the version number 3.2.4. Thanks a lot for your hard work!
  5. [AMD] Working Builds!

    Motherboard: AsRock 990FX Fatal1ty Professional Chipset: NB: 990 SB: 950 CPU: AMD Phenom II 960T X4 Black Edition (Unlocked to X6 1605T) GPU: Gigabyte GeForce GTX 760OC 2GB (Worked out of the box with stock nVidia kexts and GraphicsEnabler=No. Full QE/CI, driving three monitors at 1680x1050) RAM: Kingston DDR3-1333 16GB (4 x 4GB) Network: Broadcom BCM55781 (Found here but only functions on 10.9.0, device detected but doesn't work on 10.9.3 or 10.9.4) Audio: Realtek ALC892 - Works with a very specific VoodooHDA without crackling/hissing (I have about 5 I've tried and honestly don't remember which one it was to link it, but can supply it if needed -- currently working on getting analog 5.1 working) OS X: Mavericks 10.9.0 (Capable of 10.9.4 but lose ethernet, so holding off until newer kexts / I jump ship to Intel) Kernel: "Niresh" default amd64 (Also Tested: "mckay_kernel" and kexts, worked perfectly with myHack) Boot flags: npci=0x2000 dmar=0 GraphicsEnabler=No Bootloader: Chameleon 2.2.1