Jump to content
5539 posts in this topic

Recommended Posts

Here's the results of BasemarkGPU: https://powerboard.basemark.com/benchmark-result/717335. Results basically mirror what's already there: https://powerboard.basemark.com/top/gpu-families/basemark-gpu-1.2-high/computers/macos/default-environment/median/10/1 so not much of an improvement in beta 4.

 

The results of Heaven (ran for 15mins). Intensive scenes hit ~50 fps. Avg ~60 fps. Settings used:

2057746022_ScreenShot2020-03-05at11_16_38AM.thumb.png.d32a4b9f56936bf2892dfc362ec0addf.png

Edited by Tiem
5 minutes ago, eSaF said:

@ pkdesign - I have the same wifi version board with BIOS F12C, my query is did you use AudioGod's CFG Unlock method bearing in mind his is for BIOS F12d. The reason I am asking I tried OC sometime back with Glasgood's guide and I was able to boot and run Ok but the GUI was not appealing to me coming from Chameleon and then Clover so I knida not followed it up but seeing NDK'S effort, I am intrigued again and ran the Latest one on a test usb AudioGod posted, it booted ok but stopped at the Apple Logo with no progress bar and no back light on my k/board or mouse. Mind you, I don't know if I should have cleared the NvRam before rebooting and I haven't use the UnlockCFG steps so don't know if that has anything to do with it. I decided to ask you since our man AudioGod is run off his feet with other queries :).

Added -v to your boot arguments and try again. My money is that OC is halting on something it can't find (simple config problem).

 

Also, it's not possible to unlock your board if you have the WIFI variant using the attached firmware (it's for the Pro). You need to use the modified grub boot loader and unlock using setup_var_3. It's not ideal as it resets every time you flash your BIOS or clear your CMOS. But it's the way to go if you have F12C.

Edited by Tiem
13 minutes ago, eSaF said:

@ Tiem - now why didn't I think of that? :hysterical: - thanks will try.

Make sure to save your profile right after you disable MSR lock and then you’ll just have to load that very profile when you clear CMOS or for whatever reason load the defaults ;)

  • Like 1
2 hours ago, eSaF said:

@ pkdesign - I have the same wifi version board with BIOS F12C, my query is did you use AudioGod's CFG Unlock method bearing in mind his is for BIOS F12d. The reason I am asking I tried OC sometime back with Glasgood's guide and I was able to boot and run Ok but the GUI was not appealing to me coming from Chameleon and then Clover so I knida not followed it up but seeing NDK'S effort, I am intrigued again and ran the Latest one on a test usb AudioGod posted, it booted ok but stopped at the Apple Logo with no progress bar and no back light on my k/board or mouse. Mind you, I don't know if I should have cleared the NvRam before rebooting and I haven't use the UnlockCFG steps so don't know if that has anything to do with it. I decided to ask you since our man AudioGod is run off his feet with other queries :).

I did. The only difference was I used @Tiem advice and used the setup_var_3 to unlock. He posted a URL some posts back.

 

I boot with Clover (same reason, I really like the GUI.) Booted with OC using a USB drive once or twice. Also no problem.

 

I have no issues whatsoever on my computer. Been running rock solid for months.

 

And absolutely take @WizeMan advice and create a backup of your BIOS settings. We monkey around with our boards so much it makes it SO easy to get back to it.

Edited by pkdesign
  • Like 1

I can assure you guys that if you think the CFG unlock may fix something or may be the cause of a problem it likely won’t be that. This EFI has native nvram so there’s no real reason if it’s a pain. I would flash my board with a bios update as that’s easy and permanent. But even then, it won’t give you anything you don’t already have.

I have a question and need a little help.  I have successfully loaded Opencore from the front page EFI provided (thank you! :)) and have been trying it out, vs the Clover EFI but I have an issue with my Broadcom BCM94360CD wifi/bluetooth pci adapter.  When waking from sleep, my build loses bluetooth, also the wifi connectivity seems very slow.  I see Bluetooth in the Finder Bar although just showing Bluetooth icon greyed out and clicking on it shows (Bluetooth:Not Available).  Should I find a kext for the card or should this Apple adapter work "out of the box" with Catalina?  I seem to remember on a previous EFI having AirportBrcmFixup.kext for this card, could I just incorporate this again or is it necessary? Thanks!

