I've used Carbon Copy Cloner in the past — but I remember they had some issues with creating bootable copies after the release of Big Sur / APFS & I have not used it since.
I still have a licence for it — is Carbon Copy Cloner a reliable bootable cloner again or just a backup tool?
I have 2 x 2TB in my Hackintosh — the second one is Windows but I am willing to just wipe it and use it as a bootable clone before doing any major upgrades.
Hi again and thanks for your support. I attached the last info gathered with the last EFI setting up. I tried disconnected the iommu, resizeBAR activated and Deactivated etc...
Hi again and thanks for your support. I attached the last info gathered with the last EFI setting up. I tried disconnected the iommu, resizeBAR activated and Deactivated etc...
Please refer to the highlighted item taken from Post 1 of this thread. The link to "MMIO Whitelist guide"is stale so ignore that part. Instead, just follow the highlighted steps and post a copy of the resulting OpenCore log file. We can help you with MMIO Whitelist by examining that file.
When you say "PCIe" does not work, what does that mean?
Regarding Thunderbolt/USB4, are you referring to Thunderbolt hot plug? Or Thunderbolt devices simply do not connect and work even when connected and powered on before boot?
Finally, please download and run IORegistryExplorer (from here) and post the IOReg file (File -> Save As...).
Wi-Fi 6E
2x2 Wi-Fi 6E (802.11 a/b/g/n/ac/ax)
Supports 2.4/5/6GHz frequency band*
Bluetooth v5.3**
It's an Intel module.
PCIe: My PCIe cards are not detected. I have an audio card Lynx AES16e which is detected in Windows.
UBC devices are detected using the Thunderbolt hot plug but in the system report when clicking Thunderbolt, it indicates no hardware connected. Thinking about it now, I'm guessing that's because there is not thunderbolt hardware connected.
Thank you. I'll try the config plist and send you the IO Registry.
PrichA
When you say "PCIe" does not work, what does that mean?
Regarding Thunderbolt/USB4, are you referring to Thunderbolt hot plug? Or Thunderbolt devices simply do not connect and work even when connected and powered on before boot?
Finally, please download and run IORegistryExplorer (from here) and post the IOReg file (File -> Save As...).
Because Intel WiFi/BT is not natively supported in macOS, we need to install OpenIntelWireless drivers. This is easy enough to do, but let's address other issues before coming back to this.
UBC devices are detected using the Thunderbolt hot plug but in the system report when clicking Thunderbolt, it indicates no hardware connected. Thinking about it now, I'm guessing that's because there is not thunderbolt hardware connected.
We can ignore System Information -> Thunderbolt/USB4. That is only valid when Thunderbolt Bus is enabled, which requires flashing the firmware of Titan Ridge controllers. In most cases Thunderbolt hot plug does not work well on Ryzen Hackintoshes. There are some exceptions such as Gigabyte's B550 Vision D with on-board Titan Ridge controller, which can be flashed to enable Thunderbolt Bus.
Whenever we download software from the Internet, macOS tries to protect us from malware by disallowing the software from running. But we can give macOS permission to run the software as follows:
Run IORegistryExplorer
When you see the macOS warning, open System Settings -> Privacy & Security
Then scroll all the way down until you see a something like the screenshot below
This screenshot is from Sonoma, but you'll find a similar one in Big Sur (System Preferences -> Security & Privacy -> General)
In your case, IORegistryExplorer should be mentioned
There will be an option to Allow IORegistryExplorer, so select that and try launching it again
Interesting. Does the 5.x version of CCC make bootable backups of cryptographically sealed APFS volumes (Big Sur and newer), including Sonoma? The resulting backup disk is bootable?
Please refer to the highlighted item taken from Post 1 of this thread. The link to "MMIO Whitelist guide"is stale so ignore that part. Instead, just follow the highlighted steps and post a copy of the resulting OpenCore log file. We can help you with MMIO Whitelist by examining that file.
I tried several times and we got only this file attached. There is not any entry about MMIO. I tried connecting it into the BIOS and disable with the same result. I don't know if I making something wrong. I already had OpenCore.efi Debugger version.
I tried several times and we got only this file attached. There is not any entry about MMIO. I tried connecting it into the BIOS and disable with the same result. I don't know if I making something wrong. I already had OpenCore.efi Debugger version.
I tried again with another EFI thinking it could be the reason with the same result. It not registed nothing of MMIO. I connected MMI in the BIOS because it was set up as auto in order to check if it could be. It's pretty wird i think so.
I tried again with another EFI thinking it could be the reason with the same result. It not registed nothing of MMIO. I connected MMI in the BIOS because it was set up as auto in order to check if it could be. It's pretty wird i think so.
I tried and nothing change. I downloaded again the debug version and replace the OpenCore.efi unsuccessfully. It not registered nothing about IMMO. I triying to find a solution but it pretty wird.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.