Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Thanks for the advice but just look at it this way… Have you ever had your car break down and you didn’t know how to make the necessary repairs? Have you ever have a craving for a dish that you really like but don’t know how to cook? Just ask someone who knows, right? I’m sure they won’t hear them tell you ‘if you can fix your own car maybe it’s just not for you to own it.’ Or ‘maybe you just weren’t meant to have your favourite dish…’
In this case I’m only asking for the latest version of the vBIOS to avoid making a terrible mistake. I’m not very knowledgeable in this field so I’m just asking for a little help from the people who seem to be experts. After learning what I can I will help anyone I come across along the way and beyond if I can.
After 4 years of hoping and waiting for something good to come along and get my gorgeous iMac up and running again, I just need some help to give it another life.
I do realize that some of you guys here help people like myself all the time and maybe you’re getting tired of it. That’s fine but I do think there’s a need to tell people “maybe it’s not for you”. Help or don’t help, it’s your prerogative.
I spoke with the seller and he agreed to reserve a card for me until I get this sorted out. I feel a little less stressed now after paying for the card.
Thanks for taking the time to read.
I am sorry that my reply appears discouraging to you 😅
My point is just that you really need to read all the important info in at least the 1st post to get an idea of what you will be going thru. NO time isn't an excuse to skip that cause its success depends on more than luck but preparation with knowledge. Indeed, we wish you success in this project with the minimal troubles 😊 Thus the advice.
 
  • Like
Reactions: Ausdauersportler
If your original card was a 6970 then you have a 3 pipe heatsink.
So i buyed the K4100M..! I'don't know if it's right, if there less compatibility with recent OS but with native boot, good metal performance and nothing to mod in the heatsink (for me it's more difficult).. now when i made the upgrade for the thermal paste is right the Artic MX-5? For GPU and memory bank..
 
So i buyed the K4100M..! I'don't know if it's right, if there less compatibility with recent OS but with native boot, good metal performance and nothing to mod in the heatsink (for me it's more difficult).. now when i made the upgrade for the thermal paste is right the Artic MX-5? For GPU and memory bank..
You will have to mod the heatsink for the K4100M - this is in the 1st post. As are the answers to your other questions. Read it!
 
  • Like
Reactions: Ausdauersportler
Experimental AMD FirePro M6100 2GB (AMD R9 M380)

View attachment 1876272

This thread will chronicle my efforts to get the AMD FirePro M6100 MXM 3.0 card working on a 2009/2010 iMac. I've been working on it for several months. I will concentrate on the older iMacs as the 2011 iMacs have an issue with the "wake" cycle not recognizing the GPU and make this card nearly unusable.

This card is used internally in a iMac (Retina 5K, 27-inch, Late 2015), model Identifier: iMac17,1

SSH Access:
Code:
Adapter  0    SEG=0000, BN=01, DN=00, PCIID=66401002, SSID=00000000)
    Asic Family        :  Bonaire
    Flash Type         :  M25P10/c    (128 KB)
    Product Name       :  Dell / Compal Brooks Saturn XT C60001 A1 GDDR5 2GB 300e/150m   <-- card recognized!
    Bios Config File   :  BR44933.001
    Bios P/N           :  P/N Not Available
    Bios Version       :  015.040.000.001.044933
    Bios Date          :  10/02/13,10:35:3
    ROM Image Type     :  Hybrid Images
    ROM Image Details  :
        Image[0]: Size(65024 Bytes), Type(Legacy Image)           <-- legacy vbios recognized!
        Image[1]: Size(61440 Bytes), Type(EFI Image)              <-- PCI option ROM/UEFI recognized!

MacOS integration:
This card uses the AMD8000Controller.kext and the AMDBonaireGraphicsAcccelerator - RadeonX4000.kext which also natively runs in MacOS. The AMDMTLBronzeDriver is used to initialize its Metal capability. The default framebuffer is in use: RadeonFrameBuffer.

You will like need to apply the same Device Properties as previously stated in other posts <@Ausdauersportler> here recently.

