Skip to content

Commit af4851f

Browse files
committed
m1n1 user guide: document build/kmutil target
Introduced in AsahiLinux/m1n1#573, simplifying the amount of manual steps a lot. Signed-off-by: Florian Klink <flokli@flokli.de>
1 parent 44bce7b commit af4851f

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

docs/sw/m1n1-user-guide.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,16 @@ $ docker-compose run m1n1 make
6464

6565
m1n1 stage 1 release builds packaged with the Asahi Linux Installer have both of those options set. m1n1 stage 2 release builds packaged by distros should just have `RELEASE=1` (since they do not need to chainload further) and thus do not need Rust to build.
6666

67+
### kmutil target
68+
69+
There's also a `build/kmutil` make target, which includes a single script that can be fetched and executed from 1TR.
70+
To build that, and expose it via a webserver, run:
71+
72+
```shell
73+
ip -br a s
74+
make build/kmutil && python3 -m http.server --directory build
75+
```
76+
6777
## Installation
6878

6979
### Stage 1 (as fuOS)
@@ -74,6 +84,13 @@ m1n1 (with your choice of payloads) can be installed from 1TR (macOS 12.1 OS/stu
7484
kmutil configure-boot -c m1n1-stage1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v <path to your OS volume>
7585
```
7686

87+
This assumes you manually fetched the m1n1-stage1.bin from somewhere.
88+
If you used the kmutil target above, you can also:
89+
90+
```
91+
sh <(curl HOST:8000/kmutil)
92+
```
93+
7794
On older versions (not recommended), you need the `macho` instead:
7895

7996
```

0 commit comments

Comments
 (0)