Jump to content



Member Since 25 Jun 2012
Offline Last Active 47 minutes ago

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

Posted by RehabMan on 25 July 2016 - 04:23 PM

​This setting is not possible with Clover Configurator on the fly? I don't use Clover Configurator. And there is not a specific feature in Clover to address this problem. Also, such a feature is not necessary as the SSDT approach is efficient and works without issue. My performance is very slow, this disk Read to 2600 and write to 1500 EDIT: IONVMeFamily.kext is not loader :( Attach ioreg from IORegistryExplorer v2.1.

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

Posted by RehabMan on 25 July 2016 - 03:15 PM

How can I do it? See post #83. Your SSD seems to be under _SB.PCI0.RP01.

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

Posted by RehabMan on 25 July 2016 - 02:05 PM

Thank you for the patch, work perfectly in my OCZ RD400, but show external and icon orange in El Capitan. You need appropriate ACPI changes to make it internal. All that is required is an ACPI identity for the PCI device.

#2255056 Apple unveils "macOS Sierra"

Posted by RehabMan on 20 July 2016 - 01:56 AM

Oh sorry...the patch comes from the link/forum you located/posted here for me upon my initial inquiry too you a few weeks ago wondering if you were aware of any methods for getting Wi-Fi working in the HP Envy 15T K series  Broadcom BCM94352HMB PCI card.   http://www.insanelym...bcm94532z-wifi/   Applying this patch worked for DP1:   Kext: AirPortBrcm4360 Find: 81F952AA00007529 Replace: 81F952AA00006690   This additional fix was/is supposed keep Wi-Fi working: in DP2:   1- Place the following full path in the "force kexts to load" option of clover:   \System\Library\Extensions\IO80211Family.kext\Contents\PlugIns\AirPortBrcm4360.kext   2- In the ACPI patches menu make sure to have "AddDTGP" and "FixAirport" selected   3- in Devices menu, copy and paste into the wifi box    0x43BA14E4I have not tried the patch with anything past dp1. The proposed additional fixes do not sound necessary though... sounds like someone...

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

Posted by RehabMan on 15 July 2016 - 01:20 AM

patch shown is for Nvidia HDMi audio, consider (assuming NVME is not present in the native dsdt)Scope (NPE7) { Device (NVME) { Name (_ADR, Zero) // _ADR: Address Name (_SUN, One) // _SUN: Slot User Number Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "built-in", Buffer (0x0A) { "NVMe SSD" } }) } } } I found I needed only to add the ACPI identity for the NVMe device. This is the SSDT I use on my desktop (as an example, yours will differ, depending on scope): // add an ACPI identity for bu...

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

Posted by RehabMan on 13 July 2016 - 02:36 PM

Rehabman If i understand it right, no need to use clover kexttopatch if i already patched the kext and created the new kext if using your script correct? Correct. The script creates a kext that can be used without any config.plist-based patches.

#2250210 Clover General discussion

Posted by RehabMan on 09 July 2016 - 07:52 PM

Hello Rehab you are ready to edit the script for the future upgrade? When Pike provides the information required for such updates, the plist files that drive the script can be updated. The script itself is generic and can apply patches from any plist. Of course, such patches cannot be created before the update arrives, as that would require someone with the ability to predict the patches that will be needed in a kext that is not currently available. I don't see how that is possible (predicting the future would be quite useful, but unfortunately, impossible).

#2250109 Clover General discussion

Posted by RehabMan on 09 July 2016 - 05:01 PM

Depends on whether or not the kext has changed in a way that the patches don't work. ;) History is already an indication... So far, each version released since 10.11.5 has required new and/or different patches. And an update from 10.11.5 to 10.11.6, using 10.11.5 patches would result in a "partial patch" (10.11.6 beta4 requires two additional patches).

#2250091 Clover General discussion

Posted by RehabMan on 09 July 2016 - 04:53 PM

Regarding kexts like NVMe - maybe you would want to have patch groups? Like Clover would make sure all patterns of a group are found for them to be applied... though that could still mean a patch can be applied more often than desired. Although it would fix the problem of a "partial patch", it would still result in an unbootable system upon update. Clover KextsToPatch is just not a good fit for this task. just checked: path and file: both are correct and NOT damaged. Could open the kexts info.plist with PListEditor and with XCode. Also i got this message with every kext i try to ForceLoad. Just tried to forceload kexts from /S/L/E - not from any other place so far. But no matter what kext i try to forceload, i get the errormessage about not found "info.plist" for that kext. Strange, isn't it? Keep in mind UEFI and Clover's ForceKextsToLoad uses backslashes as directory separators, not forward slashes.

#2249686 Clover General discussion

Posted by RehabMan on 09 July 2016 - 06:10 AM

Anyway, if OS is not matched then NVME will not be patched? Not a way. Not sure what you mean. Two possibilities: 1) you use MatchOS to match only the OS version you know the patches will work with 2) you don't use MatchOS In #1, your system is not bootable following an update. In #2, your system may or may not be bootable upon an update, and one or more of the patches may not match with the new kext (in this case, data corruption is likely). Had you installed a patched kext as I propose (eg. use my patch_nvme.sh script to create HackrIONVMeFamily-*.kext), it is likely the patched kext will continue to work upon updating the system, with no risk of data corruption. You can then, at your leisure, and when such patches are developed, create a new HackrNVMeFamily-*.kext, which you can install to replace the older HackrNVMeFamily-*.kext. Note also that multiboot scenarios (multiple versions of OS X) are simplified since each system volume has its own copy of the appropriate HackrNVMe...

