Kernel panic in AMD8000Controller.kext; Firepro M6100

[imrazor]

I'm attempting to setup El Cap on my Dell Precision M6600. This laptop has a FirePro M6100 2GB GPU (device ID 0x66401002.) The device ID is already in AMD8000Controller.kext's Info.plist, which means it should have native support without any injection (right?) However, when trying to boot the clover installer the OS repeatedly KPs on AMDSupport.kext and AMD8000Controller.kext. I've tried various combinations of Inject ATI, FakeID 0x66401002 and Load VBIOS but get the same result each time. Is there anything else I can try?

[Si Vis Pacem]

Device ID may be in the kext but that doesn't help you with the port layout - aka how the framebuffer tries to communicate with the card.

Exmoor (6) @ 0x1c5f20
LVDS, LVDS, DP, DP, DP, DP
02000000000100000001010322050204
02000000000100000001020312040103
00040000040300000001030711020301
00040000000100000001040321030505
00040000040300000001050710000402
00040000000100000001060320010505

Head over to Vladas excellent post:

 

 

1. decode gpu bios with BOTH decoders

 

2. create your specific code

 

3. change framebuffer accordingly - first part is the link descriptor, e.g. 

DP

00040000 04030000

 

DDVI

04000000 14020000

 

HDMI

00080000 00020000

 

4. make sure framebuffer has the exact same amount of ports as before - at least for me a problem, was one short and had to keep the 6th one as is

 

5. FORCE AtiFramebuffer to use your framebuffer - should be Exmoor in your case. Baladi for desktop and Exmoor for laptops as far as I now.

 

Hope that helps!

 

EDIT: 

 

For a short term fix: REMOVE DEVICE ID from framebuffer!

 

Forces OS X to default to Radeon framebuffer and you should be able to boot into El Cap.

Edited July 3, 2016 by Loco Massa

[imrazor]

I forgot to mention it, but I already tried Baladi and Exmoor and just got the same kernel panics. I'll go ahead and try this in the next day or two, but I had a question before I try. From reading Vladas' post, it seems that if there was a problem with the framebuffer or connectors, I'd get a black screen *not* a kernel panic. So is there any point to patching the framebuffer?

[Marovincian]

I'm attempting to setup El Cap on my Dell Precision M6600. This laptop has a FirePro M6100 2GB GPU (device ID 0x66401002.) The device ID is already in AMD8000Controller.kext's Info.plist, which means it should have native support without any injection (right?) However, when trying to boot the clover installer the OS repeatedly KPs on AMDSupport.kext and AMD8000Controller.kext. I've tried various combinations of Inject ATI, FakeID 0x66401002 and Load VBIOS but get the same result each time. Is there anything else I can try?

 

Any luck?  

 

I also have a Dell M6600 with the Fire Pro m6100 and a nice set of kernel panics like yours!

 

I am contemplating surgery on mine to remove the offending graphics card and running on the IGP.  This model has a hardware whitelist (screw you Dell!) so choices for GPU are not exactly wide open.

 

I am attempting to run Yosemite, but at this point, I'd be willing to run El Cap or Sierra or even Snow Leopard!

[imrazor]

No, absolutely zero luck. I've resigned myself to getting my OS X fix on my Dell M6400. Yep, it's NVidia.

 

It's not worth it to me to rip out the GPU. I use the FirePro in Windows, and lately Linux support has improved. And a NVidia chip that's competitive with the FirePro is prohibitively expensive. In your case, instead of ditching dedicated GPUs altogether, I'd recommend the Quadro 3000m, which are rather cheap now (I think.) Optimus might trip you up though, so do your research first. Personally, I hate being restricted to iGPUs.