Mods:
- I modified the OBJ table to work with our current iMac models: eDP:14, EncoderID:21, I2CID:92, SenseID:03.
- I used the IM17,1 Header to trick AppleGraphicsPolicy into accepting it as native
- I used an IM17,1 VGA bootloader firmware instead of the stock Dell one and adjusted the pointer to the parser-fall-call in the TVdispout table to point to the correct area in the patched bootloader.
- I used a PC UEFI GOP to communicate with OC and/or OCLP, so you will not get a native MacOS boot picker screen, but instead the OC one.
- GPIO_Pin_LUT has 6 pin assignments for Dell ROM, there are 8 defined in the Apple ROM. This was patched.
- In EFI 1.x systems, the INT 10H and the VESA BIOS Extensions (VBE) are replaced by the EFI UGA protocol. In the more widely used UEFI 2.x systems, the INT10H and the VBE are replaced by the UEFI GOP which is what we are using here to communicate with OpenCore or OCLP using device properties.

The card is recognized as an 'HD8xxx', but that doesn't matter. With the proper OperCore config file, it should be recognized appropriately. I have only tested with High Sierra and Catalina:



View attachment 1876252


View attachment 1876257


Thermal IC chip:
The SMC "0" SMBus Connections on the iMac uses a write address of: 0x98 for the 8-bit SMC slave address. This is equivalent to a 0x4C 7-bit slave address:

Code:
0x98 = 1001 1000
0x4C = 0100 1100  (you can see that the 7-bit address is just bit-shifted to the right by 1)

So a GPU card with a ADM1032 thermal IC with a part marking "T1J" seems to work because it communicates on the 0x4C SMC address and will not cause an address collision with other thermal ICs on the logic board. In contrast, an ADM1032 chip with a part marking "T1C" is internally connected to 0x4D and therefore will not communicate with the imac SMC. An EMC1402-1 chip has a slave address of 1001_100 (corresponding to 7-bit 0x4C) and theoretically should also work, but there could be other interactions that are interfering with this. More investigation is necessary.

10/25/2021 addendum:
@dfranetic has pointed out correctly that the SMC information is not being read correctly by this chip, ADM1032. It appears that Mac Fan Control queries the thermal IC directly and not the SMC lane. So back to the drawing board! Sometimes sounds theories don't turn out as we expect in reality

Here is Macs Fan Control:
View attachment 1876141

Let's take a closer look at this IC:
View attachment 1876140
You can see here, that it uses 2 Jumper resistors (lime green) to connect the SCL and SDA lines to the GPU. The pull up resistors are right next to them, both are 100KOhm I believe. I will as an experiment remove these 0 Ohm resistors and see what happens to the GPU temp read out, stay tuned. More research here is necessary.


Benchmark:
View attachment 1876142

Other members have been working on variants of this card, but be warned, these are experimental in nature and still have a lot of troubleshooting to get them working appropriately. They are painful to recover from a bad flash. It's been a long frustrating road with these class of cards, but nevertheless, it has always been insanely great!
Enjoy.​
I successfully applied your bios to a M6100 on a 27 iMac 2010. working fine

I tried with another M6100 on a iMac 21.5 2011, and the bios was flashed correctly, is detected and the kext is loaded, but the display is not detected at all by the OS (11.6 bigsur) on a cold boot (using screen sharing to verify it). only after a reboot the screen is detected and everything works perfectly, including OC boot picker

same issue on a iMac 24 2009. boots, gets kext loaded, but the display isn't detected at all on cold boot

is there a way to delay the display detection via vBIOS? is there something we could do to fix it?

thanks
 
I successfully applied your bios to a M6100 on a 27 iMac 2010. working fine

I tried with another M6100 on a iMac 21.5 2011, and the bios was flashed correctly, is detected and the kext is loaded, but the display is not detected at all by the OS (11.6 bigsur) on a cold boot (using screen sharing to verify it). only after a reboot the screen is detected and everything works perfectly, including OC boot picker
Have similar problems with all GCN cards in the 2011 model.
Does sleep work with this card in your iMac 2011?
same issue on a iMac 24 2009. boots, gets kext loaded, but the display isn't detected at all on cold boot
This is because the 24 iMac 2009 uses a different internal connector type (LVDS vs. eDP in later models). No single vBIOS published so far will work. No solution available.
is there a way to delay the display detection via vBIOS? is there something we could do to fix it?
If we would know a way to fix it the solution would have been already published! So it is pointless to ask, it simply takes a lot of time and even access to machines like the 24 iMac 2009.

If you donate one I will start some tests ....
 
I don’t think i have a 3 pipe hetasink, i read 1st post..
Well, I doubt you did. If you have a HD6970M, you have a 3 pipe heatsink (unless the original card was previously replaced with a more powerful one without regard to heat generation). And if you don't have a 3 pipe heatsink, you cannot use the K4100M with the 2 pipe heatsink. So I guess you should take your time and read 1st post again.
 
