Radeon VII (and new AMD gpus) compatibility

[juliaan88]

@Benlehot @EpicNUFO

Man, I am using Gigabyte Radeon VII mainly due to the maximum number of 3 years of warranty, as compared to other brands.. It seems highly likely that right now only Sapphire cards are fine.

I will try removing AppleGFXHDA.kext from S/L/E temporarily to see if it helps. Brb.

 

[juliaan88]

@Benlehot @EpicNUFO

After removing the kext, for the past couple of hours, no problem. I shall not jinx it and will report back tomorrow about the same time about the progress.

Hope to hear about your progress as well.

 

[EpicNUFO]

@Benlehot @EpicNUFO

After removing the kext, for the past couple of hours, no problem. I shall not jinx it and will report back tomorrow about the same time about the progress.

Hope to hear about your progress as well.

This is great news, I suspected this would be an approach for a temporary fix, provided you don't actually need/use display audio. I actually finished the session super late, it's 4:30am here. I'm gonna crash and test on my end when I wake up. Please let us know if your situation continues problem free with the AppleGFXHDA removed, I will update once I test.

-Eric

 

[EpicNUFO]

I couldn't wait, I was too curious...haha, it's 7am now.

I tried I bunch of things such as a DSDT patch to stop the AppleGFXHDA panic, didn't work. I tried removing AppleALC, I tried -igfxnohdmi for WEG, none worked.

Manually removing the AppleGFXHDA.kext seems to have stopped the problem for me too. I need to test further, but I've been able to consistently reproduce a situation which causes the Kernel Panic, and I can't make it happen right now. So initial tests show this to be a viable solution at the moment if you can go without display audio.

I wonder, is there a way to somehow patch/rectify whatever this conflict is within the AppleGFXHDA regarding the Radeon Vii's???

Time for bed, will update further tmrw.
Err, later today lol

 

[Benlehot]

Great news! I will try the same today. I hope it can fixes it.

 

[EpicNUFO]

Great news! I will try the same today. I hope it can fixes it.

@Benlehot @juliaan88
Great, yes, between the 3 of us on 3 different brands and chipset/CPU of MOBO (Z170, 370 & 390) and with multiple brands of Vii, if this reliably fixes for all of us, perhaps a proper fix for the AppleGFXHDA can be worked into Clover or WEG, etc.

 

[Benlehot]

@Benlehot @juliaan88
Great, yes, between the 3 of us on 3 different brands and chipset/CPU of MOBO (Z170, 370 & 390) and with multiple brands of Vii, if this reliably fixes for all of us, perhaps a proper fix for the AppleGFXHDA can be worked into Clover or WEG, etc.

so far so good since this morning. This looks promising!

 

[EpicNUFO]

so far so good since this morning. This looks promising!

Same here, stress testing for past few hours, seems good to go!

 

[Gigamaxx]

Same here, stress testing for past few hours, seems good to go!

It would be a good idea to find a way to disable in clover or find a patch like find and replace that way you won’t have to manually remove it after system updates.

 

[juliaan88]

It would be a good idea to find a way to disable in clover or find a patch like find and replace that way you won’t have to manually remove it after system updates.

Great idea, I research and I found the following below.

Try an KextsToPatch/InfoPlistPatch, similar to the CoolStar patches for I2C.

Like:

Comment: Prevent AppleGFXHDA.kext from attaching to audio device
Name: com.apple.driver.AppleGFXHDA
Find: <494f4b69 74>
Replace: <494f4b69 73>
InfoPlistPatch: true

I am trying this now!