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.
View attachment 1674135



I have a SD card with OC 0.6.3:
View attachment 1674138

Should I install your patch with only select "AMD iMac 2001 Sleep patch" for my Imac 2011 with AMD WX4130 ? (201 should be 2011 in the description in your patch install ?)

View attachment 1674139
You are kidding me?

These installer packages are are made for Catalina or Mojave, NOT Big Sur.

Please start to read my posts before press the download button. And read what is printed in the windows....
 
Upon testing the RX480 for a few days, it really works very well WITH the OpenCore Catalina Loader 0.6.3 seamlessly.
But it does run a little hot with an idle temp of ~50C, reaching ~70C during benchmarking, and dropping down to ~40C upon waking from prolonged sleeping.

I have an internal SSD partition into High Sierra and Catalina in APFS format, and the OpenCore Loader in the SD slot.
I noticed that after setting the Startup Disk once to the OpenCore Loader, even if I reset it to the Catalina partition, it will still start up automatically to the OpenCore Bootloader pickup screen.
If the Loader is removed on restart, nothing comes out for internal display or external display.
But on key press, I can hear the sound response, just no video out.

When I try to reboot to High Sierra via either the Bootloader or by setting the Startup Disk in System Preferences, the 1st stage boot (full brightness screen) can work all the way to fill the status bar but then stop there, without proceeding further. So, now I can't boot back to High Sierra.

Any possible solution to that ?
I am thinking to put the patched AppleGraphicsControl.kext into the S/L/E of Catalina partition for the black screen when without OpenCore Loader as that seems to be culprit as described by many in previous posts. Will see whether this will solve the issue when I am back from work tonight.
However, I don't think it will solve the problem of failure to boot back to High Sierra with the Bootloader. Probably the OpenCore components need further fine-tuning as it is meant to boot into Catalina (and BigSur) but not older OSX.

Problem solved. It is related to corrupted prelinked Kernelcache on replacing the AppleGraphicsControl.kext into S/L/E. I rebuilt them in Terminal and can dual boot again with or without OC.

May be that's why the EG ROM is now favored by Ausdauersportler for troubleshooting.
At least you would have an external display for manipulation of the system.
But I don't dare to flash the Bootrom of my iMac at this early experimental stage yet in case I brick it. :oops:
 
Last edited:
You are kidding me?

These installer packages are are made for Catalina or Mojave, NOT Big Sur.

Please start to read my posts before press the download button. And read what is printed in the windows....

I'm sorry :( I was a little tired yesterday and I translated too quickly in my head "[...] install files on Catalina 10.15.4 and later ! " later by later OS . Your post is clear, no problem, I was the one who made a mistake.
 
  • Like
Reactions: Ausdauersportler
Upon testing the RX480 for a few days, it really works very well WITH the OpenCore Catalina Loader 0.6.3 seamlessly.
But it does run a little hot with an idle temp of ~50C, reaching ~70C during benchmarking, and dropping down to ~40C upon waking from prolonged sleeping.

I have an internal SSD partition into High Sierra and Catalina in APFS format, and the OpenCore Loader in the SD slot.
I noticed that after setting the Startup Disk once to the OpenCore Loader, even if I reset it to the Catalina partition, it will still start up automatically to the OpenCore Bootloader pickup screen.
If the Loader is removed on restart, nothing comes out for internal display or external display.
But on key press, I can hear the sound response, just no video out.

When I try to reboot to High Sierra via either the Bootloader or by setting the Startup Disk in System Preferences, the 1st stage boot (full brightness screen) can work all the way to fill the status bar but then stop there, without proceeding further. So, now I can't boot back to High Sierra.

Any possible solution to that ?
I am thinking to put the patched AppleGraphicsControl.kext into the S/L/E of Catalina partition for the black screen when without OpenCore Loader as that seems to be culprit as described by many in previous posts. Will see whether this will solve the issue when I am back from work tonight.
However, I don't think it will solve the problem of failure to boot back to High Sierra with the Bootloader. Probably the OpenCore components need further fine-tuning as it is meant to boot into Catalina (and BigSur) but not older OSX.

May be that's why the EG ROM is now favored by Ausdauersportler for troubleshooting.
At least you would have an external display for manipulation of the system.
But I don't dare to flash the Bootrom of my iMac at this early experimental stage yet in case I brick it. :oops:
No AGC and no AppleBacklightFixup for AMD cards, ends up in the situation you are describing. Have you really checked the RX480 post I made with @internetzel new Bios?
 