Last edited:
I successfully applied your bios to a M6100 on a 27 iMac 2010. working fine

I tried with another M6100 on a iMac 21.5 2011, and the bios was flashed correctly, is detected and the kext is loaded, but the display is not detected at all by the OS (11.6 bigsur) on a cold boot (using screen sharing to verify it). only after a reboot the screen is detected and everything works perfectly, including OC boot picker

same issue on a iMac 24 2009. boots, gets kext loaded, but the display isn't detected at all on cold boot

is there a way to delay the display detection via vBIOS? is there something we could do to fix it?

thanks
Have similar problems with all GCN cards in the 2011 model.
Does sleep work with this card in your iMac 2011?

This is because the 24 iMac 2009 uses a different internal connector type (LVDS vs. eDP in later models). No single vBIOS published so far will work. No solution available.

If we would know a way to fix it the solution would have been already published! So it is pointless to ask, it simply takes a lot of time and even access to machines like the 24 iMac 2009.

If you donate one I will start some tests ....
Sounds to me as if the M6100 worked with the internal screen after a warm boot!?
 
Sounds to me as if the M6100 worked with the internal screen after a warm boot!?
I would say: It is not impossible to read this from what he was writing. But there is this phrase not at all which makes me believe he meant it did not work at all on the 24 iMac?

Let us wait for his answer.
 
I would say: It is not impossible to read this from what he was writing. But there is this phrase not at all which makes me believe he meant it did not work at all on the 24 iMac?

Let us wait for his answer.
Hi. Please Help
I have an imac 27 2011.
High sierra is now installed.
Replaced the video card with K3100m. it works, but the brightness is low.
I will install Big Sur. I want to install the current version of Photoshop.
I didn't understand
do I need to have OC and OCLP? or is OCLP enough?
 
Hi. Please Help
I have an imac 27 2011.
High sierra is now installed.
Replaced the video card with K3100m. it works, but the brightness is low.
I will install Big Sur. I want to install the current version of Photoshop.
I didn't understand
do I need to have OC and OCLP? or is OCLP enough?
Download OCLP and run it to install OpenCore onto your internal disk. Then follow the OCLP docs how to install Big Sur.
 
Just plain curiosity, have you read post #1 to this part (screen capture below)?
ROM1 is the latest ROM. The link is just there under your nose.

Normally we don't provide pre-purchase consulting in the public here, as each of us has his own bias in card selection. You will have to read post#1, including the performance table and make the decision yourself.

Funny enough, this thread has impacted the card sellers in China, too. They have had to refund so many cards that now they have put tripple lines in red: "This card is not for iMac, please do not buy this card to install on your iMac bla bla bla."

Other sellers asked for the laptop model of the buyer, and when knowing that I was intended to use it on an iMac, he tried to reject the order. I have had to assure him that I would not complain him or return the card if it wouldn't work on my iMac.

View attachment 1907364
Yes sir, I have read it, copied it for offline reading and have it handy to read again and again. Once again, I’m only trying to avoid mistakes.
 
You just made it to my ignore list - that was fast!
Your response makes me wonder if you’re part of the team who macrumors employs and are tied and bored with your job. Most people who choose to ignore someone don’t usually make a public announcement about it.
I’ve come here to ask for knowledge this thread is clearly offering and after politely asking I am ridiculed for doing so. Thank you very much.
 
I am sorry that my reply appears discouraging to you 😅
My point is just that you really need to read all the important info in at least the 1st post to get an idea of what you will be going thru. NO time isn't an excuse to skip that cause its success depends on more than luck but preparation with knowledge. Indeed, we wish you success in this project with the minimal troubles 😊 Thus the advice.
Okay, I do understand and realize what you’re saying. Again, I’m just trying to be careful.
Maybe if there was a date stamp on the ‘latest’ update I and would not have to wonder if it is truly up to date. Just sayin…
Yell at me, call me names, even ignore me but, I will always hold a great respect for those of you with knowledge and are willing to share.
 
Hello everyone, I'm trying to update to Monterey, installed the latest oclp, it is installed in a mac on the desktop, then it reboots, it takes 10 minutes and big sur is loaded, how can I evaporate
 
Okay, I do understand and realize what you’re saying. Again, I’m just trying to be careful.
Maybe if there was a date stamp on the ‘latest’ update I and would not have to wonder if it is truly up to date. Just sayin…
Yell at me, call me names, even ignore me but, I will always hold a great respect for those of you with knowledge and are willing to share.
Edit: with all my carefulness I somehow missed the date. ‘(Lastest update 11/09/2021)’.
 
