Jump to content

[pre-release] macOS Ventura

fantomas

By fantomas,
in New Releases and Updates

 Share
3338 posts in this topic

Recommended Posts

jsl2000
jsl2000
Posted
Posted
3 hours ago, Joshua60 said:

@jsl2000 thanks for your post.

 

A question, does Applelntell210Ethernet.kext work with Intel I225-V? As far as I know it doesn't. Monterey and BS does not. 

That's why MinKernel=22.0.0

  • Like 1
iCanaro
iCanaro
Posted
Posted
On 7/12/2022 at 7:24 PM, meaganmargaret said:

As I mentioned in a previous post, my attempt to upgrade to the latest Ventura beta failed.

 

But up until then Ventura (Beta 2) was working. 

 

I am wondering if the issue is my Z370 board.  I did notice that most of you are running Z390 and other later boards.

 

Has anyone on this thread have a Z370 board running the very latest Ventura Beta (95/96i)?

 

Booter --> Quirks --> EnableWriteUnprotector --> Yes

 

with previous versions it was not needed, with Ventura instead it must be enabled

 

  • Like 1
iCanaro
iCanaro
Posted
Posted
15 minutes ago, kuro4kin said:

the result matters!
Yes, I work in Mac OS Catalina.
old EFI +WEG +Lilu and eventually Ventura!))

Let's talk when the time is right mac os 13!?

Since I have the same motherboard and I tried your EFI out of curiosity, it remains a mystery to me that it works for you, since it immediately crashes and causes numerous errors.

 

Please note, I already have working EFI for mojave, catalina, big sur, monterey and ventura with Clover and OC

  • Like 1
pbryanw
pbryanw
Posted
Posted (edited)
Quote

@pbryanw I was just looking at this for someone else - not sure if it's the first reference to ATY,Belknap in this thread.  Just to clarify, you are no longer using WEG after adding DeviceProperty ATY,Belknap?

 

@deeveedee - Yep, I'm no longer using WEG, and have removed "agdpmod=pikera" from my boot-args, as per this guide (that someone linked to earlier in this thread).

Edited by pbryanw
  • Thanks 2
kuro4kin
kuro4kin
Posted
Posted (edited)
1 hour ago, iCanaro said:

... it remains a mystery to me that it works for you, since it immediately crashes and causes numerous errors.
 

I just answered a question from a certain madam! 

I don't owe anything to anyone, especially to you mister! :)

Р.S  I also have a firmware old
ROG-STRIX-Z370-I-GAMING-SUS-2401.CAP

Screenshot 2022-07-14 at 8.19.52 PM.png

Edited by kuro4kin
Guest ricoc90
Guest ricoc90
Posted
Posted

In order for Ethernet to work (RTL8125B, using LucyRTL1825Ethernet.kext) I have to set it to 100baseTX full duplex. However, there appears to be a bug in the Advanced Network settings - Changes won't be saved so I added the settings manually instead by adding them directly to the preferences.plist under /Library/Preferences/SystemConfiguration/ 

	<key>Interface</key>
	<dict>
		<key>en0</key>
		<dict>
			<key>DisablePrivateRelay</key>
			<integer>0</integer>
			<key>Ethernet</key>
			<dict>
				<key>MTU</key>
				<integer>1500</integer>
				<key>MediaOptions</key>
				<array>
					<string>full-duplex</string>
				</array>
				<key>MediaSubType</key>
				<string>100baseTX</string>
			</dict>
		</dict>
	</dict>

Ethernet is now working and, fun fact - any changes that I do make in the Advanced network settings actually DO get saved now.

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted
14 hours ago, Joshua60 said:

Thank you @5T33Z0 for your answer, I appreciated.

 

To build config.plist and EFI (Comet Lake) I use this guide https://dortania.github.io/OpenCore-Install-Guide/. It is for OC 0.7.8 and as far as I know never been updated.

 

Now I activated dk.e1000=0 and e1000=0. Ventura boots fine but has no Internet connection.

Monterey has Internet connection.

 

The guide does not mention this arguments. Maybe there is a third bootarg for Ventura? 

 

Thank you for your support.

 

This case is not covered by OpenCore Install Guide. https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/Intel_I225-V_Fix_(SSDT-I225V)

jsl2000
jsl2000
Posted
Posted (edited)
12 hours ago, iCanaro said:

 

Booter --> Quirks --> EnableWriteUnprotector --> Yes

 

with previous versions it was not needed, with Ventura instead it must be enabled

 

In my Z370 hackintosh this Quirk can be disabled at Ventura with OC 0.8.3

Screenshot 2022-07-15 at 10.47.29 AM.png

Edited by jsl2000
iCanaro
iCanaro
Posted
Posted
4 hours ago, jsl2000 said:

In my Z370 hackintosh this Quirk can be disabled at Ventura with OC 0.8.3

Screenshot 2022-07-15 at 10.47.29 AM.png

 

with your configuration my Z370 hack at ventura boot immediately goes into kernel panic.

 

I currently use this setting

 

image.thumb.png.7c25b6183c155a858377be9fb0b95a78.png

 

if you attach me your complete config without your serial, I try to make a complete comparison to try to see if some other setting affects

  • Like 1
