Since I first got my cool-pi 5b back in February, I've been able to install the pre-built (Desktop) images, but there's been one hitch—including with the most recent ubuntu-23.04 June 13th image: if I perform any upgrades, whether by terminal "apt upgrade" command or by the GUI Software Updater, my image becomes unbootable.

I suspect the challenge is with the rebuilding of the kernel and/or modules and/or updating the bootloader. I'm used to working with Grub on traditional x86 systems, so I don't know what manual steps to take to make sure the bootloader is going to be able to start up.

Does anyone have any advice or references? Ultimately, I'm going to want to be able to apply software updates without worrying about rebuilding everything from scratch again!

@george Thanks for checking. That's really strange. At first I thought the issue was associated with the monitor—some HDMI compatibility glitch—but was able to get the same behavior across three different televisions. I've done it with both the 20230424 and 20230306 Ubuntu 22.04 images as well as the new 23.04 image. I've even installed the image on both the SSD care and the built-in eMMC.

I've also kept syslog and dmesg logs open (on an SSH session) and I'm not seeing any messages that make sense. All I know is that the instant I hit the OK button to log out or restart or shutdown, the screen freezes and the mouse pointer doesn't move. But it doesn't happen with the built-in default "coolpi" account.

If anyone has any theories or ideas of what I might capture to further diagnose, let me know.

I've been having a strange recurring issue with the Ubuntu desktop images, including the most recently posted version 23.04 dated 20230508.

If I create a new user account for myself and log into that account, any attempt to either shutdown, reboot, or even simply to log out causes the UI to freeze. I can remotely log in via SSH, but even if I issue a manual "shutdown -h now" command, nothing happens. It's like there's some graphical subsystem process that can neither be terminated or restarted.

I've been trying to diagnose this for a few weeks, and I've reflashed images many times. It was just today that I realized that the problem doesn't manifest as long as I use the default "coolpi" account. I'm curious if anyone else has run into this issue, or if there are any recommendations for further diagnosis. I'd love to do anything I can to help fix this for myself and others.

Cheers!

cool-pi-4-model-b-v1.1-english.pdf

Due to the magical powers of Google Translate, here is an English version of the user's guide!

When I first got my new Cool Pi model 4B, I plugged it into my monitor via the Micro DisplayPort plug. When I powered it up, nothing happened. I was afraid I had a defective unit, but I have an HDMI TV (not very great for computing purposes) so I got a microHDMI cable and that worked.

While I'm glad to be able to start playing around with my new Cool Pi, I would ideally like to use the Micro DisplayPort for my graphics. Is there any advice on how to get that to work? (I'm using the pre-installed Ubuntu release that was installed on the onboard eMMC.)

I see that in the /etc/apt/sources.list file, most of the mirrors are set to https://mirrors.ustc.edu.cn/ubuntu-ports/. I'm in the United States and would like to change this to a local mirrors, but I want to be cautious in case this repository has specific configurations to the Cool Pi 4B.

Is it safe for my to update those mirrors to something like https://mirrors.mit.edu/ubuntu-ports/ ?