Seems on par with same models.Check your Geekbench5 score, could be CPU throttling?
I notice in your sig, you have a very similar machine. Have you tried running Big Sur or still on Mojave?
Seems on par with same models.Check your Geekbench5 score, could be CPU throttling?
What are the benefits of this test build as compared to the listed one in the table ?TEST BUILD WX4170
4170 build for testing based on method used in 4150 latest custom build. If iMac 2011 requires output patching, please send me correct Object_info and TV_OutInfo modules, i will make 4150/4170 iMac builds.
***
P.S. Report of success or failure on gpu. Planing to stop creating new builds as already have successfully working vbios.
That build is working on Catalina and higher. I am not iMac 2011 user, but sharing results with community.What are the benefits of this test build as compared to the listed one in the table ?
Does it support native Apple BootPicker and support BootCamp Windows installation as well ?
What do you mean, saying “corruption”? The efi (extended bios) contain images, drivers) that understand filesystems. But as far as I know, the Mac bootloader use efi partition and boot from it? Or bootloader is located in efi platform bios?Big Sur preboot corruption
This is a short update about the preboot corruption when using High Sierra and Big Sur and later in the same machine. During the last month @internetzel had never experienced this problem with his iMac11,1 although he regularly uses High Sierra. The main difference to my own setup:
While I am using APFS only he is using HFS+ with High Sierra on his external USB connected HDD. So this seems to be the key. BTW HFS+ is faster on HDD, too.
If you still want or need to have a High Sierra installation (working target display or just a fall back) then simply use a 20-40GB HFS+ partition instead of APFS. If you manage to place it as the first partition of the internal single SSD it will be the installation where the iMac boots into after a PRAM reset automatically (great help for owners of AMD cards without an EFI Boot screen).
I have changed the first post according to this. Please report back if you have different experiences.
Here is a simple overview about the Apple PRAM.What do you mean, saying “corruption”? The efi (extended bios) contain images, drivers) that understand filesystems. But as far as I know, the Mac bootloader use efi partition and boot from it? Or bootloader is located in efi platform bios?
OpenCore is installed?
What is pram? That is alternative name to cmos?
The Amd users don’t have a boot screen? I was having this problem on Mac Pro 3... with newer gpu (GTX285) but one guy done something that unlock the the boot screen... hmm. I think that this was made with bios and vbios modding...
It’s s running Catalina and HS with no issues.Seems on par with same models.
I notice in your sig, you have a very similar machine. Have you tried running Big Sur or still on Mojave?
Boot screen in fact is gop driver and as far as I know that Apple bioses are not secure, so why not to try to replace graphic driver to the newer system in fact that will add support for part list too. As far as I know the mod of partlist will add support for gpu.Here is a simple overview about the Apple PRAM.
When I write about the preboot corruption than I mean the so called APFS preboot partition where the boat loader finds some data before the macOS boots starts up.
Starting High Sierra in coexistence with Big Sur changes the preboot volume in a way Big Sur and Monterey cannot use it with SBM (SecureBootModel).
OpenCore has to be used with AMD cards (enabling 4K H.264 and 4K HEVC) and is installed.
--
Yes, there is no EFI Boot screen support available with AMD Polaris, Navi, Vega GPU in Apple Macs. You we rely on the OpenCore boot picker and other enhancements. This works wonderfully as long as you carefully manage OC config changes or complete upgrades. Loosing the boot picker gets you a black screen on our iMac and no way to control the boot sequence (like in normal PCs using some BIOS settings).
You cannot even force the iMac to boot from an external device.
This complete thread is mainly about making the cards working within an iMac and at least for all Kepler cards listed on the very first post @nikey22 (and others) can claim there is a complete support for EFI boot screens.
What video input connectors are present on the display? What adapters and cables are you using to attach it to your MacBook Air, and what adapters and cables are you using to attach it to your iMac?Hi.. hope everyone here is fine. I am not sure if someone experienced this before or was this already solved in this thread because upon using the search button, there is no relevant answer to what i am experiencing now.
I am now trying to make a dual monitor setup with my 27inch mid 2011 imac with k3100m gpu running nikey22's rom from page 1. My external monitor is an AOC Q27P1 which is capable of 2560x1440 (tested it with my macbook air 2018) but when plugging that monitor to my imac, i can only get a maximum of 1920x1080 resolution.
Thanks for the reply... you may be right... this may be caused by the mini display port adaptor that i am using to connect the HDMI cable between the imac and the monitor but i have no way to confirm this as i dont have another high res monitor to test it out... I will try another adaptor and hopefully will be able to get max resolution in external monitor.What video input connectors are present on the display? What adapters and cables are you using to attach it to your MacBook Air, and what adapters and cables are you using to attach it to your iMac?
According to the specs linked below, the K3100m should in theory be completely capable of driving a screen with this resolution. One potential cause for this problem would be if you are using some complex dongle combination that includes VGA. This would have the potential to limit the maximum resolution to 1080p.
NVIDIA Quadro K3100M graphics card - Quadro K3100M - 4 GB Specs
NVIDIA Quadro K3100M graphics card - Quadro K3100M - 4 GB overview and full product specs on CNET.www.cnet.com
Have you gone to the system preferences and tried to adjust the output video resolution? You may need to select the "Scaled" button in order to see a 1440p option.
If you have access to another >1080p monitor, it may be useful to try connecting to it for testing.
I've read the last few hundred pages of this thread, and I've never heard of anyone encountering a similar issue, so I think this may be more closely related to a problem your display setup than with the GPU upgrade. Hopefully, you will be able to find a combination of connectors that get this working as expected!
Check first page, first post, FAQ, Q6! Something is surely broken at your side.Thanks for the reply... you may be right... this may be caused by the mini display port adaptor that i am using to connect the HDMI cable between the imac and the monitor but i have no way to confirm this as i dont have another high res monitor to test it out... I will try another adaptor and hopefully will be able to get max resolution in external monitor.
Can you describe what exactly your problem is?I managed to start the Big Sur installer with OpenCore Legacy Patcher (iMac 21.5 mid 2011 with Dell WX4150 flashed), I have put back the old AMD card and it boots without any problem to the initial configuration. What could be the problem?
PS: I have seen that the only one who has the same card is StephN999
Can you describe what exactly your problem is?
I am struggling to understand the "managed" and the need to change back the old AMD GPU afterwards?
Did the iMac boot using the new WX4150 or not?
Could you install and boot OpenCore or not?
Could you install Big Sur (or not)?
Why changing back the old GPU?
You need to run the OCLP app and configure OpenCore while the new AMD card installed! Otherwise the hardware detection of the OCLP app only sees your old AMD card and creates a wrong config.Before that I flashed the new image (GOP BIOS) via SSH and it flashed without any problem.
- Yes, my iMac booted with the new graphics card.
- I booted Opencore, formatted the SSD in APFS (because I changed the hard disk I had).
- It restarts 3 times without any problem and it comes out with several minutes left.
- At the last restart, verbose mode appears and then the screen goes black.
- If I put the old graphic card, I get the initial configuration of Big Sur.
Thanks for testing! As i said before that vbios need a patch of connectors. The edp could be connected to wrong output, and the result no backlight at edp lane. I used simple method to indicate outputs at my zbook: i connected 4 outputs and patching framebuffer to zeros find out which port related to encoder.Your VBIOS works with all three cards I have, but (as expected) it doesn't fire up the internal (iMac's) display (image is there, just no backlight).
VAUGHN 4150
1E01 - SIZE
0103 - _ATOM_OBJECT_HEADER_V3
8A02 - usDeviceSupport
3E00 - usConnectorObjectTableOffset = 04 00 00 00 14 31 62 00 68
0000 - usRouterObjectTableOffset
CE00 - usEncoderObjectTableOffset = 04 00 00 00 20 21 F2 00
0000 - usProtectionObjectTableOffset
1200 - usDisplayPathTableOffset = 04 01 00 00 02 00 0A 00 14 31 00
0000 - usMiscObjectTableOffset
DisplayPathTableOffset
04 - ucNumOfDispPath
01 - ucVersion
00 - ucPadding2
00 - asDispPath
ATOM_DISPLAY_OBJECT_PATH
0200 - usDeviceTag; //supported device
0A00 - usSize; //the size of ATOM_DISPLAY_OBJECT_PATH
1431 - usConnObjectId; //Connector Object ID
0011 - usGPUObjectId; //GPU ID
2021 - usGraphicObjIds[1]; //1st Encoder Obj source from GPU to last Graphic Obj destinate to connector.
ATOM_DISPLAY_OBJECT_PATH
ATOM_DISPLAY_OBJECT_PATH
0800 - usDeviceTag; //supported device
0A00 - usSize; //the size of ATOM_DISPLAY_OBJECT_PATH
1331 - usConnObjectId; //Connector Object ID
0011 - usGPUObjectId; //GPU ID
2022 - usGraphicObjIds[1]; //1st Encoder Obj source from GPU to last Graphic Obj destinate to connector.
ATOM_DISPLAY_OBJECT_PATH
ATOM_DISPLAY_OBJECT_PATH
8000 - usDeviceTag; //supported device
0A00 - usSize; //the size of ATOM_DISPLAY_OBJECT_PATH
1332 - usConnObjectId; //Connector Object ID
0011 - usGPUObjectId; //GPU ID
1E22 - usGraphicObjIds[1]; //1st Encoder Obj source from GPU to last Graphic Obj destinate to connector.
ATOM_DISPLAY_OBJECT_PATH
ATOM_DISPLAY_OBJECT_PATH
0002 - usDeviceTag; //supported device
0A00 - usSize; //the size of ATOM_DISPLAY_OBJECT_PATH
1333 - usConnObjectId; //Connector Object ID
0011 - usGPUObjectId; //GPU ID
1E21 - usGraphicObjIds[1]; //1st Encoder Obj source from GPU to last Graphic Obj destinate to connector.
ATOM_DISPLAY_OBJECT_PATH
ConnectorObjectTableOffset
ATOM_OBJECT_TABLE //Above 4 object table offset pointing to a bunch of objects all have this structure
04 - ucNumberOfObjects;
00 - ucPadding[3];
00
00
ATOM_OBJECT asObjects[1];
ATOM_OBJECT_TABLE
1431620068000000
13317D0083000000
133298009E000000
1333B300B9000000
012021000000040C010010010000020000000104930002040400FF
012022000000040C010010020000080000000104920002040300FF
011E22000000040C010020020000800000000104900002040100FF
011E21000000040C010030020000000200000104910002040200FF
EncoderObjectTable
04
00
00
00
2021F200F8000000 F200 and F8000 are offsets to (010011011431 and 14040F00FF)
2022FD0003010000
1E2208010E010000
1E21130119010000
01001101143114040F00FF
01001101133114040F00FF
01001101133214040F00FF
01001101133314040F00FF
i have this issue, but under Catalina this issue disappear. If you look at istatmenus ram clock, you will see it stuck at 300 mhz. I even tried force patch minimum clock as 1500, but in mac os it goes to 300 and system freezes, that i think driver problem, or driver PP usage problem.performs badly after a sleep cycle
That sound great! To complete imac edition I need to know how connectors work with imac... also please make a photos of how gpu reads at ioreqistryI have my 'test rig' available for more tests.
We should use the IORegistryTool and save the output and send this over. This is much more comfortable than sending pictures...Thanks for testing! As i said before that vbios need a patch of connectors. The edp could be connected to wrong output, and the result no backlight at edp lane. I used simple method to indicate outputs at my zbook: i connected 4 outputs and patching framebuffer to zeros find out which port related to encoder.
Example:
PORTS HP G4:
11020404 - EDP
21030303 - DP to VGA
20010101 - Thunderbolt to DP
10000202 - Thunderbolt to HDMI
PORTS HP G3:
12040303
22050404
11020101
21030202
And then i build ObjectInfo as laptop require
i have this issue, but under Catalina this issue disappear. If you look at istatmenus ram clock, you will see it stuck at 300 mhz. I even tried force patch minimum clock as 1500, but in mac os it goes to 300 and system freezes, that i think driver problem, or driver PP usage problem.
That sound great! To complete imac edition I need to know how connectors work with imac... also please make a photos of how gpu reads at ioreqistry
Okay, but you should to delete serial, userdata, uuid, etc. or only privateWe should use the IORegistryTool and save the output and send this over. This is much more comfortable than sending pictures...
Will send it via PM...