Skip to content

m1n1 user guide: document build/kmutil target #266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
flokli wants to merge 1 commit into
base: main
Choose a base branch
from
+21 −0
Open

m1n1 user guide: document build/kmutil target #266

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/sw/m1n1-user-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,16 @@ $ docker-compose run m1n1 make

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.

### kmutil target

@jannau jannau Jun 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please update for the kmutil.py script


There's also a `build/kmutil` make target, which includes a single script that can be fetched and executed from 1TR.
To build that, and expose it via a webserver, run:

```shell
ip -br a s

@jannau jannau Jun 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while somewhat helpful the ip command looks a little odd here. I would expect anyone using this to be familiar with their local network. kmutil.py itself could print network info at startup. I'm not going to implement that but would accept PRs.

make build/kmutil && python3 -m http.server --directory build
```

## Installation

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

This assumes you manually fetched the m1n1-stage1.bin from somewhere.
If you used the `build/kmutil` target above, you can also:

```

@jannau jannau Jun 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing shell annotation

sh <(curl HOST:8000/kmutil)
Comment thread
flokli marked this conversation as resolved.

@jannau jannau Jun 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with kmutil.py the URL could be simplified to HOST:8000.

```

This script contains the m1n1 binary and runs `kmutil configure-boot` with it.

Make sure to trust the network you're running this from.

On older versions (not recommended), you need the `macho` instead:

```
Expand Down