[pre-release] macOS Ventura

[obus]

2 hours ago, etorix said:

Ventura support by OCLPFrom the page on Ventura support by OCLP, the i210 driver has moved to DriverKit :

Which means that i210 nic:s still should work or? They are obviously working on  @yapan4:s C422 but not on mine but maybe @yapan4 is still on Clover.

I remember the problems we had when Big Sur was upgraded from 11.3 to 11.4 a long while ago when i210 nic was working on Clover but not on OC 0.7.0 without  LAN-WSPRO.kext provided from @joedm ru .

Anyway the biggest problem for now is the issue with my second internal NVME and thunderbolt disks doesn't initiates. 

 

Edited October 7, 2022 by obus

[obus]

2 hours ago, yapan4 said:

Hi. @obus

i210 still native supported by macOS

  Reveal hidden contents

 

Still on Clover?

[Stefanalmare]

1 hour ago, axonleo said:

where do i find that ASPP-Override.kext ?

 

ASPP-Override.kext.zip

27 minutes ago, obus said:

Which means that i210 nic:s still should work or? They are obviously working on  @yapan4:s C422 but not on mine but maybe @yapan4 is still on Clover.

I remember the problems we had when Big Sur was upgraded from 11.3 to 11.4 a long while ago when i210 nic was working on Clover but not on OC 0.7.0 without  LAN-WSPRO.kext provided from @joedm ru .

Anyway the biggest problem for now is the issue with my second internal NVME and thunderbolt disks doesn't initiates. 

 

Try this:

CatalinaIntelI210Ethernet.kext.zip

[yapan4]

1 hour ago, obus said:

Still on Clover?

Yes, Clover r5149. I210 works without any patches/additional kext/boot arguments etc. VT-d should be enabled in BIOS!!! And don't forget setting Kernel->Quirks->DisableIOMapper=NO

 

P.S. Some OC users reported problem with Wi-Fi/Bluetooth after enabling VT-d, both work perfect on my config. And don't ask why VT-d is necessary for correct functional of network .dext, I don't known😀

Edited October 7, 2022 by yapan4

[yapan4]

1 hour ago, Stefanalmare said:

Try this:

CatalinaIntelI210Ethernet.kext.zip 74.35 kB · 2 downloads

Probably this kext is obsolete together with Intel network kext in Ventura, also some boot arguments (dk.e1000=0 e1000=0 etc)... 

[obus]

1 hour ago, Stefanalmare said:

Try this:

CatalinaIntelI210Ethernet.kext.zip 74.35 kB · 2 downloads

Didn't work. Thank's anyway. 

[obus]

1 hour ago, yapan4 said:

Yes, Clover r5149. I210 works without any patches/additional kext/boot arguments etc. VT-d should be enabled in BIOS!!! And don't forget setting Kernel->Quirks->DisableIOMapper=NO

 

P.S. Some OC users reported problem with Wi-Fi/Bluetooth after enabling VT-d, both work perfect on my config. And don't ask why VT-d is necessary for correct functional of network .dext, I don't known😀

Could you please share your Clover EFI folder?

[yapan4]

20 minutes ago, obus said:

Could you please share your Clover EFI folder?

 

EFI.zip

[etorix]

10 hours ago, yapan4 said:

Some OC users reported problem with Wi-Fi/Bluetooth after enabling VT-d, both work perfect on my config.

This indicates there are some reserved memory regions which macOS would want to access.

The solution is to drop the native DMAR table, delete reserved memory regions and load the modified DMAR table instead.

Xeon-class system are designed with virtualisation and PCI passthrough in mind, so C422/C621 users are at an advantage here.

 

10 hours ago, yapan4 said:

And don't ask why VT-d is necessary for correct functional of network .dext, I don't known😀

The change from driver to virtualisation must be for performance reasons. Anyway, working VT-d is now a requirement for recent versions of macOS, and we may expect that future versions beyond Ventura will deprecate more kexts and increasingly rely on VT-d.

Edited October 8, 2022 by etorix

