Jump to content
124 posts in this topic

Recommended Posts

7 minutes ago, Slice said:

Beta usually follows last release.

Thanks Slice for explanation- now makes sense🙂

 

Build 1: iMac20,2, i5-9400F, Samsung 16GB DDR4 RAM, MSI Z390 Gaming Plus, Radeon RX 580 8GB, OC 0.8.9

Edited by ndungu6678
  • Like 2
5 hours ago, nyu1985 said:

Hello,

 

I need to disable E-Cores on my Z690 + 13600KF rig otherwise I have a kernel panic at boot saying the numbers of detected cores is not good.

No problem on the Z390 + 9900K rig.

If you may use Clover then I can look to your Clover preboot.log where significant information will be contained.

  • Like 1

I had to disable E-Cores as well, thanks to this thread, managed to get it installed. Now to enable and see if it boots after installation. Z690 and 12900K

 

***EDIT*** Tried with E-Cores on Random mode and boots to panic, E-Cores on Auto and also panic - seems that as long as E-Cores is enabled you cannot boot into Ventura 13.3 beta. Lucky I have another Ventura 13.2 on another M.2 

Edited by surenmunoo
  • Like 2

 Oh my!!! - Like owning a Ferrari and not letting the horses under the hood stretch their legs the joys of hackintoshing. I'm going to reinstall 13.2 for the moment(Three hours later lol)

 

 

Edited by BALDY_MAN
  • Like 5
On 2/16/2023 at 9:31 PM, fantomas said:

macos_13_3_beta.png

 MacOS Ventura 13.3 beta ( 22DE5219e)

 

Full Installer:

http://swcdn.apple.com/content/downloads/15/58/032-01912-A_61S1ZIFYYG/uo8x7rgi4gpep6f17gxgiqcewcfe0vy434/InstallAssistant.pkg

 

Build 1: iMac20,2, i5-9400F, Samsung 16GB DDR4 RAM, MSI Z390 Gaming Plus, Radeon RX 580 8GB, OC 0.9.0

 

Edited by ndungu6678
  • Like 7

X299 is late to the party but the update is done ( without issue ) 

BTW, thanks Mr Amazon I found the perfect use for your Fire tablet.. However the app “About this Hack” does not seem to understand what kind of monitor it is 😂.

 

4AFC6E32-5118-47CA-A735-03E63E16FBB0.jpeg.41e886ea6d95134895e9042f68578166.jpeg

 

37FDCB2A-1D80-4A4D-8366-9F47FA43C5A5.thumb.jpeg.5f7ac84de684d9bf753b870153afdad7.jpeg

 

Edited by Ellybz
  • Like 8
  • Thanks 1

I suppose the e-cores thing is caused by some new kernel (or system kext) code made specifically to error out in case some wired configurations in the cpu topology are detcted, since the x86 code in macOS is made just for cpus without a hybrid topology. Perhaps you can achieve boot by enabling the e-cores and disabling hyperthreading, but this is just an idea, it might as well just not work at all, for the moment it seems that work needs to be done to spoof the cpu tology detections being made by the kernel or to at least patch them with somenthing like a lilu plugin.

 

BTW if you have the text from the e-cores panic, even a picture, posting it will be very helful, remmeber to use the keepsyms=1 and debug=0x100 boot args and to enable your bootloader config option to disable logging of loaded kexts in the panic text, so the system will not reboot after a panic and it will display some additional info about what pieces of code causes it, but also not display info we don't need.

 

Thanks for the attention.

  • Like 2
8 hours ago, odemolay said:

Clover still rock'n you Ventura, thanks @ndungu6678 for "about-this-hack"

 

Capture d’écran 2023-02-21 à 21.11.34.png

 

 

 

1362220044_Screenshot2023-02-22at7_17_44AM.png.e7a900a59d2b121e858e1c1b52c4a8cc.png

I also got to learn about the "about-this-hack" app from info and links posted earlier in this forum (see above)- so can't really take credit- we are here to learn and help each other- that what makes this forum so special-cheers!

 

Build 1: iMac20,2, i5-9400F, Samsung 16GB DDR4 RAM, MSI Z390 Gaming Plus, Radeon RX 580 8GB, OC 0.9.0

Edited by ndungu6678
  • Like 5
Guest
This topic is now closed to further replies.
×
×
  • Create New...