PMheart Posted October 28, 2017 Share Posted October 28, 2017 Sweet, now it fully works. No verbosity. Thanks again, you're awesome. Now if I could just figure out why APFS takes such an absurdly long time to boot (persistent issue since switching to 10.13)… NP ^^ I'm not sure... Sorry. What I can tell is that APFS slightly slows down my disk's performance even on my real Mac. 2 Link to comment Share on other sites More sharing options...
chris1111 Posted October 28, 2017 Share Posted October 28, 2017 Sweet, now it fully works. No verbosity. Thanks again, you're awesome. Now if I could just figure out why APFS takes such an absurdly long time to boot (persistent issue since switching to 10.13)… After what I've seen, it's much more the Trim Enabler that slow down the SSD in APFS because if I do not activate the Trim, ssd boot as quickly as a SSD in HFS + J 1 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 28, 2017 Share Posted October 28, 2017 After what I've seen, it's much more the Trim Enabler that slow down the SSD in APFS because if I do not activate the Trim, ssd boot as quickly as a SSD in HFS + J True, same experience here. However for me there's maybe 1 or 2 seconds difference so it's not really bothering Link to comment Share on other sites More sharing options...
Mork vom Ork Posted October 28, 2017 Share Posted October 28, 2017 "4D 8B 4E 18 48 8D 0D 49 2F 03 00 48 8D 15 69 2F 03 00 41 B8 5A 03 00 00 E8 60 67 00 00" NOT FOUND in latest apfs.efi (taken from 10.13.1 beta5). but "4C0F45C8 488D0D08 40030048 8D15EC3F 030041B8 9E030000 E8DF6700 00 -> 90909090 90909090 90909090 90909090 90909090 90909090 90909090 90" works 1 Link to comment Share on other sites More sharing options...
zxv Posted October 28, 2017 Share Posted October 28, 2017 True, same experience here. However for me there's maybe 1 or 2 seconds difference so it's not really bothering For me it's an additional 2+ minutes. As if booting from an HDD—in spite of the fact that I'm on an NVMe PCIe SSD. After what I've seen, it's much more the Trim Enabler that slow down the SSD in APFS because if I do not activate the Trim, ssd boot as quickly as a SSD in HFS + J Tried 'trimforce disable', but apparently this only pertains to non-Apple SATA SSDs (thus made no difference in boot time). TRIM is natively enabled on this drive and there's no means of disabling it afaik. Link to comment Share on other sites More sharing options...
telepati Posted October 28, 2017 Share Posted October 28, 2017 This is not verbose mode of apfs. "American megatrends" this is of your motherboard. is it possible to hide this megatrends logs on BIOS? I looked but can't see it? Link to comment Share on other sites More sharing options...
crusher Posted October 29, 2017 Share Posted October 29, 2017 is it possible to hide this megatrends logs on BIOS? I looked but can't see it? Just flash your bios. But first try disable and after enable boot logo. 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted October 29, 2017 Share Posted October 29, 2017 Hi Guys, Today I fixed my apfs logs... with CsmVideoDxe-64, unlike the others times I tried, today it worked I don't know why... but 0 logs... yuppiiiii Link to comment Share on other sites More sharing options...
Common Sense Posted October 30, 2017 Share Posted October 30, 2017 As for apfs-748.21.6, try: offset 0x3E6AF - 0x3E6CB original 0x4C8B4B18488D0D33410300488D155341030041B868030000E846690000 replaced 0x9090909090909090909090909090909090909090909090909090909090 offset 0x3E816 - 0x3E832 (new patch mentioned by @zxv) original 0x4C0F45C8488D0D08400300488D15EC3F030041B89E030000E8DF670000 replaced 0x9090909090909090909090909090909090909090909090909090909090 offset 0x401DB original 0x75 replaced 0xEB offset 0x43D02 original 0x74 replaced 0xEB offset 0x44F70 original 0x55 replaced 0xC3 As for the exact patch: #1 4C8B4B18488D0D33410300488D155341030041B868030000E846690000 -> 9090909090909090909090909090909090909090909090909090909090 #2 (new patch mentioned by @zxv) 4C0F45C8488D0D08400300488D15EC3F030041B89E030000E8DF670000 -> 9090909090909090909090909090909090909090909090909090909090 #3 75254C -> EB254C #4 00741F80 -> 00EB1F80 #5 E9213B000055 -> E9213B0000C3 Thanks @modbin and @MICKHAEL for the patches! Fantastic, thank you! I get one last annoying line because of my APFS fusion drive. Any chance you would be able to find: "fusion_wbc_startup:944: Fusion is started in regular mode"? Link to comment Share on other sites More sharing options...
modbin Posted October 30, 2017 Share Posted October 30, 2017 Try this. I didn't test it! It's up to u. offset 0x48A46 original 0x75 replaced 0xEB 2 Link to comment Share on other sites More sharing options...
Common Sense Posted October 30, 2017 Share Posted October 30, 2017 Thanks modbin, that did the trick, the message is now gone Unfortunately I'm not at your expert level so I am not sure exactly how I can know which values to change. Is it simply that hex code 0x75 prints something, and whenever I find it I can disable the printout by changing to 0xEB? Try this. I didn't test it! It's up to u. offset 0x48A46 original 0x75 replaced 0xEB 1 Link to comment Share on other sites More sharing options...
PMheart Posted October 31, 2017 Share Posted October 31, 2017 Thanks modbin, that did the trick, the message is now gone Unfortunately I'm not at your expert level so I am not sure exactly how I can know which values to change. Is it simply that hex code 0x75 prints something, and whenever I find it I can disable the printout by changing to 0xEB? 0x75 means short jne (jump if not equal), and 0xEB means short jmp (unconditional jump). I guess the original code jumps to somewhere that ignores such log and a simple unconditional jump is just doing the trick which eliminates it. 2 Link to comment Share on other sites More sharing options...
PMheart Posted October 31, 2017 Share Posted October 31, 2017 (edited) Hi. In my case only applying the patches mentioned at #45 is still not enough. I was also getting "%s:%d: reloading after unclean unmount, checkpoint xid %lld, superblock xid %lld\n" For those who are encountering the same error, you can use this patch: offset 0x4445C original 0x74 replaced 0xEB I'll also update my old post. EDIT: OK. DONE. Edited October 31, 2017 by PMheart 1 Link to comment Share on other sites More sharing options...
aerz Posted October 31, 2017 Share Posted October 31, 2017 can u test this version. credit to modbin Thanks! This apfs.efi works for me in a GA-Z270-Gaming K3 on High Sierra 10.13 Link to comment Share on other sites More sharing options...
In-N-Out Posted October 31, 2017 Share Posted October 31, 2017 The apfs-748.1.47 (17A405) posted on the 28th by MICKHAEL worked great on my GA-Z170X-UD5 TH running the Supplemental update. Suppressed all those pesky messages. Thank you! 1 Link to comment Share on other sites More sharing options...
iRipper Posted October 31, 2017 Author Share Posted October 31, 2017 Can someone make a patched apfs.efi for 10.13.1 (17B48)? Link to comment Share on other sites More sharing options...
crusher Posted October 31, 2017 Share Posted October 31, 2017 Can someone make a patched apfs.efi for 10.13.1 (17B48)? Here you go apfs.efi.zip 12 Link to comment Share on other sites More sharing options...
In-N-Out Posted October 31, 2017 Share Posted October 31, 2017 Thanks crusher. Link to comment Share on other sites More sharing options...
MorenoAv Posted October 31, 2017 Share Posted October 31, 2017 here updated 10.13.1 with CsmVideoDxe-64 and 0 apfs logs... Link to comment Share on other sites More sharing options...
Gigamaxx Posted November 1, 2017 Share Posted November 1, 2017 Here you go Works great for my Ryzen 7 1700 AX370 build. Thanks, finally got rid of the Bios Verbose screen issue before clover screen. My Bios "Aorus" logo would pop up then a Verbose flash before Clover screen appeared. I was worried it had corrupted my bios. Then I spotted this thread, glad I did. After using your latest apfsefi fix its back to normal. Thanks again, it was an annoying verbose scroll and it seemed to grow over time. Now it gives normal bios symbol then clover pops up like it should be. http://www.insanelymac.com/forum/topic/327584-apfsefi-without-verbose-boot/page-4?do=findComment&comment=2526193 Gigabyte AX370 Ryzen 7 1700 with RX Vega 64 in High Sierra 13.1 DB 5, my Intel systems don't have this issue with apfs mode, just my Ryzen rig. Link to comment Share on other sites More sharing options...
ydeng Posted November 1, 2017 Share Posted November 1, 2017 Thanks modbin, that did the trick, the message is now gone Unfortunately I'm not at your expert level so I am not sure exactly how I can know which values to change. Is it simply that hex code 0x75 prints something, and whenever I find it I can disable the printout by changing to 0xEB? 0x90 is the opcode for nop. here's a disassembler to help https://defuse.ca/online-x86-assembler.htm#disassembly2 eb 25 -> jmp 0x27 1 Link to comment Share on other sites More sharing options...
xtddd Posted November 3, 2017 Share Posted November 3, 2017 Here you go apfs.efi should be necessary to update after macos new version release? Link to comment Share on other sites More sharing options...
crusher Posted November 3, 2017 Share Posted November 3, 2017 No. Sent from my A5 2017 using Tapatalk 1 Link to comment Share on other sites More sharing options...
PMheart Posted November 7, 2017 Share Posted November 7, 2017 Hi. Found an easier way to eliminate apfs verbosity - patching logging function. Try this one and report. 00 74 07 B8 FF FF -> 00 90 90 B8 FF FF 10 Link to comment Share on other sites More sharing options...
telepati Posted November 7, 2017 Share Posted November 7, 2017 Hi. Found an easier way to eliminate apfs verbosity - patching logging function. Try this one and report. 00 74 07 B8 FF FF -> 00 90 90 B8 FF FF Should I add this BootPatches right? Link to comment Share on other sites More sharing options...
Recommended Posts