Jump to content
InsanelyMac Forum

maroder

Members
  • Content count

    72
  • Joined

  • Last visited

About maroder

  • Rank
    InsanelyMac Protégé
  • Birthday 06/07/1978

Profile Information

  • Gender
    Male
  • Location
    Germany
  1. Hi there, This guide will enable your Intel addon NIC (EXPI9301CT) to fully support the Apple drivers and behave like a native Apple NIC. I wanted a solution for my trusted Intel NIC without having to use any third party kexts to get it working and also wanted it to be fully UEFI compatible. So I researched a little and would like to share my results in this short guide. Caution: This guide will only work for Intel Desktop CT NICs with PCI device ID 10D3. Also I only used OSX Yosemite to verify the results, but it should work in Mavericks, too. 1) Optional: Remove third party kext for the NIC Please remove any other third party kext you may have installed for your Intel NIC. We do not want any conflicts here later on. 2) Create a bootable DOS USB drive I used Rufus Boot USB Disk with an Image of Win98 DOS bootfiles to create it under Windows. The original ISO for the Win98 DOS Boot files can be found here http://goo.gl/WOaQi (Windows 98 DOS Boot). Any other DOS compatible Boot environment should work, too. 3) Download Intel Preboot files PREBOOT.EXE from http://goo.gl/ppSRzo 4) Copy the necessary files to the USB drive Extract the the download and copy the following files the bootable DOS USB drive Copy BOOTIMG.FLB from PREBOOT\APPS\BootUtil Copy BootUtil.EXE from PREBOOT\APPS\BootUtil\DOS 5) Restart and boot from the USB-Stick You will temporarily have to change the UEFI-BIOS settings to be able to boot from a DOS environment. I had to set the following options: Legacy USB = Enable SecureBoot = Other FastBoot = Off 6) Flash the NIC with EFI-ROM After Booting from the DOS USB drive please use the following commands in the given order. Backup the original ROM BootUtil -SAVEIMAGE -FILE=Backup.FLB Enable flash write capability on NIC BootUtil -FE -ALL Update NIC with EFI-ROM BootUtil -UP=EFI -ALL -FILE=BOOTIMG.FLB 7) Change PCI device ID with ethtool Congratulations, your Intel NIC is now UEFI compatible and should already show up in your UEFI BIOS. We now will have to change the device ID from the NIC, so that OSX can use the native driver. Boot from a Linux Live Boot environment (e.g. Ubuntu) and change the PCI device ID from 10D3 to 10F6 with ethtool. Please ensure your Intel NIC is eth0. We do not want to patch any other NICs by mistake. sudo -s apt-get install ethtool ethtool -E eth0 magic 0x10D38086 offset 0x16 value 0x00 ethtool -E eth0 magic 0x10D38086 offset 0x17 value 0x00 ethtool -E eth0 magic 0x10D38086 offset 0x1A value 0xF6 8) Start OSX and enjoy your native Apple Intel NIC Reboot and don't forget to change the UEFI-Settings back from step 4 to their original values. After this you can start OSX and the NIC should be recognized. Windows will pick up the NIC without any problems, so no worries if you want to switch back to Windows sometime later on. Disclaimer: Please note, this procedure solved a very specific problem for me and the guide is certainly not perfect. I do not take any responsibility for anything that may go wrong if you follow it. I hope this guide may be useful for someone and please feel free to give any suggestions that may improve it. Cheers, Maroder
  2. Can't Boot Every Few Days (GTX 980/Cache/Permissions)

    Try using OSXAptioFixDrv2 (=Version 2) This solved the Problem for me. You'll find it in the newest Clover-Installations.
  3. Patching Intel 82574L Pci-Id 10d3

    Thanks for this great information - I will try it later on. Out of curiosity: Which vaules would revert that change back to the default IDs?
  4. New Driver for Realtek RTL8111

    I would have guessed so as the Intel driver is having the same problems. So the issue seems independent to the driver and network card currently in use. As this problem seems to be affecting real macs, too, it probably will get resolved quickly. Let's hope with 10.10.2.
  5. New Driver for Realtek RTL8111

    Thanks for the Info Mieze. Damn, what is Apple doing lately ... seems they are being overtaken by their own success. I guess I'll stick to Mavericks/Windows 8.1 till they get things sorted out with the network stack in Yosemite.
  6. New Driver for Realtek RTL8111

    Has anyone got the current driver running stable on Yosemite without network going down occasional on heavy load with multiple files?
  7. New Driver for Realtek RTL8111

    Just wanted to thank you Mieze for the great kext! The latest Dev-Drivers are running completely stable here!
  8. Adding a new network card (en0 / en1)

    Here the solution for anyone with the same problem: 1) As OSX doesn't like more than two network cards remove the old network card from network settings 2) Remove obsolete Kext for the onboard NIC from /System/Library/Extensions 3) Remove /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist 4) Rebuild caches (I used "Kext Utility" for this) 5) Shutdown your Hack and install the new NIC 6) On the next startup enter BIOS and disable the onboard NIC 7) Save the BIOS setting and boot OSX After booting to OSX the HP NC360T will be recognized with en0 and en1.
  9. Thanks for the input boli. Well, then I'm going to get myself the Asus as soon as they drop under 600 €, although the Samsung is cheaper. Need the VESA-Option
  10. Are you scaling? Shouldn't the native resolution be 3,840 x 2,160 @ 60 Hz with Retina resolution at 1920 x 1080 @ 60 Hz?
  11. Hi, I will add a new network card (HP NC360T) to to my system which works OOTB. Therefore I will disable my current onboard lan which is currently recognized as en0. After deleting the obsolete Kext for my disabled onboard card, which plist do I have to delete, to get the first port of my new network card to be recognized as en0? Naturally it will be recognized as en1, which causes problems with Messages. Which other steps would be necessary (eg. rebuild caches)?
  12. I'm really looking forward to upgrade my old 24" screen with lovely retina beauty on my hack, but this 30Hz issue is making me to nervous to buy one right now. Has anyone got the Samsung U28D590D or the ASUS PB287Q and first hand experience with this two monitors? I read somewhere the Samsung should run @60Hz, as it's not using Multi-Stream Transport to drive the display, but what about Asus? I would prefer the Asus because of its VESA mounting option.
  13. Asus H87-Pro DSDT?

    I just noticed one thing: After sleep the temperatur sensor reading with Hardware Monitor shows my CPU-Heatsink at 125°C, but all other readings are normal. I do think this is only a cosmetic issue as all other temps readings eg. cores are at their low 30°C. After reboot the temps are OK again. Is this a issue with FakeSMC or is there a possiblilty to fix this?
  14. Asus H87-Pro DSDT?

    You are the best!!! Just compiled the DSDT without errors. And now sleep is working on my beloved Asus board! Here my freshly compiled, working DSDT, should anyone else need it. ASUS-H87-PRO (C2) / BIOS-Version 1101 https://www.dropbox.com/s/3ontnqgreyjmimo/DSDT_Asus_H87Pro.zip Thanks so much to both of you for your help!
  15. Asus H87-Pro DSDT?

    Here is the dsdt.aml directly from a clean Clover boot from the command in terminal. Removed old link
×