Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  1. Hi RehabMan, thanks for your response and thanks for all the help you give the community! Since I posted I've done a lot of research and trial and error and still had no luck despite lots of anecdotal evidence that the Plextor M8Pes are working. I have the M.2 2280 256GB M8Pe(G) with heatsink. I'm doing everything on a 10.12.4 system. I identified the PCI address using a Windows boot on the same system. I was able to create the HackrNVMeFamily kext with --spoof (it auto-detected 10.12.4 and the md5s matched). Each time I try something I boot up and go into disk utility and use that as the baseline for whether the current patch worked. The ssd has never shown up. First I tried JUST applying the various versions of the 0x10 -> [0x01|0x02|0x04|0x08] patch to IONVMeFamily in config.plist via clover configurator. None of those worked on it's own. Then I followed the full guide for NVMe including identifying the PCI address via Windows, building the ssdt, using MacIASL to build a SSDT-NVMe-ssd.aml, replacing the PCI address in both places from the template with my PCI address, compiling/saving/moving to booted EFI/CLOVER/acpi/patched; no custom dsdt so added the rename _DSM -> XDSM acpi/DSDT patch; verifying that no other aml in my acpi/patched had a name conflict with my pci address; and creating the --spoofed HAackrNVMeFamily.kext and copying it to EFI/CLOVER/kexts/other where all my kexts are (it created with 10_12_4 appended to the name but i renamed it). According to another post the m8pe does not support 4k so I didn't add any patches about 4k? I'm not entirely clear on this part. So to sum up what I've tried is - using just the 0x10 -> [0x01|0x02|0x04|0x08] patches: 4 reboots no love - creating SSDT-NVMe-ssd.aml in acpi/patched and --spoofed HackrNVMeFamily.kext in kexts/other and _DSM -> XDSM rename patch and all four variants of 0x10 rename patch: 4 reboots no love - saw a post that if you have HackrNVMeFamily the 0x10 -> 0x01 patches should be against HackrNVMEFamily instead of IONVMeFamily so tried that, four reboots no love I'll try to understand what you mean when you say "you should see if you can change the native block size to 4k". As I stated another post earlier in this thread seemed to indicate the m8pes don't support 4k. I guess that involves booting linux? Would love a bit more of your time to point me in the right direction. Or if someone else with one of these plextor M8Pes could chime in with what is working for them. I don't want to do the 15 or 17 or whatever config.plist patches. Thanks again, I appreciate your help!
  2. I bought a Plextor m8pe nvme ssd without doing my homework and it's seeming to not be supported (yet). Anyone know different? So far I've only tried the kext patches from http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/?p=2356251but Disk Utility never shows the drive. Is the drive showing up in Disk Utility a pre-requisite for the drive every working? Is there any reason try rehabman's process without the drive showing up in DU?
  3. Ok I'll try to be brief but I have spent some time on this and I still don't have it working right. I have a GA-Z77X-UP4 TH booted via Clover. I don't use any DSDT, just the Clover basic config. To get sound working, all I did was download and run the Toleda sound script from here: https://github.com/toleda/audio_RealtekALC/blob/master/audio_realtekALC-100.command.zip. After a reboot, sound works perfectly. I did have to go into the Sound control panel and manually set some stuff that first time, like the checkbox to play a note when you adjust the volume, and to set the output. However. After sleep, things get wonky. Sometimes after sleep, the sound goes out, and sometimes, if I try to adjust the volume, instead of the normal overlay, it'll display a "no can do" overlay. Sometimes, the sound just automatically shifts to USB sound (I have an old Apple crystal display that connects via USB and has USB sound output). And sometimes it works fine after sleep. I should note that internet is the same way. Sometimes after sleep internet works, sometimes it doesn't. Rebooting always cures all ills. Good luck.
  4. For what it's worth, several people seem to be having this issue. I know I have this issue on a GA X58A-UD3R/i7 930/GeForce 260 setup (booting using TonyMac's tools, not Clover). I've disabled sleep on this system until/if anyone comes up with a solution.
  5. I'm documenting what I've done so far with this board. Stay away from this board. It is wonky. At this point everything works. Sort of. - Sound works out of the built in line out until a dog across the street barks, when only Display Audio sound via USB works (I'm using a crystal Apple display and a Display Port Apple display, the latter of which supports sound via USB) - Ethernet works until the machine sleeps, and then it may or may not come back at full speed or at a fraction of it's normal speed - Sleep works on alternate Thursdays. Sometimes it works, sometimes it doesn't. - Don't even get me started on USB. It is a mystery for the ages which ports will work when. Bottom line is that I reboot. A lot. Fortunately I figured out my biggest issue which is that if both monitors were plugged into the HD 6850, Clover would fail to detect the proper mode and drop into 80x25 console mode, rendering the machine unusable until I removed the Display Port monitor (leaving just a DVI monitor plugged in) and rebooted. BIOS settings are pretty standard - load optimized defaults - XMP set to "Profile1" - all c states enabled - CPU Voltage Override disabled - SATA on AHCI mode everywhere - onboard video disabled - XBit enabled - rapid start disabled - full screen logo enabled - CSM enabled but with booting from UEFI only and other devices "legacy first" - XHCI and EHCI handoffs enabled (but i'm going to try disabling EHCI handoff at some point) Followed one of many guides to create the Clover USB stick, legacy install method. Disconnect Display Port monitor (using only DVI monitor). Replugged keyboard around USB ports until it triggered. Booted (F12) to USB stick, installed Yosemite from USB; rebooted (F12) to stick, but at the Clover menu selected new drive. NOTE: this board uses the Realtek RTL81xx series driver from Lnx2Mac. Installed Clover for UEFI booting only, installed to ESP; under Drivers64UEFI, installed CsmVideoDxe-64 and OsxAptioFixDrv-64. Install RC scripts on target volume, install preference pane. NOTE: as I mentioned I was having an issue booting with a Display Port monitor connected to the HD 6850 card. I'd get the 80x25 Clover console mode rendering the OS unusable. Finally I did three things: inject ATI in clover config.plist, set gui screen resolution to 1920x1080 in clover config.plist, and added CsmVideoDxe-64.efi. I don't know what magic soup of these things fixed the problem but I now get a clean Clover menu on both monitors and can boot up fine. After a reboot I used Toleda's 10.0 audio script for the ALC892 audio chip, audio_realtek-100.command. Finally for USB I installed a GenericXHCIUSB.kext file. Others have reported that you need do nothing, or, set a fakeid in clover config.plist. I tried everything else I could find and settled back on the kext. I have not worked much on iMessage/FaceTime. I'll post back when I have some time to work on that issue.
  6. The finickiness level seems high on this board. I discovered I can set a debug flag in the clover config to try to get a log of how/why clover is "crashing" back to the console menu rather than the GUI menu. The FAQ has a question about "why do I see a BIOS-like screen" that I'm assuming is the same as what I'm calling a console menu. The menu is white text on black screen, with all the same options as the GUI, but in text form, for example: Boot Yosemite from Macintosh HD Boot Yosemite from Recovery Partitition Clover Options Arcane menu option Reboot Shutdown I note that if I disable CSM, I can't boot at all. I think the 6850 is legacy only.
  7. I have had a great deal of success with Clover on a GA-Z77X-UP4 TH board with a discrete GA AMD HD 6850 GPU. Once the OS is up it is running very well. As far as I understand I'm in full UEFI mode. But I'm wondering if this is causing issues during booting because my 6850 is not (?) UEFI compliant (doesn't have the GOP or whatever)? I'm having issues with booting. The symptoms I'm seeing: 1. if I have two monitors plugged into the 6850 (dvi and displayport), I get the Clover "console menu" (or whatever it's called?) rather than the usual GUI menu, and if I continue the boot, the monitor attached to the displayport output only shows output in a very small section of the screen in the upper left corner, with lots of artifacts. Note that this is not the whole screen squished, it's just the upper left corner - I can see the normal Apple icon in the upper left corner, and I can type in my password, log in, and interact with the Apple menu normally. But 85% of the screen is black and what I can see, artifacts terribly. 2. if I have just my older (non thunderbolt) monitor plugged into a DVI output on the 6850, system boots fine - normal Clover GUI, normal desktop, I can then plug in my thunderbolt monitor to the displayport output and it's fine. What is that Clover console menu? It seems to be a symptom of Clover crashing or not loading properly. I have made lots of trials in the BIOS, enabling/disabling the onboard GPU, changing boot order, changing "init display" settings, turning off rapidstart, disabling full screen logo, and so on. There is no combination of BIOS settings that allows me to boot cold with both monitors plugged in and see the normal Clover GUI and get to the OS properly. Interestingly, I can't remember if I've EVER seen a POST on this board - where you see the BIOS version, the type of CPU, RAM, SATA devices, etc. Not even with just a DVI into the onboard GPU. In the boot options, I see, in addition to UEFI options for my SSD and HD (I have Yosemite bootable on both), a mystery third option labelled "Mac OS X". I have no idea what this is. Does anyone know or have a clue what this option is or where it came from? I've considered but haven't tried connecting the thunderbolt monitor using an adapter to one of the other outputs on the GPU. Most recently I've tried enabling onboard GPU, plugging a THIRD monitor into onboard DVI, plugging usual monitors into 6850 DVI and displayport, and booting. This displays normal Clover GUI to onboard DVI output, and black screens to 6850 outputs; and eventually the 6850 outputs come on and everything looks good. But then I noticed that the mouse seems to "stutter" if I look at it closely. I swear interacting with the OS in this configuration introduces a lagginess that is hard to quantify. Anyone have any thoughts? I'm on the latest "stable" BIOS for this board. FYI I would recommend everyone stay away from this board. For this reason and wonky USB support. I got it because I thought thunderbolt was the future, but it's just not worth it.
  8. Need some help with install

    My advice is to go slowly, leave your Mav disk alone and use another disk while you figure things out with Yos. I had perfect luck with TonyMacx86's guide here: ##### You'll need the Realtek drivers installed via m u l ti be as t, and you can just use your current kext if your Mav box ethernet is working. For sound, it can get tricky, so be patient. I had excellent luck with Toleda's scripts: https://github.com/toleda/audio_RealtekALC I also have an 892 so I followed the instructions (Yos/Clover) here: https://github.com/toleda/audio_CloverALC, using https://github.com/toleda/audio_CloverALC/blob/master/audio_cloverALC-100.command.zip Then I had to install a new USB 3 driver (http://sourceforge.net/projects/genericusbxhci/files/) (use ke xt be as t or similar to move GenericUSBXHCI.kext to /S/L/E) Then I had to follow the instructions at http://www.insanelymac.com/forum/topic/298027-guide-aio-guides-for-hackintosh/?do=findComment&comment=2020598 to fix FaceTime/iCloud/iMessage. Finally to hide the Thunderbolt firmware update on the App Store/Software Updates I had to run in terminal: softwareupdate --ignore ThunderboltFirmwareUpdate1.2 May also need the trim patch if you're using an SSD that doesn't have trim built in. mult i be as t can do that for you too.
  9. Clover: Various Issues

    Regarding your sleep issue: I had the exact same issue on a GA Z77X mobo all through the Yos DPs, but now I do not have the issue with the GM. It's hard to say if it's a fix in the GM, or if it's because I installed clover differently. What was happening to me and I believe is happening to you (look in Console.app) is that your hack is waking around 6AM and crashing out, causing the machine to reboot to your boot loader screen. You have basically two options: 1. wipe and reinstall the GM using TonyMacx86's instructions for installing Clover via USB stick at http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html. Note that I don't know exactly what I did differently between the DPs and the GM, I just know, after installing the GM to two different disks (an SSD and a spinning HD) I do not have this issue any more. The thing about reformatting the EFI partition stands out as something I didn't do before, but I have no idea if that has anything to do with it. 2. follow the instructions in the thread here to disable periodic waking: http://www.insanelymac.com/forum/topic/300072-wake-reason-rtc-alarm-how-to-deactivate/. My understanding is that a few major releases ago, Apple decided to significantly alter sleep/wake to basically create a "nap" mode (hence app nap) where the screen doesn't light but the system wakes enough to do software updates, check bonjour servers, do time machine backups, etc. So you can use these instructions to basically stop "nap" mode from ever happening. Some of the folks on the thread I copied are irritated by the noise of the machine waking up, hence creating a solution. May be other solutions but either of these might get you there. I know the SDST file controls speed step and your BIOS/UEFI settings could be affecting it. In my case, I had a Mavericks hack that slept fine but started crashing once I put the Yos DP on, so I was pretty confident that my issue was not SDST or BIOS/UEFI related. No clue on your wifi issue. My hack uses ethernet. Stop surfing questionable sites?
  10. This is a GA Z77-series mobo, so it's BIOS/UEFI, currently booting clover/UEFI. I think darkwake is mobo-agnostic; I know I changed it with my older BIOS mobo. My recollection is that somewhere around snow leopard or lion, Apple completely revamped how sleep/wake worked. Prior to that, wake was wake - screen lit, system on. Apple wanted to support a "silent wake" to support periodic silent time machine backups and system updates - the machine would wake up enough to do that stuff but not light the screen. That's when I needed to set darkwake, so that the magic packet wouldn't use the "silent wake" style of waking, but rather, the full screen lit wake that I wanted.
  11. My understanding is that the normal process is that the screen does not light. Certainly on real Macs I don't think the screen lights. Hacks of course have different c-states etc (stuff managed by the SDST file) that indicate how deeply to sleep, how lightly to wake, in addition to the darkwake setting. This can also muck with "wake for network access". Earlier I was trying to get my hack to wake via network "magic packet" and I could hear the drive wake up but the screen wouldn't light. So I changed darkwake to 0, and solved that issue; the screen fully lit. It all depends on what you want to accomplish. My understanding is that real Macs wake without lighting the screen periodically by design, and wake for network access fully. Hacks are an entirely different beast and it can take some fiddling to get the behavior you want, including not waking every two hours as this thread is primarily geared towards.
  12. Keeping in mind that I haven't personally witnessed the behavior because my hack sits upstairs, yes, to the best of my knowledge, the hack is waking itself up every 2 hours or so and then going back to sleep automatically. I think it's doing this because the console log shows that it wakes up by RTC alarm roughly every two hours. Since the machine is always asleep when I check on it, I'm assuming it's just going back to sleep each time. To the best of my knowledge, that is the designed intention on Apple's part. They sort of intend their machines to "silently" wake up, check for stuff like new mail, time machine backups, software updates, etc., and then go back to sleep. The darkwake stuff is sort of an override to that, as far as I know - when you tell it "darkwake 0" my understanding is "never wake silently, always come fully awake" but it's been a while since I messed with that so I may be way off.
  13. I was having issues with the Yosemite DPs booted via Clover waking in the middle of the night, often at 6am, and crashing out. I'd wake up to find the machine had rebooted, and could check the console log to gather that it had woken and crashed. I followed this thread as a lurker to keep track on what folks have been doing. I realize most of you just don't want your machines waking every few hours. That part doesn't bother me; it was the crashing out that I was trying to fix. I'm pleased to report that on my rig at least, a GA 7 series board with discrete AMD graphics card, and a fresh install of the latest Clover and Yosemite GM, my machine wakes every few hours but does NOT crash, at least in the 2 days since I built it. That's the behavior I'm looking for so I'm happy. I didn't mess with any of the darkwake settings, so when I say the machine wakes, I am referring to the stuff in the console log. For all I know it's waking "silently" and going back to sleep. If it helps anyone, I followed tonymacx86's clover installation guide at http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html, including the part about converting the EFI partition to MBR (something I hadn't known to do previously).
  14. System reboots on wake from sleep

    I have this issue as well. The log shows that the system is waking from sleep from an internal scheduled alarm early in the morning, and presumably KPing and rebooting. I thought applying the sleep/wake fix in the clover installer would help but it has happened for me since DP1. I'll upgrade to DP4/latest clover tonight, see if it makes any difference.
  15. Installing Clover on USB drive

    I've only begun trying to figure out Clover but I've built several generations of Hackintoshes running Snow Leopard on up, so I have some experience in general. The most obvious thing I see is the error message about "Can't find volume with the name /Volumes/Untitled 1". This seems to clearly indicate a basic issue finding your USB stick. Often when you use Disk Utility to format a USB stick the default volume name is "Untitled 1". The reference to /Volumes/Untitled 1 is how Mac OS X sees mounted volumes - it creates an alias under /Volumes to any external disk or network drive. So something is looking for your USB stick under /Volumes and not finding it. Did you manually rename your USB stick to something other than Untitled 1? I would go back through your steps and see what the USB stick volume is supposed to be called, perhaps you have a script that is assuming it's called Untitled 1 and you renamed it, or it's now just "Untitled" or something else. Start with what the USB stick actually is now and work backwards.You can see what the USB stick volume name is by, among other methods, inserting the stick, opening Terminal.app, and going to /Volumes ("cd /Volumes") and seeing what's there ("ls"). Andrew