Jump to content

RehabMan

RehabMan

Member Since 25 Jun 2012
Offline Last Active Today, 02:07 AM
*****

#2285056 [pre-release] macOS Sierra 10.12.1

Posted by RehabMan on 25 September 2016 - 03:02 PM

hello.  many laptop users suffer fn key and capslock bug in sierra. temporary fix스크린샷 2016-09-25 오후 9.41.37.png here is   add. we have to wait Sierra open source IOHIDFamily. and maybe developer will fix this issue. thank you Installing only IOHIDFamily.kext will seriously break many other kexts.  You can update kernel cache to see:sudo kextcache -i / I notice in the new IOHIDFamily.kext/PlugIns there is IOHIDNXEventRouter.plugin, which is new in 10.12...

#2282791 Clover General discussion

Posted by RehabMan on 22 September 2016 - 06:38 PM

Maybe the installer could delete older backups when the number exceeds a certain threshold. Probably would be better to move the older backups to the system partition if the space is needed. But of course, now the problem has been made even more complex... I use a simple approach: - before installing a new version of Clover, I insure I have a USB that can be used to boot my system should the update go poorly - yes..., I actually test the USB before running the Clover update Then, should it fail due to a Clover bug or other problem, I can fix it by booting from the USB.

#2282781 Clover General discussion

Posted by RehabMan on 22 September 2016 - 06:31 PM

Question/Suggestion:   Why isn't the EFI-Backup installed to EFI partition along with the rest of the bootloader when installing to ESP?   I see 2 benefits for that: - Not touching the OS X partition - Having the older Clover on the EFI partition, I can recover from a bad clover update (using Windows) without needing access to HFS+ The huge disadvantage of your proposal is that you will very quickly run out of space on the EFI partition by filling it with backups.

#2275513 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 08 September 2016 - 09:02 PM

Is here:https://opensource.a...extcache_main.cif (myKextVersion > 0 && myKextVersion > theKextVersion ) { // already have newer version of this kext, do not add it OSKextLogCFString(NULL, kOSKextLogDebugLevel | kOSKextLogArchiveFlag, CFSTR("%s: found newer, skipping %@"), __func__, theKext); return; }Ok, it's time for me to dedicate time to other ...  go to BAR   :) And it will also remove an older kext already present and replace it with a newer one when encountered.   ... if (myKextVersion > 0 && myKextVersion == theKextVersion ) { // already have same version of this kext, do not add it OSKextLogCFString(NULL, kOSKextLogDebugLevel | kOSKextLogArchiveFlag, CFSTR("%s: fou...

#2275482 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 08 September 2016 - 08:30 PM

Jokes aside the Info.plist loaded in the memory-map and later unserialized in OSKext.cpp inside the XNU kernel ...and you can see specific rule:if (sameVersion && sameExecutable) { OSKextLog(this, (existingIsLoaded ? kOSKextLogWarningLevel : kOSKextLogStepLevel) | kOSKextLogKextBookkeepingFlag, "Refusing new kext %s, v%s: a %s copy is already present " "(same version and executable).", getIdentifierCString(), newVersionCString, (existingIsLoaded ? "loaded" : "prelinked")); } So is clearly documented, and this was the message I was talking about today... so now I'm also sure that this messagge will not show up because two kexts must be the same (the case a secondary kext is just renamed) I was aware of that message. It happens more commonly when people are mistakenly injecting kexts that they also have installed to the system volume... But that particular message w...

#2275435 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 08 September 2016 - 07:36 PM

Is still compatible by enabling a macro for me, but this way the same user was experience a kp have its nvme ssd working. I'll provide both binaries in the download section. I suppose... there is plenty of evidence that the version hack works (dummyHDA technique), but I'd rather not use it as Apple doesn't document it that way...

#2275308 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 08 September 2016 - 03:52 PM

I mean that they should probably have their "kern_return_t IONVMEFamily_stop" function, I hope. I'm not sure I get what you're saying... should probe fail, start is never called. And stop is not called in the event start is never called or in the case that start fails.

#2274955 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 07 September 2016 - 06:35 PM

