Jump to content
12 posts in this topic

Recommended Posts

Hi all,

My secondary hackintosh works fine, except that in about every 10 boots it will stuck at here:

image.thumb.jpeg.1c2a47ab8d9dcc2cfadf4d0960aceee4.jpeg

This is a mini PC with what I believe is a proprietary logic board, an i7-10510U, and no dGPU (NOT the one in my signature), bought from Taobao, and the EFI is provided by the seller (with my modifications). The EFI folder is attached below. Can soeone provide some insights on what could be causing this?

 

Thanks in advance.

EFI.zip

Edited by i0ntempest
Guest 5T33Z0

@i0ntempest Here are my observations:

 

ACPI:

  • Your SSDT-EC includes also includes a fake RTC. But at the same time you are using SSDT-AWAC which diasbles the AWAC clock and enables an Existing RTC in the DSDT. So: does your DSDT contain a real RTC or not? Because RTC0 is usually only needed for boards with 300-series chipsets where the RTC is missing. But my guess is this board doesn't use a 300-chipset since it has a 10th gen Intel CPU. I would remove the RTC0 from SSDT-EC and see what happens.
  • If it's not a 300 series chipset, you probably also don't need SSDT-PMC

Booter Quirks: I know "SetupVirtualMap" is not required for 10th gen dektop CPUs. Maybe try without it.

Kexts: are you sure you need XHCI-unsupported.kext?

Kernel Quirks: AppleXcpmCfgLock is not enabled. Unless you can disable CFG Lock in BIOS, you need this quirk

Misc > Secutity: I would disable SecureBootModel for now. It's the number 1 reason why systems wont boot initially. You can get the security thing working later, once the system is up and running

NVRAM > csr-active-cong: why 6F000000? Which macOS do you want to install?

PlatformInfo: I don't know if macMini is the right SMBIOS for this, since I can't tell the graphics chip on the CPU. It only states "Intel UHD" on the Intel site.  But the macMini uses HD 6000/Iris Pro 6200 instead. So yo may have to check what iGPU is used on this CPU and then pick the SMBIO accordingly.

 

Rest looks good to me as far as I can tell.

 

 

@5T33Z0Appreciate your reply, I'll modify my EFI and see if I still get random boot freezes. It's gonna take some time as most of the times it boots just fine.

About CFG lock: ControlMsrE2 reports "This firmware has UNLOCKED MSR 0xE2 register!" so I should be fine.

About my csr-active-cong and SecureBootModel choices: the system is already up and running for months, it arrived with Big Sur installed and I upgraded it to Monterey. Those are required for system update to function (6F000000 is the max I can set without borking software update).

About PlatformInfo: I have a real Macmini8,1 and I'm pretty sure it uses Intel 630? I think 10510U has a 620 so sould be fine?

Guest 5T33Z0

About the SMBIOS:

According to everymac.com, the macMini uses an 8th Gen i7-8700B (Coffee Lake) with UHD 630

From what I can tell, the only Mac model with a 10th Gen mobile CPU is the MacBookPro16,2 which has an i7-1068NG7 (Ice Lake). You could try how this performs in comparison.

 

But you should definitely check the AWAC/RTC0 situation by analyzing the DSDT. Maybe this helps: https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/System_Clock_(SSDT-AWAC)

 

 

Yes, for now I have removed RTC0 from SSDT-EC, and made a few other changes following your suggestions. Let’s see if I get another freeze, if I do then the next thing I’ll try is AWAC manual patching, and then SMBIOS change.

Though I’d like to keep using Macmini8,1 if possible, because the mini PC’s form factor is more like a Mac mini.

Edited by i0ntempest
On 4/23/2022 at 10:34 AM, i0ntempest said:

Yes, for now I have removed RTC0 from SSDT-EC, and made a few other changes following your suggestions. Let’s see if I get another freeze, if I do then the next thing I’ll try is AWAC manual patching, and then SMBIOS change.

