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.
Question on the OCLP install process

I've had my 12,2 working (almost always, save sleep issues) on High Sierra with a K3100M for a couple of months now and want to give Big Sur a go. Can I upgrade my High Sierra after I install OCLP with the Big Sur distro on a flash drive or do I have to reformat the whole thing and start from scratch and then migrate from the backup?

thanks
Apple has introduced mayor changes to APFS with Big Sur (so it is no longer possible to read Big Sur APFS from High Sierra).

From this perspective I hope/assume that doing such an upgrade from High Sierra to Big Sur will apply those changes on the fly.

But in general I do not like the idea of cascading endless OTA upgrades on top. So it might work, but you should have a backup in place and ready to do a fresh installation creating the new APFS with the Big Sur disk utility within the installer and restore user data.

Using High Sierra and Big Sur in parallel both installed on different APFS file systems is not a good idea since starting High Sierra is causing an unusable Big Sur preboot partition (you need to disable SecureBootModel to boot Big Sur). The latest versions of OCLP have it disabled anyway because of Monterey, but this may change in future blocking boot of an unusable preboot partition.

About the sleep issues with High Sierra:

1. Try to run your system without OC (and without full brightness) and observe sleep/wake
2. Try to disable spoofing when installing OC on your system while using High Sierra, only. (OCLP patcher settings) and observe sleep/wake
3. OLCP was never meant to run with High Sierra on the Mid 2011 with an NVIDIA GPU because it disables the iGPU and cut‘s away Airplay and some other features.

If your system cannot even sleep in case 1 it has a hardware problem caused by your new graphics card.
 
Hello everyone, I just asked for your help because I have a problem on my Imac 27 mid 2011 .
The graphics card being HS , I made a change for a Quadro K2100M .
Unfortunately the mac refuses to display anything, I accessed the imac with the remote control but it does not show me a video card .
I would like to point out that there are only 2 led presente on the computer.
The card has already been flashed and tested but it does not work on my imac .
You got any ideas?
I’m on hight sierra 10.13.6
Cordialy
 

Attachments

  • IMG_3187.jpg
    IMG_3187.jpg
    565.8 KB · Views: 131
  • IMG_3188.jpg
    IMG_3188.jpg
    514.7 KB · Views: 139
Hello everyone, I just asked for your help because I have a problem on my Imac 27 mid 2011 .
The graphics card being HS , I made a change for a Quadro K2100M .
Unfortunately the mac refuses to display anything, I accessed the imac with the remote control but it does not show me a video card .
I would like to point out that there are only 2 led presente on the computer.
The card has already been flashed and tested but it does not work on my imac .
You got any ideas?
I’m on hight sierra 10.13.6
Cordialy
1. Try to reset the PRAM (at least once, better three times in a row directly after switching on).

2. Try to pull the GPU from the slot and clean both slot and card (using alcohol) from dust. Try to reset the PRAM without the card installed. Reseat the card after cleaning.

3. Try to run the iMac without the internal LCD mounted and access your iMac remotely to see if the GPU has been discovered.

Your GPU should show three LED without the LCD installed if your have flashed the correct vBIOS.
This is not a plug and play solution, you need to be able to run some basic functionality tests on your own.
 
Apple has introduced mayor changes to APFS with Big Sur (so it is no longer possible to read Big Sur APFS from High Sierra).

From this perspective I hope/assume that doing such an upgrade from High Sierra to Big Sur will apply those changes on the fly.

But in general I do not like the idea of cascading endless OTA upgrades on top. So it might work, but you should have a backup in place and ready to do a fresh installation creating the new APFS with the Big Sur disk utility within the installer and restore user data.

Using High Sierra and Big Sur in parallel both installed on different APFS file systems is not a good idea since starting High Sierra is causing an unusable Big Sur preboot partition (you need to disable SecureBootModel to boot Big Sur). The latest versions of OCLP have it disabled anyway because of Monterey, but this may change in future blocking boot of an unusable preboot partition.

About the sleep issues with High Sierra:

1. Try to run your system without OC (and without full brightness) and observe sleep/wake
2. Try to disable spoofing when installing OC on your system while using High Sierra, only. (OCLP patcher settings) and observe sleep/wake
3. OLCP was never meant to run with High Sierra on the Mid 2011 with an NVIDIA GPU because it disables the iGPU and cut‘s away Airplay and some other features.