Im sure this has been asked in this thread before but after hours of searching I havnent found what I need.

2011 iMac 21.5
DOS DUDE Catalina Patch running
K2000m with new vbios flash today

every boot ends in a black screen unless I reset the PRAM. This is an easy work around until I need to boot from a different drive like updating the OS. Hope someone can point me in the right direction. Thanks
 
Just installed a pre-flashed K3100M for my iMac12,2. To my amazement that it actually turned on and displayed everything including the boot screen. And it worked correctly with High Sierra including the brightness control (minus the full brightness issue for which I am yet to seek help later) and external display as a 2nd screen.
But the excitement stopped after booting into OCLP (v 0.3.1 / latest v0.3.2 nightly) Monterey (12.0.1). Each time when I tried to apply the Post-Install Volume Patch for Kepler, it failed with the error messages shown below.
I then booted with Big Sur (11.6.1) and half the menu bar not showing up and was told I don't need to patch anything when trying to run Post-Install Volume Patch.
Any idea?
Your help will be greatly appreciated.

- Downloading package
- 169.2537136077881MB Downloaded
- Download completed
- Unzipping download...
- Renaming folder
- Binaries downloaded to:
/private/var/folders/30/ppvxv7y52xxc0hp8rvgyjn0w0000gn/T/_MEIzfgTdq/payloads
Press [ENTER] to continue
- Found Root Volume at: disk3s5
- Mounting APFS Snapshot as writable
Password:
- Successfully mounted the Root Volume
- Running patches for iMac12,2
- Installing Kepler Patches
- Detected supported OS, installing Acceleration Patches
- Installing Kepler Acceleration Kext patches for Monterey
- Adding GeForce.kext
- Adding GeForceAIRPlugin.bundle
- Adding GeForceGLDriver.bundle
- Adding GeForceMTLDriver.bundle
- Adding GeForceVADriver.bundle
- Adding NVDAGF100Hal.kext
- Adding NVDAGK100Hal.kext
- Adding NVDAResman.kext
- Adding NVDAStartup.kext
- Installing legacy Wireless support
- Merging Wireless CoreSerices patches
- Merging Wireless usr/libexec patches
Press [ENTER] to continue with cache rebuild:
- Rebuilding Kernel Cache (This may take some time)
- Unable to build new kernel cache

Please report this to Github
Reason for Patch Failure:
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use 'com.apple.GeForce' because: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

com.apple.GeForce specific:

1: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

" UserInfo={NSLocalizedDescription=Error occurred while building a collection:

1: One or more binaries has an error which prevented linking. See other errors.

2: Could not use 'com.apple.GeForce' because: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

com.apple.GeForce specific:

1: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

}

checking collections...

Warning: com.apple.driver.KextExcludeList was not found!

updated extension 'com.apple.nvidia.driver.NVDAResman' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/NVDAResman.kext' (mach-o UUID changed from <unknown> to 879FE28C-BC88-3553-B3C7-1CCFAE357D45)

updated extension 'com.apple.nvidia.NVDAStartup' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/NVDAStartup.kext' (mach-o UUID changed from <unknown> to B7E8FE3A-5A44-3EA0-9A3B-345B583BFF31)

updated extension 'com.apple.nvidia.driver.NVDAGF100Hal' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/NVDAGF100Hal.kext' (mach-o UUID changed from <unknown> to 83ECEC97-996E-3E74-A930-5EF165210C51)

updated extension 'com.apple.nvidia.driver.NVDAGK100Hal' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/NVDAGK100Hal.kext' (mach-o UUID changed from <unknown> to CCDFB15A-E29E-38CE-A6C0-732F5648BC28)

updated extension 'com.promise.driver.stex' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/PromiseSTEX.kext' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)

updated extension 'com.apple.driver.usb.AppleUSBVHCICommonRSM' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/AppleUSBCommon.kext/Contents/PlugIns/AppleUSBVHCICommonRSM.kext' (mach-o UUID changed from <unknown> to 4DA8930B-6C41-3E17-8D1C-5525EA5981B7)

updated extension 'com.apple.GeForce' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/GeForce.kext' (mach-o UUID changed from <unknown> to B907167E-E164-36D8-9E8F-695A72E738F7)