Thought I’d like to keep using Macmini8,1 if possible, because the mini PC’s form factor is more like a Mac mini.

Make your signature contains this computer else I don't understand what about you.

At the first screen I see the panic just after VirtualSMC loaded. So my proposition is to try FakeSMC. It is more stable and tested over years.

@i0ntempest Hi there,

I could be wrong here but I can see; there is a Broadcom WiFi module present which could possibly be the cause of this random intermittent freezes here while booting macOS Monterey. Is your hackintosh, by any chance, fitted with a DW1820A or similar 3rd-party-chipset of the BCM94350 family variant ? If so, there is a current known issue/bug from Apple's end where certain affected 3rd party Broadcom chipsets randomly happen to get initialized twice during boot causing a freeze or KP on macOS 12. Only workaround available at the moment is to try and delay the boot init process with the help of AirportBrcmFixup's handy boot-arg: brcmfx-delay=[delay in milliseconds]  Recommended to test with a starting value of 15000 (milliseconds) and upwards, if this is case i.e.

@aben, Thanks for the info, I just checked and I have a BCM94352Z, is it also also affected by this problem? Also where did you get this information on this double initialization bug?

Yup, that should most likely explain the intermittent freezes seen here. I would suggest you try disabling/ removing the card and initiating a few reboots to further confirm this.
 

My Dell Inspiron too was previously fitted with a similar chipset; the BCM94350ZAE: Dell branded DW1820A model and was affected by the exact same random freezes during boot on macOS 12. (As far as I’m aware, you are the only other user to have reported this exact behavior apart from myself)
 

Having been a proactive tester of pre-release macOS builds, this peculiar bug has been present since one of the earliest pilot betas of macOS Monterey (12.0 b4+).
The discovery of the underlying issue being the double initialization bug affecting some of these 3rd party Broadcom cards was further confirmed by one of Acidanthera’s developer: lvs1974 who is currently responsible for maintaining the AirportBrcmFixup project. The details were shared via a thread dedicated to AirportBrcmFixup on the Russian forum: appleLife.ru. To help alleviate this issue, the handy workaround with delaying the boot init was implemented as a configurable boot-arg flag allowing the user to flexibly test with choice of delay in milliseconds. However, as per my testing, this workaround is sometimes a hit & miss and not quite the perfect solution yet with this bug still present on current macOS release. This was actually one of the main reasons that forced me to finally bid farewell to 3rd party Broadcom chipsets and switch to original Apple Airport card for better compatibility with macOS 12’s Bluetooth stack as well. Personally I would recommend the same given the current situation with these affected cards.

@aben

Actually I have not yet get another boot freeze after I modified my DSDT and some other stuff following suggestions from 5T33Z0. If I do then I'll definately try your suggestions. Right now I'm looking into sourcing a BCM94360CS2 with an adapter, which I believe should not even need AirportBrcmFixup at all?

Also, you mentioned that the bug could cause a freeze or a KP but I'm only having freezes. Were you getting both? And what was the chance for you for getting one?

@i0ntempest If you haven't encountered another freeze yet after making those suggested edits, then I highly doubt you're affected by this particular bug. As per my testing, macOS 12 now appears to have acceptable native Wifi support for some 3rd party Broadcom cards, without the need for AirportBrcmFixup, as long as the original device id is part of AirportBrcmNIC driver. In my case, no KP was shown during boot, only random freezes once every 10 ~ 15 reboots, seen when AirportBrcmNIC driver was initializing the card (similar to the verbose log output as seen on your end) with a subsequent KP report that always followed upon successful boot.


And yes, AirportBrcmFixup nor BlueToolFixup required for genuine Apple AirPort cards.

@aben My verbose log does show BrcmNIC init twice, also since I use this system as an always on server I don’t reboot it that much, so could be just luck. Maybe tomorrow I’ll try rebooting it a few dozens of times in a row.

What’s different here tho is that I never see any panic logs after those freezes… so idk.

×
×
  • Create New...