If your system cannot even sleep in case 1 it has a hardware problem caused by your new graphics card.
Not only High Sierra, even Catalina can't show the Big Sur and Monterey disks, since I have 3 internal SSDs, each of the respective macOS, and I can switch among them.

Agree that a fresh install of a new system is advisable. Backup is essential.
Nevertheless, I have my Monterey beta installed directly on top of High Sierra and it seems running fine upon the multiple OTA updates.

The only strange thing is that my Catalina remains at H1040 and can't see the Catalina Security Update 005 and later, Only Big Sur update is shown by System Update.
I suspect it may be related to OCLP spooling and Config.plist setting, but haven't investigated further since I really intend to migrate it to Big Sur / Monterey soon.
 
The only strange thing is that my Catalina remains at H1040 and can't see the Catalina Security Update 005 and later, Only Big Sur update is shown by System Update.
You need to set the CpuidMask and CpuidData (aka the VMM) flags as described on this post to get Catalina updates and Monterey updates after B7.

You can disable it after the successful update (by deleting one value and keeping the other to be able to copy it back on the next update).
 
  • Like
Reactions: KennyW and m0bil
If your system cannot even sleep in case 1 it has a hardware problem caused by your new graphics card.

Thanks for the thoughts on Big Sur. I'm with you that I'm hesitant to apply lots of upgrades on top of each other, although this High Sierra was a clean install. I have a couple of spare HDD's (left over from upgrading all of my iMacs to SSDs) so I'll make a full backup of my disk and then just transfer all ofmy stuff after the install.

I'm not using OCLP right now to boot High Sierra, don't need it. I'm not displeased with the brightness as I don't keep it that bright anyway so saw no need.

The sleep issue is, I'm sure of it, related to the hardware. The system also has this weird tendency to not power on after the power has gone off or I've done a full shut down. Some things I've discovered over the months:

  • If I "reboot" the system will restart, if I shut down and have to push the power button it won't
  • if the power goes off the system won't easily restart
  • If after the power off/shutdown I wait a few minutes I have a much better chance of it booting than if I try right away
  • pushing the power button a couple of dozen times, 2-seconds or so between pushes will usually get it back, but waiting 5 minutes almost always gets it on the first push.
I had none of these issues with the 6970M that used to be in the system but failed on me. I baked it once but that was not long lasting, which is how I ended up here. The lack of booting is not that big an issue for me so I just don't allow the system to sleep.

Oh and I was going to try the K3100M in my 2010 11,3 iMac but I got tired of taking it apart trying to get the GTX880 that I had working in it. That card would not POST at all in the 12,2 but it did turn on and I was able to log in via Linux to flash the ROM but it has issues (photo posted earlier) so I gave up on that one. And the 11,3 is now at my store being used so I'm not taking it apart anymore.
 
it will not let me cd into the directory. idk what im doing wrong can someone help me out please
 
You need to set the CpuidMask and CpuidData (aka the VMM) flags as described on this post to get Catalina updates and Monterey updates after B7.

You can disable it after the successful update (by deleting one value and keeping the other to be able to copy it back on the next update).
Thanks. It does work ! Always something to learn from our coding masters ;-)
Unable to study deep and wide on this subject of Opencore o_O

Screenshot 2021-10-08 at 9.30.45 PM.png
Screenshot 2021-10-08 at 9.46.26 PM.png
 
idk what to do cause this is the error im getting:

NVIDIA Firmware Update Utility (Version 5.414.0)

Simplified Version For OEM Only
Checking for matches between display adapter(s) and image(s)...
Adapter: NVS K1 USM (10DE,0FE6,103C,2256) H:--:NRM S:00,B:01,D:00,F:00
NOTE: Only IFR present:
NOTE: Skipping Board ID and Device ID checks.
NOTE: EEPROM does not contain board ID, skipping board ID check.
WARNING: None of the firmware image compatible PCI Device ID's
match the PCI Device ID of the adapter.
Adapter PCI Device ID: 0FE6
Firmware image PCI Device ID: 0FF6
WARNING: Firmware image PCI Subsystem ID (1028.15CC)
does not match adapter PCI Subsystem ID (103C.2256).

