Jump to content

Installing Sonoma on Asus Sabertooth X79 - PLEASE HELP


Billsy11
 Share

19 posts in this topic

Recommended Posts

I have been racking my brain for literally weeks. I have tried so many different posts and have also tried building my own using dortania github but i get so many different panic errors and i just cant figure out where i am going wrong.

My setup is as follows:
MOBO: Asus Sabertooth X79
CPU: Intel Core i7 -3820
GPU: AMD Radeon RX580
RAM: 48GB Corsair Vengeance

My current EFI Folder looks like this and this is the error i keep getting.......

Image is the error im getting from EFI compiled with a shared SABERTOOTH.ZIP after i enable AppleCpuPmCfgLock, AppleXcpmCfgLock and AppleXcpmExtraMsrs and then because i have AMD i tried the USB remap, adding the 2 kext files NoAVXFSCompressionTypeZlib-AVXpel.kext and CryptexFixup.kext and then also the boot arg -amd_no_dgpu_accel of which none work for me as i get error as shown in image.

i just cant seem to figure it out. I also compiled my own EFI with still no joy.

PLEASE PLEASE PLEASE can someone help me get this up and running

EFI.zip

Before changes.jpeg

Edited by Billsy11
added image
Link to comment
Share on other sites

Hi! I'm not sure, maybe I'll be wrong, but those errors have the prefix HCI which refers to Bluetooth controller. Do you have a Bluetooth device? I can see you have a BT kext on your EFI, try removing that.

Link to comment
Share on other sites

19 hours ago, t80u said:

Hi! I'm not sure, maybe I'll be wrong, but those errors have the prefix HCI which refers to Bluetooth controller. Do you have a Bluetooth device? I can see you have a BT kext on your EFI, try removing that.

i did have a bluetooth device installed but i removed it. Let me try and i'll see if there is any difference. Thanks for getting back to me

 

Link to comment
Share on other sites

"Non-Monotonic time" panic means the CPU TSC is not properly synched after power on. This would cause booting issue, commonly seen since Monterey. Unfortunately, this is hardware related because the BIOS failed to initialize the CPU's TSC for all cores. This is discussed in this thread. There was a trick discussed in that thread by modifying the CPU definitions in DSDT which worked for HANNANZHI X79 board. You may give it a trial, but success is not guaranteed.  Also, you should try install Big Sur first, so you get a working EFI. Then try to get Monterey working (if you could solve the TSC out of sych issue), before trying newer OS. Goodluck!

Link to comment
Share on other sites

On 10/25/2024 at 4:27 PM, BillDH2k said:

"Non-Monotonic time" panic means the CPU TSC is not properly synched after power on. This would cause booting issue, commonly seen since Monterey. Unfortunately, this is hardware related because the BIOS failed to initialize the CPU's TSC for all cores. This is discussed in this thread. There was a trick discussed in that thread by modifying the CPU definitions in DSDT which worked for HANNANZHI X79 board. You may give it a trial, but success is not guaranteed.  Also, you should try install Big Sur first, so you get a working EFI. Then try to get Monterey working (if you could solve the TSC out of sych issue), before trying newer OS. Goodluck!

Thank you.... I just can't thank you enough.....

I will try it. Thanks once again

Link to comment
Share on other sites

On 10/25/2024 at 3:27 PM, BillDH2k said:

"Non-Monotonic time" panic means the CPU TSC is not properly synched after power on. This would cause booting issue, commonly seen since Monterey. Unfortunately, this is hardware related because the BIOS failed to initialize the CPU's TSC for all cores. This is discussed in this thread. There was a trick discussed in that thread by modifying the CPU definitions in DSDT which worked for HANNANZHI X79 board. You may give it a trial, but success is not guaranteed.  Also, you should try install Big Sur first, so you get a working EFI. Then try to get Monterey working (if you could solve the TSC out of sych issue), before trying newer OS. Goodluck!

Thanks. I will try to get a working Big sur first and then see what happens.

Thank you so much 

Link to comment
Share on other sites

On 10/25/2024 at 3:27 PM, BillDH2k said:

"Non-Monotonic time" panic means the CPU TSC is not properly synched after power on. This would cause booting issue, commonly seen since Monterey. Unfortunately, this is hardware related because the BIOS failed to initialize the CPU's TSC for all cores. This is discussed in this thread. There was a trick discussed in that thread by modifying the CPU definitions in DSDT which worked for HANNANZHI X79 board. You may give it a trial, but success is not guaranteed.  Also, you should try install Big Sur first, so you get a working EFI. Then try to get Monterey working (if you could solve the TSC out of sych issue), before trying newer OS. Goodluck!

Thanks. I will try to get a working Big sur first and then see what happens.

Thank you so much 

 

EDIT:

So i have tried installing Big Sur and keep getting stuck here. Everytime i think im getting somewhere theres always something else 😕

 

And then second image after i enable XHCI Handoff in BIOS.

 

IMG_0997.JPG

IMG_0998.JPG

Edited by Billsy11
Link to comment
Share on other sites

2 hours ago, Slice said:

I succeeded in Monterey at least with X79.

As well as many other users.

 

This i would love to achieve next but i just kept getting stuck. I had tried so many options but always had a panic error somewhere. The more i researched, the more it got complicated as so many people have different views of how it works best. So im thinking at least if i can get Big Sur on there as BillDH2k mentioned above and have a working EFI then i can maybe use that to create one for Monterey. A little help in hand would be amazing.

Link to comment
Share on other sites

7 hours ago, strangeron said:

 

Thank you sir. I really appreciate this. Im going to match your EFI Folder to mine to see where i was going wrong. Yours seems to be working so far so thank you very much 🙏😁

 

EDIT: This EFI worked an absolute treat. Mine had far too much going wrong hence the panic errors 😰. Now onto Monterey hopefully 🙏. Although Big sur is working very well. I have just added Kexts for Wifi and Bluetooth. All working perfect.

Edited by Billsy11
  • Like 1
Link to comment
Share on other sites

5 hours ago, strangeron said:

Start comparing from the ACPI folder :) 

 

Yes makes sense. Mine needed a big re-jig tbh. i managed to get Big Sur working fine. Added wifi and bluetooth with my old adapters so had a full working system. Good news is that the same EFI works great on Monterey too. So ive installed Monterey but now do not have bluetooth and wifi due to my adapters being old and MacOS not supporting Atheros anymore.

 

So MacOS Monterey 12.7.6 full install, working well just waiting for my new bluetooth and wifi adapter to come.

 

Yet again Thank you so much for your help. 💪

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...