Search results

Question... I created my USB port configurations, as detailed here, and it works fine, except I don't have access to all my ports because there are more than I can map. Do I no longer need to use the port configuration kexts I created now that OC 0.9.3 has fixed the XhciPortLimit Quirk? And, if...

Yep. That was it. Muchas gracias!!!

ISSUE: OpenCore bootloader options include an EFI volume that I cannot remove. Editing ScanPolicy key to remove EFI, removes other bootable windows and linux drives. STEPS TAKEN: 1. Read this TonyMacx86 article. Based on that, tried using UEFI Shell to perform bcfg boot dump --> Result...

Instead of the device ID for the 6900 device, I used the device ID for a 6600 device, which is: FF730000. There is a whole database of device IDs for AMD GPUs, which you can find by googling "Coelacanths Dream AMD GPU Database". Of course, you could use Hackintool to find the device ID, but if...

Issue/Problem: "Unknown Display" on new Hackintosh build. MacOS Display Settings show "Unknown Display" and only 1 available resolution (see screenshot). Monitor connected to GPU via HDMI does work, but only at one resolution (2560 x 1444). My other hackintosh builds show a specific display...

Nevermind... I missed it on the dortania url, "As of 12.1, Apple has added support for the RX 6600 XT." Still not getting it to work though. That will be a separate post.

Product Family: AMD Radeon™ RX 6600 Series Product Line: AMD Radeon™ RX 6600 Series Chipset: Radeon RX 6600 XT Model number: RX-665X8D

I've just installed OpenCore 0.8.8 and macOS Ventura (13.0.1) on a new computer - it's my 3rd Hackintosh. The GPU is an AMD Radeon RX-664X8D and it is not recognized. Reading here it looks like Monterey is the highest supported OS, so I think that explains why it's not working. My questions...

Problem Description: USB 3.1 Gen 2 ports (red) don't recognize GUID partition drives, but do recognize MBR drives USB 3.1 Gen 1 and lower ports (blue and white) recognize all drives (GUID and MBR) Steps taken: Built USBMap.kext according to instructions here: Dortania/OpenCore USB Mapping...

Everything is working now. The system crash was caused by using an old Airportltlwm.kext (Monterey version). Had update to v2.2.0-alpha so I could get Ventura kext. Also, I downloaded the full 13 Gb Ventura install file and installed that, instead of the 3 Gb update version.

Nevermind... just had to update Airportltlwm.kext to v2.2.0-alpha so I could get Ventura kext. Problem resolved.

After updating to Ventura my system shuts down / restarts at about 54 seconds after MacOS launch. If I turn off WiFi, the behavior resolves. Anyone have an idea what could be causing it? SPECS: ASUS ROG MAXIMUS XI HERO (WI-FI) - Z390 (Coffee Lake) Intel(R) Core(TM) i9-9900K Radeon RX 580...

After emptying my trash, the installation proceeded normally. But, after it completed, and launched into Ventura, my system shutdown and rebooted without warning. After the reboot, it got stuck during launch (midway through the progress bar), every time. So, I had reinstall from a...

I emptied my trash bin and the error went away. I was able to install Ventura, but then it crashed and wouldn't load anymore from the bootloader. Fortunately, I did make a backup / clone of Monterey 12.6.1 and am going back to that.

Anyone getting this error, or know a solution? When I click the upgrade button, the software downloads and then begins trying to prepare the update, and then I get this error (see screenshot). Specs: Current macOS: 12.6.1 Current bootloader: OC 8.5 ASUS ROG MAXIMUS XI HERO (WI-FI) - Z390...

Not working for me. On Monterey 12.6.1 with OC 8.5. Will look around for a solution.

Easy peasy lemon squeezy. Was already up to date on OC 0.6.9 with current kexts (ALC, Lilu, WhateverGreen). Last month, finally took the plunge and learned how to map USB ports using USBMap tool (https://github.com/corpnewt/USBMap), so never have to worry about that again. Today... clicked...

Smooth update. Already had most recent kexts from Feb 2, and OC 0.6.6, so just clicked update, walked away, and came back in about 20-25 minutes. Donzo.

Thanks for responding. I can confirm the BIOS boot disk is the one that has the .disk_label files added, and I can confirm those files are there, by pressing cmd-shift-period. Those files are in the boot folder, with bootx64.efi and disklabel. I can also confirm I've completed the OC GUI...

I do have a follow up question. I've been able to create the .disk_label files, using the procedure above. And, I changed the pickerattributes value to 3 in the config file. But, I don't see the new label in the OC bootpicker. Am I missing something?