Search results

Hi everyone, CaseySJ and others already helped me a lot while building the DDR5 version of this setup, many thanks so far. Now, I have a completly different issue: I can't upgrade my system beyond 13.5.1. When I tried to install 13.5.2 from the system settings, it started doing so, restarted...

It simply seems to work. I would never have guessed that the BIOS would cause such sort of a problem... exploring the new system now. I'll be back if there's more problems ;) Thanks for the help!

Oh, using the red USB 3.2 seemed to start up the installer... I'll try to install now and come back here.

Okay, so I downgraded to F6, re-started with your 0.8.3-EFI and modified config.plist myself. I have the impression, we're a little better now, as ... the Recovery Assistant started up?! Not the installer? It is currently examining my volumes but there's nothing to be found I guess... what now?

Still doesn't come up. I currently using the USB 3 drive and it seems to depend on the port I am using where it will get stuck. When I am using one of the four blue ports (I think there's a hub behind those), it'll be stuck at "AppleFileSystemDriver: using boot-uuid" and using the red 3.2 port...

The two modifications did something but it didn't help much. Now I'm stuck a couple of lines lower (s. attachment).

I can't seem to downgrade to F8, because I cannot download it. F6 maybe? Edit: Or, if you still have a copy of it, maybe you can provide it to me? Edit 2: No, don't. I found it on the support page for the DDR-4 version of the mainboard. My board might not support it and I don't want to...

Ok, somehow I feel a little stupid now. I seem to have missed activating the cores. I've now activated all of them and hyperthreading is enabled, too (didn't miss this before). The BIOS screenshots in post 1 seem not to be in sync with the textual description, i.e. there is no word about...

Thank you for the suggestion, but neither USB port nor using an USB 3 drive did change anything.

@CaseySJ First of all, I'd like to thank you for all the efford you have put into this build and in helping people getting it up and running. Maybe I'm a little late, but I now decided to use this build for my new hack and - of course - I wouldn't be writing here, if everything worked as I...

In case anyone is interested, I could sort this issue. It is quite unlikely that any other person on this planet will run into exactly THIS problem. There is one device in my setup that I kept quiet about, because I didn't think, it would matter (or if it mattered then not in this way). I use a...

Hi everyone. I have a working dual-monitor setup with a NVIDIA GeForce GTX 760. Until short my monitors consisted of 1) some AOC 21,5" (1920x1080) monitor and 2) an quite old Acer 22" (1680x1050). "Until short" means, the second monitor (the Acer) died a couple of days ago and I replaced it...

Ok, it IS a DSDT problem. When I remove all my SSDT hot-patches from OC/ACPI and add my old DSDT.aml from clover instead, it all works. Now, I know, it is not 'recommended' to do this and we should rather let OC determine the hardware and just patch it afterwards... Should I put efford in...

Hello dear community, in preparation for installing BigSur some time in the future, I am trying to move my existing Mojave installation from Clover to OpenCore, and I ran into a strange problem there. Currently I CAN boot my Mojave partition using the OpenCore boot of my BigSur install usb...

Updated directly from store, worked like a charm. Took about half an hour on my machine.

And yes, given the right drivers and kexts, Clover appears and works just fine when installed in UEFI mode on my supposedly legacy BIOS system. Weird, but... it's not stupid if it works, so...

Thanks for your answer. :) No, I am not stuck at the apple boot. Currently Mojave boots just fine, the only drawback is the double boot menu screens. So, it's more anoying than a real error. The installed drivers are: ApfsDriverLoader, AppleImageCodec, AppleKeyAggregator, AppleUITheme...

Exactly this happened to me, when I updated my BIOS to its newest Version (it's FE now, not FB anymore) while running on my Windows 10 partition and (i don't know if this has to do with it) updating Windows 10 to the current build 2004. I had started Windows 10 from the drive directly (BIOS Boot...

I'm sorry, I still don't quite get why things are working with clover as they do. So you could try to connect your windows hd to a different controller or user fdisk to remove the primary flag from the windows partition or stuff like that... For me, disabling USB 3 did work somehow...

Hmmm. This sounds like exactly the same problem, that I have installing clover on an older version of the gigabyte boards. I didn't try it yet, but I just read on some different thread that someone solved it by switching off usb 3 in their bios. Will try that tomorrow, but if you do so in...