I tried more official or unofficial images to run any system over Le Potato. Any time it seems to have some sort of memory/file system problem.
When I flashed debian-12-base-arm64+aml-s905x-cc.img.xz
doas dd if=debian-12-base-arm64+aml-s905x-cc.img of=/dev/mmcblk0 bs=1M
I can see autoboot booting up GRUB. When I stop it, it seem to read all USB devices correctly. Though, if I wait for GRUB to load, the moment I see the GRUB command-line, keyboard stops being handled completely.
The same result with 2023-10-10-raspbian-bookworm-arm64+aml-s905x-cc.img
.
I assume it’s due to the same file system check (storage mount) error as below, but please help me debug this from here. I don’t know uboot, and GRUB does not allow me to type anything because of the mentioned problem.
LibreELEC (LibreELEC-AMLGX.aarch64-12.0.1-lepotato.img), on the other hand, gives me access to busybox featured console boot-loader, and presents me with this error
*** Error in mount_storage: mount_common: Could not mount LABLE=STORAGE ***
Lakka and older versions of LibreELEC also return storage mount error.
I run fdisk
and it reported two partitions on the sd card, which seems okay.
dmesg
provides some more explanation
fsck: couldn't find matching filesystem: LABEL=STORAGE
loop0: detected capacity change from 0 to 258744
LABEL=STORAGE: Can't lookup blockdev
followed by several “unable to read id index table”.
ALSA and init, in dmesg
, is as follows
ALSA device list:
#0: LIBRETECH-CC
Freeing unused kernel memory: 8320K
Run /init as init process
with arguments:
/init
with environment:
HOME=/
TERM=linux
boot=LABEL=LIBREELEC
disk=LABEL=STORAGE
Checking disk(s): LABEL=LIBREELEC LABEL=STORAGE