Jump to content
3338 posts in this topic

Recommended Posts

@miliuco@eSaF

 

Okay Miliuco and eSAF, see if this works for you. This is my working config.plist file for the Coffee Lake Acer.
I've had to disable the WiFi & BT at the registration stage as otherwise my system would crash but otherwise

it should work.

 

config.plist

  • Thanks 1
1 hour ago, Henties said:

Need some advice on a new install of Ventura with an install stick with opencore 0.8.2 and latest kexts to a spare SSD on my Z490 Vision G mobo, AvoidRuntimeDefrag is disabled.

The installation goes into a reboot loop, never reaching the language picker.

 

A normal upgrade of Monterey with a downloaded Ventura "+/- 3.4 Gigs."  also enters into a reboot loop.

 

Tried to disable iGPU as well as i225-V in bios but also no success, using an Amd RX 6800 TX DGPU.

Monterey boots with AvoidRuntimeDefrag Yes or No, -lilubetaall also makes no difference.

 

Greetings Henties

Okay Henties.

I haven't yet tackled Z490 yet (that will be my next task) but I think it could work.
If you have Monterey already running, see if you can get it to upgrade to OC 0.8.1. If you can run that on the Monterey first, then the transition to Ventura should be easy.
My general recommendation is - don't do anything with Ventura until the OC 0.8.1 config can be boot in Monterey. Then from there all you need to do is the following:
disable AvoidRuntimeDefrag
add Maxkernel 22.99.99
add -lilubetaall
enable AdviseFeatures & Spoofvendor
enable all VirtualSMC & SMCProcessor & SMCSuperIO
enable CPUFriend & CPUFriendData
If system still cannot get to install screen, disable WiFi & LAN driver kext

Edited by Middleman
  • Like 1
3 hours ago, PMheart said:

Could you please try this codeless kext provided by @dhinakg? Thanks in advance!


Can confirm: this kext fixes the YouTube-playback issue on Safari :) Also, LVDS display no more wakes up to black screen from sleep. Thank you very much!

Edited by aben
  • Like 5

Just Reboots Here

6 hours ago, Hervé said:

Thank God we still have Clover to handle multiple config files that can be called from the main menu. That's how I'm able to boot Ventura on my E7270 with a dedicated config file whilst the default config file is used to boot Big Sur/Monterey.

Maybe Clover need to be programmed with more smarts in it

It Knows What It Is Booting So should load different configs AUTOMATICALY

Wouldn't hurt to do same with OC

 

Care to share your EFI Folder, Lost The One I Was Using...

Edited by STLVNUB
48 minutes ago, aben said:


Can confirm: this kext fixes the YouTube-playback issue on Safari :) Also, LVDS display no more wakes up to black screen from sleep. Thank you very much!

Hello dear, how are you, may i have your efi file for testing as i am trying to inject the new kext but the resolution is not qc , only 5mb graphics, my system is dell as shown in my signature, waiting your efi plz .. thank you 

39 minutes ago, PC IT said:

Hello dear, how are you, may i have your efi file for testing as i am trying to inject the new kext but the resolution is not qc , only 5mb graphics, my system is dell as shown in my signature, waiting your efi plz .. thank you 


Try this EFi - contains both kexts (WEG + SKL patch) + 32MB DVMT patch.

OC.zip

Ok Guys 

Anybody Who Can't Boot Big Sur Monterey and Ventura Try This

Boots All 3 Fine Here, Just Put In Your Own Kexts

avoidruntimedefrag is set to no

Enjoy ;)

EFI.zip

 

 

Well it did work once in that order 

just tried it again and only BS booted 

Go figure :(

Edited by STLVNUB
  • Like 4
5 hours ago, Middleman said:

Okay Henties.

I haven't yet tackled Z490 yet (that will be my next task) but I think it could work.
 

@Middleman Thank you for your response however I think you may have misread my original post.

 

There is no need for me to try and get Monterey to boot.

Presently Monterey is booting flawlessly with either OC 0.8.1 or OC 0.8.2

I nevertheless followed your suggestions, unfortunately without success.

 

Keen to hear from you as soon as you have tackled your Z490 

 

Greetings Henties

 

  • Like 1
8 hours ago, eSaF said:

I need a board to utilise my Ninth Gen CPU or am I on the wrong track?

I’m afraid you need a newer CPU. Z490 mobos need 10th gen. Z590 can have 10th or 11th. 690 chipset with 12th gen are very very powerful but more difficult to install macOS. 

After successfully booting my Z690 mobo with Ventura ß1 (described here), I tried to get Ventura to install and boot on an MSI Creator TRX40 mobo.  On another forum, fabiosun has done a lot of work and had it working on his TRX40 mobo. After trial and error, I got it partially working, but it would stop short of login. Since this stoppage was similar to what I've read others have observed on other mobos, I thought that the solution might help other, non-TRX40 mobo users.

 

While I'd not needed the following kext with the TRX40 for Big Sur or Monterey, the AppleMCEReporterDisabler kext file is now needed for Ventura ß1 (this kext is not required for the Z690 mobo).

 

Once, this kext was loaded, Ventura would finish the install and boot. However, once booted, the machine would crash and boot-loop in less than a minute. It turns out there was one more problem: the Aquantia ethernet port.

 

After disconnecting the cable  to the Aquantia port, Ventura became stable. The built-in Aquantia is an AQC107 (not the newer Aquantia AQC113 that is working in Ventura ß1 on the Z690 mobo). BTW, enabling v082 OC's Kernel/Quirks/ForceAquantiaEthernet had no effect on the stability of Ventura; the cable could not be left connected to the port.

 

So besides the latest OC and OC kexts and disabling Booter/Quirks/AvoidRuntimeDefrag, with the TRX40 mobo, Ventura required the AppleMCEReporterDisabler kext and disconnecting the built-in Aquantia AQC107 port.

AppleMCEReporterDisabler.kext.zip

Edited by iGPU
  • Like 4
4 hours ago, aben said:


Can confirm: this kext fixes the YouTube-playback issue on Safari :) Also, LVDS display no more wakes up to black screen from sleep. Thank you very much!

