And I literally just installed my FirePro V4900 to Update to Sierra shiit xD
Well I'm glad they released it, and so quickly too maybe they just wanted to focus completely on the Sierra 10.13.0 Driver instead of making 9+ Beta Releases which would have made no sense at all
Here's my Score TDP Unlocked GTX 970, sadly not boosting completely to it's max. And my 4.8 GHz 1-Core 4.7 GHz 2 Core and 4.6 GHz 3 and 4 Core I adjusted Turbo boost so on and so on all well stored in a PowerMac G5 Case Yay :3
P.S. I have no special kexts in /S/L/E or /L/E in Library Extensions I only have the Generic Sata --> 9 Series AHCI Controller path from Multibeast Side Note: Multibeast isn't working for me I just installed The Packages under Multibeast 9.2/Contents/Resoruces...
Thankss :3
I remember now the TyMCEDriver Patch didn't work so I deleted the kext.
It didn't work with any Patch out there tried yours tried the one from tonymacx86 some from other forums
I remembered it because I redid the installation over my existing Macintosh HD to restore my AppleHDA and some other...
I also tried just creating a vanilla 10.12.6 installer disk partition on my SSD and booting directly from Clover on the SSD to that partition but it always panics on TyMCEDriver and therefore reboots I just don't know what the problem could be my config.plist has 0 errors (checked it with...
I don't care about the Recovery HD Partition anymore I now know that I can't access it while using FileVault and that's Okay but it still isn't explaining why I can't boot off of any Installer USB while having a Mac Pro 5,1 SMBIOS (TyMCEDriver again) I have the patch and everything is unchanged...
Thank you really much for explaining you actually were really helpful! <3
But it doesn't solve the problem that I can't boot any Installer disk from Clover while using MacPro5,1 would this be off Topic ? Kinda not I think because the TyMCEDriver ist still the problem I even tried taking out all...
Yes it's showing up but it's only a boot record for Legacy Boot Mode a UEFI disk only shows up when the UEFIBOOT.efi can be read thats why you can see a CD ROM as a boot device without any Disk in it but only when let's say a Windows 8.x+ DVD is inserted it will show up a | UEFI: DVD Drive...
I sometimes can only try the options above to get some bugged out USB Devices to work (It's only a problem on UEFI USB's) it will only show up on Peripherals but not able to boot in my case your solution wouldn't work so I told to do the above
But it's fair to say that he could have disabled...
I usually just use my NVRAM to store the Nvidia driver information for booting it works best and what's really good about it it disables the NVIDIA driver when there was a kernel panic which is extremely helpful
Sooo.
The Gigabyte Bios has a nice bug in which it sometimes bugs out on USB Sticks with UEFI boot :
Try powering your Hack off and insert your USB in different places USB 2.0 USB 3.0 other neighboring USB ports, just try it.
You can also try to get a similarly equipped USB (also a Unibeast...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.