Pavo Posted August 12, 2016 Share Posted August 12, 2016 Here is all my clover, i only deleted the sn-bsn-smuuid this is my situation : 1 ssd with el capitan + sierra Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this: You should remove the following and test: CsmVideoDxe-64.efi EmuVariableUefi-64.efi DataHubDxe-64.efi OsxAptioFix2Drv-64.efi VBoxHfs-64.efi Link to comment Share on other sites More sharing options...
Doublepranks Posted August 13, 2016 Share Posted August 13, 2016 Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this: You should remove the following and test: CsmVideoDxe-64.efi EmuVariableUefi-64.efi DataHubDxe-64.efi OsxAptioFix2Drv-64.efi VBoxHfs-64.efi He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader. Link to comment Share on other sites More sharing options...
UltraLaser Posted August 13, 2016 Share Posted August 13, 2016 Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this: You should remove the following and test: CsmVideoDxe-64.efi EmuVariableUefi-64.efi DataHubDxe-64.efi OsxAptioFix2Drv-64.efi VBoxHfs-64.efi He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader. @Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with : - VBoxHfs-64.efi - PartitionDxe-64.efi - OsxFatBinaryDrv-64.efi - OsxAptioFixDrv-64.efi - FSInject-64.efi But still remaining the nvram prob. I think isn't a clover problem... @Doublepranks i run an Asus Z97i (Mini Itx) Link to comment Share on other sites More sharing options...
Gurqn Posted August 13, 2016 Share Posted August 13, 2016 He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader. What's that ? Im using "OsxAptioFixDrv-64.efi" not "2" and it's pretty much not breaking anything (MSI-Z97). Link to comment Share on other sites More sharing options...
Squidderlee Posted August 13, 2016 Share Posted August 13, 2016 Same here I'm afraid GTX 750 Ti PB4 broken... defaults to OSX driver on reboot!+ Link to comment Share on other sites More sharing options...
Doublepranks Posted August 13, 2016 Share Posted August 13, 2016 What's that ? Im using "OsxAptioFixDrv-64.efi" not "2" and it's pretty much not breaking anything (MSI-Z97). You can either use one or the other just the matter you have at least one of them. V2 is a simplified version of the first one. It has to do with Aptio Bioses support for Clover, be my guest try and remove this, you'll be stuck at boot. Link to comment Share on other sites More sharing options...
cgaddict Posted August 13, 2016 Share Posted August 13, 2016 Last Version of the WebDriver 367.10.10.05b01 --> build 16A286a (ver2) for Developer 5 makes trouble with METAL (GMxxx Maxwell chipsets) You need to disable Transparecy under "accessibility" "reduce transparency" If any body knows new Drivers with CUDA support please tell ... 3 Link to comment Share on other sites More sharing options...
drowsyhaze Posted August 13, 2016 Share Posted August 13, 2016 @Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with : - VBoxHfs-64.efi - PartitionDxe-64.efi - OsxFatBinaryDrv-64.efi - OsxAptioFixDrv-64.efi - FSInject-64.efi But still remaining the nvram prob. I think isn't a clover problem... @Doublepranks i run an Asus Z97i (Mini Itx) Try disabling EmuVariableUEFI - don't think you need it with most EFI boards... Link to comment Share on other sites More sharing options...
Pavo Posted August 13, 2016 Share Posted August 13, 2016 @Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with : - VBoxHfs-64.efi - PartitionDxe-64.efi - OsxFatBinaryDrv-64.efi - OsxAptioFixDrv-64.efi - FSInject-64.efi But still remaining the nvram prob. I think isn't a clover problem... @Doublepranks i run an Asus Z97i (Mini Itx) Try using PartitionDxe-64.efi instead of DataHubDxe-64.efi Link to comment Share on other sites More sharing options...
sl0wtarget Posted August 14, 2016 Share Posted August 14, 2016 That's weird... I am using driver 367.10.10.05b01 (the latest, and the same driver released for PB3) on PB4 (16A286a) with no issue... I wonder why you guys are having issues and are seeing new drivers... Public Beta build (mine) is 16A284a, I think 16A286a is the Developer Preview build. Using the "DP4 & PB3" drivers work for me, the "DP5 & PB4" driver doesn't. Link to comment Share on other sites More sharing options...
drowsyhaze Posted August 15, 2016 Share Posted August 15, 2016 How curious! I'm definitely running a public beta, 16A286a, but it wouldn't be too surprising if Apple released different revisions (maybe different revisions for different SMBIOS?). I just downloaded both versions of the driver from the front page, unpacked them and: claes2:~ claes$ diff -r /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a claes2:~ claes$ diff /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a Common subdirectories: /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f/1.5-81-367.10.10.05b01-NVWebDrivers and /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a/1.5-81-367.10.10.05b01-NVWebDrivers Common subdirectories: /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f/NVPrefPane and /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a/NVPrefPane claes2:~ claes$ diff -qr /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a claes2:~ claes$ The difference, if one exists (diff says there is none), between the driver revisions shouldn't matter as they're both prepared for "16A" in general according to NVDAStartupWeb.kext (both have same GetInfoString and ShortVersion, too): <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>BuildMachineOSBuild</key> <string>11A511</string> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>NVDAStartupWeb</string> <key>CFBundleGetInfoString</key> <string>NVDAStartupWeb 10.13.59 (367.10.10.05b01)</string> <key>CFBundleIdentifier</key> <string>com.nvidia.NVDAStartupWeb</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>NVDAStartupWeb</string> <key>CFBundlePackageType</key> <string>KEXT</string> <key>CFBundleShortVersionString</key> <string>10.13.59</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>10.1.3</string> <key>IOKitPersonalities</key> <dict> <key>NVDAStartup</key> <dict> <key>CFBundleIdentifier</key> <string>com.nvidia.NVDAStartupWeb</string> <key>IOClass</key> <string>NVDAStartupWeb</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOPCIClassMatch</key> <string>0x03000000&0xff000000</string> <key>IOPCIMatch</key> <string>0x000010de&0x0000ffff</string> <key>IOProbeScore</key> <integer>200000</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>NVDARequiredOS</key> <string>16A</string> <key>NVDAType</key> <string>Web</string> </dict> </dict> <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOPCIFamily</key> <string>1.0b1</string> <key>com.apple.kpi.iokit</key> <string>7.0</string> <key>com.apple.kpi.libkern</key> <string>8.0d0</string> </dict> <key>OSBundleRequired</key> <string>Safe Boot</string> </dict> </plist> Wonder what could've broke for so many of you between the two revisions... Link to comment Share on other sites More sharing options...
Squidderlee Posted August 15, 2016 Share Posted August 15, 2016 How curious! I'm definitely running a public beta, BOTH 16A284a and 16A284a are BETAS! To Be CLEAR: 160284A is Public Beta 4 160286A is Developer Preview 5. For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers Link to comment Share on other sites More sharing options...
UltraLaser Posted August 15, 2016 Share Posted August 15, 2016 BOTH 16A284a and 16A284a are BETAS! To Be CLEAR: 160284A is Public Beta 4 160286A is Developer Preview 5. For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers I'm not a developer, I'm running a public beta : Beta 10.12 (16A286a) 1 Link to comment Share on other sites More sharing options...
Doublepranks Posted August 15, 2016 Share Posted August 15, 2016 I'm not a developer, I'm running a public beta : Beta 10.12 (16A286a) Are you running into any glitch aside from the ones you've sorted out? Link to comment Share on other sites More sharing options...
levifig Posted August 15, 2016 Share Posted August 15, 2016 Interesting thing: my secondary monitor got screwed up colors after the 10.12 update. Worked fine in 10.11, works fine in W10… Tried a different cable, different port from the graphics card… Other monitor works just fine (in both ports and with both cables). Weeeeirdest thing. Basically, blues are yellows, yellows are blues, and reds are blues too… It's like my red channel got screwed up! :X SOO WEIRD! I tried checking the accessibility option to invert colors, but it's not it: whites and blacks are not inverted. I also tried switching to a different color profile… No help! Any idea? Anybody running into similar issues? PS: When booting with nv_disable=1 (aka no Nvidia driver), colors are perfectly fine! ¯\_(ツ)_/¯ Link to comment Share on other sites More sharing options...
drowsyhaze Posted August 15, 2016 Share Posted August 15, 2016 BOTH 16A284a and 16A284a are BETAS! To Be CLEAR: 160284A is Public Beta 4 160286A is Developer Preview 5. For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers Source? As you can see from my screenshot, Mac App Store says I've downloaded the public beta. I am aware of there being a difference between the developer and public betas, but my post was more concerned with the fact that some PB4 users are having issues with PB4/DP5* drivers that they weren't having with PB3, while it appears that the drivers are identical between PB3/DP4 and PB4/DP5 (well, at least the drivers linked to by the OP). It would not seem related to the OS as these cards didn't work without the drivers in any case, which makes me curious as to where these issues are occurring (in non-NVRAM cases where a user's card was working in PB3/DP4, at least). *I am also aware that these are likely different revisions, just want to connote that the nvidia driver release is the same for both the developer and public betas that were released together. Link to comment Share on other sites More sharing options...
ergot Posted August 16, 2016 Share Posted August 16, 2016 BOTH 16A284a and 16A284a are BETAS! To Be CLEAR: 160284A is Public Beta 4 160286A is Developer Preview 5. For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers I am with 750ti and the default is always web drivers, i had problem with glitches and it was fixed by enabling reduce transparency under system pref->accessibility I can watch youtube / MKV etc. but not working with editing SW like resolve and others that using CUDA because CUDA still not working in 10.12 Link to comment Share on other sites More sharing options...
fantomas Posted August 16, 2016 Author Share Posted August 16, 2016 Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 6 and Public Beta 5 (16A294a) Check the first page, #1. Regards 3 Link to comment Share on other sites More sharing options...
d5aqoep Posted August 16, 2016 Share Posted August 16, 2016 Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 6 and Public Beta 5 (16A294a) Check the first page, #1. Regards Any luck with Pascal support? Link to comment Share on other sites More sharing options...
cydia2020 Posted August 16, 2016 Share Posted August 16, 2016 Any luck with Pascal support? Don't think so Link to comment Share on other sites More sharing options...
sl0wtarget Posted August 16, 2016 Share Posted August 16, 2016 Alright, downloaded and installed latest pkg just fine while still on 16A284a build (PB4 with "PB3 drivers") then downloaded and installed PB5, all appears peachy. Off topic; this OS phones home a LOT! Link to comment Share on other sites More sharing options...
Gurqn Posted August 16, 2016 Share Posted August 16, 2016 Any luck with Pascal support? It's not a new version that released from nvidia, so basically no. Mods should clearly express that they are patching same version in order to making current driver compatible with new os builds. It can prevent misleadings. Link to comment Share on other sites More sharing options...
Riley Freeman Posted August 16, 2016 Share Posted August 16, 2016 They're not patching the same version. It is the same version. I downloaded the "latest" driver from the link in the first post a little earlier and compared it to the one I downloaded two weeks ago. It's the exact same pkg file. The hashes match. 3 Link to comment Share on other sites More sharing options...
sl0wtarget Posted August 16, 2016 Share Posted August 16, 2016 They're not patching the same version. It is the same version. I downloaded the "latest" driver from the link in the first post a little earlier and compared it to the one I downloaded two weeks ago. It's the exact same pkg file. The hashes match. I didn't even think of doing that! Thanks. Link to comment Share on other sites More sharing options...
drowsyhaze Posted August 16, 2016 Share Posted August 16, 2016 They're not patching the same version. It is the same version. I downloaded the "latest" driver from the link in the first post a little earlier and compared it to the one I downloaded two weeks ago. It's the exact same pkg file. The hashes match. Which begs the question why so many PB3 users are having troubles with PB4... 1 Link to comment Share on other sites More sharing options...
Recommended Posts