NOTE: Exception caught.
Nothing changed!
ERROR: GPU mismatch
 
Hi All
idk what to do cause this is the error im getting:

NVIDIA Firmware Update Utility (Version 5.414.0)

Simplified Version For OEM Only
Checking for matches between display adapter(s) and image(s)...
Adapter: NVS K1 USM (10DE,0FE6,103C,2256) H:--:NRM S:00,B:01,D:00,F:00
NOTE: Only IFR present:
NOTE: Skipping Board ID and Device ID checks.
NOTE: EEPROM does not contain board ID, skipping board ID check.
WARNING: None of the firmware image compatible PCI Device ID's
match the PCI Device ID of the adapter.
Adapter PCI Device ID: 0FE6
Firmware image PCI Device ID: 0FF6
WARNING: Firmware image PCI Subsystem ID (1028.15CC)
does not match adapter PCI Subsystem ID (103C.2256).

NOTE: Exception caught.
Nothing changed!
ERROR: GPU mismatch
If you understand what you are doing, and the only problem you have is flashing firmware complain, then you can try to use nvflash_5.692_linux which doesn't perform verification - I was able to use it to flash bios with different ID
 
Hi All

If you understand what you are doing, and the only problem you have is flashing firmware complain, then you can try to use nvflash_5.692_linux which doesn't perform verification - I was able to use it to flash bios with different ID
tried it and now im getting this error:
ERROR: GPU PCI Device ID mismatch
 
tried it and now im getting this error:
ERROR: GPU PCI Device ID mismatch
Try this (which is part of the original docs made by @xanderon):

Code:
./nvflash_linux --protectoff
./nvflash_linux -6 NEWBIOS.rom

If this fails you need to buy a CH341A clip programmer and use the flashrom software.
 
In the past month, @edwardgeo, @internetzel, @m0bil and me had some very fruitful conversations. Result: We now have (a) workable solution(s) to make various makes of AMD WX4130/WX4150/WX4170 cards function properly in all iMacs from the iMac11,1 - iMac12,2 range! ('Big' WX4170 cards only fit 'big' iMacs, of course!) I have updated my original posts, so if you just want to know what to mod, simply visit the WX4130/WX4150 mod post or the WX4170 mod post. Curious types - read on below.
As I have reported in my HP WX4150 mod post, and @m0bil reported later for a Dell WX4130, some of those cards caused 'SMC confusion' in iMac11,2. I also found that the (originally) modded HP WX4150 will not POST in an iMac12,1. We found the culprit: All problematic cards have a temperature sensor IC, TMP431B (with top marking DUFC) present. This IC is connected directly to the iMac's SMC "0" SMBus. The problem: I2C address of this IC is 0x9A/0x9B, which is also the address of the TMP423B on iMac11,2 logic board (on the same bus). This causes a so-called 'address collision' and consequently 'SMC confusion'. My proposed solution: Disconnect TMP431B (on the dGPU) from SMBus to remove the offending I2C address. Luckily, there are two jumpers on the WX4130/WX4150 we can remove to achieve that. And it works!

View attachment 1856617
Surprisingly, this also works in iMac12,1 - and it POSTs and runs with that (additional) mod. I do not have an explanation why it works in this machine - possibly some SMC code 'remnant' from previous generation tries to read from that offending address, preventing the machine from POSTing.
Would, alternatively, simply removing the IC with that offending I2C address from the dGPU also work? I don't think so. (And it did not work in one iMac12,1 case.) There are other (safety) signals from that IC directly connected to the MXM connector, which can prevent the computer from POSTing when absent. While there are WX4130/WX4150 cards without that IC, they have different placing of some other components to route appropriate signals to the MXM connector.
While I was trying to upgrade my iMac11,1 with a modded (originally EEPROM-less) WX4170 I encountered a whole lot of issues - the machine would not POST, but it did allow a PRAM reset and did POST after that. While running macOS it would randomly shut down and wouldn't POST again until another PRAM reset. I (again) traced the problem to the TMP431B temperature sensor IC present on that card. Again, we have that IC on the iMac's SMC "0" SMBus, along with EMC1402-2 on the iMac logic board on the same I2C address (0x9A/0x9B), ie. another address collision. Proposed solution: Disconnect TMP431B (on the dGPU) from the SMBus (again). Luckily, WX4170 also has appropriate jumpers to do that!

