06-27-2018, 10:59 PM
(06-27-2018, 10:01 PM)pfeerick Wrote:(06-26-2018, 10:33 PM)chadc Wrote: The Xenial image is named with the date of 20160528...This is for a Pine64 2GB. Yes, a normal update using the Mate GUI app.
Sounds like I either (a) try to start with a fresh image or (b) keep working to get the SD mounted on another system.
Sounds like that is an older image still... so unfortunately it would have been broken from install as far as the GUI update app (although a command-line apt update worked just fine?!)
(06-27-2018, 06:07 PM)chadc Wrote: Solved. With gparted via Ubuntu running on another PC, I was able to move the mmcblk0p2 partition and then enlarge mmcblk0p1. Unfortunately, gparted wouldn't go higher than 128MB with a FAT16 file system. But, this will do.
Fantastic. Be interesting to know why the updater app thinks that much free spaces is needed for, because the kernel updates don't use that much space, etc... and updating from the command line used to work just fine.
Agreed. During the update, had a DF running and it barely touched the boot device. Something wrong with Updater.