Contribute
Register

Monterey upgrade stuck at virtual boot IONVMeController::start(IOservice *)

Status
Not open for further replies.
Joined
Sep 6, 2013
Messages
47
Motherboard
Asus X299 TUF Mark 1
CPU
i9-7900X
Graphics
RX 570
Mac
  1. iMac
Mobile Phone
  1. Android
Hello,
Every 2 years I have to upgrade my hackintosh, and everytime it seems as I forgot everything...
So I tried for 3 days now to upgrade my Hack running Big Sur 11.7.2 to Monterey (last version 12.6.2)
I used a USB key to load OC 0.8.4
I try to install Monterey on USB JMICRON adapter with an NVMe drive included.
On this drive there is already a full working Big Sur install.

Now after the third reboot (when the MacOS install disk has disappear) I'm stuck with the message :
virtual boot IONVMeController::start(IOService *)::778:IONVMeController::start
If someone could look at my EFI included it will be great.
In this version I have disable NVMeFix.kext, but with or without it's the same.
Many Thanks

PS: Sorry for my bad english.
 

Attachments

  • EFI.zip
    59.5 MB · Views: 32
Mismatch :
System definition = <string>iMacPro1,1</string>
USBMap.kext = <string>MacPro7,1</string>

You might need something like SSDT-EC.aml or SSDT-EC-USBX-DESKTOP.aml.
 
Wouah thanks Pilgrim for your quick answer.

Yes my definition was always iMacPro1,1 and I have grab USBMap.kext from an EFI in this forum cause I never understood the thread explaining how to do USB mapping.
So first question: Do I have to change this only in config.plist ?

You also right about the second point, I had in my previous EFI SSDT-EC-USBX-DESKTOP.aml.
Second question : If I put SSDT-EC-USBX-DESKTOP.aml in the ACPI folder how I modify the config.plist to apply it?

I feel stupid asking you that but before I was running OC0.6.9 and I was using OCAT to make my EFI.
Now OCAT is only working until OC0.7.8 and for upgrading to Ventura I need at least OC0.8.4.
So I don't know how to apply things in the config.plist.
Upgrade to Ventura will be the next step.
What is weird is that it works well with these 2 errors under Big Sur.
 
I have grab USBMap.kext from an EFI in this forum
you should be making your own:
 
Hello,
I added SSDT-EC.aml
I change system def to MacPro7,1.
I have made my own USBPorts.kext using "the New Beginner's Guide to USB Port Configuration".
Everything works great on my old system (Big Sur 11.7.2), all USB ports are working now...
But I still can't boot the drive where I just installed Monterey.
I have error :
matching deferred by IOUSBHOSTHIDdevice
PCI configuration end, bridges 22, devices 106

Seems my USBPorts.kext is bad, I don't why, I just followed the guide.
I wonder why I see in the Hackintool picture : Z370 Chipset, my Mobo is an Asus X299 TUF Mark1.
Here included my last EFI and error pic.
Thanks for the help, I feel I'm closed...

PS: Happy new year to the whole community.
 

Attachments

  • EFI.zip
    59.6 MB · Views: 29
  • Hckintool_USB.png
    Hckintool_USB.png
    128.5 KB · Views: 95
  • USBerror.jpg
    USBerror.jpg
    3.4 MB · Views: 98
My previous message was just after the Monterey install at the drive reboot.
Now when I boot on the monterey drive I have this error.
PCI configuration end, bridges 22, devices 106
No IOUSBHOSTHIDdevice.
I'm a little bit lost..
 

Attachments

  • 20230102_174445.jpg
    20230102_174445.jpg
    2.7 MB · Views: 52
And now after third reboot on this drive, error is different again ... ??
 

Attachments

  • 20230102_175843.jpg
    20230102_175843.jpg
    2 MB · Views: 52
OpenCore could do with an update to current version.
Why do you have two EC SSDT files ?
Boot argument agdpmod=pikera not required for RX 570.
Misc->Serial->PciDeviceInfo cannot be empty (use 0xFF instead)
 
Thanks for your answer.
I removed SSDT-EC.aml and kept SSDT-EC-USBX-X299.aml.
I removed agdpmod=pikera in NVRAM, boot-args
and put 0xFF in Misc->Serial->PciDeviceInfo
I got error :
... matching deferred by IOUSBHOSTHIDdevice
Virtu[PCI configuration end, bridges 22, devices

Weird, the message seems incomplete...

About OC update, I found this
Part 4 seems more complicate.
Can I update OC0.8.4 directly to OC0.8.7 by following this guide ?

Why OC0.8.4 is not enough for Monterey ?
 
Status
Not open for further replies.
Back
Top