SOLVED IONvmeController/Kernel Panis

[AMDAzure]

Hi everyone, I have been trying to install BigSur on my Hp laptop with ryzen 3 3200u, with kioxia hp OEM NVMe SSD, I successfully installed MacOs, can enter recovery mode, but have been trying to enter setup through Macintosh HD, but get kernel Panics .... Please help, I'm guessing this is an nvme error, as I can easily enter recovery and install, but cannot boot into OS, I am using HoRONDIS kext for internet and have currently for entering is have disabled it, I have an unsupported realtek wifi card... Will be attaching config/efi and kernel panic... Thank you

 

[AMDAzure]

I have added panic picture in efi folder itself for ease!

 

[EliteMacx86]

Happy New Year!

Provide the Kernel Panic log/photo

 

[AMDAzure]

I have provided in efi folder, Happy new Year to you too!, thank you for replying so quickly, love your forum!

 

[AMDAzure]

 

[EliteMacx86]

View attachment 7056

Why using EnableWriteUnprotector and RebuildAppleMemoryMap together?

Add nvme=-1 to your boot args and check if the installer boots. If it boots, replace the NVMe with a compatible one.

 

[nisel]

Most likely, this will not solve the problem, but you have incorrectly configured kernel patches

 

[AMDAzure]

Why using EnableWriteUnprotector and RebuildAppleMemoryMap together?

Add nvme=-1 to your boot args and check if the installer boots. If it boots, replace the NVMe with a compatible one.

I tried adding nvme=-1, but then it loads to the grey cross/prohibited sign

 

[AMDAzure]

Most likely, this will not solve the problem, but you have incorrectly configured kernel patches

So I believe, I it is an incompatible nvme, and what should I do about the kernel patches, I am new to hackintosh

 

[AMDAzure]

I tried adding nvme=-1, but then it loads to the grey cross/prohibited sign

On adding nvme=-1 I get the still waiting for root device error, I am believing this is because I have loaded the efi onto a partition onto the same SSD, but doesn't explain why I can easily boot into recovery on the same drive?, i am wondering if this is not an nvme compatibility error....