Ubuntu 24.04 installation issues

Canonical Ubuntu Ubuntu OS issues
1

Dear RubikPi community,

I have a Rubik Pi 3 and want to flash the Canonical Ubuntu 24.04, from a Ubuntu desktop 24.04 Host.

Qualcomm Launcher Method

I tried to flash via the Qualcomm Launcher.
Sadly, the GUI logs return the following error:

File 2: gzip: /tmp/qualcomm_launcher/ubuntu-24.04-preinstalled-server-arm64+rubikpi3-20250912-127/ubuntu-24.04-preinstalled-server-arm64+rubikpi3-20250912-127.img.xz: unknown suffix -- ignored

Error in Unzip: Extraction failed: Extraction process exited with code 2

Manual Method

Then I tried to follow the manual method from Troubleshooting section as suggested if the Launcher wouldn’t work.

However on step 3 ( Flash Renesas ), the flash exits on the following error:

flashed "usb_fw" successfully
[1]    214802 segmentation fault (core dumped)  ./qdl --storage ufs prog_firehose_ddr.elf rawprogram*.xml patch*.xml

Moreover, I also want to point out that the link to download :link:rawprogram0.xml in step 4.c. is dead.

Rubik Pi forum

I also searched your forum. I was surpise to see that no one complains about the Launcher not working, so maybe this is an issue on my side (?).
The following link, though, seems to be related to ubuntu install issue and suggest an installation method that work for the OP, sadly the link is also dead, even though the post is quite recent.

Kludge around Launcher and manual methods

I noticed that the unzip issue could be fixed by hand since the /tmp/qualcomm_launcher dir is on the host, so I decompressed it with

unxz /tmp/qualcomm_launcher/ubuntu-24.04-preinstalled-server-arm64+rubikpi3-20250912-127/ubuntu-24.04-preinstalled-server-arm64+rubikpi3-20250912-127.img.xz

Then I applied the manual steps from this folder, And it seems to solve some issues, but Idoubt this is how we are supposed to use the Launcher.

Do you have any insight about why neither the Launcher would not work nor the manual version ?

Best regards, AP.

2

We are currently syncing this issue internally.

3

The Launcher:
Based on the error log, gzip is unable to extract the .xz file. May I ask if you downloaded the latest version of the Launcher?

The manual version：
Are you using an Ubuntu host?
Kindly verify the qdl version and whether you have run
sudo apt-get install libxml2-dev libudev-dev libusb-1.0-0-dev

4

Hi @kinkin,

Thanks for your answer. Here are the info you asked me for.

Launcher version:

❯ sudo apt list --installed | grep qualcomm

qualcommlauncher/now 1.2.1 amd64 [installed,local]

Manual install:

  1. Host machine:
    • OS: Ubuntu 24.04
    • kernel version: 6.11.0-26-generic
  2. libxml2-dev libudev-dev libusb-1.0-0-dev → Well installed
  3. Qdl version: 2.3.4

Follow up

By the way, I managed to install Ubuntu 24.04 on the Rubik Pi via the mix of the launcher version to download the image and install it manually after decompressing it with unxz, and then flashing it with qdl.
So I guess you just have to fix the decompression in the script launched by the Qualcomm Launcher.

And for the Manual method, you should also fix the dead link in the manual install. I think this one is easy for you.
And for the Manual Flash Renesas step, I don’t know why it does not work.

However, the Flash Renesas command (qdl --storage ufs prog_firehose_ddr.elf rawprogram*.xml patch*.xml) worked properly when I ran it from the directory created by the Launcher :

cd /tmp/qualcomm_launcher/ubuntu-24.04-preinstalled-server-arm64+rubikpi3-20250912-127/
qdl --storage ufs prog_firehose_ddr.elf rawprogram*.xml patch*.xml
5

I think latest version of Launcher has resolved this issue.
Please update to the latest version and try it again. Thank you!

6

Hi Rosh,

Thanks for your answer.
I see that Launcher v1.2.2 was released indeed.
However I’ve already started to work with the Rubik Pi, since I was finally able to install ubuntu as explained above.
Therefore I am not so willing to flash it again, and beta test the new launcher version.
But I trust you did a good job by testing it yourself.
So I guess we can close this issue.

N.B.: I notice that the manual method still has dead links I pointed above.

Best regards, AP

7

Thanks for your report!
So as we can coordinate with QC to fix this quickly.