08-23-2025, 02:58 PM
I just got a pinetab-v as well and had a similar problem where it failed to start the graphical interface when booting from the pre-installed system image from emmc.
I was able to log in from the serial console from my pc using the uart adapter, only the GNOME graphical shell wouldn't start.
The issue turned out to be a corrupted file system. The kernel log was full of ext4 fs errors and running fsck (in read only mode since the file system was still mounted) found plenty of errors as well.
Putting the provided system image https://github.com/starfive-tech/Debian/...b-V-v1.3.0 onto an sd card worked fine and booted into the graphical interface without errors. Once you're running from the sd card and the emmc root partition (`[color=oklab(0.952331 0.000418991 -0.00125992)]/dev/mmcblk0p4[/color]`) is no longer mounted, you can run fsck on it to fix the file system errors (answer yes to all). After doing that, booting from the internal emmc worked properly and it successfully started the graphical interface.
The periodic ` [WARNING][BB]Skip gain error setting in scan status` message seems to be unrelated.
I was able to log in from the serial console from my pc using the uart adapter, only the GNOME graphical shell wouldn't start.
The issue turned out to be a corrupted file system. The kernel log was full of ext4 fs errors and running fsck (in read only mode since the file system was still mounted) found plenty of errors as well.
Putting the provided system image https://github.com/starfive-tech/Debian/...b-V-v1.3.0 onto an sd card worked fine and booted into the graphical interface without errors. Once you're running from the sd card and the emmc root partition (`[color=oklab(0.952331 0.000418991 -0.00125992)]/dev/mmcblk0p4[/color]`) is no longer mounted, you can run fsck on it to fix the file system errors (answer yes to all). After doing that, booting from the internal emmc worked properly and it successfully started the graphical interface.
The periodic ` [WARNING][BB]Skip gain error setting in scan status` message seems to be unrelated.