#2249649 Clover General discussion

Posted by RehabMan on 09 July 2016 - 12:37 AM

I think what RehabMan is saying is that if the NVMe kext gets updated and any of the patches fail, you could likely end up with an unbootable system.  Actually, an "unbootable system" would be the *best result* in that scenario.  I'm more concerned about a partial patch scenario that allows the system to boot, but results in corrupt data due to a buggy partially patched kext.   Unfortunately, I think the chances of "unbootable" vs. "bootable but incorrect/dangerous" are about 50/50 or maybe worse. 404 error here.. :(Consider that to avoid bad patches for newer versions, MatchOS can be set to match specic revision of macOS X. Off course DPs/Betas are another story.. Locking it down to specific versions mostly avoids the problem of a partial patch, but also would result in an unbootable system in the case of an update. I say "mostly avoids" because Apple has been known to update the kernel and other kexts in "security updates", which don't come with a new vers...

#2248819 Clover General discussion

Posted by RehabMan on 07 July 2016 - 06:06 PM

To me, who started with Apple ][ and VC-20, that UEFI looks quite the OS - it provides most of the basic requirements an OS offer: Resource (cpu, memory, hardware access) allocation and control. Anything more is just fancy stuff an OS doesn't need to provide but delegates to its drivers :) An interface is just a declaration of interoperability. An OS and a kernel _implement_ interfaces.   Unles I really still misunderstand what UEFI does (still didn't get to read that all, still trying to get my HackMac going properly). Anyway, you've answered all my questions, thanks a lot! There is a lot missing from UEFI if you were trying to consider it a modern OS.

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

Posted by RehabMan on 05 July 2016 - 04:30 PM

Attached is the script (and supporting files) to create a patched kext that can be used without modifying or deleting existing vanilla IONVMeFamily.kext. ... Note 2: The original attachment found here is the first version. Since then, I've moved the script and supporting files to github. The new version at github uses IOPCIClassMatch to match against the well-known NVMe PCI class code, so it is not necessary to supply the vendor/device-id for IONameMatch. github repo: https://github.com/RehabMan/patch-nvme Project moved to github (and updated).

#2247661 Clover General discussion

Posted by RehabMan on 04 July 2016 - 03:29 PM

i hope to change audio id. Conexant to realtek Not possible (and complete nonsense). HDA codec ids come from the codec itself which is connected to the HDA chip via some sort of serial interface...

#2247643 Apple unveils "macOS Sierra"

Posted by RehabMan on 04 July 2016 - 02:04 PM

Thank Rehabman. It is ApplePS2Mouse. It is AL0PS. ioio: setting property 'ApplePS2Mouse:Clicking' as number to 1 (0x1) However two and three fingers tap not work. Regarding MacOs, xgps and python-gps is missing. I try install gpsd but no xgps client and python-gps ApplePS2Mouse does not support "trackpad" gestures. It is a mouse driver.

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