Edited by Hifi33
clarified some wording
53 minutes ago, Hifi33 said:

I have a question and need a little help.  I have successfully loaded Opencore from the front page EFI provided (thank you! :)) and have been trying it out, vs the Clover EFI but I have an issue with my Broadcom BCM94360CD wifi/bluetooth pci adapter.  When waking from sleep, my build loses bluetooth, also the wifi connectivity seems very slow.  I see Bluetooth in the Finder Bar although just showing Bluetooth icon greyed out and clicking on it shows (Bluetooth:Not Available).  Should I find a kext for the card or should this Apple adapter work "out of the box" with Catalina?  I seem to remember on a previous EFI having AirportBrcmFixup.kext for this card, could I just incorporate this again or is it necessary? Thanks!


Hi, :) 
There’s a little bit of a misconception when it comes to the meaning of Out the box working.

it means if you plug it in it will work and this much is true but it doesn’t mean you won’t need additional bits to make it run perfectly and what works for one person might not work for the other so With that in mind If you were using airportfixup previously and it was working correctly for you then add it back in to the oc EFI and see if it corrects your problem.

i hope that helps.

2 hours ago, AudioGod said:


Hi, :) 
There’s a little bit of a misconception when it comes to the meaning of Out the box working.

it means if you plug it in it will work and this much is true but it doesn’t mean you won’t need additional bits to make it run perfectly and what works for one person might not work for the other so With that in mind If you were using airportfixup previously and it was working correctly for you then add it back in to the oc EFI and see if it corrects your problem.

i hope that helps.

Thanks, that's very true about the Out of the Box solution. ha  I think I solved it without editing my EFI folder.  The system was set to "Wake for Network Access" in the Energy Saver of System Preferences.  I have disabled that and now, upon waking my build, there isn't an issue.  Not sure why that works but so far, so good!

  • Like 1
On 3/5/2020 at 6:25 PM, pkdesign said:

Could you elaborate on changes made to DSDT? I'm on Wifi version at 12c. Your EFI works great with my current setup.

Hey, I also have this WiFI-board and CPU like you! but audiogods files didn't work fore some reason. Could you please share your EFI Folder and Bios ? I would be very appreciative !

6 hours ago, Blesh said:

Hey, I also have this WiFI-board and CPU like you! but audiogods files didn't work fore some reason. Could you please share your EFI Folder and Bios ? I would be very appreciative !

When you have been trying to get things to work you make so many changes that usually there is some configuration that is off and which leads to trouble when you say try to use an EFI from anyone.

 

I suggest to take the battery from your motherboard for 2 minutes.  Then your bios and hardware will be at their defaults.  Now make your changes to Bios and the placing of the new EFI files.  Then test.

 

 

regards

 

 

  • Like 1
On 8/21/2019 at 4:58 PM, AudioGod said:

 

If you prefer using SMBios 1,1 then by all means switch to it but all the old problems of using 19,1 are corrected now with this EFI plus DRM is fully working unless you have a Polaris gpu. Just to add, SMBios 19,1 is the correct one to be using for our chipset and cpu, if you check the spec of a real macpro it is not a using a CoffeeLake CPU or Z3xx chipset. It does work perfectly but correct is correct so 19,1 it is.

 

Please Note, If you use a 5700 or 5700XT then SMBios 1,1 in unstable using the Navi GPUs so please stick to 19,1 with igpu enabled.

 

Yes sir, I am using a 5700XT and SMB 1,1, I really want to change it to 19,1, but I cannot get the igpu enabled bcz CPU is 9600kf.. so sad

 

BTW, My MB is z390 aorus pro WIFI with BIOS F12C (latest version for my MB) and cfg unlocked, your clover EFI(updated 05/03/2020 and last one, both for your F12D BIOS)  just works fine. everything I tried got no problems. thanks for your work..

14 minutes ago, eSaF said:

Maybe my query is more suited to the OpenCore forum but since this one is based mainly on the Z390 platform I will ask here and hope someone can offer a semblance of an answer - Why the Difference in 'Energy Saver' same specs just different boot loaders. At the moment I am just playing around with OpenCore and as a lay person - not that impressed, hopefully I will become more informed and educated as time goes on.

 

 

 

