Search results

Late to the party, but Sonoma is working great on my i9/Z390 system, seems to have improved several things, snappier in several ways.

This worked for me too! Thanks.

Was finally able to update to Ventura with this release. Almost certainly it was nothing 13.4 specific, it is just that this time I used OCAuxiliaryTools to upgrade my OpenCore configuration, and the upgrade actually went through. NB, this is the Coffee Lake machine.

The update went smoothly for me, but now my monitors won't go to sleep, they stay on with the screensaver running. I am just posting here for information, not asking for assistance! Please don't consider me a "Violator!" :) And ... after posting this now it is working. The magic of tonymacx86!

I really should update my build info, that was my original hackintosh. This one is the replacement it is a i9-9900K on a Maximus ROG XI Hero motherboard, with a AMD RX 580 GPU (as you suggest!). I had to get reid of the 1070 some time back.

So to refresh my memory I tried again. Used the Install app, it rebooted my machine twice, no visible errors, but I am still on Big Sur, 11.6.8

I can no longer recall the error message. At this point I think I am going to wait for Ventura to come out of Beta, so I don't have to go through the pain twice. I was just posting here to see if there was an "easier" way to configure OpenCore, or to figure out what is missing.

Is this a path towards an easier opencore configuration method? I switched from Clover to OpenCore prior to installing Big Sur, and it went relatively easily. After the initial install, all the point updates were completely seamless (once I removed the USB hub that blocked clean reboots) but...

I just came here to say that this worked for me also. I had read the article, and thought I had tried that .. but apparently not. This page prompted me to try again. BTW, OpenCore is really helping my system a lot. It did the most recent upgrade without me manually specifying the correct...

I see an available update in Software update, but there is no mention of it here? How is that even possible? My rule is never to update until I read about it here.

100% this. Thanks!

After this update it seems my MOTU firewire audio device doesn't work? I can select it from System Preferences, but I don't get any sound out. New audio kext required? Edit: Never mind. Likely was user error.

Just in case it is helpful to someone else: I was wondering about the Monome I had connected to the computer, because that was also a "new" thing, in addition to the 590 and the Mojave upgrade. I disconnected it, and the machine now wakes up from sleep just fine. The drivers are a bit long in...

Maybe the 590 really is a problem? It is not available from the dropdown box in the build signature gadget. Ebay describes the card thusly: Sapphire Radeon NITRO+ RX 590 8GB GDDR5 PCI-E Dual HDMI / DVI-D / Dual DP OC w/ Backplate SPECIAL EDITION (UEFI), 100415NT+8GSEL

I have a similar problem with my system. I'm now running a 590, so I could upgrade to Mojave, and I see the same black screen on wakeup problem.

My system upgraded no trouble, and it seems to have fixed the "black screen after sleep" problem I was having also (based on a couple of successful wakeups anyway.

I just installed a supplemental update to 10.13.2 that further addresses spectre. See: https://support.apple.com/en-us/HT208397 If you have NVIDIA drivers, there is an updated version available.

I am still unable to upgrade to 10.13. I've tried several times, but I never see the "Install High Sierra" (or whatever it is supposed to be) boot option in my Clover screen. I updated to the latest Clover, and put the apfs.ext in the correct place, but ... no dice. Any ideas? (this thread...

This same problem suddenly developed on my system, shortly after I installed an Oculus Rift, though that is probably a coincidence. I solved it by disabling my Windows boot drive in the bios. Strangely that drive still appears when clover scans for drives, and I can boot both Win10 and Sierra...

I tried to change those settings, but I could not boot with them set differently. My solution was to buy a 250Gig internal flash drive (under $100) and use it as a boot drive for Windows. Dual booting is not so convenient as a VM of course, but it is now working for my purposes.