Jump to content

RehabMan

RehabMan

Member Since 25 Jun 2012
Offline Last Active Today, 03:28 AM
*****

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

Posted by RehabMan on Today, 01:51 AM

Please Help-me to fix this. Obs:. Sorry for my bad english. Suggest you read the guide carefully, and stick only to what is written... (you have some additions in your SSDT that are not part of the guide... and wrong).

#2429336 Clover General discussion

Posted by RehabMan on 22 May 2017 - 01:40 PM

As well there is no need to keep MatchOS and MatchBuild. Just make patch search to be unique. MatchOS and MatchBuild are very useful features.

#2429049 Clover General discussion

Posted by RehabMan on 21 May 2017 - 07:52 PM

@RehabMan:Any chance of incorporating the patches of IntelGraphicsFixup.kext into a Clover patch? I probably won't look at doing that until I have hardware that demonstrates the problem.So far, I don't have any HD520/HD530/HD620/HD630 hardware.
  • nms likes this

#2427626 Clover General discussion

Posted by RehabMan on 19 May 2017 - 09:35 PM

@RehabMan - i really agree the frame buffer patch method is better than patch the assertion.Bravo to you for cracking the code for us lap-toppers with immutable bios!!! @sherlocks- i figured out why the DVMTFixup 1.1.3 was not working.- not a problem with Lilu- need change your patch count for each pattern Unlike, the old method which is a patch to avoid assertion, RehabMan's new buffer patches have more that 1 occurrence. so here is an example : changed number 1 to 7 matches for 01030303 00002002 00005001                     const uint8_t find2[]   = {0x01, 0x03, 0x03, 0x03, 0x00, 0x00, 0x20, 0x02, 0x00, 0x00, 0x50, 0x01};   const uint8_t replace2[] = {0x01, 0x03, 0x03, 0x03, 0x00, 0x00, 0x30, 0x01, 0x00, 0x00, 0x90, 0x00};   KextPatch kext_patch2 {   {&kextList, find2, replace2, sizeof(find2), 7},   KernelVersion::ElCapitan, KernelVersion::Si...

#2426022 Clover General discussion

Posted by RehabMan on 17 May 2017 - 10:23 PM

I just test other user. But some users report that fail boot(framebuffer panic). If you want to change some or idea, i will do it. Now, i cant test myself. Because my laptop release dmvt 64mb from factory 나의 LG-F410S 의 Tapatalk에서 보냄 I think the code in IntelGraphicsDVMTFixup is sound.Problem is in Lilu...I will need more time to become familiar with the Lilu code. For now, I'd rather use KextsToPatch.  It is simple and reliable.

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

Posted by RehabMan on 16 May 2017 - 12:28 AM

Note: Added NVMe_patches_10_12_5.plist for 10.12.5 support.The patches are the same as for 10.12.4... just the md5 sums changed.https://github.com/RehabMan/patch-nvme (added for latest security update in 10.11.6 too)

#2422491 Airport - PCIe Half Mini

Posted by RehabMan on 12 May 2017 - 08:29 PM

hellò Racer , can you see now is perfect? Looks good. Now focus on correct country code patch/etc.

#2421731 Airport - PCIe Half Mini

Posted by RehabMan on 11 May 2017 - 01:35 PM

Hello Racer      I did, as you said, I put kexs fakePCIID, i deleted ssdt, but the problem persists, and i only do it after sleep ... i also tried to take a check of energy saving for the wi fi but without any positive results.     Where am i wrong ?? What news do I still have to give? Your ioreg still shows ACPI patching regarding the WiFi... (the OEM did not likely use ARPT for the ACPI name...)

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

Posted by RehabMan on 02 May 2017 - 02:02 AM