No AGC and no AppleBacklightFixup for AMD cards, ends up in the situation you are describing. Have you really checked the RX480 post I made with @internetzel new Bios?
Learning is infinitely complex. Even today’s neuroscientists struggle to fully map our cognitive architecture.
Traditional unsubstantiated wisdom tells us that we remember only
  • 10 percent of what we READ
  • 20 percent of what we HEAR
  • 30 percent of what we SEE
  • 50 percent of what we SEE and HEAR
  • 70 percent of what we SAY and WRITE
  • 90 percent of what we DO.
You can't blame me keep forgetting the various important points in your notes that may not be relevant or thought of significant value during my initial few readings. 🤗 We have unavoidable biased selective assimilation. I did go thru it multiple times and thus can draw the same conclusion you revealed as simple fact in your perspective ;)

Will try tonight for the solution. But really thanks for the functional vBIOS 👍

P.S. The dual boot problem is solved by rebuilding the kernel cache on both partitions in Terminal.
 
Last edited:
System/Library/Extensions
** NVIDIA GeForce GTX780M Mac Edition ROM **
Genuine Native Boot Screen & Brightness Control


View attachment 942195



There are many members here that have this card now and have been using it with & without Opencore. The previous rom iterations did not initialize the “built-in” iMac LCD screen but instead spoofed it to use the Cinema Display as the internal screen which rendered brightness control non-functional, and forced the use of a bootloader to add the feature back via a kernel extension.


This ROM does not require a 3rd party bootloader like OpenCore.

ROM testing has already been underway for the past few weeks by @Ausdauersportler and @highvoltage12v.

There is an overclock present on the GTX780M from the base rom. I would suggest you to use a 3-pipe heatsink for this GPU. Apply proper thermal pads and appropriate heat dissipating grease like K5pro to the areas that are in contact with the heat sink. Keep mac fans up and running to achieve better control of cooling as well.

Brightness Control Stepping Modifcation

-Turn computer on, hold down Command(⌘)-R
-Choose Utilities > Terminal
-Enter:csrutil disable
-Reboot
-Download and open 'Kext Utility v2.6.6'

-Navigate to S/L/E (System/Library/Extensions)
-Copy "AppleBacklight.kext" to Desktop
-Edit: AppleBacklight.kext/Contents/Info.plist
-Scroll down to: IOKitPersonalities > AppleIntelPanelA > ApplePanels
-There you find several Apple LCD profiles.
-For the iMac 2011 27" machine locate:
<key>F10Ta007</key> <data> ABEABgALABQAHAAnADMAPwBOAFwAZwBzAIEAkQClAL8A 2wD/ </data>

-Change the <data> section to:
ABEAAgA3AF8AigCzAOsBJAFnAakB1AIJAlQCogL4A00DlgRpBGk=

-Drag your modded kext into Kext Utility, allow it correct permissions
-Applebacklight.kext.bak folder will be created
-Reboot

The above data pattern will allow for a wider span of steppings for the brightness control and utilizes more of the capacity of the HD3000. If you have a different machine, your panel ID can be found by going to System Preferences > Displays > Color > Open Profile > mmod

There will be a separate instruction for Windows 10 users to adjust the RMBrightness scaling accordingly.


Important Links:
USB Flashing for SSH @xanderon method <link>
@Curtis Gross – walkthrough video <link>
Heat Sink MOD to grind down the edges <link>
Heat Sink mounting @tgaillar <link>
Kexts for sleep/iGPU (Mojave/Catalina) <link>



More GPU Roms to come... Enjoy!

Some info about Big Sur: the above method works to get back the proper max brightness, but I wasn't able to use Kext Utility. It works fine using the method described in the Big Sur Micropatcher though. So the process is this:

1. Boot into Big Sur as normal
2. Run /Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh.
3. Run sudo pico AppleBacklight.kext/Contents/Info.plist
4. Scroll down and change the line mentioned int he post
5. Save the file (ctrl+x)
6. Run "$REBUILD_KC" (with quotes)
7. Reboot, now you you can adjust the brightness normally :)
 
So I put the old ATI back in and eventually managed to boot the thing in safe mode to install HS via an external screen. It's since done all the updates successfully. In an overly excited manor I've put the K3100 back in but have forgot to disable SIP.

The issues remain basically but slightly different. I can boot in to HS with the K3100 but the external display is corrupted now, I did enable VNC with the ATI installed and that thankfully works fine. The card is correctly found and I can see the BIOS is by Nikey and everything appears to working well. Hard to say over VNC but seems HW acceleration is working.

