Search results

Other things that come to mind: 1) remove -igfxvesa bootflag if you're using it 2) remove -wegnoegpu bootflag if you're using it 3) try -igfxnohdmi on both DP and HDMI 4) try -cdfon on HDMI 5) try disabling your iGPU in your motherboard BIOS settings

What about the USB-C? My thinking was if Apple supports this for their eGPUs, they probably want to connect it on that output. Especially for their Pro Display XDR.

Have you tried connecting the display to another output on the graphics card? It shouldn't change much but who knows, maybe switching from HDMI to DisplayPort will make a difference? Possibly even using that USB-C might change things

Based off of the 5700xt installation guide you could try: 1) Deactivate GPU Injection 2) Config your macOS model 3) Update WhatEverGreen.kext and Lilu.kext to the latest version Try also updating AppleALC.kext and FakeSMC.kext. I'll be looking for more potential solutions. For now i guess...

What display output are you connected to? And have you tried any bootflags?

Keep us updated. This is really exciting!

You have just possibly saved about 3 hours of my life. Your actions shall be remembered fellow hacker.

I'm doing a build with a similar motherboard for my friend. As far as Clover and FakeSMC, just use multibeast. For Lilu i'd recommend installing it in /Volumes/EFI/EFI/CLOVER/Kexts/Other/ because any kext you install outside of that folder (for example in /System/Library/Extensions/) might...

Flawless... Thank you

Yes, i know, i'm building a Hack for my friend with a Z370N wifi. Anyway i just decided to do a clean install because even after replacing the broken config with the good one it panicked. Go figure...

The computer was turning on and off perfectly several times before installing "100/200/300 Series Audio Support". Now it can't boot anymore. Its going into kernel panic. The description for "100 [...] Support" on multibeast reads: "Required for 100 / 200 / 300 Series onboard audio. Must be...

Do i simply drag and drop the Kexts to /EFI/EFI/CLOVER/kexts/Other ? Or do i also have to run some command line? P.S. I dont want them to be installed on /System/Library/Extensions or /Library/Extensions as that could cause troubles after OS updates.

AHA! Got it! It seemed like it was booting from my UniBeast USB. So what i did was i unplugged it, and now it works. It loads the right SMBIOS. There is just one little problem. The Theme is bootcamp, and i'd like to have the default one, and the Resolution is very low. How do i make the...

Is there a way to know where clover is booting from? Or at least, to know from where the config.plist is loaded from?

I know how to boot from the Clover USB Stick. And I did, its what i'm doing right now, simply because the main SSD is loading Chimera and not Clover. But that's not the problem. The thing i don't understand is why is it loading the wrong SMBIOS despite it being correct in the Clover stick. P.S...

USB and SATA information in attachments, i dont know if thats what you asked for.

I am booting from my Clover USB, which has the correct config.plist on it. But when I reach the screen where I have to choose which drive to boot (the one with MacHD, WindowsNTFS) if I go on Options/Settings I see the wrong SMBIOS settings. I have no idea how to explain why this happens, because...

It's always nice when people get their hackintoshes to work. I personally think things like these are the ones that give you the most satisfaction. "Fixing problems is the opposite of fun" is what some people tend to say, but I say no! Fixing problems is one of the most satisfying things ever...

I did change config.plist on the USB from which i boot, telling it to be a MacPro3,1. And if I open it, it still tells me the correct serial number. The problem is, when i boot from the USB and go in the CLOVER OPTIONS and click on SMBIOS, iMac shows up. I can change the SMBIOS from there, and...

Going Bald is right. When i got your same error message i wasn't using UniBeast. Try creating a Unibeast USB and see how it goes.