Apply microSD write tweaks; correct docs: neon is on the built-in microSD slot

commit=30 on the root fs, journald capped at 100M, smartmontools disabled.
The neon root is a microSD card in the built-in slot (USB-attached reader),
not an external USB card; wording fixed across docs and the install script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ergosteur
2026-09-27 13:18:03 -04:00
co-authored by Claude Opus 5.5
parent c8afa460f4
commit 5374c2a5ed
5 changed files with 32 additions and 14 deletions
+4 -4
View File
@@ -7,10 +7,10 @@ hp-chell (HP Chromebook 13 G1, MrChromebox UEFI firmware) dual-boots:
| OS | Disk | Notes |
|---|---|---|
| KDE neon | `sda`, external USB/SD card (117GB) | primary OS, owns GRUB |
| KDE neon | `sda`, microSD card in the built-in slot (117GB; the reader is USB-attached internally) | primary OS, owns GRUB |
| FydeOS (was ChromeOS Flex) | `mmcblk0`, internal eMMC (29GB) | installed from neon, see below |
Because neon lives entirely on external media, the eMMC can be wiped and
Because neon lives entirely on the microSD card, the eMMC can be wiped and
reinstalled from the running neon system with no risk to neon.
## Installing / reinstalling
@@ -177,9 +177,9 @@ Two ways:
Run `sudo update-grub` after editing `40_custom`. The install script
rewrites the `--fs-uuid` value automatically.
2. **From the firmware boot picker** (MrChromebox UEFI, `Esc` during
POST): `efibootmgr -v` shows `neon` (Boot0005, on the USB card) and
POST): `efibootmgr -v` shows `neon` (Boot0005, on the microSD card) and
`Internal eMMC` (Boot0001), with `BootOrder` `0005,0001,0000,0003,0002`.
With the USB card unplugged, the firmware falls through to `Internal
With the microSD card removed, the firmware falls through to `Internal
eMMC` and boots FydeOS with no menu.
## Flex takes over the UEFI boot order on updates