Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

gandem said:
...
@CaseySJ In your testing did you use the F12 boot menu.

It is clearly causing problems for me and it appears that you need a fresh BIOS, reloading settings does not work.
Click to expand...
Because I ran all my AptioMemoryFix tests from a USB flash disk, I was using F12 each time. I can certainly rerun a subset of the tests by booting directly from an internal macOS disk. (Added to my To Do list.)
 
Last edited:
PicLock said:
@CaseySJ
My Asus X99 Deluxe II is working great with your great EFI sharing. However I just realise that thunderbolt isn't working. I'm using the AsusThunderbolt 3 card that came with the MB. It used to work before with the KGP build guide though not hot-pluggable. Previously, I have WINDOW installed to 'activate' the thunderbolt card and installed the driver etc. The thunderbolt .

Apologies,. I checked my notes again, the Thunderbolt was actually working fine with your file. S,o it was working and suddenly stop working now.

I'm not sure whether the card has died because, when I first plugged in a Thunderbolt drive, it couldn't mount the drive but it did power up the drive. After a few more tries, the drive didn't power up anymore. I tried with other Thunderbolt device and with the same result.

I have also try to reseat the Thunderbolt card in other PCI slot to no avail. When I boot into WINDOWS, I can't find any Thunderbolt device, too. In the BIOS I can see the Thunderbolt settings. I'm thinking of buying another Thunderbolt card to try, but just want to make sure that I have taken all the necessary troubleshooting steps.

May I know which Thunderbolt card are you using?
Click to expand...
I am using the Asus ThunderboltEX 3 and Asus ThunderboltEX 2 (one at a time, of course). Some suggestions:
  • Power down the system fully (including flipping power switch on PSU).
  • Remove and reconnect THB_C header cable from both motherboard and Thunderbolt card.
  • Power up the system.
  • Boot into Windows.
  • Can you connect Thunderbolt devices?
I would be surprised if the card actually failed, but it can happen.
 
kwalter said:
I just booted my system with AptioMemoryFix to see if it would work - using Catalina and f8 bios
Intel CNVi (WiFi) enabled
CSM disabled
Slide=0
Bluetooth card (similar but not the same as Fenvi) installed
Internal Graphics - enabled

So far all seems to work OK - I have Sidecar working, VDA Decoder Fully supported, Messages, iCloud

Fingers crossed
Click to expand...
This means you have iMac19,1 (because Sidecar is working). I will try this SMBIOS later tonight.
 
svandive said:
Unfortunately I don't think folks will be too active in remembering to update the signature to the correct OS level every time they upgrade. I could be wrong but I believe it could result in making false diagnoses based on out of date information.
Click to expand...

I figured that would be the case. Guess we'll just have to keep replying with what we're running. Just today another person asked if I was having the same issues and he is running Cat and I'm running Mojave.
 
djx8605 said:
Well Done on the testing! :)

So what you are finding is that booting via f12 and booting Windows first will bot cause macOS to fail?
Click to expand...

Yes. I think I'm going to give OsxAptioFix3Drv.efi another look to see if it makes a difference with CSM, Boot Menu or booting into Windows via Clover and then hitting the allocation error going back to Mac OS. The thing is AptioMemoryFix.efi has been rock solid, the only potential issue is hitting the allocation error on boot, and I have not hit it outside the above circumstances.
 
gandem said:
Yes. I think I'm going to give OsxAptioFix3Drv.efi another look to see if it makes a difference with CSM, Boot Menu or booting into Windows via Clover and then hitting the allocation error going back to Mac OS. The thing is AptioMemoryFix.efi has been rock solid, the only potential issue is hitting the allocation error on boot, and I have not hit it outside the above circumstances.
Click to expand...

Hmmm... Wonder what could be triggering such behavior...

Did you ever try booting using f12 to boot when Windows wasn't installed? By that I mean that Windows bootloader wasn't even in the boot menu...

Wonder if it's a Windows thing or a UEFI firmware thing :)

If you unplug the Windows drive and remove Windows bootloader entry from NVRAM, does F12 still crap the macOS boot? If you need to know how to remove NVRAM boot options, just say the word :)
 
