- Joined
- Jul 17, 2020
- Messages
- 25
TYTY!this is your previous posted config with MMIO converted and enabled following "the zen 4 Schema"
fill @CaseySJ request to serif you have also to adjust ACPI part
TYTY!this is your previous posted config with MMIO converted and enabled following "the zen 4 Schema"
fill @CaseySJ request to serif you have also to adjust ACPI part
To me personally as if it says that I am using chameleon, as long as it works well that does not matter
We have too few data points at the moment so yes I would encourage you to test the X570 Creator. The fix we made affects all AMD processors whether they have on-board GPU or not, so the more variety of processors we test, the better.Ahh the "good ol' days" -- I remember them well
I have an X670 Creator that I've been too lazy to build b/c I am still tinkering with my X570 Creator, I also have 7950X.
would it be helpful if I beta tested or do we know everything we need to from the systems already in use?
I have never run a debug version of OC, but it's never too late to start, right?
I would encourage you to test the X570 Creator.
The patched version of OpenCore.efi applies to all versions of macOS.I was mostly asking about the X670 Creator when I offered.. but.. I guess I am here to serve.. and learn.
I'm running Ventura on my X570. it's been a downgrade from Monterey for me. should I still proceed, or is this Gold Master for Monterey only?
@CaseySJYes, I promised to do that and I will hold myself to that pledge. The weekend is here so you can expect an update soon. It is, however, 1:50am in Silicon Valley, which means I woke up about 40 minutes early. Which also means I’m sitting by the fireplace sipping a nice hot cup of pour-over coffee while enjoying this Zen moment…oh oh I mean this Zen 4 moment.
Just stepped out for lunch. Will test Aquantia as soon as I get back. I’m also eager to see if it will work. In Ventura, Apple has deepened its adoption of Vt-d, which can be a problem for us, but in that case we can try injecting the Aquantia driver from Big Sur or Monterey.@CaseySJ
Any update?
Just stepped out for lunch. Will test Aquantia as soon as I get back. I’m also eager to see if it will work. In Ventura, Apple has deepened its adoption of Vt-d, which can be a problem for us, but in that case we can try injecting the Aquantia driver from Big Sur or Monterey.
@drmeatball What exact motherboard do you have?
Okay, can you make an USB Map from Windows? Once done, replace UTBMap.kext here with your own.Sorry for the late reply!
ASRock Steel Legend X670E
128GB, 6900XT
ASRock X670E Steel Legend
Supports AMD Ryzen™ 8000 and 7000 Series Processors; 16+2+1 Phase Power Design, SPS; 4 x DDR5 DIMMs, Supports Dual Channel, up to 7600+ (OC); 1 PCIe 5.0 x16,, 1 PCIe 3.0 x16,, 1 PCIe 3.0 x1; Graphics Output Options: 1 HDMI, 1 DisplayPort; Realtek ALC1220 7.1 CH HD Audio Codec, Nahimic Audio; 1...www.asrock.com
It was the best of all the models my local Microcenter had in stock that supported 4 NVME on day 1.
Does your Aquantia port work in Big Sur?Thanks, and I hope you have a good lunch!
Apple has implemented Apple-VTD since macOS Monterey 12.3 so I guess you will have to get it from macOS Big Sur.
Does your Aquantia port work in Big Sur?
But not in Monterey and Ventura?
I've made one last change, which is to log Family and ExtFamily in hex rather than decimal. I'm just testing it now. No need for wider beta on this minor change.@CaseySJ The Beta 3 OC works with no changes as the vanilla one on my AM4 machine. Do you think it's ready for PR? I'd create it so Acidanthera has time to tell us if we need to change anything with it...
// For AMD Processors
if (CpuInfo->Family == 0xF && (CpuInfo->ExtFamily == 0x8 || CpuInfo->ExtFamily == 0xA)) {
DEBUG ((DEBUG_INFO, "OCAK: Setting FSB and TSC for Family 0x%x and ExtFamily 0x%x\n", (UINT16)CpuInfo->Family, (UINT16)CpuInfo->ExtFamily));
busFreqValue = CpuInfo->FSBFrequency;
busFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), busFreqValue, NULL);
busFCvtn2tValue = DivU64x64Remainder(((1000000000ULL) << 32), busFCvtt2nValue, NULL);
tscFreqValue = CpuInfo->CPUFrequency;
tscFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), tscFreqValue, NULL);
tscFCvtn2tValue = DivU64x64Remainder(((1000000000ULL) << 32), tscFCvtt2nValue, NULL);
}
//
// Perform TSC and FSB calculations. This is traditionally done in tsc.c in XNU.
//
// For AMD Processors
if (CpuInfo->Family == 0xF && (CpuInfo->ExtFamily == 0x8 || CpuInfo->ExtFamily == 0xA)) {
DEBUG ((DEBUG_INFO, "OCAK: Setting FSB and TSC for Family 0x%x and ExtFamily 0x%x\n", (UINT16)CpuInfo->Family, (UINT16)CpuInfo->ExtFamily));
busFreqValue = CpuInfo->FSBFrequency;
busFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), busFreqValue, NULL);
busFCvtn2tValue = DivU64x64Remainder(((1000000000ULL) << 32), busFCvtt2nValue, NULL);
tscFreqValue = CpuInfo->CPUFrequency;
tscFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), tscFreqValue, NULL);
tscFCvtn2tValue = DivU64x64Remainder(((1000000000ULL) << 32), tscFCvtt2nValue, NULL);
}
// For all other processors
else {
busFreqValue = CpuInfo->FSBFrequency;
busFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), busFreqValue, NULL);
busFCvtn2tValue = DivU64x64Remainder (0xFFFFFFFFFFFFFFFFULL, busFCvtt2nValue, NULL);
tscFreqValue = CpuInfo->CPUFrequency;
tscFCvtt2nValue = DivU64x64Remainder ((1000000000ULL << 32), tscFreqValue, NULL);
tscFCvtn2tValue = DivU64x64Remainder (0xFFFFFFFFFFFFFFFFULL, tscFCvtt2nValue, NULL);
}