After installing the Ubuntu 19.10.1 64-bit server image for Raspberry Pi 4, installing kubuntu-desktop, and rebooting, the system hangs during boot up. There appears to be no way to get to the desktop GUI. (Note: I've tried every available desktop, although Kubuntu is my preferred one. The results are the same for all of them.) The steps to reproduce the problem follow.
- Raspberry Pi 4B 4GB Model B with 1.5GHz 64-bit quad-core ARMv8 CPU (4GB RAM)
- 32GB SD card
- 500 GB external SSD
- ubuntu-19.10.1-preinstalled-server-arm64-raspi3.img image file downloaded from https://ubuntu.com/download/raspberry-pi.
Steps to reproduce
- Download image file and burn to SD card using Balena etcher (format FAT32).
- Also burn image file to external SSD using Balena etcher (format EXT4).
- Attach/insert both storage devices to Raspberry Pi 4.
- Boot Raspberry Pi 4. After changing ubuntu user password, boot up succeeds with no issues. In fact, at this point, I can SSH into the RPi and do pretty much anything I want to do from the PuTTY terminal. It's only when I try to add a GUI that the whole thing starts to crash.
- Install Kubuntu desktop with
sudo apt install kubuntu-desktop. No errors reported during installation. (Note: Performed these same steps for ubuntu-desktop, xubuntu-desktop, and a number of other desktops. All had the same results.)
Rebooted Raspberry Pi with
sudo reboot. Reboot occurred until it hung at [ 28.5791341] cloud-init: cloud-init v. 19.2-36. … At this point the system froze (Sorry for not having the full line at the point it froze. It's obviously on a different machine with a lot of strings letters and numbers, so copying and pasting is out of the question. It does report that cloud-init finished and the correct time for it finishing.
cloud-initprocess begins immediately following the snap application
lxd.activateservice starts successfully.
At this point the system hangs with the cursor on the line described in Item 6 above. I've tried pressing [Enter], entering Ctrl+C, and everything else I could think of; nothing will move the cursor or restart the process.
Of interesting note, at this point I can SSH (with PuTTY) into the Raspberry PI, successfully and can enter and execute all kinds of terminal commands with no problems. Thus, it's pretty clear that some process (cloud-init?) is hung, not the system.
Also, from the machine with SSH entry, I can do a
sudo reboot, several times, and it will successfully go through the reboot process until it hits the same point where it hung before, at which point, it will hang again, just like before.
Note that I am using an external SSD for the operating system. Using this methodology, the system uses the 32-Gb SD card for the bootloader, then switches automatically to the 500-Gb SSD on sdb for operations. Ubuntu has done a great job of making this happen automatically. It used to be a horrible ordeal to get it configured and working. Anyone who would attempt to run a system off an SD card has got to be a foolhardy soul who takes delight in being beaten up by attempting to do so, especially since SSDs have gotten to be dirt cheap. (Even with that, the Raspberry Pi folks have made it difficult by being picky about which external drive controllers the RPi will recognize and accept. Fortunately, folks like James Chambers have given us lists of those that do work. In decades of working with external drives, I never, ever had any problems with any external drive until the RPi 4B. And we still must have the SD card for the bootloader instead of booting directly to the SSD — something which the RPi 3 did quite nicely. Talk about one small step for RPi, one enormous, gigantic leap backwards! But I digress.) I've used this functionality before. Just wanted to let you know that it does work.
Also, sorry about the ineffective use of tags. StackOverflow's rules regarding tags prevent me from using something like
19.10.1 instead of
19.10, a difference which is critically import in this issue. Ditto for a multitude of other tags.