Just tried this -- unfortunately, VanillaMon goes into a boot loop very early in the process.I found something interesting, can you try adding the acpi=0x10000 boot arg and booting vanilla Monterey?
Where exactly does it panic? NVMe initialization?Just tried this -- unfortunately, VanillaMon goes into a boot loop very early in the process.
I should add that a PCIe card (Fenvi) is installed, which I believe is what we want.
NVMe has been removed. Only Thunderbolt and Fenvi are installed. Have stepped out for lunch. Be back shortly.Where exactly does it panic? NVMe initialization?
Where exactly does it panic? NVMe initialization?
Some Updates:NVMe has been removed. Only Thunderbolt and Fenvi are installed. Have stepped out for lunch. Be back shortly.
I think the only chance we have at properly fixing this issue is serial debugging, would you be able to get one of those set-up?Some Updates:
Results:
- Thunderbolt disabled
- NVMe SSD removed (since early this morning)
- Fenvi FV-T919 installed
- boot-arg includes acpi=0x10000
View attachment 7885
- Vanilla Monterey boots up fully -- this is being posted from that boot
- Fenvi WiFi appears in IOReg, but no driver attaches, as shown:
I read through the Dortania article, which seems to require the presence of an RS-232 serial port or header. Alas, this motherboard does not have RS-232.I think the only chance we have at properly fixing this issue is serial debugging, would you be able to get one of those set-up?
Also having it on board or via an USB RS232 could be a no go, because it could need of a UEFI driverwhich seems to require the presence of an RS-232 serial port or header. Alas, this motherboard does not have RS-232.
I already have a USB-to-RS232 cable that uses a FDTI chipset. Just verified that CoolTerm in macOS works with it. I’ll need a second such cable, preferably with null modem configuration— or a separate null modem adapter. These are cheap so I can set up the experiment soon.Also having it on board or via an USB RS232 could be a no go, because it could need of a UEFI driver
In the past I did some tests about it but I have had no success (I have used PCIEx RS 232 add-on and an USB One
OC devs said in the past I should have need of a UEFi driver for it
Maybe today things are different
Have you tried OpenCore's Serial feature? This seems to imply that OpenCore includes pre-boot drivers...Cross my fingers for you, but it seems the same steps I did and no useful data because I miss an Efi drivers in problematic rig
Reading data from another pc with macOS or windows didn’t produce a serial debug
Not sure if USB Serial will work, but we'll see...I already have a USB-to-RS232 cable that uses a FTDI chipset. Just verified that CoolTerm in macOS works with it. I’ll need a second such cable, preferably with null modem configuration— or a separate null modem adapter. These are cheap so I can set up the experiment soon.
Not sure if USB Serial will work, but we'll see...
I have just ordered this one, which has a CP2102 chipset.Venel USB 2.0 to RS232 Female DB9 Serial Adapter Cable (Clear Blue) 1.8 Meters, with CD / PL2303 Chipset/Support 98/ME/2000/2003/2008/Andoid/XP/win7 8 8.1 10/Mac OS/Linux. : Amazon.it: Informatica
Venel USB 2.0 to RS232 Female DB9 Serial Adapter Cable (Clear Blue) 1.8 Meters, with CD / PL2303 Chipset/Support 98/ME/2000/2003/2008/Andoid/XP/win7 8 8.1 10/Mac OS/Linux. : Amazon.it: Informaticawww.amazon.it
these for me didn't work
Sure -- kext attached (Monterey 12.6)I have a new idea, what if we redirect the kexts like IONVMeFamily to use another IOPCIFamily version which we'd inject with OC? It can be changed in the Info.plist of the kexts.
@CaseySJ Can you dump Monterey's IONVMeFamily?
It seems all of the patched kexts were skipped because the standard versions of those kexts have the same class names as those in the patched versions...@CaseySJ Please try this EFI, it's the latest one you sent but with:
- Patched IOPCIFamily from Big Sur named BigSurIOPCIFamily.kext
- Patched IONVMeFamily from Monterey named PatchedIONVMeFamily.kext
- Patched AppleIntelI210Ethernet from Monterey named PatchedAppleIntelI210Ethernet.kext
The BundleIdentifier of the kexts was changed and the IOProbeScore was set higher than the original kexts to they attach to the devices instead of the vanilla ones.
Try with disabled Thunderbolt since that kext was not patched, if everything goes right we should have I225-V LAN and NVMe working without modifying the system partition.