On Sat, Jun 4, 2022 at 8:11 PM Stephen E. Baker <baker.stephen.e@xxxxxxxxx> wrote: > > I reached out on the archlinuxarm IRC room and amstan offered the use > of his device. > > When he boots my image he sees: > "EXT4-fs (sda2): can't mount with superblock charset: utf8-12.1.0 not > supported by the kernel. flags: 0x0." At amstan's request I created a new root filesystem without casefold, and created a loop device with casefold enabled. I am able to boot with that filesystem. zgrep UNICODE /proc/config CONFIG_UNICODE=y CONFIG_UNICODE_UTF8_DATA=y CONFIG_UNICODE_NORMALIZATION_SELFTEST=m mount /dev/loop0p1 /mnt [ 679.358591] EXT-fs (loop0p1): can't mount with superblock charset: utf8-12.1.0 not supported by the kernel. flags: 0x0 mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop0p1, missing codepage or helper program, or other error. So it seems I can produce the same error after boot that we saw in early boot, which makes debugging much easier. Given that is there anything I should be trying / looking for?