I can't boot in to the recovery console to disable SIP as it appears to get to the same point as described in the boot process and lock up. I can't boot the Catalina Patcher either as it also gets to the same point in the boot process with the same IOConsoleUsers message as the last entry to the screen if I do a verbose boot.

Argh! looks like the ATI back in and SIP disabled and I'll try the AGC patch. Not convinced that is going to work. Suspect I might have hardware issues somewhere :-/
So further picking at it shows that while it appears that the card is recognised, should it now not show in videoproc as having HW acceleration enabled? See below - anyone got an ideas what's up?

1605867792270.png
 
Learning is infinitely complex. Even today’s neuroscientists struggle to fully map our cognitive architecture.
Studies found that we remember only
  • 10 percent of what we READ
  • 20 percent of what we HEAR
  • 30 percent of what we SEE
  • 50 percent of what we SEE and HEAR
  • 70 percent of what we SAY and WRITE
  • 90 percent of what we DO.
You can't blame me keep forgetting the various important points in your notes that may not be relevant or thought of significant value during my initial few readings. 🤗 We have unavoidable biased selective assimilation. I did go thru it multiple times and thus can draw the same conclusion you revealed as simple fact in your perspective ;)

Will try tonight for the solution. But really thanks for the functional vBIOS 👍
It is even more complex:

Most people read what they want to see printed regardless what is really written in black in white because it does not fit in their private believe or expectation system.

I agree this new BIOS type does some unexpected things....
 
  • Like
Reactions: KennyW
Some info about Big Sur: the above method works to get back the proper max brightness, but I wasn't able to use Kext Utility. It works fine using the method described in the Big Sur Micropatcher though. So the process is this:

1. Boot into Big Sur as normal
2. Run /Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh.
3. Run sudo pico AppleBacklight.kext/Contents/Info.plist
4. Scroll down and change the line mentioned int he post
5. Save the file (ctrl+x)
6. Run "$REBUILD_KC" (with quotes)
7. Reboot, now you you can adjust the brightness normally :)

Hi!

I appreciate your post, but something must have gone wrong during the Big Sur patching. The AppleBacklightFixup.kext needed to get the full brightness level with the @nikey22 ++ cards has been included with the micro patcher. There should be no need to manually install extensions on Big Sur.

Could you please post the output of your terminal while patching. It could still be visible in the command history.

Thanks in advance
 
Hi!

I appreciate your post, but something must have gone wrong during the Big Sur patching. The AppleBacklightFixup.kext needed to get the full brightness level with the @nikey22 ++ cards has been included with the micro patcher. There should be no need to manually install extensions on Big Sur.

Could you please post the output of your terminal while patching. It could still be visible in the command history.

Thanks in advance
I don't have the output, but I remember that when I ran patch-kext.sh(the updated version you mentioned in the Big Sur thread) it did say that my GPU is not recognised. Everything works fine though, I have sleep, brightness control, ethernet, wifi etc...
 
  • Like
Reactions: Ausdauersportler
I don't have the output, but I remember that when I ran patch-kext.sh(the updated version you mentioned in the Big Sur thread) it did say that my GPU is not recognised. Everything works fine though, I have sleep, brightness control, ethernet, wifi etc...
Please report back the output of this:

Code:
/usr/sbin/system_profiler SPDisplaysDataType | fgrep "Device ID" | awk '{print $3}'

:cool:
 
