Jump to content

AppleNVME Assert failed... AppleUSBXHCI::start : Unable to get device memory


4 posts in this topic

Recommended Posts

I've been tasked with updating a hackintosh to Mojave (I originally built it but hadn't touched it since late 2017). It was acting up on a number of fronts so I updated the BIOS and went to work remaking the DSDT and SSDT patches from scratch but it seems I still broke something...

 

I'm currently getting three errors that are preventing me from booting, not sure which of the three is actually the most relevant.

 

First, during ACPI loading I get the following: 

ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0

 

But loading seemingly continues without much issue. Then, I begin getting several AppleNVME asserts (I'm using a Samsung 960 EVO and it was working before) and then sometimes I also get an AppleUSBXHCI panic. Whether I get this last panic or not, the computer hangs.

 

Any idea what might I be doing wrong?

 

P.S. I know it's unorthodox but I've decided to drop all my OEM SSDTs and inject them back (I've gone through them all correcting compilation errors and warnings, as far as I could, as well as making sure to rename what needed renaming. I guess I might have added some stuff I didn't need?)

 

 

 

 

acpi.zip

config.plist.zip

Edited by Lord Kamina
Change topic to the likely actual issue

Update:

 

1) The AE_EXCEPTION issue related to PciConfig also appears when I boot ubuntu without Clover so it's most likely not a product of my patches and a benign message.

2) I'm not getting the USB panic anymore, I think it might have been due to me trying to get cute and renaming the USB 3.1 ports (Not Intel) XHC2.

3) I'm now seeing a new error that looks like it takes the money, and I've updated the topic title to reflect this... the entire error message is:

 

AppleNVME Assert failed: fIOMapRegs 000002.705297 PXSX@: AppleUSBXHCI::start: unable to get device memory

 

EDIT: It seems the above was not quite correct. I booted using cpus=1 (does that even actually work anymore? seems like it does at least...) and the screen changed a bit; it seems that was a mashup of more than one error message.

 

 

IMG_9942.jpg

Edited by Lord Kamina
wrong image
×
×
  • Create New...