[yapan4]

@obus

I have instaled MSI Thunderbold 3 card in my hackintosh and noticed some changes in Ventura vs Monterey(new items in PCI info, new Menu Item), so Apple do changes and solutions for Thunderbolt probably need modification/correction. Or need VT-d too? Currently i dont have any Thunderbold devices to verification.

Spoiler

 

Edited October 8, 2022 by yapan4

[obus]

13 hours ago, yapan4 said:

P.S. Some OC users reported problem with Wi-Fi/Bluetooth after enabling VT-d, both work perfect on my config. And don't ask why VT-d is necessary for correct functional of network .dext, I don't known😀

No problems with WiFi but weird Bluetooth problems with my Apple BCM94321MC card. Bluetooth is mostly working straight after booting in to OS but when looking in system preferences bluetoothradio is off. Scrolling and Secondary click is working first after I manually enabled Bluetooth and first after maybe 2 or three minutes.  

VT-d enabled in bios and DisableIOMapper set to NO. My biggest problem is still that my second NVME disk is not recognised.

Any help for solving this problem is appreciated.

[deeveedee]

7 hours ago, etorix said:

working VT-d is now a requirement for recent versions of macOS, and we may expect that future versions beyond Ventura will deprecate more kexts and increasingly rely on VT-d.

 

I admit to being out of touch with the latest OC install methods, so forgive what is probably a remedial question.  As of OC 0.8.5 [Release] and Ventura Beta 10, I am still disabling Vt-d in BIOS (or enabling DisableIoMapper quirk) as per OC installation instuctions here.  My Coffelake rig continues to run perfectly (I think) with Monterey 12.6 and Ventura Beta 10.  Can you please elaborate on this "new" VT-d requirement for "recent versions of macOS."  If VT-d is required and I am disabling it in BIOS, what issues should I observe to indicate that my rig isn't working properly?

 

Thank you.

[Stefanalmare]

34 minutes ago, deeveedee said:

 

I admit to being out of touch with the latest OC install methods, so forgive what is probably a remedial question.  As of OC 0.8.5 [Release] and Ventura Beta 10, I am still disabling Vt-d in BIOS (or enabling DisableIoMapper quirk) as per OC installation instuctions here.  My Coffelake rig continues to run perfectly (I think) with Monterey 12.6 and Ventura Beta 10.  Can you please elaborate on this "new" VT-d requirement for "recent versions of macOS."  If VT-d is required and I am disabling it in BIOS, what issues should I observe to indicate that my rig isn't working properly?

 

Thank you.

I have enabled AppleVTD even in SMBIOS who doesn't need it.

[Stefanalmare]

On 10/7/2022 at 3:54 AM, jsl2000 said:

1. Still need replaced os.dmg at first otherwise it got automatic reboot before login desktop

If you use SMBIOS who has by default AVX2 (your case 19,1), I think you need to force  cryptexfixup.kext -> boot-args = -crypt_force_avx

[etorix]

@deeveedee Dortania's guides have been in need of updates for quite some time. As Apple increasingly relies on VT-d, I expect that the rewrite will come with a recommendation to enable VT-d whenever possible. Since Monterey, VT-d is required for networking with Intel i210, i225 and Aquantia ACQ-108/113 NICs.

I suppose you're saved by your Q370 hack using an i219 rather than an i210, and you may of course keep it as it is as long as it works.

[deeveedee]

@etorix Thanks.  Just to be clear, are you suggesting the following?

1. Leave VT-d enabled in BIOS
2. Disable DisableIoMapper quirk
3. Drop original DMAR table
4. Inject modified DMAR table (table without reserved regions)

Am I understanding your suggestion correctly?

[Stefanalmare]

44 minutes ago, deeveedee said:

@etorix Thanks.  Just to be clear, are you suggesting the following?

1. Leave VT-d enabled in BIOS
2. Disable DisableIoMapper quirk
3. Drop original DMAR table
4. Inject modified DMAR table (table without reserved regions)

Am I understanding your suggestion correctly?

