- Apr 4, 2014
- Vega 64
- Mobile Phone
It is mainly Samsung NVMe drives. Samsung Sata SSDs are fine, no TRIM problems with macOS Monterey.Is it only Samsung, or other drives having problems as well?
Happy holidays! I've only now had a chance to go over these settings and have some questions:It's always advisable to manually verify config.plist settings. With OpenCore 0.7.4 we should verify the following:
P.S. Always have a bootable backup of macOS.
- ACPI --> Add --> SSDT-DMAR.aml --> Checked on
- ACPI --> Delete --> DMAR --> Checked on
- Kernel --> CustomSMBIOSGuid --> Enabled
- PlatformInfo --> UpdateSMBIOSMode --> Custom
- PlatformInfo --> DataHub --> AdviseFeatures --> Enabled
- BIOS --> VT-d --> Enabled
Items 3, 4, and 5 allow Windows to use the computer name specified within Windows itself. Otherwise OpenCore will generate a new name.Happy holidays! I've only now had a chance to go over these settings and have some questions:
This is for OC setup to boot into windows on a separate SSD that's internally attached to one of the SATA headers on the Z390.
- ACPI --> Add --> SSDT-DMAR.aml --> Checked on --> DONE.
- ACPI --> Delete --> DMAR --> Checked on --> DONE. Using this article.
- Kernel --> CustomSMBIOSGuid --> Enabled --> Disabled by default, just checked it on. What does this do?
- PlatformInfo --> UpdateSMBIOSMode --> Custom --> Set to "Create" by default. I just changed it to Custom. What does this do?
- PlatformInfo --> DataHub --> AdviseFeatures --> Enabled --> Disabled by default, just checked it on. What does this do?
- BIOS --> VT-d --> Enabled --> DONE. This was enabled during my transition from Clover to OC.
Any help/insight is much appreciated!
EDIT: I've successfully booted into windows after following all the steps using the BIOS boot manager (not the OC booter). Is there anything I should know about letting Windows update itself? Something to look out for?
Items 3, 4, and 5 allow Windows to use the computer name specified within Windows itself. Otherwise OpenCore will generate a new name.
Regarding booting Windows through OpenCore, please see the first section of either the OpenCore 0.7.5 or 0.7.6 mini-guide in this thread. It provides a link to a post that describes how to disable AppleVTD. That, in turn, solves this problem for most people.
I should add that I have Windows installed on all of my Intel-based Hackintosh systems and have not experienced this problem. It does not affect everyone.
Anyone update to the latest BIOS. Could you post your results with latest OC?
I second. Anyone had tested the new BIOS? Something I don’t like however:
« Introduce capsule BIOS support starting this version.
Customers will NOT be able to reverse to previous BIOS version due to major vulnerabilities concerns. »
Happy New Year everyone!@canyondust installed a similar capsule BIOS on his Z490 Vision G with no negative consequences for macOS. It's been several days now, and still running okay.
However, I have not seen anyone do this on Z390 Designare. Because I have two of these systems -- one of which is a test bench -- I am willing to try the capsule BIOS in about 2 weeks.
When you say « USB-C devices do not hot-plug on Thunderbolt ports », you mean they are working when you plug them once booted or missing completely like on f9j? If they work not hot-plugged, I think the behavior was the same with old working USB-C on TB3 Bios versions if I recall correctly…Happy New Year everyone!
As promised, I've installed BIOS F9 (capsule BIOS) on my Z390 Designare and found no issues so far. Some notes:
- Once this BIOS is installed, we cannot install any previous BIOS.
- Sleep, wake, restart, shutdown all work under macOS Monterey.
- USB-C devices do not hot-plug on Thunderbolt ports.
Hi Casey,While most folks have flashed the controller successfully, there have been a few accidents that have left the board permanently damaged. These accidents all had one thing in common:
- When attaching or detaching the 8-pin SOIC clip to the Winbond chip, a nearby surface mount device was accidentally dislodged.
- To avoid this problem, the following guidelines are absolutely and unequivocally critical:
- You must have excellent near-sightedness.
- If you wear corrective lenses to see distant objects, remove those lenses and use your natural near-sightedness.
- If you are far sighted and need corrective lenses to view nearby objects, determine whether you can see objects clearly when they are only 2 inches away from your eyes. If you cannot do this, please enlist the help of someone who can.
- When attaching and detaching the spring-loaded 8-pin SOIC clip to the Winbond chip, use very steady hands and gentle motions. Position the clip directly over the chip and move it up-and-down over the chip. Never move it side-to-side otherwise nearby components can be hit and dislodged.
Yes it can certainly be undone. We first extract three copies of the original firmware, compare their checksums and then flash the modified version. We can flash any of the three copies of the original firmware back to the chip at any time.
Hello @synnys,Hi Casey,
I know this is an rather old reply I decided to skip Big Sur and try my luck with Monterey.
I did a clean install of Monterey 12.1 with OC 0.7.6, installed the latest MOTU drivers for my MOTU 16A (drivers are supported for Monterey) but I still have the same issue as I had in the beginning of 2021, the device is not recognised.
I still have a good stable system on Catalina and don't want to mess that up and feel slightly anxious about bricking it by flashing the TB firmware... Have there been any new developments? Any suggestions on what I could try to make it work? Haven't really followed along last year.