All who are involved with testing different memory fix drivers and such, have you guys messed with above 4g decoding? I just realized that setting is enabled in my UEFI firmware (I can't remember why I enabled it, but it is enabled, I know by default it is disabled). Another thing I just realized about my UEFI config, I disabled the second ethernet adapter (the i211), mainly because I'm not use it at this location, the i219 is good enough for what I need...

I'm only mentioning these because they may perhaps play a role in getting all this working? Perhaps disabling certain features may allow more memory to be freed for the macOS kernel space, resulting in successful boots each time.

I just now tested booting using f12 menu, booting directly into Windows (7 and 10), macOS still working. IGPU has been enabled, CSM was disabled (will try later with it enabled), no WIFI card installed, still on F7 BIOS (will update to F8 some time later today). But as mentioned above, above 4g is enabled, and the second ethernet adapter disabled. Maybe we all have to find some sort of tradeoffs in enabling/disabling certain things to make enough room for kernel space? I mainly got this board because it was at a good price, less than what I would pay for a Z390 Aorus Pro and a separate TB3 card lol.
 
Last edited:
djx8605 said:
Hmmm... Wonder what could be triggering such behavior...

Did you ever try booting using f12 to boot when Windows wasn't installed? By that I mean that Windows bootloader wasn't even in the boot menu...

Wonder if it's a Windows thing or a UEFI firmware thing :)

If you unplug the Windows drive and remove Windows bootloader entry from NVRAM, does F12 still crap the macOS boot? If you need to know how to remove NVRAM boot options, just say the word :)
Click to expand...

I believe I tested that last night, as the last thing I did was just test F12, and I believe I had pulled the Windows drive. Will confirm that when I'm testing this evening. Might as well let me know how to remove NVRAM boot options so I can make sure there is nothing left referencing Windows.:)
 
djx8605 said:
@ALL who are involved with testing different memory fix drivers and such, have you guys messed with above 4g decoding at all? I just realized that setting is enabled in my UEFI firmware (I can't remember why I enabled it, but it is enabled, I know by default it is disabled). Another thing I just realized about my UEFI config, I disabled the second ethernet adapter (the i211), mainly because I'm not use it at this location, the i219 is good enough for what I need...

I'm only mentioning these because they may perhaps play a role in getting all this working? Perhaps disabling certain features may allow more memory to be freed for the macOS kernel space, resulting in successful boots each time.

I just now tested booting using f12 menu, booting directly into Windows (7 and 10), macOS still working. IGPU has been enabled, CSM was disabled (will try later with it enabled), no WIFI card installed, still on F7 BIOS (will update to F8 some time later today). But as mentioned above, above 4g is enabled, and the second ethernet adapter disabled. Maybe we all have to find some sort of tradeoffs in enabling/disabling certain things to make enough room for kernel space? I mainly got this board because it was at a good price, less than what I would pay for a Z390 Aorus Pro and a separate TB3 card lol.
Click to expand...
i don't think:

ALL

www.tonymacx86.com www.tonymacx86.com

has the same hardware as you
 
CaseySJ said:
​



The experiment has concluded and the results are in:

All experiments conducted with this configuration:
  • BIOS version F8
  • SMBIOS: Mac mini 8,1
  • Catalina 10.15 with both Supplemental Updates
  • MSI RX 580 Gaming X in PCIe slot 1
  • Fenvi FV-T919 WiFi/BT in bottom short x1 slot
  • PCIe NVMe in M2M slot
  • PCIe NVMe in M2P slot
Purpose of Experiment:
  • To determine the conditions under which AptioMemoryFix works.
Observations:
iGPU Intel CNVi CSM Support Fenvi WiFi/BT slide=0 Result
Enabled Enabled Enabled Installed checked FAIL
Enabled Enabled Enabled Installed unchecked FAIL
Enabled Enabled Disabled Installed checked FAIL
Enabled Enabled Disabled Installed unchecked FAIL
Enabled Disabled Disabled Installed checked FAIL
Enabled Disabled Disabled Installed unchecked FAIL
Enabled Disabled Disabled Removed checked FAIL
Enabled Disabled Disabled Removed unchecked FAIL
Disabled Disabled Disabled Removed checked SUCCESS
Disabled Disabled Disabled Removed unchecked FAIL
Disabled Enabled Enabled Installed checked SUCCESS


Conclusion:
  • AptioMemoryFix works with my system configuration only by (a) disabling IGPU and (b) setting slide=0.
Click to expand...

That seemed to be the results of my testing as well, except I never tried removing my Wi-Fi card, which is not a Fenvi but a PCI adapter for a native broadcom module. If iGPU is off, slide=0 is mandatory but it always boots with AptioMemoryFix.

I recently added an Aquantia 10G Gaming NIC which caused no issue. I noticed that disabling Audio and Onboard LAN had no effect on my memmap size in the relevant area. I never bothered turning CSM on, it's always been off.

What did change my memmap with iGPU enabled was lowering DVMT from 64MB to 32MB, and I got it to boot a few times and then it stopped booting.

Does disabling CNVI in the new BIOS remove the need for the CNVW SSDT? Does it disable the onboard bluetooth as well?
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top