Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues booting into Ventura #6

Open
BugByte14 opened this issue Oct 8, 2023 · 4 comments
Open

Issues booting into Ventura #6

BugByte14 opened this issue Oct 8, 2023 · 4 comments

Comments

@BugByte14
Copy link

Hello! I have an Asus B550-f (AMD) motherboard which has an i225-v ethernet controller. However, when I enable the kext I can't boot into the os.

I get the following message that hangs for a couple seconds and then repeats:

ALUC:clientDied(PID: ###), lifsd_entitled 1 koio_entitled 0
ALUC:init(PID: ###), lifsd_entitlement 1 koio_entitlement 0
methodSetClientDomain entered
registerNotificationPort entered

My Kexts:

  • AppleALC
  • AppleIGC (The one that causes the os not to boot)
  • AppleMCEReporterDisabler
  • Lilu
  • NVMEFix
  • VirtualSMC
  • WhateverGreen

Additionally, I've verified that DisableIOMapper is enabled, but it didn't make a difference. Any advice?

@rx-837
Copy link

rx-837 commented Oct 9, 2023

Hello! I have an Asus B550-f (AMD) motherboard which has an i225-v ethernet controller. However, when I enable the kext I can't boot into the os.

I get the following message that hangs for a couple seconds and then repeats:

ALUC:clientDied(PID: ###), lifsd_entitled 1 koio_entitled 0
ALUC:init(PID: ###), lifsd_entitlement 1 koio_entitlement 0
methodSetClientDomain entered
registerNotificationPort entered

My Kexts:

  • AppleALC
  • AppleIGC (The one that causes the os not to boot)
  • AppleMCEReporterDisabler
  • Lilu
  • NVMEFix
  • VirtualSMC
  • WhateverGreen

Additionally, I've verified that DisableIOMapper is enabled, but it didn't make a difference. Any advice?

i have similar issue on Gigabyte Z490 AORUS PRO AX. Startup, shutdown and restart takes a long time with subject kext.

On tomato forum writes that i225-v controller have native support in Ventura by com.apple.DriverKit-AppleEthernetE1000(https://www.tonymacx86.com/threads/help-ventura-freezing-at-login.322811/page-4#post-2345073)

@rx-837
Copy link

rx-837 commented Oct 10, 2023

@rx-837: Have a look at this: https://github.com/5T33Z0/OC-Little-Translated/blob/main/01_Adding_missing_Devices_and_enabling_Features/Intel_I225-V_Fix_(SSDT-I225V)/README.md#method-1-add-appleigckext

I have seen it.

For my board with latest biosVendor ID, Subsystem Vendor ID and SubSystem ID is correct.
My OC version is 0.8.3, i see no reason to update it. VT-d is enabled, DisableIoMapper enabled(https://dortania.github.io/OpenCore-Install-Guide/config.plist/comet-lake.html#quirks-3).

I have revert the actions from Dortanya's documentation with network controller and Mac OS identified it as Intel(R) I225 V with com.apple.DriverKit-AppleEthernetE1000 driver.

Why I should use AppleIGC kext when device is defined correctly?

@5T33Z0
Copy link

5T33Z0 commented Oct 11, 2023

My OC version is 0.8.3, i see no reason to update it.

There were some significant updates to OpenCore since 0.8.3 in regards to Ventura. So you are using a version of OpenCore which is more than a year old with a kext which is couple of months old.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants