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.
its helped me to create modded my personal bios,
i want to compare two bios to find difference.

and create clean bios without serial for help people who have their imac 27 late 2009 with black screen problem

we stuck for find working bios with supporting out of the box nvidia cards for imac 27 late 2009

u have working out of the box imac with support k4100
that will be helped us.

thank u.
I want to try to do this to you

Romtool works on Bigsur? because I have an error message (kext error).
Give me your email I will try on highSierra



otherwise a big thank you to @nickey22 and @Ausdauersportler

everything works, I have the impression of having a brand new Imac (threw under HS and now under BS)

I used the micropatcher automator 2009

Before I was under OCLP and I had very bad sound and catastrophic graphics performance

with micropatcher I have better graphics performance under BigSur than under HighSierra

Thank you again and I will try to help in my turn within the limits of my skills
 

Attachments

  • Capture d’écran 2021-03-01 à 16.39.52.png
    Capture d’écran 2021-03-01 à 16.39.52.png
    390.2 KB · Views: 151
  • IMG_8043.jpeg
    IMG_8043.jpeg
    919.6 KB · Views: 116
  • IMG_8044.jpeg
    IMG_8044.jpeg
    961.8 KB · Views: 121
  • Like
Reactions: sergiodadi
Where did you get that information pal?
Internet maybe.



This could be false as it is very rare to see a 4GB GTX880M.
 
Internet maybe.



This could be false as it is very rare to see a 4GB GTX880M.
Yes I think you are talking about the Asus Version but this is Green and my graphics card is Blue like the others on this site, so strange
 

Attachments

  • H848b0efb1d304dc0be9770ef269dc149U.jpg_q50.jpg
    H848b0efb1d304dc0be9770ef269dc149U.jpg_q50.jpg
    79.8 KB · Views: 100
Last edited:
I want to try to do this to you

Romtool works on Bigsur? because I have an error message (kext error).
If you start to read carefully all security information when you try to start romtool you can make it work. If you just ignore what the macOS Big Sur is trying to tell you than you most likely have to start another macOS versions.

You post here faster than you read the docs or the OS messages - which is not a good sign at all.
 
If you start to read carefully all security information when you try to start romtool you can make it work. If you just ignore what the macOS Big Sur is trying to tell you than you most likely have to start another macOS versions.

You post here faster than you read the docs or the OS messages - which is not a good sign at all.
The operating system message: "kext error DirectHW.kext could not be loaded.The operation cannot procceed"
What did I not understand?
Capture d’écran 2021-03-01 à 21.05.51.png


when I click on OK the software closes

it's nice to create software but spending your time denigrating beginners like me is less so
 
The operating system message: "kext error DirectHW.kext could not be loaded.The operation cannot procceed"
What did I not understand?View attachment 1737235

when I click on OK the software closes

it's nice to create software but spending your time denigrating beginners like me is less so
Just an example:

You could have searched the thread for the 256gb Valley thing (comes top every three weeks if not more often)

I am not your personal assistant in reading security messages coming up with Big Sur if you try to start up programs wanting access to load third party extensions. Do you need more hints? Security, security, SECURITY!
 
Pascal, I cannot believe that you did not see the message in the security pref pane after first try to start romtool....
I did.
But sometimes romtool has some unexpected behaviour. And launching it not long after boot can resolve this. Just my experience, i cannot explain why. It was the same behavior till High Sierra. i believe it's not related with security pref pane authorisation.
you can even get some freeze using romtool.
I just used romtool now in big sur on a system started two days ago, and it works, in total contradiction with what i have just said, but ... it can happen.
 
Last edited:
I did. But sometimes romtool has some unexpected behaviour. And launching it not long after boot can resolve this. Just my experience, i cannot explain why. It was the same behavior till High Sierra. i believe it's not related with security pref pane.
When I start up romtool for the very first time on a new Big Sur installation the system asks me to allow romtool to load the third party kext within the security pref pane. This is not a modal dialog and sometimes the window/message got buried under a load of other open windows and messages. And this is different from the other macOS version, where this message does not come up and romtool just crashes the system when loading it.

You have to check this box and reboot the system. After that you can happily use romtool on the same system unless you do a new installation. Just checked it on my main gear (WX4170, Big Sur 11.2.1 (20D64)).
 
Last edited:
  • Like
Reactions: BadBiscuit
When I start up romtool for the very first time on a new Big Sur installation the system asks me to allow romtool to load the third party kext within the security pref pane. This is not a modal dialog and sometimes the window/message got buried under a load of other open windows and messages. And this is different from the other macOS version, where this message does not come up and romtool just crashes the system when loading it.

You have to check this box and reboot the system. After that you can happily use romtool on the same system unless you do a new installation. Just checked it on my main gear (WX4170, Big Sur 11.2.1 (20D64)).
Yes, with Big Sur, things are clear and straight. But not before Big Sur. You have to use a small time gap for romtool to work on "older" systems. Sometimes. It's a kind of error we do not like because we cannot track them easily. Or most of us cannot track them or understand them.
 
Last edited:
When I start up romtool for the very first time on a new Big Sur installation the system asks me to allow romtool to load the third party kext within the security pref pane. This is not a modal dialog and sometimes the window/message got buried under a load of other open windows and messages. And this is different from the other macOS version, where this message does not come up and romtool just crashes the system when loading it.

You have to check this box and reboot the system. After that you can happily use romtool on the same system unless you do a new installation. Just checked it on my main gear (WX4170, Big Sur 11.2.1 (20D64)).
sorry i never had any of this
Let's stop talking about it
 
sorry i never had any of this
Let's stop talking about it

You are like a child playing hide and seek closing it's eyes and hoping not to be found or the famous bird who put's his head into the sand if something unexpected happens.

The dialog is not modal, i.e. it does not stop your interaction with the program unless you acknoledge it by clicking OK.

But it is there!

It is really sad to be forced to prove that somebody is wrong. You made it really quickly to my ignore list.
 

Attachments

  • Romtool on Big Sur.png
    Romtool on Big Sur.png
    438 KB · Views: 114
  • SecurityPrefPane.png
    SecurityPrefPane.png
    202.3 KB · Views: 112
  • AllowThis.png
    AllowThis.png
    175.6 KB · Views: 107
  • Reboot.png
    Reboot.png
    110 KB · Views: 120
You are like a child playing hide and seek closing it's eyes and hoping not to be found or the famous bird who put's his head into the sand if something unexpected happens.

The dialog is not modal, i.e. it does not stop your interaction with the program unless you acknoledge it by clicking OK.

But it is there!

It is really sad to be forced to prove that somebody is wrong. You made it really quickly to my ignore list.


5DF08FED-CFA9-408E-A7E2-318DEF455BB8.jpegit is about this dialog box which you speak about in your previous messages (green arrow)?

 
Last edited:
Have you run AHT or ASD? A damaged or disconnected sensor will cause the system's CPU to throttle.


What @KennyW stated is dead on. With the HD connected internal it is booting first instead of the SD card, and the default item it is trying to load is not working with the card change. When you move the HD external to be USB, the boot order is changing to the SD. To prove that to yourself, install a HD with High Sierra only and install internal. You won't see an OC boot screen, but it should boot HS even after a PRAM reset (i.e. where the selected boot object is cleared). It is not that you don't have HS installed, but that it is not the first OS found on the SSD (i.e what @KennyW stated).

UPDATE: With that said, a damaged SATA port or cable is possible, but I would ask how you made that deduction? I had such a system which was maddening, and was eventually traced to a failing power supply. You might see if the SATA cable on the optical drive works with the SSD in troubleshooting that (in my case it did), but I think this scenario is less likely.
Hi
Thank you for this post. Indeed the devil hides in details : I should have plugged an SSD with only High Sierra on it. No other MacOS on top.
In the meantime I have put the k2100m back and the internal SSD works like a charm. So the sata cable is ok.
I will give the WX4150 another try once I’ve recieved the Kapton tape. I will make sure only HS is installed on main internal sata channel.
 
No, you won't get a picture on the stock vBIOS without a back-light mod,

AMD users should flash the GOP vBIOS attached, you can do it from windows.

Then use OpenCore to get boot-screen and brightness control with no other mods!



Download: iMac OpenCore Loader.dmg


FEATURES:

[1] Native brightness control
on Quadro K1100M & K2100M cards.

(more cards may be added in the future through vBIOS updates)

[2] Target Display Mode on Quadro K1100M & K2100M cards.

[3] Real-time hardware monitoring using HWMonitor app:

Nvidia GPU Die Temp + GPU, VRAM & CPU core Frequencies.

[4] Reduced boot-screen delay, no more random black-screen boots.

[5] OpenCore + rEFInd boot-pickers on AMD cards with NO MODS!

(allows bootscreen & native brightness control simultaneously)

[6] SideCar + Video acceleration on new AMD cards (Mojave+)

Huge H264 & HEVC video encoding speed improvements in FCPX etc

Playback of DRM protected streaming content (Netflix 4K etc)


2011 iMacs only -

[7] UEFI Windows: Sound fix
for HDAudio code 12 driver error,

can also fix some ThunderBolt eGPU resource issues in Windows.

(Enable DSDT in ACPI section of the OpenCore configuration tool)

[8] Mojave & Catalina: Integration of SandyBridge iGPU Kexts

required for the AirPlay + Sleep + GVA QuickSync video fixes

Catalina needs IOSurface.kext replacing FIRST, more details here:



INSTALLATION:

Restore the image to an SD card or USB stick, I do not recommend installing to a non-removable drive. If using an AMD card show hidden files and extract the AMD config.plist file inside the /EFI/OC/ folder. Set the "Catalina Loader" drive as the default boot disk in system preferences or by using Ctrl+Enter from the Apple boot-picker. If you have problems booting delete any Lilu or Whatevergreen kexts from S/L/E, to disable OpenCore just remove the drive and do an NVRAM reset.


WARNING:

Congratulations, you are now running a Hackintosh! I have done some basic safety checks but I can't test everything, there is a non-zero risk that something will go spectacularly wrong. I accept NO responsibility if Apple ban your accounts or if your iMac blows-up, wipes all your data, and injures your cat... Make sure you have current back-ups of all your drives, and use the RomTool to make a back-up of your iMacs BootRom so it can be restored in case of corruption (very unlikely, but possible). Configuration tools are included, be careful - here be dragons! ;)


Based on "Catalina Loader" by Rastafabi.

Thanks to Highvoltage12v & Ausdauersportler for testing.

Full credit to all the original developers & those who shared essential information.



Better late than never...

:p
Is anyone else getting the “sorry cannot download this because it contains a virus”

not that I think it has a virus, it just won’t let me download it.🤣

mom trying to get Target Display Mode working
 
Is anyone else getting the “sorry cannot download this because it contains a virus”

not that I think it has a virus, it just won’t let me download it.🤣

mom trying to get Target Display Mode working
Meanwhile we had at least ten updates of it you will find them reading the first post. Unfortunately we cannot change these old posts after google claimed to find a virus in the archive.
 
Meanwhile we had at least ten updates of it you will find them reading the first post. Unfortunately we cannot change these old posts after google claimed to find a virus in the archive.
No problem!!

Iv been reading through all the spoilers and am figuring it out now. It was overwhelming and confusing at first with all the different download links. So I went back to the first post and started reading all the spoilers.
pretty much everything on my iMac is working with the latest 0.6.6 and installing Big Sur with the iMac micropatcher.
But I can’t get target display mode to work while booted in HS or Mojave. It tries to work tho. The Mac Pro thinks it’s in target display mode with the iMac but the iMac stays black. Sometimes it will flicker but never see the Mac pro
then I saw that old post where target display mode was a benefit of Catalina loader and fell into a rabbit hole of old post.
I’m just wondering if I should use an older version to get target display mode to finally work on mid 2011 27” iMac.
 
No problem!!

Iv been reading through all the spoilers and am figuring it out now. It was overwhelming and confusing at first with all the different download links. So I went back to the first post and started reading all the spoilers.
pretty much everything on my iMac is working with the latest 0.6.6 and installing Big Sur with the iMac micropatcher.
But I can’t get target display mode to work while booted in HS or Mojave. It tries to work tho. The Mac Pro thinks it’s in target display mode with the iMac but the iMac stays black. Sometimes it will flicker but never see the Mac pro
then I saw that old post where target display mode was a benefit of Catalina loader and fell into a rabbit hole of old post.
I’m just wondering if I should use an older version to get target display mode to finally work on mid 2011 27” iMac.
This is more complex. Target display mode works only with High Sierra! It may not even work with HS when using OC to spoof a different board-id. Have never tested it.

So my advice: I you desperately need TDM use a unpatched High Sierra partition on your SSD to have it. If you need more modern macOS versions you have to sacrifice TDM. You cannot have it all.
 
  • Like
Reactions: Nguyen Duc Hieu
This is more complex. Target display mode works only with High Sierra! It may not even work with HS when using OC to spoof a different board-id. Have never tested it.

So my advice: I you desperately need TDM use a unpatched High Sierra partition on your SSD to have it. If you need more modern macOS versions you have to sacrifice TDM. You cannot have it all.
That’s what I did. I have it so at the boot screen I can either
A: boot into OC and then boot into Big Sur or
B: boot into an unpatched version of HS

I get a black screen or sometimes it flickers in both cases with HS either with or without using OC on that particular volume.
I’ll keep poking away at it to see if I can get it sorted out.
I only mention Mojave before because while it’s technically not supported TDM will activate on a Mojave machine

Thanks for the reply’s
 
That’s what I did. I have it so at the boot screen I can either
A: boot into OC and then boot into Big Sur or
B: boot into an unpatched version of HS

I get a black screen or sometimes it flickers in both cases with HS either with or without using OC on that particular volume.
I’ll keep poking away at it to see if I can get it sorted out.
I only mention Mojave before because while it’s technically not supported TDM will activate on a Mojave machine

Thanks for the reply’s
You have to reset the PRAM each time you are changing the mode away from OC. Otherwise your will not really have a clean boot into your unpatched version of HS.
 
This is more complex. Target display mode works only with High Sierra! It may not even work with HS when using OC to spoof a different board-id. Have never tested it.

So my advice: I you desperately need TDM use a unpatched High Sierra partition on your SSD to have it. If you need more modern macOS versions you have to sacrifice TDM. You cannot have it all.
And I would assume it would work on a patched version because of this post. And the k2100m is the card I’m using. That’s how I got reading all those older post
 

Attachments

  • 0AA2AF4B-46E1-4CC3-9C35-311941C5E6D5.png
    0AA2AF4B-46E1-4CC3-9C35-311941C5E6D5.png
    855.1 KB · Views: 102
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.