Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by diddl14

  1. To fix iMessage (ROM value all zero's), I've migrated to Clover in UEFI mode.

    iMessage problem was solved but now wake from BT-keyboard no longer works.


    Funny thing is that in BT-preferences, the option 'allow wake from BT-keyboard' is set.

    When booting again via Chameleon, that option is greyed out but wakeup via BT-keyboard works fine.


    What could I check to get wakeup from BT working also under Clover?

  2. I have the same board and it's working fine so the issue is probably either with the configuration or the network, not the driver.


    Some suggestions on what you could check:


    What driver version is current installed?


    Are the lights on the ethernet port blinking?


    How do you wake the system up?


    When it is sleeping, check the the ip and arp table on your router - it might be an issue with a sleep proxy http://en.wikipedia.org/wiki/Bonjour_Sleep_Proxy


    Anything in the console log after you wake it up manually?


    Hope this helps..

  3. @hnak any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?


    I fixed WOL for the AppleIntelE1000e.kext in a patched 2.5.4f, see #1988601 and #1993817

    @hnak, could you have a look at this and maybe add it to the next 3.x update?

  4. As I haven't read the full source yet, I don't know what bugs are still waiting to be found. Based on my experiences with network driver programming, I just wanted to explain how WoL works in principle so that you can check if it correctly implemented.



    As I haven't read the full source yet, I don't know what bugs are still waiting to be found. Based on my experiences with network driver programming, I just wanted to explain how WoL works in principle so that you can check if it correctly implemented.



    I'll check the WOL code agains your learnings. Do hope that the original developer joins the discussion so the whatever changes required can make it into the latest build.

  5. When the system goes to sleep the driver's disable()-routine gets called which has to put the NIC into a state so that it can generate wake-up events. Finally the OS calls setPowerState() where you have to put the NIC into D3(cold) state and enable generation of PME events.

    Are you saying the driver has a more fundamental issue with WOL?

  6. It seems WOL isn't working on a GA-Z87MX-D3H and OSX 10.9.1.


    On sleep, the lights on the adapter go and stay out. A magic packet does not wake it up. Testing with another adapter (USB2ETH) worked ok.

    I've not yet tested with an other OS myself but from what I understood, WOL works fine in Windows on this board with build-in LAN.


    That leads to the conclusion that it might be a driver issue..


    I did some debugging in AppleIntelE1000e.kext and at least found that AppleIntelE1000e::__e1000_shutdown does not get called.

    This seems to be critical for activating the APM/WOL state.


    Edit: I got it working with a small code change and setting link-speed from 'Auto' to '100baseTX'... 
    Doing some more testing over the weekend hoping to also get it to work with 1000baseTX
    Update: after disabling Intel Rapid Start Technology in the bios, WOL works with 'Auto' and GbE speed.
    Copy the this code from AppleIntelE1000e::stop to the end of method AppleIntelE1000e::disable, before pciDevice->close(this):
    bool wake;
    __e1000_shutdown( &wake, false);

    Since this was more a trial-and-error fix, I hope someone more knowledgeable with the actual driver code could check if this makes sense or not  :)


  7. I just took a look at it using Pacafist, thinking it was probably just a roll back to version 1.3.5 or 1.3.6, but it is newer version 1.5, next question would be is there and difference in performance or other benefits to using this instead of the older version? Will test myself shortly, curious to see if 2 min boot delay still occurs in ML

    The version number "1.5" seems misleading. I did a binary compare of the content and found that the patched version is nearly identical to AppleACPIPlatform.kext 1.3.5. Just a few bytes changed in the actual binaries. Size is identical.

  8. Updated today my P6T-SE from from SL to Lion. Had the same issue that the App Store no longer worked.


    Turned out that I still had an Ethernet EFI string in com.apple.boot.plist with the wrong PCI path..

    After fixing that and rebooting, everything worked perfect.


    Thanks for all the hints in this thread!

  9. I recently purchased a p67a-ud7 and an i7 2600 to test over the coming months in order to be ready for when Apple starts supporting the new processors. So far, I've installed with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and have:


    Audio working with ALC8XX kext

    LAN working with 8111e by Lnx2Mac

    Restart and shutdown working

    QE etc working with NVenabler

    I've also installed Bridgehelper

    I'm currently trying to get a p8h67-m working. 10.6.0 install went smooth, update to 10.6.6. resulted in the system hanging on kernel load. Not yet tried BridgeHelper as this seems to be just a modified 10.6.0 kernel (?)


    What gfx-card are you using? I'm trying to get Intel HD working with QE but so far no luck...

  10. Is anyone else here trying to get the build-in graphics of an i5/i7 Sandy Bridge CPU working (2xxx, H67 chipset)?


    Doesn't look like there is solution yet so I would like to compile what doesn't work.


    Not working:

    - latest MacPro kext's


    Not yet tried:

    - latest 10.6.7 combo update

    - Lion kext


    Has anyone the these yet or can think about what might be worth a try?

  11. Very nice tutorial! Thanks for taking the effort of compiling/documenting this!


    Currently I'm running 10.5.8 on an P6TSE with everything working fine.

    Before I try installing 10.6.x, could someone confirm having a P6TSE running the 64bit kernel+kext's?


    Anything specific that need to be taken into account to have that working or is it covered by this tutorial + essentials package?