Jump to content

pbryanw

Members
  • Content count

    17
  • Joined

  • Last visited

About pbryanw

  • Rank
    InsanelyMac Protégé
  1. @MICKHAEL - Thanks, that worked for me. However, I had to disable SIP (CsrActiveConfig=0x67) before installing the .104 Nvidia driver, and applying the patch. I guess this is so the patched drivers can load. Found this out the hard way after having SIP enabled, and going through the install process, only to find the modified drivers weren't loading. Now, the lag issues are fixed for me in macOS 10.13.3. Thanks again.
  2. Hi, I was having an occasional instant-reboot on startup problem with my Nvidia graphics card (it happened just as my GPU was being initialised during boot). I now think this was caused on my system by macOS sometimes falling back on the older, out-of-date, Nvidia drivers in S/L/E rather than the newly installed web ones in L/E. To fix this, I disabled Nvidia Graphics injection in Clover by adding this to config.plist: <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>Nvidia</key> <false/> </dict> </dict> I had this problem on my hackintosh, which consists of a GTX 1070 with an Asus Ranger VIII Z170 motherboard. I've had no instant reboots since adding this code. Hope this might help someone
  3. Many thanks to captain-j a few pages back - with their instructions I was able to install the Nvidia web drivers without the need for NVWebDriverLibValFix.kext. As they note, you need to set CsrActiveConfig to 0x00 before you install the new drivers (after uninstalling my previous attempt at installing them). Doing it this way, I got a prompt to enable a kext during the installation process, and also no error message during the setup process. Afterwards, there was no black screen on boot, and I could reset CsrActiveConfig back to 0x67 after installation was finished with no issues. Update: Seems the kext prompt was due to another program running at the same time. However, the lack of error message was correct.
  4. Yep, I still needed NVWebDriverLibValFix.kext or else I got a flashing black screen on High Sierra startup. If, like me, you forgot to install NVWebDriverLibValFix.kext in your L/E directory, I also noticed you can install it in Clover -> kexts -> Other and it will still work as intended. Luckily, I could install it on my Clover USB drive and get High Sierra bootable again, after I had installed the Nvidia web drivers.
  5. pbryanw

    [pre-release] macOS High Sierra

    Hi, just extracted a new apfs.efi from my High Sierra Beta 9 installer, and it also has a created date of 26 August (see attached pic). Had a nice surprise as I was making a USB Drive today to install beta 8. When I had updated High Sierra and went to About This Mac, I realised my macOS version number was now 17A360a, and that I must have downloaded the new installer (Edit: This was a few hours ago in the UK)
  6. pbryanw

    [pre-release] macOS High Sierra

    Thanks for your detailed post to me a few pages back. I use a separate Clover USB flash drive, specially configured for my High Sierra install, and had deleted EmuVariableUEFI.efi from it before starting installation of High Sierra. However, I still had EmuVariableUEFI.efi on my main macOS SSD (along with an NVRAM.plist file) - maybe this is why when I disabled this drive I was able to proceed with the High Sierra installation? I took BIOS details & FF/FFM for my smbios from Sherlocks post on this, and didn't know Clover could do this for you, so thanks also for bringing this up and reminding me to download the latest Clover using the Build_Clover command (I'm using r4176 and don't know if a new version has been released since then). Also, can I ask how APFS damaged your flash drive - I've heard of problems using it on magnetic hard drives - but if it also causes problems on flash drives, I'll reinstall with HFS+ if it means I won't corrupt my drive? Edit: For brevity
  7. pbryanw

    [pre-release] macOS High Sierra

    Hi, no need - my flash drive is just for testing out High Sierra. Once the final version of this OS gets released, I will upgrade my main hackintosh SSD drive (which has all my apps & files on it) with everything I've learnt from the beta. I suppose I could clone but this system has worked for me so far @KGP-X99 - I'm glad to hear it worked for you too. I thought there might be another solution to this, as I spent too long making sure my smbios was right, and my installation was still failing. Hopefully, someone can go on and find a better workaround than having to disable drives in the BIOS, and find out why having some SSDs enabled causes this error?
  8. pbryanw

    [pre-release] macOS High Sierra

    @dehjomz - I was also having the "an error occurred while updating firmware" problem with dp6. Your post made me think that disabling my m.2 drive in my BIOS might get me past this error. It didn't, but then I tried disabling all my SSDs in my Asus Z170 BIOS, and I was able to get past the firmware error, and High Sierra dp6 is currently installing with no problems I'm installing dp6 on a Sandisk 64GB flash drive, so was able to do this, but it means you don't have to remove your SSDs - just disable them in your BIOS if you have one like Asus that lets you do this. Now, I suppose the next thing to test is which SSD is causing the firmware error. Is it my hackintosh drive or a different one (I have 4 SSDs in my system)?
  9. pbryanw

    [pre-release] macOS High Sierra

    @WarDoc - If it's any consolation I've been stuck on the same error for the past day or two. I've tried using Clover r4176 with and without FF & FFM, but haven't found the right combination yet. I'm using MacPro6,1 Smbios - will try iMac17,1. I notice as well that others get stuck on verifying firmware, while we got stuck on updating firmware - not sure it if has the same root cause?
  10. pbryanw

    EFI Variable Store on Aptio V (Haswell-E and up)

    Same with Asus VIII Ranger BIOS 3007 - not saving to NVRAM - have reverted back to BIOS 2202 for the time being.
  11. pbryanw

    Clover General discussion

    Hi, I just updated my Asus VIII Ranger motherboard to the latest 3007 BIOS and, after installation, noticed that my NVRAM settings weren't being saved across boot sessions (I don't use EmuVariableUefi-64). So, I inserted a test value in my NVRAM, rebooted, and saw that it wasn't carried across to the next boot. Also running NVRAM -p in terminal only brought up basic information. After rolling back to BIOS 2202, my NVRAM immediately started working properly again. I'm just wondering if this problem is unique to this BIOS version, or whether there have been similar problems with new BIOS updates for ASUS Z170 motherboards? The new bios was released on the 16th December 2016.
  12. pbryanw

    Clover General discussion

    Hi, I've just noticed the new Skylake setting in Clover 3879, and tried setting HWPEnable to true in my config.plist. . I'm using an Intel i5-6600 CPU with an ASUS Z170 motherboard - before my processor would only down-clock to 1.0GHz, and turbo to 3.7GHz with the MacPro6,1 SMBIOS. After enabling HWPEnable, it goes down to 800MHz, and reaches the maximum turbo of 3.9GHz, with the same SMBIOS. I'm just wondering if HWPEnable is working as intended, and how it's doing this?
  13. pbryanw

    Clover General discussion

    @arsradu - I'm also using a Dell U2515H monitor. In my case with an Asus Z170 motherboard, and running OS X using Clover. Have you checked to see if you have any kind of fastboot enabled in BIOS? Also, in my config.plist I changed the ScreenResolution setting to the U2515's native 2560x1440 and Clover seems to run at native resolution: https://clover-wiki.zetam.org/Configuration/GUI#gui_screenresolution Like you I'm using a HDMI input.
  14. pbryanw

    Clover General discussion

    Hi, I've just downloaded Clover r3270 from http://sourceforge.net/projects/cloverefiboot/ However, Avast for Mac flags the download as having 19 suspected infections of type Win32:Evo-gen[susp] Can I safely ignore these warnings and put it down to false positives?
  15. pbryanw

    clover disables keyboard

    I've also deleted GenericUSBXHCI.kext and used XhciDxe-64 instead. You can use XhciDxe-64 on a UEFI boot by unticking "Install for UEFI Booting only" in Clover setup. Your UEFI boot will still continue to function fine. Also, a side effect of using XhciDXE-64.efi is that the long pause after shutdown I've experienced with Yosemite, has been fixed. EDIT: And sleep works perfectly now.
×