Jump to content

RehabMan

RehabMan

Member Since 25 Jun 2012
Offline Last Active Today, 08:35 PM
*****

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

Posted by RehabMan on 16 February 2017 - 12:56 AM

i use only 10.12 folder it is the same? If you are only running 10.12, then it is the same as placing in Other. I put everything in Other and delete (or leave empty) the version specific directories, as I never find it necessary to use different kexts on EFI/Clover/kexts for different versions of OS X. After installation, I install all kexts to /L/E or /S/L/E (depending on version), and use kext injection only for the scenarios that require it (installer and recovery) and only for "essential" kexts.

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

Posted by RehabMan on 15 February 2017 - 01:22 AM

But as far as i know, JUST for the INSTALLATION of Sierra, the kext clover patches will suffice, right? i don't need anything else.   HackrNvmeFamily doesn't work for installation, right? HackrNVMeFamily works for installation if you use the class-code spoof.

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

Posted by RehabMan on 07 February 2017 - 03:01 PM

Yep, but IMHO for real Macs we don't need InjectKext (hard to do so) and a legacy patched kext is enough... Yes. My method is focused on hackintosh, as is this site... I'm really sorry as I know this question has probably been answered somewhere in this thread. I've read through as much of it as i can but haven't found it...   I'm currently on 10.11.6 using a patched HackrNVMeFamily-10_11_6.kext, which i generated using rehabman's script (thank you so much to you, Pike R and anyone else involved).   I think it's high time i upgrade to macOS Sierra, and i'm wondering what the safest way to do this upgrade is? I normally just do it with the app store these days, but would i need to upgrade the system, and then swap over the .kext without booting into the system, for the new one for Sierra? Or would i need to temporarily use the genericnvme kext again while i upgrade? Or can i use a sierra one now?   Thanks a lot in advance for any guidance you can offer.   D I...

#2363424 Clover Bug/Issue Report and Patch

Posted by RehabMan on 05 February 2017 - 08:54 PM

if you have not turned off indexing for the ESP, meaning there is a .Spotlight-V100, then after writing nvram.plist, mdutil will lock it up for a short time. Good idea to 'touch /Volumes/ESP/.metadata_never_index' That will disable spotlight indexing for the ESP.... no need to adjust with mdutil.

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

Posted by RehabMan on 05 February 2017 - 04:46 AM

Hello,   Please bear with me, as I am definitely new here. I am trying to install an ADATA SX8000 NVMe SSD on a 2015 MacBook Pro, using a Sintech adapter. I have run RehabMan's script, using the --spoof option, to create the kext files for 10.12.1β€”10.12.3. When I run a trial with the stock Apple SSD installed, the kext loads up perfectly fine, however with the non-Apple, ADATA SSD is installed, the kext fails to load on account of a permissions issue. I have been posting to PikerAlpha's blog as well. Any assistance you may be able to offer would be greatly appreciated.   Thank you, Matthew Novices can use a kext installer to install kexts, such as Kext Wizard. I tend to use Terminal: sudo cp -R KextToInstall.kext /Library/ExtensionsNote that once you install a kext with incorrect permissions, you must remove it before attempting to install properly: sudo rm -Rf /System/Library/Extensions/KextToRemove.kext# orsudo rm -Rf /Library/Extensions/KextToRemove.kextBut you will not...

#2360952 Clover General discussion

Posted by RehabMan on 01 February 2017 - 03:37 PM

Hi. Anyone wanna test the new way of KernelPm patching? If this works fine then I would be very appreciated! I just noticed that we can do the same thing for 10.8.5, 10.9.x, @RehabMan and @Pike R. Alpha 's good old way is a little complicated... LOL   new_kernel_patcher.c_kernelPm-newway.zip CLOVERX64.efi.zip I think your new code is a fair bit slower than the original. Cleaning up the original is a fine idea, but we might want to keep some of the optimizations: - data was aligned on 16 byte boundary (no need to start search at every byte) - early termination of search when final patch is found/replaced

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

Posted by RehabMan on 01 February 2017 - 03:02 PM

