I'm having the EFI mounting issue also. The only way I can mount it is through Terminal with this command:
sudo mkdir /Volumes/EFI && sudo mount_msdos /dev/disk0s1 /Volumes/EFI
Make sure to replace disk0s1 with the correct disk and partition.
I saw someone mention somewhere else that it happens when you are running in a scaled resolution on a Retina display. This also applies to people with 4K monitors like me using a scaled resolution.
I updated a few days ago from 10.12.6 and got everything running smoothly. I noticed that after a few hours, WindowServer would be consuming 3GB+ of memory, with a few GB compressed. This caused noticeable slow downs. I am using a 1080 with the latest nvidia drivers for 10.13. Is this happening...
I do understand that, but also understand that a clean installation doesn't mean your EFI partition is clean. Did you start with a brand new clover install too? Do you actually have SIP fully enabled and it still doesn't work? SIP settings won't change with a clean install since clover sets it...
I installed directly over 10.12.6, not a clean install. I did install the drivers for 10.13 with SIP disabled once I booted for the first time (which loaded the basic graphic drivers, not the NVIDIA ones since they were for 10.12.6). Then I re-enabled SIP during boot up.
When booting right after High Sierra install, I installed them the normal way: using the driver package provided by NVIDIA. During boot, I went into clover options > System Parameters > changed System Integrity Protection to 0x00 and it booted with the drivers fully functional. Then I edited my...
I was having this problem too and already had the latest Lilu. I looked into what causes the driver installer to show that error upon installation and it is caused by the installer detecting that SIP is disabled for kext signing. I re-enabled SIP and was able to boot successfully.
Update: After leaving my system alone for a few hours, the CPU is now running better with XCPM; all the way down to 0.8GHz! No idea what could've changed, though. System was idle during my testing.
I'm having a problem(?) with this power management. For some reason, it causes my CPU to run at...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.