You mind trying the same Kext but from the "old.zip" upload, a change was recently made to the Kexts that had no issues on my end.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iM 4,1-14,4 2011 iMac Graphics Card Upgrade
- Thread starter MichaelDT
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
That did it! Thanks so much for the amazing work and quick responses!
I did see that zip, but wasn't sure if it was a backup of the original AGC or the older modified version - I didn't want to break anything further without direction.
Let me know if you need me to test anything to see why the new version didn't work on my setup.
Well that means some things need to be looked into @Pascal Baillargeau (not asking you to, sorry) I need to go re-create a 2011 21.5" k2100m iMac to test this issue further.
Last edited:
We simply changed Board-id to Board-ix on the latest release to help with AMD cards. (white screen) The Kext was working fine on my 27" 780m/k4100m iMac. I just need to make another k2100m/21.5" iMac to test the issue.
Last edited:
Judging by recent feedback, they may only be selling a link to this thread not an actual file.
in my case with K5100M (@nikey22 vbios flashed) both ThunderBolt ports are working but not at same time
Sorry, for being stubborn on that 
...but I'd really like to participate, but we definitely need some common repository for all the stuff that's being developed, including original ROMs and all subsequent versions of the modified ones.
Maybe @nikey22 has such private repo? If not, I think it would be a good idea to create one (on GitHub or BitBucket) and put all the stuff there instead of linking certain posts within this thread.
I know I'm new here, do not get me wrong - just trying to improve things...
...but I'd really like to participate, but we definitely need some common repository for all the stuff that's being developed, including original ROMs and all subsequent versions of the modified ones.Maybe @nikey22 has such private repo? If not, I think it would be a good idea to create one (on GitHub or BitBucket) and put all the stuff there instead of linking certain posts within this thread.
I know I'm new here, do not get me wrong - just trying to improve things...
Stubborn is probably correct. You cannot force other people to share their knowledge and time just to satisfy your curiosity.Sorry, for being stubborn on that
Maybe @nikey22 has such private repo? If not, I think it would be a good idea to create one (on GitHub or BitBucket) and put all the stuff there instead of linking certain posts within this thread.
I know I'm new here, do not get me wrong - just trying to improve things...
There is no such guide how to modify a BIOS. But if you spend the same time in the BIOS development as others did before you are free and welcome to write such a guide on your own...
Sharing original copyright protected original ROMs on a public platform is a really cool idea, what comes next: Sharing of hacked software? You may use the well known search machines to find other platforms doing this, I know at least one. And if you are really able to help this thread you will find this platform on your own. It has been named here several times.
You can improve things a lot here by answering other people posts and questions...
@Ausdauersportler sure I can begin from scratch and do all the work on my own. It's just wiser to build up on others experience instead of having several people working maybe on the same stuff and not willing to share their findings... That reminds me the old times when many coders were squeezing amazing things out of the 8 and 16 bit computers and competing on demo scene between each other...
But... got the message, thanks.
Have already found the vBIOS Collection and will start working on k2100 and k610 from scratch... If I get any useful results, I will certainly publish the guide which will surely improve the chance other GPUs will get sooner and better support.
But... got the message, thanks.
Have already found the vBIOS Collection and will start working on k2100 and k610 from scratch... If I get any useful results, I will certainly publish the guide which will surely improve the chance other GPUs will get sooner and better support.
Just checked your issue using the old 10.15.6 version of AGC @highvoltage12v added back to his post on my iMac 2011 21.5" with a K2100M, Catalina 10.15.6 latest (19G2021).
Using this AGC you can boot into Catalina directly without a black screen (and without brightness control). Honestly I cannot see a real issue here since you always have been able to force the screen to come up using alt/option on boot.
Talking about OpenCore an Lilu and Whatevergreen: The two extensions are developed and maintained by different people on a different platform. I cannot and will not keep track of this day by day, so you have to check for new versions on your own.
EDIT:
The new version (including the agpmod=pikera) of the 10.15.6 brings back the black screen on the system. At the same time all combinations tested this morning lead to low Valley scores because the GPU does not boost properly. Sometimes it stucks at 135 MHz, sometimes at 405 MHz instead of max 810 MHz. To solve this one needs a modified version of the AppleGraphicsPowerManagement extension which is ready and in use here and @highvoltage12v will probably publish it during the next hours, again.
Last edited:
This is not longer stubborn, it has become a simple insult: "not willing to share their findings"!
You cannot claim others knowledge to become public on request because it needs a lot of time to write it down in a way others understand it. You can ask politely and if you get no answer or not the answer you expected than I would recommend to spend your personal own life time into this and do better.
Try to understand the situation here: We have approximately 20+ BIOS version for different card types. Some rely on additional software like OpenCore (available in different versions). Some are widely unknown (AMD EG BIOS), because most readers here are consumers and not able to do complicated software or firmware modifications.
We have patched extensions for at least 5 different machine types. How would you organise this on a single (different) platform without a sophisticated entry page listing all the options and choices as the first page here?
Before claiming to be able to improve things I would start to dig into the f***ing details....
Well, maybe I'm used to work with different conditions and rules, where people share their knowledge with others who want to contribute... I was going to offer my help as a developer. I was just asking for some tips about with what and where to start with. I could also think of organizing that whole stuff in a usable way. If that would require developing a custom frontend to a git repo backend - what a problem?
I know I'm new here, but with a lot of experience in IT. Have been joining many teams before and was including people into my teams. Sharing the current knowledge is a key thing and it's obvious for me. But of course I can respect the fact that it is not obvious for everyone in the same way... I'm a straightforward person, asking simple questions and hoping for simple answers. If @nikey22 was not going to share his knowledge to me or provide any tips, he could have simply said that.
Anyway, the last thing I was going to do was insulting someone, but if anyone took it this way - my apologies. I'm surprised this escalated here so much...
Last edited:
You are welcome to contribute based on your knowledge and experience. All the other regular contributors on this thread do it in the same way. I like writing docs, I do not like reverse engineering binary BIOS code without documentation from a manufacturing company like Nvidia or AMD. Unfortunately it seems to work in exactly this way. Software development using an IDE and tons of documentation is a kinder garden task compared to this.
Sometimes even asking a question crosses an invisible line. Better going one step back than three ahead unless you know the guys you are talking to.
Last edited:
Attachments
First why are you using a DVD?
Second, is this Version 2004? Rufus hasn't been working well with version 2004. Even on Some ivy bridge Dell PC's it will hang. I'm trying the official windows Download Tool now.
Do you have the white display AFTER installing Windows or when you try to do this?
If you still can run your OSX, go there, install VirtualBox and validate your install DVD there.
If you cannot boot at all, use either OpenCore or rEFInd to get the boot partition selection.
When I try - I cannot install and don’t see setup window , only white display
After upgrade I had been installed Windows on HDD and it also didn’t start.
It was said me that I must forget about bootcamp installation and try flash boot in uefi, made by rufus. Only Windows 10, not 7 with flash in uefi. Another one way is Virtual Box way, but I can’t imagine how to do it.
I download official windows 10 from Microsoft official. I don’t understand what 2004? It’s 2011, not early made. Windows 10 it for iMac 2011 same way to do windows setup, but with my modification I don’t think so that I can install win 7, Catalina said me only win 10, but I can’t start installation. I will try with rufus uefi iso, how it was said me.
Now my Mac in service center, after 1-2 days I will take it back and will trying. They also cannot fix it and thinkin bad bios, but I not think so.
2004 is the new version number. Windows 10 was in the 1900s for the longest time.
Use the Windows 10 Media creation tool to create a USB installer of Windows 10. Do not use Rufus, do not use a DVD. The installer loads just fine for me over USB
Attachments
There are quite many guides on the Net how to do that - it's pretty simple, you just create new Virtual Machine in VirtualBox, choose guest operating system, virtual drive size, and then you need to mount your DVD or even better the ISO installer and it should run fine.
However, indeed first try what @highvoltage12v suggests. Take your iMac back from service - that may be beyond their standard servicing procedures
I prefer VirtualBox. Less rebooting and faster access to Windows. I could see how you might need to dedicate the computer resources to Windows tho.There are quite many guides on the Net how to do that - it's pretty simple, you just create new Virtual Machine in VirtualBox, choose guest operating system, virtual drive size, and then you need to mount your DVD or even better the ISO installer and it should run fine.
However, indeed first try what @highvoltage12v suggests. Take your iMac back from service - that may be beyond their standard servicing procedures
At some point they (service center/poster) will also need to Disable the HD3000 GPU in safe mode as well, hope either party is capable of doing this. You'll end up in an endless BSOD if you don't, these iMacs were never designed for EFI copies of windows 10... Also plan on using an external DAC in windows 10, unless you want to disable driver signing and follow a moderately difficult DSDT patching guide...