Discussion in 'High Sierra Desktop Support' started by baryw, Sep 22, 2017.
Sleep worked fine.
Thats good. Dont see why it shouldn't.
"Just remember to install Kext Correctly."
Sound like something they should teach you at school.
By the way, I have another computer (same as this one) but without a GPU that I will update next week. It should go much smoother! I have definitely learned a lot.
Certainly. Enjoy your hack .
If its the same as H77N-WIFI or Z77N-WIFI create a new post over at (Guide) H77N-WIFI with Intel HD4000 using Clover UEFI Hotpatch | tonymacx86.com
Will do. I am sure this upgrade will go much smoother. Should I avoid APFS? It seems like most people don't think it is worth it.
I think you mentioned that you didn't do it.
Better to avoid APFS conversion on a Hack. Stick with HFS+.
I didn't migrate to APFS on my Desktop. Read Post #10.
Same here, On nVME Samsung EVO 960 it takes 20sec or less. I'm with you its not that problem to break a working set-up. But I like to get it solved. I tried nvram erase / SSD trim turn off / And rebuild caches. It looks that it rebuilds the whole kextcache every time because I see a lot sustained access to the nVME drive. ... reading... reading... Wonderfull You found the fix! There are two questions remaining for me and possibly for others as well:
Why is this delay happening with APFS?
Why is this delay happening also on my daughters iMac 21,5 inch?
The common factor is that in 1) a hack is used with an unofficial SSD (nVME Samsung EVO 960) and in 2) there is an unofficial supported SSD used (Samsung EVO 850).
Next weekend I make time to get rid of APFS and go back to HFS+ as mentioned clearly explained by Rehabman. Further I'm impressed by VioletGragon and Rehabman how committed those guys are to help baryw. I would like to share my honest respect to those guys.
VDragon - Today I updated my system from the latest beta to Release. Regrettably all the work we did to fix sound didn't stick. I am back to not seeing any outputs.
I did re-read all of our notes and you mentioned that after an update I should run a command in the Terminal two times. I ran it three times but no luck.
The info from terminal wasn't anything with errors. Standard responses as far as I could tell.
Not sure if it interests you but do you want to troubleshoot? I can send you my output if you want. Did you have any issues when you updated?
Separate names with a comma.