CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,195
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
Thanks for the reply!Glad to hear it! The entries in PCI are populated by:
If the PCI page continues to remain empty, please compress and upload your CLOVER folder, but redact serial numbers from config.plist.
- Thunderbolt hot plug SSDT in combination with SSDT-DTPG. Both of these are in Post-Installation Files.zip. Please check your CLOVER/ACPI/patch folder.
- Manually entered device properties as explained in Specifying Device Names and Types.
Please change iMac19,2 to iMac19,1 by clicking the pop-up menu on the bottom right of the SMBIOS page, then reboot and see whether the PCI page is populated. If it's still not populated please let me know and we can take the next step.Thanks for the reply!
I checked the folder and re added them and made sure they were the latest version with no luck, heres my folder. Thanks!
Okay, I had chosen iMac 19,2 because of the CPU and I adjusted the USBInjectAll.kext to reflect that, but I'll change it and let you know.Please change iMac19,2 to iMac19,1 by clicking the pop-up menu on the bottom right of the SMBIOS page, then reboot and see whether the PCI page is populated. If it's still not populated please let me know and we can take the next step.
View attachment 429327
So that didn't fix it. I should note that I'm currently using a SAPPHIRE NITRO+ Radeon RX 5700 XT unaccelerated, and am hoping for kexts in the next week or so or else I'll be getting a different card. Could that be causing problems?Okay, I had chosen iMac 19,2 because of the CPU and I adjusted the USBInjectAll.kext to reflect that, but I'll change it and let you know.
I only switched though because I wanted to use AptioMemoryFix, as I don't do video/audio editing or anything where the GPU difference would matter. I'd probably switch back to iMac19,1 if it didn't break Quick Look with iGPU off (I think there are additional kexts that can fix this but the less modifications needed the better as far as I'm concerned).
shikigva=32
shiki-id=Mac-7BA5B2D9E42DDD94
*** SideCar SideDiscussion ***
Meanwhile, for everyone that has upgraded to Catalina and has a compatible iPad:
- On my system, SideCar fails with SMBIOS Mac mini 8,1. The late 2018 Mac mini has a T2 chip.
- I'll change the SMBIOS to iMac19,1 and try again.
- I also have an Asus X99 system without iGPU set up as iMacPro 1,1. The real iMacPro 1,1 has a T2 chip.
- If the Hackintosh ****** indicates that SideCar works on an iMacPro1,1 Hackintosh, I'll find out soon enough.
- Does SideCar work? If so, what SMBIOS?
- Does SideCar fail? Is so, what SMBIOS?
Some early results:
User URL SMBIOS Has T2? Motherboard Result @ummario link iMac 18,3 No AORUS Xtreme Success @NicoDiePlume link iMac 19,1 No Designare Z390 Success @NicoDiePlume link iMac 18,3 No Designare Z390 Success @CaseySJ link Mac mini 8,1 Yes Designare Z390 Failure @svandive link iMacPro 1,1 Yes Designare Z390 Failure
@CaseySJ Thanks a ton! I had a few snags at first but got Mojave fully working, with L/E and Clover/kexts/other setup exactly as you explained. I've booted it about 5 times, no weirdness so far, so looks like I've got a stable buildWhen we press F12 at BIOS to open the BIOS Boot Menu and select either the 10.13 drive or the 10.14 drive, the system run Clover on the chosen drive.
I'm sure you knew this already, but the point is that these are two independent installations of Clover that will not interfere with each other if:
- If the 10.13 drive has its own EFI partition with Clover installed, then that Clover will run if this disk is chosen as the boot disk.
- If the 10.14 drive has its own EFI partition with its own Clover, then that Clover will run if this disk is selected.
Installing EmuVariable and RC scripts has the effect of bypassing the built-in NVRAM in favor of a software solution that writes nvram parameters to a local file in the EFI partition of the booted drive. If both drives have their own EFI partitions, then each drive will have its own nvram.plist and you should not have any interference.
- You use AptioMemoryFix and ...
- You install EmuVariableUefi-64 and RC Scripts in Target Volume
But these two installations can interfere with each other if:
In this case, the system will store NVRAM parameters into actual NVRAM. Because there's only one NVRAM, both 10.13 and 10.14 will write values into it.
- You install AptioMemoryFix and ...
- Do not install EmuVariableUefi-64
AptioMemoryFix is being replaced by FwRuntimeServices. But we can still install AptioMemoryFix from Clover Configurator as shown:
View attachment 428981
I run my system without IGPU and AptioMemoryFix. I also run iMac19,1. I got QuickLook running with 19,1 by using the following shikigva changes. I forget where I picked it up. But it works just fine.
Code:shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94
Those would go into your Boot section.