Skip to content

Commit 44fa2c7

Browse files
Enhance ARCHPower setup instructions
Added prerequisites for binfmt setup and updated installation instructions for ARCHPower. Thanks again to Mitchell for proof reading.
1 parent 4b66162 commit 44fa2c7

1 file changed

Lines changed: 13 additions & 2 deletions

File tree

docs/Linux/Distros/Arch/archpower.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,16 @@ TechFlash has packaged the Xenon Linux kernel into ARCHPower in 2025. This guide
44

55
## Prerequisites
66

7+
You must have binfmt set up on your host system. If your host system is Arch Linux:
8+
```
9+
pacman -Sy --needed arch-install-scripts qemu-user-static qemu-user-static-binfmt dosfstools util-linux e2fsprogs
10+
systemctl restart systemd-binfmt
11+
```
12+
If you are not using Arch Linux as a host machine then you will need to identify which packages are required on your system.
13+
14+
15+
16+
717
### Xenon Linux Loader (XeLL / Bootloader)
818

919
XeLL as the bootloader must be updated. The v0.993 release from years ago was built with the original toolchain and is
@@ -36,6 +46,7 @@ Format the partitions like this:
3646
3. Final partition is ext4
3747

3848
Identify and mount the ext4 block device to a mountpoint such as `sudo mount /dev/sdb3 /mnt/archpower`.
49+
You will also want to identify the PARTUUID of your root partition: `blkid -s PARTUUID -o value "/dev/sdb3"` -> save this to a file for later.
3950

4051
Get the pacman.conf file here to your disk:
4152
```
@@ -137,7 +148,7 @@ Server = https://repo.wii-linux.org/arch/extra/$arch
137148
```
138149

139150
Follow these steps to install ARCHPower to the external disk that will be booted by the 360. These steps assume Arch Linux is being used as the host operating system or otherwise your environemnt is set up to bootstrap Arch Linux.
140-
1. `pacstrap -KMC /PATH/TO/PACMAN.CONF /PATH/TO/TARGET_DISK_PARTITION base archpower-keyring linux-xenon networkmanager vim nano less wget openssh`
151+
1. `pacstrap -KMPC /PATH/TO/PACMAN.CONF /PATH/TO/TARGET_DISK_PARTITION base archpower-keyring linux-xenon networkmanager vim nano less wget openssh`
141152
2. `arch-chroot /PATH/TO/TARGET_DISK_PARTITION`
142153
3. `pacman-key --init`
143154
4. `pacman-key`
@@ -164,7 +175,7 @@ timeout=100 ; In seconds
164175
speedup=1 ; Full speed CPU
165176
linux_hdd="uda1:/vmlinuz-linux-xenon root=/dev/sda1 rw console=tty0 console=ttyS0,115200n8 panic=60 coherent_pool=16M" ; Linux kernel entry
166177
```
167-
**NOTE**: the final line will take some tuning unless you supply `root=PARTUUID=partuuid-02` as an example to definitively boot the detected device with this UUID. Identify the PARTUUID of your boot disk (NOT the filesystem UUID) using the `mount` command while the 360 boot drive is still plugged into the host OS. Otherwise if you are using the 360 SATA bay it is pretty good about being `sda`, but each *hard* power cycle of the 360 may vary.
178+
**NOTE**: the final line will take some tuning unless you supply `root=PARTUUID=partuuid-02` as an example to definitively boot the detected device with this UUID. Identify the PARTUUID of your boot disk (NOT the filesystem UUID) using the `mount` command while the 360 boot drive is still plugged into the host OS. Otherwise if you are using the 360 SATA bay it is pretty good about being `sda`, but each *hard* power cycle of the 360 may vary. Or, `blkid -s PARTUUID -o value "/dev/sdb3"` while your boot disk is plugged into your host machine still.
168179

169180
Boot your console to XeLL via any means available and enjoy ARCHPower! The rest of normal Arch Linux system setup and config can take place on the console itself with an attached keyboard.
170181

0 commit comments

Comments
 (0)