Ryzen 7000 Testing
- Thread starter PoMpIs
- Start date
- Joined
- Aug 7, 2022
- Messages
- 843
These properties are either cosmetic or useless, and it wouldn't get stuck here if it was a GPU issue.
@PoMpIs,
Just a note on the above post, I believe there is a minor error I made. You'll notice that the PCIRoot address for both are similar. Reason for this is - the top one is one I used for my B550 Vision D booting a RX6800 card. The second image on the bottom is using the PCIRoot from my Atari VCS which booted using the onboard Picasso APU but using Whatevergreen. I have placed your Raphael device-id details on the bottom one.
What we really need to get it working is find out is your actual PCIRoot address for the Raphael IGPU. If we can do that then you should be able to boot into macOS, even if it is in VESA mode. The reason you are getting the ACPI error is because the system is looking for the IGPU. You could try using just the Raphael settings first with Whatevergreen and see how it goes.
Just a note on the above post, I believe there is a minor error I made. You'll notice that the PCIRoot address for both are similar. Reason for this is - the top one is one I used for my B550 Vision D booting a RX6800 card. The second image on the bottom is using the PCIRoot from my Atari VCS which booted using the onboard Picasso APU but using Whatevergreen. I have placed your Raphael device-id details on the bottom one.
What we really need to get it working is find out is your actual PCIRoot address for the Raphael IGPU. If we can do that then you should be able to boot into macOS, even if it is in VESA mode. The reason you are getting the ACPI error is because the system is looking for the IGPU. You could try using just the Raphael settings first with Whatevergreen and see how it goes.
They aren't useless. I've built many hackintoshes to know it works 100% of the time. And yes before you ask I've successfully booted into Monterey and Ventura using the AMD Picasso APU in my Atari VCS build here > https://www.tonymacx86.com/threads/guide-atari-vcs-2020-console.309903/
- Joined
- Aug 7, 2022
- Messages
- 843
Forgot to attach the EFI, lol, here it is.
@Middleman I also got it working on a few AMD laptops with unsupported iGPUs and didn't need any of the properties
@Middleman I also got it working on a few AMD laptops with unsupported iGPUs and didn't need any of the properties
Last edited:
@ExtremeXT I am assuming you added a SSDT-iGPU-Off.aml? Good going...that's what I was just thinking too!Forgot to attach the EFI, lol, here it is.
@Middleman I also got it working on a few AMD laptops with unsupported iGPUs and didn't need any of the properties
- Joined
- Jul 8, 2021
- Messages
- 292
@ExtremeXT
It hasn't worked..
It restarts instantly when trying to start Ventura and in Monterey it doesn't go from here:
It is that the bios of this motherboard is quite bad, it has bugs... it is a BETA bios
On all motherboards, Gigabyte, MSI, Asrock, iGPU can be disabled...
I have tried in a thousand ways, even with this latest EFI, I have tried to disable Resize bar and virtualization in bios, but nothing changes
It hasn't worked..
It restarts instantly when trying to start Ventura and in Monterey it doesn't go from here:
It is that the bios of this motherboard is quite bad, it has bugs... it is a BETA bios
On all motherboards, Gigabyte, MSI, Asrock, iGPU can be disabled...
I have tried in a thousand ways, even with this latest EFI, I have tried to disable Resize bar and virtualization in bios, but nothing changes
- Joined
- Aug 7, 2022
- Messages
- 843
Try enabling DevirtualizeMmio.@ExtremeXT
It hasn't worked..
It restarts instantly when trying to start Ventura and in Monterey it doesn't go from here:
View attachment 7427
It is that the bios of this motherboard is quite bad, it has bugs... it is a BETA bios
On all motherboards, Gigabyte, MSI, Asrock, iGPU can be disabled...
I have tried in a thousand ways, even with this latest EFI, I have tried to disable Resize bar and virtualization in bios, but nothing changes
- Joined
- Jul 8, 2021
- Messages
- 292
Tried..
The following happens:
Monterey:
Ventura:
I attach the EFI with the modifications
- Joined
- Aug 7, 2022
- Messages
- 843
@Shaneee I think we need a new kernel patch...
- Joined
- Jul 8, 2021
- Messages
- 292
Thank you very much
I will do that as soon as I have a Mac at home, I have several but I left them in another address that are portable, and now here I only have windows computers and it is complicated to edit the config.plist
- Joined
- Aug 7, 2022
- Messages
- 843
@PoMpIs Looks like it's a TSC issue. https://github.com/apple-oss-distri...3dfdf34262bb0042026747cc/osfmk/i386/mp.c#L904
Can you try adding this kext? https://github.com/naveenkrdy/AmdTscSync
Make sure to change the IOCPUNumber to 31 in Info.plist.
If its still not working, try to add TSC_sync_magin=0 to boot-args.
Maybe set TscSyncTimeout to 500000 too.
- ExtremeXT
Can you try adding this kext? https://github.com/naveenkrdy/AmdTscSync
Make sure to change the IOCPUNumber to 31 in Info.plist.
If its still not working, try to add TSC_sync_magin=0 to boot-args.
Maybe set TscSyncTimeout to 500000 too.
- ExtremeXT
- Joined
- Aug 7, 2022
- Messages
- 843
They messed it up on accident when removing the SMBIOS data, this one should work. (I just fixed the error, no other changes.)
@PoMpIs No reason to remove SMBIOS data... Nobody will do anything with it...
- ExtremeXT
- Joined
- Jul 8, 2021
- Messages
- 292
- Joined
- Jul 8, 2021
- Messages
- 292
I have tried several times... reset the bios, with Resibar enable and disable... nothing works
the first time I booted with AmdTscSync it showed this:
on the following attempts it seems different:
- Joined
- May 2, 2020
- Messages
- 2,391
Few things spring to mind having reviewed the EFI and config.plist.
1. Order of Lilu.kext and VirtualSMC.kext is interrupted by NVMeFix.kext and RestrictEvents.kext, i.e. these two Lilu plugin kexts are loaded after Lilu, but before VirtualSMC.kext.
I always thought VirtualSMC.kext had to be the first plugin following Lilu. Is that not the case?
2. Have you tried setting SecureBootModel to Disabled instead of Default.
I know you are using the MacPro7,1 SMBIOS and it is normally set with SecureBootModel > Default. But as this is an unsupported setup, running Secure Boot mode set as 'medium' might cause a KP, when expected settings are not present.
3. Adding RadeonSensor.kext and SMCRadeonGPU.kext makes little sense to me as these kexts aren't usually essential to having a working RX6000 series GPU.
As both kexts contain 'executable' code within them, wouldn't it be better to wait till the system is up and running before adding these two non-essential kexts.
Otherwise it looks good.
1. Order of Lilu.kext and VirtualSMC.kext is interrupted by NVMeFix.kext and RestrictEvents.kext, i.e. these two Lilu plugin kexts are loaded after Lilu, but before VirtualSMC.kext.
I always thought VirtualSMC.kext had to be the first plugin following Lilu. Is that not the case?
2. Have you tried setting SecureBootModel to Disabled instead of Default.
I know you are using the MacPro7,1 SMBIOS and it is normally set with SecureBootModel > Default. But as this is an unsupported setup, running Secure Boot mode set as 'medium' might cause a KP, when expected settings are not present.
3. Adding RadeonSensor.kext and SMCRadeonGPU.kext makes little sense to me as these kexts aren't usually essential to having a working RX6000 series GPU.
As both kexts contain 'executable' code within them, wouldn't it be better to wait till the system is up and running before adding these two non-essential kexts.
Otherwise it looks good.