Is there a link to setting up the HackrNVMeFamily with class-code spoof? I am assuming it is here...   https://www.tonymacx...e-spoof.210316/   I am a novice trying to learn...I was able to follow Mork's instructions easily IF someone has something similar to the above... thanks Yes... the class-code spoof guide is on tmx, linked from patch-nvme github README.
  • jsl likes this

#2360387 With "PNLF" internal display turns off after apple logo

Posted by RehabMan on 31 January 2017 - 04:21 PM

Brightness level is remembered across reboots so I think NVRAM is working. It seems to work correctly 90% of the time. Sometimes though (randomly) it just dims to zero on boot. It will only dim to zero when zero is stored in NVRAM.

#2360019 [pre-release] macOS Sierra 10.12.4

Posted by RehabMan on 30 January 2017 - 10:34 PM

Having the same issue... Should I remove IntelBacklight kext then? I would use "Brightness" by bergdesign until I figure a fix for IntelBacklight.kext (or Apple fixes what they broke).

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

Posted by RehabMan on 29 January 2017 - 03:41 AM

Yes. For laptops it's better to keep the DSDT vanilla cuz it may break something after upgrading BIOS. No different for desktops, actually. Both are ok just cuz there's no absolute right or wrong.  ;) For someone new here it's easy to bin-patch because the ACPI patching may be not universal... A binpatch provided by someone else is easier initially, but more work long term (patch must be updated with upgrades). Property injection is the easiest kind of ACPI patching to do... Admittedly though, it requires more skills.

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

Posted by RehabMan on 29 January 2017 - 12:55 AM

Why not do this by editing DSDT? If all you want is avoiding patching DSDT and then you may do this by patching ACPI dynamically instead of tiny SSDT IMHO. I use ACPI hotpatch... no DSDT.aml in my ACPI/patched. Anyway. Both are good and there's no absolute right or wrong, is there? :D Just keep your preference. Correct. I prefer to not have to create new patches when the binary changes in system updates, unless that is the only way to accomplish the fix.

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

Posted by RehabMan on 29 January 2017 - 12:28 AM

I prefer doing some hacks to editing ACPI. Too many ACPI tables will slow down the startup speed. I have no issue with ACPI tables slowing the boot process. Such add-on SSDTs tend to be extremely small. My SSDT-NVMe-Pcc.aml is 157 bytes. I don't, for one second, believe it will have material impact on boot speed.

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

Posted by RehabMan on 28 January 2017 - 05:31 PM

Yup. I think so. But sometimes bin-patch could be an easier way... And not everything can be done via properties injection. I never claimed "everything" could be done with property injection. But this specific problem, definitely yes.

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

Posted by RehabMan on 28 January 2017 - 06:35 AM

Hi. I found that the external icon patch had been changed under 10.12.4 16E144f. This is for 10.12.4. FYI. 48 85 C0 74 07 80 8B 18 01 00 00 10 ==> 90 90 90 90 90 80 8B 18 01 00 00 10      # 10.12.4+ Previous the $8 was 0x08 and now it’s 0x18.   PMheart   ==========   Update: @jsl for 10.11 you may need this one to fix the external icons issue: 48 85 C0 74 07 80 8B 00 01 00 ==> 90 90 90 90 90 80 8B 00 01 00              # 10.11.x   Note: The patches are for IONVMeFamily.   Edit: Pike has provided the external patch already! Deprecated.   PMheartLess trouble and won't break in future versions if you just inject "built-in"...

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

Posted by RehabMan on 27 January 2017 - 04:08 PM

Hi, Matthew82 & DMMA: Thanks for your config-nvme.plist which is also working for Plextor 256M8PeG M.2 SSD in my Asus Z87 Deluxe/Dual hackintosh at 10.12.2(16C68) & 10.12.3(16D32) now ! But it did not work at 10.11.6(15G31). The only pity is it's shown as an external SSD instead of internal one. The patch would need to be different for 10.11.x. Adding an ACPI identity (with an SSDT) for the NVMe device and injecting "built-in" should fix the internal vs. external problem.
  • jsl likes this

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