01-31-2017, 07:34 AM
I have a Pine A64 2GB, with a 32GB microSD. Monitor is 27 inch Iiyama 1920 x 1080 with HDMI connection
I downloaded Longsleep's Ubuntu image 'https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ubuntu/xenial-pine64-bspkernel-20161218-1.img.xz'
The image was transferred to the microSD using my 64 bit Ubuntu Mate 16.04 system, using 'xzcat xenial-pine64-bspkernel.xz|pv|sudo dd of=/dev/sdd bs=1M oflag=sync'
I then transferred the MicroSD to the Pine and booted it. I logged in as ubuntu and ran 'sudo /usr/local/sbin/resize_rootfs.sh'
Following resizing of the root filing system, I rebooted and ran 'sudo /usr/local/sbin/install_mate_desktop.sh'
Rebooting after this, I get the Mate login screen and login as ubuntu.
So far, so good. It looks excellent!
However, I did a check for updates and there are some.
But Ubuntu tells me there isn't enough space on /boot to do the updates.
I've checked the structure of the MicroSD and there is a small unallocated space at the beginning, /boot, which is about 52MB followed by / which takes up the rest of the 32GB space.
Is there a reason why the updates are trying to install to /boot rather than /?
I downloaded Longsleep's Ubuntu image 'https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ubuntu/xenial-pine64-bspkernel-20161218-1.img.xz'
The image was transferred to the microSD using my 64 bit Ubuntu Mate 16.04 system, using 'xzcat xenial-pine64-bspkernel.xz|pv|sudo dd of=/dev/sdd bs=1M oflag=sync'
I then transferred the MicroSD to the Pine and booted it. I logged in as ubuntu and ran 'sudo /usr/local/sbin/resize_rootfs.sh'
Following resizing of the root filing system, I rebooted and ran 'sudo /usr/local/sbin/install_mate_desktop.sh'
Rebooting after this, I get the Mate login screen and login as ubuntu.
So far, so good. It looks excellent!
However, I did a check for updates and there are some.
But Ubuntu tells me there isn't enough space on /boot to do the updates.
I've checked the structure of the MicroSD and there is a small unallocated space at the beginning, /boot, which is about 52MB followed by / which takes up the rest of the 32GB space.
Is there a reason why the updates are trying to install to /boot rather than /?