updated extension 'com.apple.driver.AppleMobileDevice' found on disk at '/Library/Apple/System/Library/Extensions/AppleMobileDevice.kext' (mach-o UUID changed from <unknown> to <unknown>)

updated extension 'com.Areca.ArcMSR' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/ArcMSR.kext' (mach-o UUID changed from <unknown> to 01FC5EBD-0A34-3E77-9216-53B89DDD8CE4)

rebuilding release collections: boot, system
rebuilding release collections:
boot kernel collection
system kext collection
failed to build release collection:
One or more binaries has an error which prevented linking. See other errors.
Could not use 'com.apple.GeForce' because: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

com.apple.GeForce:

Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN27IOAccelLegacyDisplayMachine10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN24IOAccelLegacyDisplayPipe10gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN20IOAccelLegacySurface10gMetaClassE' to be defined in another kext

Please reboot the machine to avoid potential issues rerunning the patcher
Press [ENTER] to continue
Edit: added Spoiler
 
Last edited:
Well, I doubt you did. If you have a HD6970M, you have a 3 pipe heatsink (unless the original card was previously replaced with a more powerful one without regard to heat generation). And if you don't have a 3 pipe heatsink, you cannot use the K4100M with the 2 pipe heatsink. So I guess you should take your time and read 1st post again.
maybe I have not explained myself well, I own the Radeon 6970M, of this I am sure. So I have a 3 tube .. I reread the first post many times, I'm not an expert but I think I understand. If, on the other hand, I'm wrong, I think a correct behavior would be to correct my mistake .. and not keep telling me to read the first post. Peace.
 
Any idea?
Your help will be greatly appreciated.


Please report this to Github


Sorry for the long text because I can't attach this error report as an RTF file.
There are [SPOILER]long content[/SPOILER] tags to avoid such ridiculous long and unreadable posts!
You can always compress files and attach them.

There is already a clear action named in your long post. Nevertheless you choose to send this off topic post (it is about OCLP post install patching and not about the graphics card change) to this thread.
 
Last edited:
So i buyed the K4100M..! I'don't know if it's right, if there less compatibility with recent OS but with native boot, good metal performance and nothing to mod in the heatsink (for me it's more difficult).. now when i made the upgrade for the thermal paste is right the Artic MX-5? For GPU and memory bank..
Being 2 or 3 pipe has nothing to do with modding. It's just the amount of heat it can dissipate.

You'll have to mod the heatsink, look at pictures on first post. It's not that difficult, use a Dremel or similar tool to remove the parts you see on first post pictures.
 
There are [SPOILER]long content[/SPOILER] tags to avoid such ridiculous long and unreadable posts!
You can always compress files and attach them.

Now the part where I get disappointed, again:

There is already a clear action named in your long post. Nevertheless you choose to send this off topic post (it is about OCLP post install patching and not about the graphics card change) to this thread.

So please re read such error messages twice before posting!
Thanks for the advice. I've changed to <SPOILER>, which is new to me. I've also reported this issue to OCLP GitHub.
The initial thoughts were that this issue may be related to the newly installed K3100M card.

Add: Subsequently I tried to login to OCLP Catalina and applied the Post-Install Volume Patch. It only applied Sandy HD3000 patch. But it failed to login again even in safe mode: it keeps logout immediately after login. It's the same for Big Sur & Monterey now. I suspect it's more to do with the K3100M card than the OCLP because this iMac can run all of them with the stock HD6970. However everything seems working fine with High Sierra, even the full brightness after applying the AppleBacklightFixup.kext.
I am stuck now. If this K3100M card can only work with High Sierra, there is absolutely no point for me to buy this card in the first place.

Update: After following @Ausdauersportler 's suggestion, I can now login to Big Sur after rolling back to OCLP 0.3.0 and reinstalling Big Sur to get rid of any previously installed Post-Install patch (for the stock HD6970 card). Everything is working fine now including the Messages app, together with all the other apps like Maps, News, etc.
 
Last edited:
  • Like
Reactions: Ausdauersportler
maybe I have not explained myself well, I own the Radeon 6970M, of this I am sure. So I have a 3 tube .. I reread the first post many times, I'm not an expert but I think I understand. If, on the other hand, I'm wrong, I think a correct behavior would be to correct my mistake .. and not keep telling me to read the first post. Peace.

While others would have to guess, based on the information you provided, you have the chance to verify it yourself.
Just open your iMac and count the number of the copper pipes on the GPU heatsink.
Why didn't you do that already but post your question here then doubt every answer to it?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.