Thanks for your confirmation! And does this mean that everything goes as flawless as Monterey?

 

Thanks @dhinakg

  • Like 1
8 minutes ago, iGPU said:

After successfully booting my Z690 mobo with Ventura ß1 (described here), I tried to get Ventura to install and boot on an MSI Creator TRX40 mobo.  On another forum, fabiosun has done a lot of work and had it working on his TRX40 mobo. After trial and error, I got it partially working, but it would stop short of login. Since this stoppage was similar to what I've read others have observed on other mobos, I thought that the solution might help other, non-TRX40 mobo users.

 

While I'd not needed the following kext with the TRX40 for Big Sur or Monterey, the AppleMCEReporterDisabler kext file is now needed for Ventura ß1. 

 

Once, this kext was loaded, Ventura would finish the install and boot. However, once booted, the machine would crash and boot-loop in less than a minute. It turns out there was one more problem: the Aquantia ethernet port.

 

After disconnecting the cable  to the Aquantia port, Ventura became stable. The built-in Aquantia is an AQN107 (not the newer Aquantia AQC113 that is working on the Z690 mobo). Enabling v082 OC's Kernel/Quirks/ForceAquantiaEthernet had no effect on the stability of Ventura; the cable could not be left connected to the port.

 

So besides the latest OC and OC kexts and disabling Booter/Quirks/AvoidRuntimeDefrag, with the TRX40 mobo, Ventura required the AppleMCEReporterDisabler kext and avoiding any Aquantia AQN107 connection.

AppleMCEReporterDisabler.kext.zip 2.5 kB · 2 downloads

ForceAquantiaEthernet patch itself should be still there; I confirmed that some days ago.

 

This means that most likely we will need some other patches.

  • Like 2
18 minutes ago, PMheart said:

Thanks for your confirmation! And does this mean that everything goes as flawless as Monterey?

 

Thanks @dhinakg


Yup, so far so good with regards to iGPU aspects; extremely content with the performance. Really don't see any difference TBH compared to Monterey; just as fluid and snappy. Thank you once again and best regards to @dhinakg as well!

  • Like 1

Any news for the people that needs avoidruntimedefrag in order to successfully boot into monterey? (and so can't boot into ventura)

  • Like 1

Just to confirm, currently the Z370 platform stops with "Required Firmware Update", right?

 

I have HD630, so tried Macmini8,1 and iMac19,1, -disablegfxfirmware, no_compat_check, ... Of course, latests OC 0.8.2 and Kexts.

Does anyone have a working Ventura system with Clover?

I would switch to OpenCore for my laptop but i need a custom DSDT and it needs to be wife friendly so uefi boot option isnt a fix.

DSDT.aml

Edited by SavageAUS
  • Haha 1
Just now, ITzTravelInTime said:

Any news for the people that needs avoidruntimedefrag in order to successfully boot into monterey? (and so can't boot into ventura)

I can confirm it works on Monterey without AvoidRuntimeDefrag on Coffee Lake. My config file is in post above.
@miliuco I thought you should know this too.

  • Like 2
11 minutes ago, Middleman said:

I can confirm it works on Monterey without AvoidRuntimeDefrag on Coffee Lake. My config file is in post above.
@miliuco I thought you should know this too.

My question is different, i am asking if there are any developments for the people that NEED avoidruntimedefrag to boot big sur or more recent, and so can't really boot into venura (with an attempt at booting without that quirk enabled resulting into a system stuck during boot, for example shortly after `[pci configuration end]` or similar, like my x99 system does).

Edited by ITzTravelInTime
  • Like 2
4 minutes ago, ITzTravelInTime said:

My question is different, i am asking if there are any developments for the people that NEED avoidruntimedefrag to boot big sur or more recent, and so can't really boot into venura (with an attempt at booting without that quirk resulting into a system stuck during boot, for example shortly after `[pci configuration end]` or similar, like my x99 system does).

Do you have any settings under DeviceProperties?

7 minutes ago, ITzTravelInTime said:

My question is different, i am asking if there are any developments for the people that NEED avoidruntimedefrag to boot big sur or more recent, and so can't really boot into venura (with an attempt at booting without that quirk resulting into a system stuck during boot, for example shortly after `[pci configuration end]` or similar, like my x99 system does).

Right. And to answer your question, 'Yes there are developments for you folks'. My previous Acer config on Monterey using OC 0.7.8 was unable to boot without AvoidRuntimeDefrag enabled. Since I managed to get Ventura going on OC 0.8.1, I can confirm Montery can now also boot from the same config file on Coffee Lake. So yes.

  • Like 2
Just now, Cyberdevs said:

Do you have any settings under DeviceProperties?

 

I am just using some patches for device names and audi layout id, stuff that i can remove, the same config can boot fine into monterey (once i enable avoidruntimedefrag).

1 minute ago, Middleman said:

Right. And to answer your question, 'Yes there are developments for you folks'. My previous Acer config on Monterey using OC 0.7.8 was unable to boot without AvoidRuntimeDefrag enabled. Since I managed to get Ventura going on OC 0.8.1, I can confirm Montery can now also boot from the same config file on Coffee Lake. So yes.

 

I still have the same problem after updating to OC 0.8.1.

Guest
This topic is now closed to further replies.
×
×
  • Create New...