Very weird. I have been messing around with OpenCore (both the "original" one and n-d-k) and I have never observed such a difference. 

1 hour ago, eSaF said:

Maybe my query is more suited to the OpenCore forum but since this one is based mainly on the Z390 platform I will ask here and hope someone can offer a semblance of an answer - Why the Difference in 'Energy Saver' same specs just different boot loaders. At the moment I am just playing around with OpenCore and as a lay person - not that impressed, hopefully I will become more informed and educated as time goes on.

Screenshot 2020-03-09 at 07.44.36.png

Screenshot 2020-03-09 at 07.54.57.png

Looks different from what i get when booted from OC ...  Mine is more inline with your Clover one .. 

 

 

oc-energy-saver.png

  • Like 1
33 minutes ago, eSaF said:

 

Yea I can see that but that revelation don't help much now does it :hysterical: To be quite honest I am gonna have to stop being so lazy and compile the damm thing my self.


Check your inbox G ;)

 

On 3/5/2020 at 1:35 PM, Tiem said:

So couple of things I've noticed on beta 4.

 

iMac19,1 there is video corruption saving a file in QuickTime. Not there on iMacPro1,1. Can't say if it's a new bug or not. Maybe someone on 19,1 can test this. https://file-examples.com/index.php/sample-video-files/sample-mov-files-download/ Download the 2.2 MB file. Open it in QT and then select save as and save it as a 720p. Play it back. You should see lots of corruption.

 

On 10.15.3 I see stuttering and artifacts when exporting at 720p in QT. Same file exports fine on MBP. Compressor on Hackintosh works fine, just QT is borked.

  • Thanks 1

It seems that with every Catalina revision smbios 19,1 is becoming more and more of a pain to use. smbios iMacpro1,1 is always there as a second option and works just fine but if your a Navi User then be careful as heavy prolonged GPU usage can cause the system to freeze. 

Edited by AudioGod
19 hours ago, saCULar said:

When you have been trying to get things to work you make so many changes that usually there is some configuration that is off and which leads to trouble when you say try to use an EFI from anyone.

 

I suggest to take the battery from your motherboard for 2 minutes.  Then your bios and hardware will be at their defaults.  Now make your changes to Bios and the placing of the new EFI files.  Then test.

 

 

regards

 

 

As you said, I removed the battery from my motherboard for 2 minutes and it works! THANK YOU!

 

But now after installing macOS successful I put the EFI Folder from the usb stick to the EFI Partition of my computer and after a reboot a forbidden symbol appears. What happened? Straubing macOS install from USB works but not booting from intern SSD.

1 hour ago, Neek said:

 

On 10.15.3 I see stuttering and artifacts when exporting at 720p in QT. Same file exports fine on MBP. Compressor on Hackintosh works fine, just QT is borked.

 

Update: If I remove "shikigva=80" then the QT export does not having stuttering or artifacts. Blame WEG DRM patches?!? :hysterical:

  • Like 1
  • Thanks 1
7 minutes ago, Neek said:

 

Update: If I remove "shikigva=80" then the QT export does not having stuttering or artifacts. Blame WEG DRM patches?!? :hysterical:

 

Was about to report the same thing.  I removed shiki, pikera and also did agdpmod=ignore.

  • Like 1
29 minutes ago, hungrywallet said:

 

Was about to report the same thing.  I removed shiki, pikera and also did agdpmod=ignore.

Does agdpmod=ignore stop the black screen still?

Just now, AudioGod said:

Does agdpmod=ignore stop the black screen still?

 

I'm sorry, which black screen?  If you mean at login then I didn't have the issue.  Also, I've just booted with whatevergreen completely removed and see no issues except for the DRM gate ones that shiki fixes.  Actually I see things I didn't see before with it removed.  For instance HWMonitor now shows more GPU info, and I don't recall being able to choose between GPU's in Geekbench or API's but perhaps I never looked hard enough.

Screen Shot 2020-03-09 at 4.20.35 PM.png

Screen Shot 2020-03-09 at 4.39.13 PM.png

Screen Shot 2020-03-09 at 4.39.34 PM.png

Screen Shot 2020-03-09 at 4.38.07 PM.png

×
×
  • Create New...