Fyi, thanks to @Santa's Little Helper we now have a working m4000m vbios with GOP allowing for boot screen under rEFInd and OpenCore!
M4000M with GOP
M4000M with GOP
Slight differences in same model GPUs manufactured by different vendors makes the whole process a lottery, on a recent GTX880m install I did, on a 2011, the card works beautifully except it has broken the sleep/wake function of the iMac. Nothing I have tried fixes it, it’s happened to only a few other users on this forum with 880 installs.
So yeah the model of iMac also changes the variables the wake problem might be non existent in a 2010 or the card might not even post in a 2009.
Not a great deal you can do about it except learn how to mod roms and potentially fix it yourself or hope a dev can help.
Really good idea to save the original rom.
Yeah, I screwed that one up when I let OCLP patch my thumb drive with the backup rom on it.I had to flash a few different vbios until I found a working one. On my m4000m it only worked correctly with the stock vbios, which we now have GOP added.
You should be able to download it from techpowerup.comYeah, I screwed that one up when I let OCLP patch my thumb drive with the backup rom on it.
the rom for my specific card is up there. At least I had written down the subsystem ID…You should be able to download it from techpowerup.com
Does yours also take like 40 seconds when initializing the windows driver?Slight differences in same model GPUs manufactured by different vendors makes the whole process a lottery, on a recent GTX880m install I did, on a 2011, the card works beautifully except it has broken the sleep/wake function of the iMac. Nothing I have tried fixes it, it’s happened to only a few other users on this forum with 880 installs.
So yeah the model of iMac also changes the variables the wake problem might be non existent in a 2010 or the card might not even post in a 2009.
Not a great deal you can do about it except learn how to mod roms and potentially fix it yourself or hope a dev can help.
Really good idea to save the original rom.
Try a PRAM reset whenever you plan to boot into a different (new or old) OC version.
Not entirely clear to me what your problem and your current plan is. So it would be really nice to have a:Tried PRAM reset several times, same issue. I still get the circle with line through it, at about 1/3 of the progress bar.
Is this the race condition bug I read about? Do I just need to keep booting back into the installer several times to get it to work? I don't think so because I haven't even started the installation, just trying to get into the installer.
My High Sierra is installed in an APFS volume. Could that be the issue? I would think I should still be able to get into the installer though.
I'm able to launch the Big Sur Installer GUI from inside High Sierra, and when I choose an APFS volume it says I need a firmware update. OCLP docs say that means I need to set SMBIOS mode to Moderate. So I rebuilt my OC with that setting and tried to boot into the Big Sur Installer again and still same problem. Doing a PRAM reset every time.
I am using the OCLP terminal UI to build and install it.
Not entirely clear to me what your problem and your current plan is. So it would be really nice to have a:
Where I am? Where would I like to go? What is my planned path to achieve this?
Do you want to OTA upgrade an existing High Sierra installation to Big Sur? Or do you try to start an Big Sur installer application from the running High Sierra to install into another APFS partition?
1. Never share the same APFS container for High Sierra and Big Sur!
2. Try to create an USB installer (USB stick or USB disk) to install Big Sur, this way you do not need to use moderate spoofing in the middle of the process. Moderate spoofing is needed to install Mojave and Catalina, but not to run it.
3. Try to install OCLP on your single internal SSD (makes it faster and more reliable to use).
4. On the long run get rid of High Sierra if you can. Booting into HS overwrites some parts of the Big Sur preboot partition and makes it unbootable - you would need to disable SecureBootModel to get it working, again.
5. The OCLP docs always writes about using an USB installer - there is a complete section about this. Do not use short cuts.
6. When you successfully started the Big Sur (Monterey) installer use the internal new disk utility to delete (aka re-create) the target AFPS partition/container. You may share an APFS using multiply container between several Big Sur and Monterey installations.
Only pre 2011 systems suffer of the race-condition named problem so far.
Having an EFI Boot screen you always can force a PRAM reset on boot, press option after the second chime and finally select the High Sierra partition directly without using OpenCore.I would like to move from High Sierra to Big Sur and have a blank installation of High Sierra so I can still use target display mode or for emergencies. Right now I'm just trying to see if I can get Big Sur working on my machine. If it does work then I will transfer all of my files and apps to it and remove the High Sierra APFS volume and reinstall High Sierra in a HFS+ partition.
I am using an external USB drive for the installer. I also have installers for High Sierra and Mojave on the same drive in separate partitions. The external drive also has the OCLP EFI partition on it.
I'm hesitant to install OCLP on my internal drive until I can verify that Big Sur works. I still want to use High Sierra in case it doesn't work.
So far I can't even get into the Big Sur installer. Thanks for the help. Maybe I should ask in the OCLP forum.
Having an EFI Boot screen you always can force a PRAM reset on boot, press option after the second chime and finally select the High Sierra partition directly without using OpenCore.
The complete SD story has only been created to give the AMD users a chance to survive a bad OC installation somehow. Using an OC Recovery CD makes even this superfluous. I have all the SD cards lying unused on the desk these days.
OCLP will (being used) disable the iGPU, so you will loose some functionality like AirPlay. Unfortunately I could only bring back the HD3000 and Airplay with the old ATI GPU on Big Sur but not using an Nvidia Metal GPU - it would have needed root volume patching. Another project....
Big Sur will work, there is no doubt about it. When booting OC the first time press CRTL on select to make it the default boot choice. Otherwise you will need to sit in front of the keyboard all night long to boot through OC every time by hand.
The Big Sur installer it is a stock one, right?
Haven’t tried boot camp, running windows with Parallels atm.Does yours also take like 40 seconds when initializing the windows driver?
Did you check which memory the K2100M has and did you flash the correct vBIOS version?Ok, that makes sense. Thanks for the info. I don't need Airplay, just want to keep target display mode if I can.
The actual problem I'm having is I think something is wrong with my K2100M. I get random kernel panics in Mojave, while High Sierra is completely stable, but sometimes randomly the entire menu bar or some menu bar icons will turn completely black for a few seconds before fixing itself. I'm guessing there is some bad video memory or something. I am totally fine with this, but I wanted to see whether Big Sur would also kernel panic, or whether I need to buy another K2100M.
I got the Big Sur installer from the python script on this page: https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER.html#downloading, and then I ran the createinstallmedia command. It's Big Sur 11.5.2.
This special card will work perfectly and it will perform exactly as good as the K3100M.Hello! Apologies if I'm being dumb, but why is the Nvidia GTX 675MX not listed as a working card in the first post? I am considering buying a pre-flashed one from Nick [D]vB on eBay and I'm curious about the performance vs other options. Thanks in advance!
It’s not listed because only cards with free community accompanying vroms are uploaded so users here have an as OEM experience as possible.Hello! Apologies if I'm being dumb, but why is the Nvidia GTX 675MX not listed as a working card in the first post? I am considering buying a pre-flashed one from Nick [D]vB on eBay and I'm curious about the performance vs other options. Thanks in advance!
Aha, thanks for the information. I'd be interested if anyone has any links to benchmarks for the 675MX 4GB in a 2011 27", I'd love to see them.It’s not listed because only cards with free community accompanying vroms are uploaded so users here have an as OEM experience as possible.
Nick used to upload roms here but now uses his talents for his own business and rightly so.
Did you check which memory the K2100M has and did you flash the correct vBIOS version?
Firewire boot is broken or unsupported sinceSo I found the solution. And yes pretty sure I have the SKhynix memory with ROM #1.
I went to try installing Big Sur on my MacBook Pro 7,1 and I thought surely this will work, but same exact problem getting into the installer. Then I realized, I'm actually using an external FIREWIRE drive! Could that be the issue? YES! If I simply plug it in with a USB cable then I can load the installer.
Wow. So, maybe someone should document that. Installer works with USB drive, not FireWire.
Thanks for your help @Ausdauersportler
In principle all MXM cards can run somehow in these iMacs. But this card is rated with 100W and needs surely a modified vBIOS to avoid over heating on load and more importantly there has been no other user testing this card before and it is unclear if you will face problems like we had/experience with other AMD cards, i.e.:Does anyone know if this would work in the imac 2011
Synergy AMD FirePro S7100X MXM taken from an HP machine?
Firewire boot is broken or unsupported since Mojave came up, but you can re-enable it using OCLP (I assume hidden in the patcher settings).
There is no need to document something what is already well known to the public.
Replace Mojave with Catalina. FireWire boot has been disabled by Apple with Catalina. Sorry about the confusion.I suggest mentioning it in the first post in the OCLP instructions. I've been reading this thread for several years and I didn't know that.
I've been using the FireWire drive successfully to install and update Mojave on my MacBook Pro 7,1 for a few years, so I don't know what you mean. Installing Big Sur is the first time it's been a problem for me.