Replies: 14 comments 29 replies
-
Beta Was this translation helpful? Give feedback.
-
Is this supposed to fix the shortcoming that only 2/3 or 3/4 of the unified memory can be used for Metal inference? If so, I am very eager to test it out and would like to thank you for your contribution! I am wondering if "reduced security" is only temporary. Can you enable full security after the patch? Did you also ping @ggerganov - I guess he will also be interested in this concept |
Beta Was this translation helpful? Give feedback.
-
Yes, this fixes that. You need relaxed security or else it will boot the unpatched kernel. This is why changing the security level undoes the patch. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your work! I understand that it will not boot a custom kernel with full protection, comparable to a locked (secure) bootloader on a phone. However I would advice against people disabling or loosening their security unless they understand all the risks associated. It can open a path to sophisticated and persistent threats, especially when working in AI research as some of us are. More info: https://support.apple.com/guide/security/startup-disk-security-policy-control-sec7d92dc49f/web I know someone at the Apple software engineering team. I will try to ask him if they can consider upping the limit a bit or if there is a way to use a similar approach without sacrificing on security. (I guess it will be difficult but I can at least give it a shot) |
Beta Was this translation helpful? Give feedback.
-
That's an interesting find! but with your current approach we need both disabled SIP (protects the entire system by preventing the execution of unauthorized code) AND reduced security boot policy? what happens if you re-enable SIP but keep reduced security boot policy? |
Beta Was this translation helpful? Give feedback.
-
not quite sure, you need sip disabled to write to /library/kernelcollections |
Beta Was this translation helpful? Give feedback.
-
This is great progress! I agree that permanently disabling SIP and Full security is a risk some might not want to take too lightly. I think it would be good if some more eyes could look at this. I will also ponder about another way of implementing this change
|
Beta Was this translation helpful? Give feedback.
-
Hey @r3muxd As you might know the new MacOS 14 (Sonoma) Public Beta 3 has been released and includes some updated CoreML and other libraries which are used in AI development. I had to update to the 14.0 beta to work on some AI projects that required the updated frameworks. Do you think this script works on MacOS 14 Beta or will this code need an update? I will be happy to help/test and figure it out with you! However, I can use the help and you already have some expertise from creating this in the first place :) I tried the script before on my older Macbook Pro M1 Pro and it seemed to work but I am just a bit on the cautious side with my new M1 Max MBP. |
Beta Was this translation helpful? Give feedback.
-
just try it, worst come to worst you'll need to flip back on security when
you get booted to recoveryos if theres an error
if the pattern is wrong for new MacOS, then you'll get an error running the
script and nothing will happen
…On Monday, August 14, 2023, CyborgArmy83 ***@***.***> wrote:
not quite sure, you need sip disabled to write to
/library/kernelcollections or at least you need it to delete from it, which
is necessary if you patch again maybe you could avoid it by writing to
another path that's not sip protected but idk where the physical file on
disk isnt the actual kernel that gets booted from fwiw because you can rm
or corrupt the entire file you set-boot-object'd and it will still boot
Hey @r3muxd <https://github.com/r3muxd>
As you might know the new MacOS 14 (Sonoma) Public Beta 3 has been
released and includes some updated CoreML and other libraries which are
used in AI development. I had to update to the 14.0 beta to work on some AI
projects that required the updated frameworks.
Do you think this script works on MacOS 14 Beta or will this code need an
update? I will be happy to help/test and figure it out with you! However, I
can use the help and you already have some expertise from creating this in
the first place :)
I tried the script before on my older Macbook Pro M1 Pro and it seemed to
work but I am just a bit on the cautious side with my new M1 Max MBP.
—
Reply to this email directly, view it on GitHub
<#2182 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK7NTZTI4ZZGM7Q42GVXMJTXVHW2PANCNFSM6AAAAAA2GNVSEI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@r3muxd I’m having some trouble following the instructions for my system on the latest (stable) macOS Ventura. When I boot into recovery, the directory The KernelCollections directory on my system is available at Did you need to do any additional steps after booting into recovery, before running the script? Thanks for any help! I’m looking forward to running Q4_K_M falcon 180B if I can get this to work. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for this. I'm getting this error: I'm on macOS Sonoma 14.1, M2 Air 24GB. Trying to set percent to 87.5. Any help would be appreciated. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Folks... just do: |
Beta Was this translation helpful? Give feedback.
-
It’s expecting a value in megabytes. So if you’re using RAM math instead of HD/SDD math, for 60GB you’d want 60*1024 = 61440
…-Ken
On Nov 29, 2023, at 11:48 AM, CyborgArmy83 ***@***.***> wrote:
For those who've already tried this
What does this line sudo sysctl iogpu.wired_limit_mb= expect?
is the value within the brackets on the end a percentage value like 0-100% or a number in mb? like "60000" for 60GB
—
Reply to this email directly, view it on GitHub <#2182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH24SEDLJZZ3CNWUIWEFSCLYG6GRBAVCNFSM6AAAAAA2GNVSEKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOMBZGI4DA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
(Sorry for necrothreading, but I've spent some serious time looking for the solution for this particular problem, and I think I found the easiest one) What worked for me (Sonoma) is to create sysctl.conf, and add appropriate parameter to it:
and inside:
(as already mentioned, the number is max RAM in MB that GPU can have; select some value reasonable for your machine). I'm not sure why /etc/sysctl.conf does not exist by default (good old unix habit is to put some template with commented out defaults), but as far as I know sysctl is not deprecated, so it should keep working. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
All reactions