I thought I was having no problems, but I just tried to restore my 960 evo with time machine and it doesn't appear as a destination drive.   Is it possible for someone to go into recovery and test this? (you can pull out at the last moment lol.)   What I had to do was to restore to a USB hard drive and then CCC it to the NVME. It took hours... And also now I have some unexplained crashes after login. #@%# Recovery will recognize the drive with the correct configuration on EFI/Clover. Using class-code spoof: - SSDT-NVMe-Pcc.aml in Clover/ACPI/patched (correct for your NVMe ACPI path) - _DSM->XDSM patch in config.plist/ACPI/DSDT/Patches - correct (with --spoof) HackrNVMeFamily-?.kext in Clover/kexts/Other - kext injection

#2414880 Clover General discussion

Posted by RehabMan on 30 April 2017 - 01:53 PM

Hey Slice, I found "Size" here currently uninitialized. Using globals like that will eventually get you...

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

Posted by RehabMan on 23 April 2017 - 01:12 PM

Hi RehabMan. Thanks for your work on this tool.   I'm experiencing a super weird SSD issue with 10.12.4 and was wondering if you've experienced it before or know what might be causing it. I've got an Intel 600p 512GB NVMe that has worked flawlessly right up until the 10.12.4 update. It's running with the patched IONVMeFamily.kext and what I'm experiencing is that at completely random times - it could be a couple hours or a couple days or a week - the read and write speeds completely tank, all the way down to about 5MB/s! The system is completely unusable/sluggish at that point. If I warm reboot, macOS boots back up and the drive is still immediately slow. If I cold reboot, the drive is speedy again at 600MB/s write and 1500MB/s read, but eventually - hours, days, a week - and I'm back to the same 5MB/s read and write issue. Trim is enabled and the drive is error free, per intel's drive tools (smart/scan etc). The same issue happens when booting into safe mode. I'm not seeing...

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

Posted by RehabMan on 23 April 2017 - 02:31 AM

Def /dev/nvme0 exists.   and I see it in lspci output 03:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller [144d:a802] (rev 01) You might want to read here: https://www.smartmon...ki/NVMe_Support When I was gathering the same info on my Samsung 950 Pro, I found the wiki to be quite useful... FYI: Last I checked, the 950 Pro cannot be switched to 4k. Assuming no firmware update has become available, I'm guessing your drive is the same.

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

Posted by RehabMan on 22 April 2017 - 08:12 PM

I did not understand yet one thing, but if I buy a ssd nvme with 4k i do not need any kext hack and do it all with the vanilla kext? If the blocksize is 4k instead of 512, it negates the need for the large set of patches that change the block size assumptions in the kext from 4k to 512.

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

Posted by RehabMan on 13 April 2017 - 01:05 PM

Dear Rehabman   First of all thanks for all the work and knowledge   My problem comes when I have two NVMe installed at the same time, I get KernelPanic. CRUCIAL MP500 and SAMSUNG PM961 both of 204GB   I´m booting SIERRA 10.12.4 from an SSD, not from the NVMe´s. Everything works fine (but the USB 3.0, I´ll investigate later)   I´ve followed (succesfully I think) for two drives, with ACPI paths 09 and 17 :   https://www.tonymacx...e-spoof.210316/   with one NVMe drive installed everything works fine, either MP500 or PM961 and either in M.2 1 or 2 slots ,always there is only one drive at a time   When I install a second one, OSX gives Kernel Panic. It does not matter if I exchange the NVMe slots. With one, everything fine, with two,..no success. BIOS and Windows 10 recognises both drives (W10 boots from the MP500)   I attach two verbose boot screens. for the second I renamed IONVMEFAMILY.kext Just in case since I had spoofed class, similar resul...

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

Posted by RehabMan on 30 March 2017 - 02:10 PM

hi, I have a working 10.12.3 with Samsung 960 evo nvme class-spoofed. Now for update to 10.12.4 do I have to replace HackrNVMeFamily 10.12.3.kext with the new one before the update or after? I wonder if after the update I can not boot with the 10.12.3 kext. Update procedures are covered in my class-code spoof guide, linked from the patch-nvme README. Here goes one question: do i still need to generate new spoof class kext after every system update? If so, can you add script for 10.11.6 2017-001 security update? It is best practice. Already added.

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