Please add your hardware to the signature. We will not answer in posts where we have to guess what hardware could be used....
I've updated it....for more context, the iMac (late 2009) wouldn't boot to the High Sierra installer with the K3100 in. Put the old ATI card back in and booted in safe mode for the install. Put the K3100 and I have a scrambled external display (VNC works) and I can't boot to recovery console. Each time the boot failure stops at an IOConsoleUsers message, also does this with a Catalina Dosdude boot. I haven't yet got AGC updated for the internal display, will that affect this? (because I stupidly didn't disable SIP while the ATI card was in).
 
So further picking at it shows that while it appears that the card is recognised, should it now not show in videoproc as having HW acceleration enabled? See below - anyone got an ideas what's up?

View attachment 1674657
This is a nice try:

Only SandyBridge (iMac Mid 2011) and newer have internal HD3000 and so iGPU support. This was clearly stated in all posts about the H.264.

Please reread carefully the posts and get an idea which patches you really need....you are not the first to try this.
 
I've updated it....for more context, the iMac (late 2009) wouldn't boot to the High Sierra installer with the K3100 in. Put the old ATI card back in and booted in safe mode for the install. Put the K3100 and I have a scrambled external display (VNC works) and I can't boot to recovery console. Each time the boot failure stops at an IOConsoleUsers message, also does this with a Catalina Dosdude boot. I haven't yet got AGC updated for the internal display, will that affect this? (because I stupidly didn't disable SIP while the ATI card was in).
The AGC fixes the black screen, not a scrambled screen. If you cannot get an Apple Installer or an Apple macOS version to boot into graphics mode the card is probably damaged.
And at this point all my help stops. Go back to post #1 and read the post about hardware problems.
 
Cannot be really possible. And now please report output of this script....to cross check.

:)

chroot: /: Operation not permitted - this is the issue probably. Should i try to run this from the USB installer / terminal?
Unknown GPU model. This may be a patcher bug, or a the original Apple iMac AMD GPU which is
not really supported by Big Sur and will run without any graphics acceleration.
Unknown GPU model. This may be a patcher bug, or the original Apple iMac ATI GPU which
is not really usable with Big Sur and will run without any graphics acceleration.
IMACUSE_OC == NO

Edit: works with sudo, so i guess the patch should be applied using sudo to resolve this?

0x119f
NVIDIA 780M found
NVIDIA Kepler Kx100M, Kx000M, GTX8xx, GTX7xx Card found
IMACUSE_OC == NO
 
Last edited:
  • Like
Reactions: Ausdauersportler
chroot: /: Operation not permitted - this is the issue probably. Should i try to run this from the USB installer / terminal?
Unknown GPU model. This may be a patcher bug, or a the original Apple iMac AMD GPU which is
not really supported by Big Sur and will run without any graphics acceleration.
Unknown GPU model. This may be a patcher bug, or the original Apple iMac ATI GPU which
is not really usable with Big Sur and will run without any graphics acceleration.
IMACUSE_OC == NO

Edit: works with sudo, so i guess the patch should be applied using sudo to resolve this?

0x119f
NVIDIA 780M found
NVIDIA Kepler Kx100M, Kx000M, GTX8xx, GTX7xx Card found
IMACUSE_OC == NO
This code is part of the patch-kext.sh - so if if works right now on your system it should work within the patcher, too. Therefore I do not understand why your patching came back with "unknown GPU".

Checked the code here on several systems with NVIDIA and AMD card from the booted Big Sur terminal app and the recovery USB Installer. Worked in both environments....

You may revert patching on Big Sur by patch-kext.sh -u and repatch after reboot from Big Sur by calling patch-kext.sh, again. Then you might save the terminal output ...
 
This code is part of the patch-kext.sh - so if if works right now on your system it should work within the patcher, too. Therefore I do not understand why your patching came back with "unknown GPU".

Checked the code here on several systems with NVIDIA and AMD card from the booted Big Sur terminal app and the recovery USB Installer. Worked in both environments....

You may revert patching on Big Sur by patch-kext.sh -u and repatch after reboot from Big Sur by calling patch-kext.sh, again. Then you might save the terminal output ...

Yeah, i'm not sure whats the issue is, but i modified the patch and included my device id manually and run the patch like this, works fine now. I think its a permission issue with the chroot... line, not sure why it doesn't work for me. But doesn't really matter also, i'm up and running now :)
 
Yeah, i'm not sure whats the issue is, but i modified the patch and included my device id manually and run the patch like this, works fine now. I think its a permission issue with the chroot... line, not sure why it doesn't work for me. But doesn't really matter also, i'm up and running now :)
I would like to find the root cause. Patching from Big Sur needs the admin permissions anyway and asks for the password at the beginning - possibly this is a recovery problem? Which environment did you use to patch?
 
I would like to find the root cause. Patching from Big Sur needs the admin permissions anyway and asks for the password at the beginning - possibly this is a recovery problem? Which environment did you use to patch?

I used an empty High Sierra to create the install file and i still have HS installed on the same SSD, just a different apfs volume. Maybe this is the issue? I will try to create a new installer usb tomorrow and see if i can run the patcher or not.
 
I am trying to get an iMac 27" 2010 (High Sierra) running a K1100m to run Opencore for brightness but it is hanging on a black screen when the graphics loads. It also does not see a boot camp partition. I used the default Nvidia plist file.
Any ideas?
 
Last edited:
I am trying to get an iMac 27" 2010 (High Sierra) running a K1100m to run Opencore for brightness but it is hanging on a black screen when the graphics loads. It also does not see a boot camp partition. I renamed used the default Nvidia plist file.
Any ideas?
Go back to post #1 and search for the "black screen" issue. And about OpenCore and BootCamp you probably just search for the original announcement @Nick [D]vB made and which is still linked to the post #1. Cannot comment on this, most moved to UEFI installations...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.