jsl2000
jsl2000
Posted
Posted (edited)
2 hours ago, iCanaro said:

 

with your configuration my Z370 hack at ventura boot immediately goes into kernel panic.

 

I currently use this setting

 

image.thumb.png.7c25b6183c155a858377be9fb0b95a78.png

 

if you attach me your complete config without your serial, I try to make a complete comparison to try to see if some other setting affects

My config.plist was attached here.

config.plist

1 hour ago, Joshua60 said:

@jsl2000 I can't find IntelMausiEthernet 1.0.8 or latest.

 

Thank you so much for your help.

For your I225-V at Ventura you need Applelntell210Ethernet.kext (from Monterey) instead of IntelMausiEthernet 1.0.8.

You can google IntelMausiEthernet 1.0.8 and got it there.

https://github.com/acidanthera/IntelMausi

The newest version is v.2.5 instead of 1.0.8

You can check this post:

 

Edited by jsl2000
  • Like 3
  • Thanks 1
Joshua60
Joshua60
Posted
Posted (edited)

@jsl2000 I'm confused, your link points to IntelMausiEthernet 1.0.7.

 

Internet with Ventura was working fine with OC 0.8.2 (#dk.e1000=0 and #e1000=0) no additional kext.

The problem arise in OC 0.8.3. Now Monterey and BS work with dk.e1000=0 and e1000=0.

Ventura doesn't.

Edited by Joshua60
  • Sad 1
Guest ricoc90
Guest ricoc90
Posted
Posted
52 minutes ago, Joshua60 said:

Internet with Ventura was working fine with OC 0.8.2 (#dk.e1000=0 and #e1000=0) no additional kext.

The problem arise in OC 0.8.3. Now Monterey and BS work with dk.e1000=0 and e1000=0.


I might have missed it, but what NIC are you trying to get working?

Slice
Slice
Posted
Posted
47 minutes ago, 5T33Z0 said:
Today I wanted to reset kernel cache in Ventura.
 
So I entered the usual sudo kextcache -i /
 
In return, I get this:
 
Executing: /usr/bin/kmutil install --volume-root / --check-rebuild
Unknown option '--check-rebuild'
 
Did the command change?

The command is for 10.x systems to update prelinkedkernel. Since BigSur we have KernelCollection instead of prelinkedkernel. 

DEPRECATED
     The kextcache utility has been deprecated. It should no longer be
     necessary to use.  See kmutil(8)

 

  • Like 5
  • Thanks 3
deeveedee
deeveedee
Posted
Posted (edited)

@Slice Does this mean that if needed, we can install kexts in /L/E and repair owner/permissions or delete kexts from /L/E without needing to rebuild kextcache?

Edited by deeveedee
Irish_Man
Irish_Man
Posted
Posted
2 hours ago, 5T33Z0 said:
Today I wanted to reset kernel cache in Ventura.
 
So I entered the usual sudo kextcache -i /
 
In return, I get this:
 
Executing: /usr/bin/kmutil install --volume-root / --check-rebuild
Unknown option '--check-rebuild'
 
Did the command change?

This might help?

 

kmutil unload -p /path/kextname.kext unloads the kernel extension specified by /path/kextname.kext. This terminates and unloads it, but may not remove the original kernel extension or a staged copy. Unless you also remove the kernel extension and remove it from its collection, it could load again at the next boot.

kmutil clear-staging clears the contents of the staging directory /Library/StagedExtensions.

kmutil trigger-panic-medic, which is only available in recoveryOS, clears the AKC at /Library/KernelCollections and forces it to be rebuilt, which requires each kernel extension to be re-approved before it can be loaded.

kmutil inspect lists all currently installed kernel extensions according to their collection.

  • Like 2
  • Thanks 1
Guest ricoc90
Guest ricoc90
Posted
Posted (edited)
4 hours ago, Joshua60 said:

Now Monterey and BS work with dk.e1000=0 and e1000=0


I don't really feel like reading back the comments to figure out what your current progress on the matter is, so you'll have to excuse me if I'm repeating.
dk.e1000=0 is for Big Sur, e1000=0 is for Monterey, so it makes sense that the NIC works in Big Sur and Monterey.

In Ventura however AppleIntel210Ethernet.kext got removed and the NIC connects to the dext instead. As far as I've understand you can just inject AppleIntel210Ethernet.kext through OC and use e1000=0 to have your NIC connect to it.

 

Edit: Which is actually beautifully explained in much more detail by 5T33Z0 in their linked guide (section Stock Firmware Users): https://github.com/5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/blob/main/I225-V_FIX.md#option-1-using-a-ssdt-with-corrected-header-description

Edited by ricoc90
rubenpp
rubenpp
Posted
Posted (edited)

After so many trials and searching , I finally have macOS Ventura working on the Asus Z390 Prime-A !

 

Many thanks to Christian for the Guide below 

 

I had to change the device properties to match my specs and use iMac 20.1 

 

MACOS 13. X INSTALL VENTURA ON THE ASUS PRIME Z390-A

Spoiler

image.thumb.jpeg.928064b55f2034af1c267f966533ce6d.jpeg

 

 

Edited by rubenpp
Updated image
  • Like 2
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...