You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
+
7
17
### Xenon Linux Loader (XeLL / Bootloader)
8
18
9
19
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:
36
46
3. Final partition is ext4
37
47
38
48
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.
39
50
40
51
Get the pacman.conf file here to your disk:
41
52
```
@@ -137,7 +148,7 @@ Server = https://repo.wii-linux.org/arch/extra/$arch
137
148
```
138
149
139
150
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`
**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.
168
179
169
180
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.
0 commit comments