Give me your original DMAR table.

[RoberT_XeS]

On 10/8/2022 at 12:43 AM, Slice said:

See Clover generator in work Xeon E5 2650 v2

 

 

Have you tried this in OpenCore ?

 

Because its been long since I have used Clover

On 10/7/2022 at 1:50 PM, Slice said:

I have preliminary result with x79+E5 2650v2. The powermanagement works with Clover settings from 1800 up to 3200MHz.

Please share your EFI

[jsl2000]

6 hours ago, Stefanalmare said:

If you use SMBIOS who has by default AVX2 (your case 19,1), I think you need to force  cryptexfixup.kext -> boot-args = -crypt_force_avx

Thanks for your hint.

But after add this boot-args in NVRAM without replaced os.dmg always got KP (FX-6300) or automatic reboot (Z77) during booting.

Edited October 9, 2022 by jsl2000

[axonleo]

I dont get it, is it plain forward now to download ventura beta 10 and make usb install of it and then create opencore 0.8.5 efi folder for x79 board and boot with it or is there some other stuff that is going to mess the boot/ install process i should know about before getting started ? 

[miliuco]

Spoiler

@etorix Thanks.  Just to be clear, are you suggesting the following?

1. Leave VT-d enabled in BIOS
2. Disable DisableIoMapper quirk
3. Drop original DMAR table
4. Inject modified DMAR table (table without reserved regions)

Am I understanding your suggestion correctly?

@deeveedee

 

Waiting for @etorix, I think you are right. These are the steps I followed to have Vtd enabled and DisableIoMapper false without loosing eth and wifi. 

Edited October 9, 2022 by miliuco

[miliuco]

@etorix  

 

I remember (not sure about this) that you have written in a post something about an object to look for it into the DSDT, if the object exists we don’t need to drop DMAR table. But I don’t remember anything else. Is it so or am I wrong?

[etorix]

10 hours ago, deeveedee said:

@etorix Thanks.  Just to be clear, are you suggesting the following?

1. Leave VT-d enabled in BIOS
2. Disable DisableIoMapper quirk
3. Drop original DMAR table
4. Inject modified DMAR table (table without reserved regions)

If it ain't broken, my first suggestion is not to fix it.

 

If you want to have a go at VT-d, step 0 is to keep of copy of your working EFI.

Then try 1. and 2. together (VT-d ON, DisableIoMapper OFF); you may need to adjust further quirks to boot.

If you can boot with VT-d on, and see AppleVTD in IOReg, check the native DMAR table: If there are no reserved areas, there's nothing more to do. If there are reserved regions, or you've noticed issues (wired and/or wireless networking not working), then drop the original DMAR and inject a modified one.

BIOS updates can provide new DMAR tables, so check, and potentially redo steps 3/4 after any BIOS update. (Again, if BIOS ain't broken don't fix BIOS.)

[axonleo]

On 10/7/2022 at 10:20 AM, Slice said:

I have preliminary result with x79+E5 2650v2. The powermanagement works with Clover settings from 1800 up to 3200MHz.

what smbios are you using to boot ventura for x79 and could this smbios work with 3930k sandy bridge ?

[deeveedee]

@etorix "If it ain't broke don't fix it" has become my recent hacking philosophy, although I'll admit to the days where I lived to break it and fix it. 😂

 

If the Dortania guide is modified with new recommendations for BIOS VT-d and DisableIoMapper, I agree that there needs to be some qualification, since it's clear that not everyone needs VT-d enabled and DisableIoMapper disabled.

 

I read your post here and realize that I've taken us way off-topic, so I'll stop, but it appears that the revised procedure (if there is one) needs to mention the need for a DMAC (Direct Memory Access Controller) device in ACPI with _HID 'PNP0200'

 

Thank you.  I'm going to play with enabling VT-d on my rig to see if I notice any difference, but it does appear to me that in my case, it is not needed (at least with Monterey 12.6 and Ventura Beta 10).

Edited October 9, 2022 by deeveedee