View attachment 1856619
I still don't have an explanation why the (modded) HP WX4150 did not cause such problems in iMac11,1 and iMac11,3. Maybe it's a combination of other additional factors...
Possibly. Maybe replacing the temperature sensor IC (TMP431B on those cards) with a supported one would work. I tried to do this with an ADM1032, but it did not report the temperature to SMC. (Even though ADM1032 is used on Apple's HD 6970M.) Another possibility would be EMC1402-1 (or maybe even TMP431A). (Currently both unobtainable at my usual suppliers.) If any of these ICs (in place of the original temperature sensor IC on those AMD cards) actually works, it should even report the appropriate temperature to SMC, which would make SMC properly control iMac's fans wrt. GPU temperature. Anyway, @Ausdauersportler 's ODD temp. sensor solution (probably) keeps the GPU even coller, so I won't be investing more time into such experiments.
I'm also happy to report that no GPU was damaged/broken during all the experiments and tests @edwardgeo, @m0bil and I did. One came close, though.

My purchased WX4170 appears to have no EEPROM chip at U10 position, but it has a slightly different board
1. The zero ohm resistor R1342 is on the back. (upper right, surrounded by a red rectangle)
2. I couldn't find the location of R2 resistor, no IC chips around that area, too.
3. the RP1 resistors group has already been soldered.

I will report the result when plugging it in my iMac 2009 and 2010.
Proceed to buy the EEPROM chips for soldering and testing if iMac don't recognize the card.
 

Attachments

  • WX4170_back.jpg
    WX4170_back.jpg
    669.5 KB · Views: 124
  • IMG_0013.JPG
    IMG_0013.JPG
    682.2 KB · Views: 128
  • Like
Reactions: m0bil
My purchased WX4170 appears to have no EEPROM chip at U10 position, but it has a slightly different board
1. The zero ohm resistor R1342 is on the back. (upper right, surrounded by a red rectangle)
2. I couldn't find the location of R2 resistor, no IC chips around that area, too.
3. the RP1 resistors group has already been soldered.

I will report the result when plugging it in my iMac 2009 and 2010.
Proceed to buy the EEPROM chips for soldering and testing if iMac don't recognize the card.
This one is very similar to one of the WX4170 cards I have. It looks like it's only missing the EEPROM chip. (Edit: It looks like it also has that dreaded temperature sensor IC present...) I have attached photos of my card, maybe they'll be helpful. (I do suspect you'll need to solder that EEPROM onto the card... I also suspect it is that lower grade WX4170, which will only work reliably with the lower clocked - WX4150 - ROM.)
 

Attachments

  • IMG_0154.jpeg
    IMG_0154.jpeg
    631.8 KB · Views: 141
  • IMG_0157.jpeg
    IMG_0157.jpeg
    692.6 KB · Views: 118
Last edited:
  • Like
Reactions: Nguyen Duc Hieu
Why would you want that?
Try the ROM1 link from the first post; there I uploaded a WX7100 GOP VBIOS that should work well.
I tried your bios - it works.
But, your bios is 2016. And my original bios is 2017. More recent. It will be better if it is modified. Thanks.
 
This is a GTX 880m pulled from Clevo the seller says. What I want to know before I buy it, is it flashable so I can get it to work in my iMac mid 2011 27"?


Screenshot_20211009-135723.jpg
 

Attachments

  • Screenshot_20211009-135740.jpg
    Screenshot_20211009-135740.jpg
    428.4 KB · Views: 93
  • Screenshot_20211009-135749.jpg
    Screenshot_20211009-135749.jpg
    642.8 KB · Views: 95
  • Screenshot_20211009-135825.jpg
    Screenshot_20211009-135825.jpg
    661.6 KB · Views: 93
  • Screenshot_20211009-135838.jpg
    Screenshot_20211009-135838.jpg
    465.4 KB · Views: 98
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.