Yes, agreed, but I don't own this disk and when I said "tested" was that an user reported it as working (the only difference from me and you, than, at this point is the class code... how can match otherwise?). BTW the 08h define another tech.... but not NVM Express strictly, not sure what is now. Or I lost something. EDIT I would say that Apple treat the disk as a generic mass storage, like any other, with NVM tecnology, this affect performance. And in fact is. I based my class match on what is written in the NVMe 1.0 specification.

#2274912 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 07 September 2016 - 04:04 PM

Yep the same, pci id is added for El Capitan kexts only (in truth always if the "IONameMatch" array exist). mentioned just to compare with @PatriotSpade if want let us know its id No need for device-id specific matching with NVMe class match.

#2270289 Patch for using NVMe under macOS Sierra is ready.

Posted by RehabMan on 27 August 2016 - 01:09 AM

I am able to generate the kext. However I can see, using kextstat, that OS X is not loading it....even when I put it in the /EFI/Clover/kexts folder? If you have FakeSMC.kext installed in the system volume (therefore in kernel cache) and config.plist/SystemParameters/InjectKexts=Detect, all kexts in EFI/Clover/kexts are ignored by Clover. Is this a kext signing issue? You should install to the system volume and see if you get errors from kextcache: sudo kextcache -i /Then you'll know if you properly disabled SIP. I am a registered developer, so to avoid this signing problem, is there a way I can compile the kext in Xcode? The kext is patched from the Apple provided binary. Hence, "compile the kext in Xcode?" is nonsense. Apple does not provide source to the kext... if Apple did make it open source, creating a generic version would have been a lot easier (thanks Pike!).

#2268744 SSDT Edit Causing KP

Posted by RehabMan on 22 August 2016 - 02:21 PM

I did it as per this guide. http://www.insanelym...ite-1010210103/ incomplete/wrong. FakePCIID method is more complete and a lot easier...

#2268740 SSDT Edit Causing KP

Posted by RehabMan on 22 August 2016 - 02:18 PM

Odd that it appears that I removed those, since I patched them. For what purpose? No need to patch them except for HDMI audio (and that can be done in config.plist). Do I just use the install usb and run the installer from there Yes. Without erasing your system partition. It will restore all Apple provided kexts to vanilla.

#2268638 SSDT Edit Causing KP

Posted by RehabMan on 22 August 2016 - 02:55 AM

I just want to make sure I did this right.  I found a version of IORegistryExplorer (2.1 like you said) then just immediately saved it as lcronosioreg.  I didn't need to search for anything in particular within IORegistryExplorer right?   Oh I also thought I should mention, I was reading through your guide on editing DSDT/SSDTs for the battery patch and thought I should mention that the one in your repo for the Pavilion (there was only one) worked on my Pavilion 15t-p000.  I didn't see it listed, but figured trying the patch wouldn't hurt (it was the only one my DSDT needed actually lol).  Not sure if you wanted to add that model number to the list of ones it's known to work with or not, but though I'd mention it. It is as if you removed the Azul/HD5000 kexts. And FakePCIID.kext+FakePCIID_Intel_HD_Graphics.kext is not installed. Install FakePCIID kexts. Run the OS X installer to refresh all kexts.

#2268572 SSDT Edit Causing KP

Posted by RehabMan on 21 August 2016 - 08:17 PM

Well everything compiles now, and no more KP so I'd say that for the purposes of this thread it's solved.  Thanks for the help :)  One more question though, and if it needs a new thread that's fine, but when doing the battery monitor patches from your repo, what should I look for to decide where it goes?  Like for brightness I knew to look for IGPU (or GFX0 originally). As for battery patching, suggest you read my guide and work through the example DSDT, so you know what you're looking for in your own DSDT.

#2268558 SSDT Edit Causing KP

Posted by RehabMan on 21 August 2016 - 07:39 PM

Okay, thank you for your help.  I think I may have it, just need to finish the edits. So I've been using Clover Configurator to modify my config.plist, and some of these were options I never set in the first place and as such can't find.  I edited out the ones I could find from out of the quote.  I don't mind editing the config.plist directly, I'm just not familiar with it's layout since I've relied on the Configurator for so much of this. Use a plist editor such as Xcode or PlistEditPro to edit your config.plist.

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy