-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOKit Patch Broken by El Cap Security Update - Unknown version of IOKit found.. #247
Comments
Hm, actually I'll take a look at the IOKit again, and I'll be getting a TV that has HDMI 2.0 anyway so i can test is as well. Will be back here later |
Actually, just force the patch it should still work. Please let me know if you need some help with that, but I'll not be able to help now. Tonight i can give some info. (And please see the readme :) it should show some information that could help) |
Thanks, Floris! I don't know how to "force the patch." How would I do that? |
Please check readme something like patch.command patch v4 (idk what version you would need exactly check the code to find out should not be to difficult. Thake a version that's closest to the version you have :) |
Thanks. I have no way of knowing which version to try. Just as an experiment I tried v7 and got this message:
Since I don't know what "backup file" is or what losing it would mean or what "undoing the patch" means, and "reinstall the OS" sounds terrifying, this all seemed way too scary to proceed at my present level of knowledge. Therefore, I chose n and aborted. |
I'll get back to you in like 2h okay? |
Ping? Still out there, Floris? I'm guessing you ran into a snag? |
Ah sorry I didn't remember.. |
So why not use the CoreDisplay patch? |
Wait you are on old version of macOS ehm try |
I am still on El Capitan. I would like to upgrade to High Sierra but cannot at present. See above for what happened when I tried to do v7. I don't understand the warning message but it seems to suggest that I could mess up my OS and have to reinstall. I cannot take that risk. |
You can ignore the warning I think. As the backup file was not removed on update of the system. That happens sometimes. If you want to be really sure go to the directory where the backup file is and make another copy of the file. Reinstalling the system is usually only annoying because of the time it takes. But no time files will be lost. It's basically replacing all systems files. |
Forgive me if what you're saying doesn't exactly fill me with confidence. For starters, what is this "backup file" we are talking about? You say "go to the directory where the backup file is and make another copy of the file" but I don't know what I'm looking for, much less the directory in which to find it. And what good will having this back up file do me? That is, at what point will the process go wrong and I will an opportunity to "replace" this "missing file." Reinstalling the system... We are talking about a complete reinstall of Mac OS 10.11.6? That can be done without losing the data file contents on the system drive? I have no back up of this drive, mind you. Having never done something like this before, even if possible, would be quite harrowing for me. |
I deeply appreciate the help with this, Floris. But it kind of sounds like you are saying there is nothing you can do to IOKit (a tweak to the code, perhaps ) to fix this problem? My only option is to "force" it to install and possibly corrupt my System drive to the point where I'd have to reinstall the system? But I should ignore the warning and try anyway... Is that it? Thank you for helping me to understand more about what is going on. |
Nah, it sounds all more 'dangerous' as it is tweaking the code has the same result actually.. i fell asleep :p Okay, so the case is: |
OK, some things are starting to become a little clearer. (A little. :) ) So all this time I thought that "IOKit" was just the name of the patch script. But I see now that it is a part of the system. It is in fact a "framework". It can be found in /System/Library/Frameworks. And what the patch does is alter this framework. So this "back up" that we are talking about would be making a copy of the IOKit.framework file before doing the patch, then? And then if something went wrong (what might that be? A Kernel Panic on boot or something? One shudders to think...) I would somehow have the ability to drop in the backed up version of the framework (the copy made before running the patch), and all would be restored, then? |
Keep in mind, while this might all seem obvious to you, Floris, I am just a humble soul who prior to all this was just looking to plug in and use my new LG Ultrawide monitor via HDMI. :-) |
Also, and this is just a guess... I am asking for your advice, your confirmation on this... If you reveal the contents of the IOKit.framework file you get this: Am I correct in assuming that the "IOKit.bak" file buried in the "A" folder is a backup of the original default OS 10.11.6 framework file, before I altered it back in December by running the patch? |
Yes the .bak file is indeed the backup file i was talking about. So when something (if anything at all) goes wrong you can swap out the corrupted file with the backup when booting into Single User Mode (cmd + s) while booting. |
Thanks Floris! I need to ponder my next move for now. Ultimately I do want to upgrade to High Sierra, and then I will have to go through this all over again. I may try getting by w/ SwitchResX for now until the issues with High Sierra get sorted out (two pieces of software I use are currently incompatible under High Sierra, but a fix is in the works). If I do end up trying to force v7 and run into problems, I may try to text you! Thanks. Babz. |
As far as incan see it's copletely safe to try Patch v7 :) (but i can never gurantee it ofc..) |
Hi Floris. Back again! :) I decided to force run the v7 patch (after making a copy of IOKit.framework and storing it on an external drive just for safety). The patch ran but it seems it did not work. This is what it says in Terminal: SIP looks to be disabled, all good! What does this mean? Nothing was changed? Right? It seems to suggest I need to ask the "maintainer of this script" (you) to "add support". I'm guessing that the recent Apple Security Update for El Capitan that I did last week changed 10.11.6 in such a way that the pixel clock patch will no longer work, unless it is updated to take into account whatever was changed by the Apple Security Update. Is that right? |
Ping? Any ideas or suggestions? Would it help to try to run another version, v6, v5, etc.? |
Ah.. sorry.. I thought I responded to the message.. if you email me the backup from the framework I'll have a look at it later this week :) |
You want the IOKit.framework before or after I ran v7? |
I sent you the version before I ran V7 to your .nl address. Thx! :) |
Hi Floris. Just checking... Did you receive the file I sent you? Thx. |
Hi, yes i did (i think i send back an email that i would look at it this weekend, tomorrow it'll be) |
Oh yes, I found the email now in my spam folder. Thanks for the update! |
Oh I feel like a fool now.. You should have used v6 instead of v7 (7 is for 10.12) I didn't realise there was an update for 10.12 in there.. anyway I updated the script and it should work for you now :) |
I downloaded the latest version and ran it but it did not work. This is what I got (same as before) : Unknown version of IOKit found..
otool IOKit.bak: d8829f2234464985863c7a501c288547 ---- ENDING MD5 HASH SUMS ------- |
Also, (question about your previous comment), you say v7 is for 10.12, but I thought 10.2 or higher were supposed to use CoreDisplay Patcher ??? Not applicable to me, since I'm still on 10.11, but just trying to understand your comment. |
Wait that's strange.. just run v6 :) will check later |
Guess what? It looks like v6 worked! Hooray! :-) So it seems I'm good for a while. Next challenge will be when I have to update to High Sierra. Thanks so much for your help with this, Floris! |
Yay! You're welcome :) Enjoy! |
Hi patch v6 seems does not work for me(OSX 10.13.5).
|
The IOKit Pixel Clock patch worked fine for me under El Capitan (10.11.6) when I ran it back in early Dec. 2017. During the process, something called “otool” was required and it was automatically downloaded and installed as part of the script. All good. I was able to get 2560x1080/60Hz for my LG Ultrawide monitor on my 2012 Mac Mini.
Then yesterday I ran the latest El Capitan Security Patch and I lost 2560x1080/60Hz.
I thought, “No problem, I’ll just run the script again.” No joy!
I got a message saying something about missing otool. It apparently could not find otool this time and unlike last time would not automatically download and install it.
I located and installed Xcode 7 (the latest version that would install under El Capitan).
Now when I run the patch I get:
Can you help?
(Please note, I am not a programmer and know next to nothing about terminal and commands.)
The text was updated successfully, but these errors were encountered: