Hey! Sorry for necro’ing this thread, but I’m seeing similar issues and wanted a place to paste my reform-check output other than IRC.
This is the output I see when I run the check:
I: Contents of /proc/device-tree/model: MNT Pocket Reform with i.MX8MP Module
I: `uname -a` output: Linux zephyr 6.15.6-mnt-reform-arm64 #1 SMP Debian 6.15.6-1~exp1+reform20250719T140750Z (2025-07-19) aarch64 GNU/Linux
I: Version of linux-image-mnt-reform-arm64: 6.15.6-1~exp1+reform20250719T140750Z
I: Version of reform-tools: 1.76-1+reform20250622T103710Z+1
I: Mount source of /: /dev/reformvg/root (LVM vg 'reformvg' on LUKS device 'reform_crypt' on SSD)
I: Mount source of /boot: /dev/mmcblk2p1 (eMMC)
I: the following files differ from how they are shipped by reform-tools (ignore /var/lib/alsa/asound.state):
??5?????? /var/lib/alsa/asound.state
I: kernel boot parameters which are the default but your system doesn't use them:
- fbcon=font:TER16x32
- console=ttymxc1
Things seem to be working OK, but I want to make sure reform-check is in a happy state to avoid any confusion in future updates. I’ve confirmed the ${bootargs} mentioned above are in my version of reform-tools, but I’m not sure the correct way to have them used when booting:
root@zephyr:/usr/share/reform-tools/machines# egrep fbcon 'MNT Pocket Reform with i.MX8MP Module.conf'
BOOTARGS="ro no_console_suspend cryptomgr.notests pci=pcie_bus_perf nvme_core.default_ps_max_latency_us=0 console=tty1 fbcon=rotate:3 fbcon=font:TER16x32 cma=256MB console=ttymxc1"