HoRNDIS 9.2 works perfectly on Apple Silicon (M1), macOS 12 Monterey with no code changes, as long as you compile the kext from source!
I'm glad to report that the latest version of HoRNDIS (9.2) works perfectly on Apple Silicon machines with no code changes required! Basically, just compiling an additional arm64e (not arm64) binary slice to the HoRNDIS kext works! @jwise Tested on macOS 12.0.1 21A559, "Monterey". (I do realise that this isn't really an _issue_ per se, but I just felt really bad for all the users complaining about broken functionality here…) (Plus, speaking from my own personal experience as a fellow developer, I _do_ find it quite helpful when someone else already tested compatibility for me ;P) --- ## If you're a general user coming who just wants to use HoRNDIS on Apple Silicon right this instant… Ever since macOS / OS X 10.10 Yosemite, Apple has required kernel extensions (kexts) to be signed by developers who are subscribed to the Apple Developer Program, who _also_ have to apply for a special kext signing privilege. You're… probably not one of those people. ;P Luckily, there _is_ a way for you to sign your own kexts using an Xcode feature called ad-hoc signing! But it does require changing some settings first. ### Switching to "Reduced Security" mode If you've _already_ placed your Mac in "Reduced Security" mode before, simply skip this section. 1. Shut down your Apple Silicon Mac. 2. Press and hold down the power button _until_ the text under the Apple logo says "Loading startup options…", then let go. 3. Select "Options". 4. You are now in recoveryOS — enter your password if
Posted by akemin-dayo on Nov 24, 2021, 10:15 AM
Tags
Related issues
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
- in the middel of a coding session with 5.6 sol.
- [Hero Run] 535B-A23B on 18T tokens
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
reliability (Other)
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I hate that this is how AI is being used..
inexperienced protobuf user here -- why do non-googlers generally use protobuf?
HoRNDIS 9.2 works perfectly on Apple Silicon (M1), macOS 12 Monterey with no code changes, as long as you compile the kext from source!
I'm glad to report that the latest version of HoRNDIS (9.2) works perfectly on Apple Silicon machines with no code changes required! Basically, just compiling an additional arm64e (not arm64) binary slice to the HoRNDIS kext works! @jwise Tested on macOS 12.0.1 21A559, "Monterey". (I do realise that this isn't really an _issue_ per se, but I just felt really bad for all the users complaining about broken functionality here…) (Plus, speaking from my own personal experience as a fellow developer, I _do_ find it quite helpful when someone else already tested compatibility for me ;P) --- ## If you're a general user coming who just wants to use HoRNDIS on Apple Silicon right this instant… Ever since macOS / OS X 10.10 Yosemite, Apple has required kernel extensions (kexts) to be signed by developers who are subscribed to the Apple Developer Program, who _also_ have to apply for a special kext signing privilege. You're… probably not one of those people. ;P Luckily, there _is_ a way for you to sign your own kexts using an Xcode feature called ad-hoc signing! But it does require changing some settings first. ### Switching to "Reduced Security" mode If you've _already_ placed your Mac in "Reduced Security" mode before, simply skip this section. 1. Shut down your Apple Silicon Mac. 2. Press and hold down the power button _until_ the text under the Apple logo says "Loading startup options…", then let go. 3. Select "Options". 4. You are now in recoveryOS — enter your password if
Comments (0)
No comments yet. Start the discussion.