That is perfectly normal. Certain child nodes will be terminated and reestablished dynamically as needed. The driver in the screenshot is for AMD discrete GPU.So on my day off I figured I would do some reading and see if I can figure out how to get headless working with the igpu. trying to familiarize myself with IORegExp, I see something a bit off and wondering if its an issue or not. can someone take a look and possibly explain?
I actually made an error in that linked post! Only the bottom long slot can be switched between CPU lanes and PCH lanes.Thank you @CaseySJ for the excellent guide. I followed and was up and running way faster than my first hackintosh, so cheers
I used a Samsung 970 EVO for my OS drive and upon testing the speed post-installation, I noticed it was significantly slower than expected (see attachments). I can't figure out why the link width is stuck at x1. I searched this thread and saw your comment here and decided that perhaps the fact that I had the NVMe SSD installed in the M2P slot, the PCI lanes may be limited.
It almost seems like a problem with the NVMe drive itself. Before returning or replacing it, please try updating its firmware using Samsung Magician in Windows.So, I popped the SSD out of M2P and put it into M2M, moved my SATA drives to S1/S2/S3. But this led to the issue of that drive not being recognized at all; in BIOS, there are no NVMe devices... I swapped it back to M2P and it booted back up (interestingly now it has a Link Width of x2 - Screenshot also attached).
Can someone help me understand why I wouldn't be able to swap the SSD from M2P to M2M? Do I need to start over with SSD installed at M2M
That is perfectly normal. Certain child nodes will be terminated and reestablished dynamically as needed. The driver in the screenshot is for AMD discrete GPU.
If you're using OpenCore, then enabling IGPU in BIOS will, in most cases, cause a Couldn't allocate runtime area error at the very start of the boot process.thanks. I actually just noticed that regexplorer is dynamic. while reading I saw more being built while others terminated as you said.
anyway, this may be a catch 22 thing.... without the IGPU being enabled in BIOS its not going to be seen in regexplorer. but turning it on causes a panic. awesome puzzle
That's a good question. So far we need to make two changes to DSDT in order to use the new (but still experimental) version of Thunderbolt SSDT:You guys are crazy, and this is so interesting. I wish I knew how to do all this. Can I ask a question? Does this need to be done for each new BIOS?
So, Casey, if you're on f8, and I'm on f9b, as an example, and I use your DDST/SSDT, would I be missing feature, or possibly introduce issues?
If you're using OpenCore, then enabling IGPU in BIOS will, in most cases, cause a Couldn't allocate runtime area error at the very start of the boot process.
But if you're using Clover, there should be no problem enabling IGPU.