Can't use L5 after update!

[MV71]

@guru

@irvinewade

I think it is best to ignore your questions about software development - and we will focus on attempting to get your Librem 5 up and running!

I’m a developer with 30++ years on UNIX. That a kernel installer into such a small device does not check for free space and let you at the end with a non-boot-able system, is clearly a bug and should be fixed asap, even without waiting for an upstream fix. Or with a clear message to all users like “before installing any kernel check for at least nnn free Mbytes below /boot”.

you’re totally right

[7p5l]

I’ve had the exact same problem and just reflashed the phone following the instructions that can easily be found in this forum. The instructions are technical, yes, but there’s nothing particularly difficult about them.

Coming from the software development field myself, I have to say that s**t like this simply just happens. Especially when you have a niche product, the revenue of which can only support a small test team. In this instance the update obviously wasn’t tested on a sufficiently “mature” phone and nobody was aware that space can run out when you’re performing many kernel updates in a row without reflashing. I can’t blame them, I’ve had similar stuff happen on my watch. Hindsight is always 20/20.

In think it is important to point out that, while expensive, the L5 overall is by far the best privacy-focused Linux phone money can buy. IMHO, Purism has been doing an amazing job. Could they improve? Sure, but at the same time it’s obvious that you can’t expect the same perfection you see with devices that are produced in the millions (the revenue of which can support orders of magnitude larger development & testing teams).

[irvinewade]

@MV71

I’m using Ubuntu 20.04.3 LTS…

So you have a problem then. Possible solutions that I can think of.

• Upgrade your Ubuntu. On the one hand, being more current is a good thing anyway. On the other hand, you may have a specific reason for wanting to stick with LTS (in which case you would be waiting until April, probably a little later, before being able to upgrade, and that isn’t likely to work in this scenario).
• Install the latest Ubuntu on a portable drive.
• Create a live bootable version of the latest Ubuntu on a portable drive (e.g. flash drive), choosing the ‘persistence’ option. (This is probably faster and easier than the previous approach.) You use Startup Disk Creator for this.
• Build uuu yourself using my instructions - which were specifically written originally for Ubuntu 20.04 so that could work well. https://source.puri.sm/Librem5/community-wiki/-/wikis/Building-uuu-and-Jumpdrive (note: in this case there is no need to build Jumpdrive, you would only need to build uuu)
• Find someone nearby who can do any of the above for you.

[MV71]

Hi irvinewade,
first of all and regardless of I 'll able to solve the issue thank you very much for your help.
I’ll try to download the latest version and create a live bootable version.
A question about: what is the ‘persistence’ option?
Then I’ll try to follow your instruction

@irvinewade

@MV71

I’m using Ubuntu 20.04.3 LTS…

So you have a problem then. Possible solutions that I can think of.

• Install the latest Ubuntu on a portable drive.
• Create a live bootable version of the latest Ubuntu on a portable drive (e.g. flash drive), choosing the ‘persistence’ option. (This is probably faster and easier than the previous approach.) You use Startup Disk Creator for this.
• Build uuu yourself using my instructions - which were specifically written originally for Ubuntu 20.04 so that could work well. https://source.puri.sm/Librem5/community-wiki/-/wikis/Building-uuu-and-Jumpdrive (note: in this case there is no need to build Jumpdrive, you would only need to build uuu)
• Find someone nearby who can do any of the above for you.

[irvinewade]

@MV71

what is the ‘persistence’ option?

It sets aside a portion of the space on the flash drive for use as permanent (persistent) storage, over and above the contents of the flash drive that are used for the live bootable image. Maybe it is the default these days.

Anyway, worst case if you have two flash drives then you could use one flash drive as the live boot and the other flash drive to hold the files that you download and unpack in Steps 2, 3 and 4 (which you can do on most versions of most distros i.e. you can do in advance on your existing version of Ubuntu).

[Quarnero]

@MV71

Can I follow the procedure (which one? I see many adds…) using my desktop with Ubuntu distro?

@MV71, buongiorno, please reread this main post and start from the very first step:

@mladen

On your computer with GNU/Linux system:

1. Install the package uuu , on PureOS and other Debian based systems, from a terminal run the command: sudo apt install uuu
2. Open terminal and run command: mkdir jumpdrive && cd jumpdrive (creates new folder and changes location to it)
3. Download: wget https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/purism-librem5.tar.xz
4. Unpack: tar -xf purism-librem5.tar.xz

P.S. I just guess here that uuu package might be available within your Linux distro as well:
$ apt list uuu

[MV71]

@irvinewade

@MV71

I’m using Ubuntu 20.04.3 LTS…

So you have a problem then. Possible solutions that I can think of.

• Create a live bootable version of the latest Ubuntu on a portable drive (e.g. flash drive), choosing the ‘persistence’ option. (This is probably faster and easier than the previous approach.) You use Startup Disk Creator for this.

Done

• Build uuu yourself using my instructions - which were specifically written originally for Ubuntu 20.04 so that could work well. https://source.puri.sm/Librem5/community-wiki/-/wikis/Building-uuu-and-Jumpdrive (note: in this case there is no need to build Jumpdrive, you would only need to build uuu)
• Find someone nearby who can do any of the above for you.

With 21.04 live I’m facing a ‘problem’: following the instruction I got an error with:
sudo apt install libzip-dev
after reading the dependency, build the dependency root
I got
impossible to find libzip-dev package (translated from italian)
Is it possible that the name package for 21.04 is libzip4?
Solved
but an other issue:
doing the clone
git clone https://source.puri.sm/Librem5/librem5-devkit-tools.git
the terminal asks:
username for: 'https://source.puri.sm
and
password…

[amarok]

@amarok

You should be able to tap on each one, then scroll upwards to reveal its size.

Actually, I’m wrong: I just noticed that the size of the packages available for download isn’t displayed here in the Store app.

Just for info, one way to see the size of the update first is to do it in the terminal:
sudo apt update && apt list --upgradable -a, then
sudo apt upgrade if there are updates found.
You will see how large each download will be.
(Don’t worry, you can still cancel the upgrade with “N” when it asks you if you want to proceed.)

[amosbatto]

@MV71

but an other issue:
git clone https://source.puri.sm/Librem5/librem5-devkit-tools.git
the terminal asks:
username for: 'https://source.puri.sm
and
password…

I’m able to git clone without entering a username/password on my PC (Debian bullseye). However, you can use these commands instead of git clone:

wget https://source.puri.sm/Librem5/librem5-devkit-tools/-/archive/pureos/byzantium/librem5-devkit-tools-pureos-byzantium.tar.gz
tar -xzf librem5-devkit-tools-pureos-byzantium.tar.gz
cd librem5-devkit-tools-pureos-byzantium

[pure_fede]

buongiorno a te, sono utente italiano da Brescia e se posso aiutarti, volentieri.
Tieni anche conto che c’è una discussione aperta sul forum di Debianizzati:
https://forum.debianizzati.org/viewtopic.php?t=56325

[MV71]

Ciao pure_fede, felice di leggerti.
Sto provando a seguire il percorso di irvinewade ma sto incontrando diversi problemi con error.
Io sono di Trento.
Al momento non sono molto fiducioso di riuscire a risolvere il problema da solo…
Se tu sei in grado posso pure mettermi in macchina e venire giu a Brescia a portartelo per metterlo a posto… sono cose troppo tecniche per me…

[MV71]

@amosbatto

@MV71

but an other issue:
git clone https://source.puri.sm/Librem5/librem5-devkit-tools.git
the terminal asks:
username for: 'https://source.puri.sm
and
password…

I’m able to git clone without entering a username/password on my PC (Debian bullseye). However, you can use these commands instead of git clone:

wget https://source.puri.sm/Librem5/librem5-devkit-tools/-/archive/pureos/byzantium/librem5-devkit-tools-pureos-byzantium.tar.gz
tar -xzf librem5-devkit-tools-pureos-byzantium.tar.gz
cd librem5-devkit-tools-pureos-byzantium

I guess I made a mistake…

ubuntu@ubuntu:~/librem5-devkit-tools-pureos-byzantium$ ./scripts/build_uuu.sh -i
Clone in ‘mfgtools’ in corso…
warning: redirezione a https://source.puri.sm/Librem5/mfgtools.git/ in corso
remote: Enumerating objects: 2991, done.
remote: Total 2991 (delta 0), reused 0 (delta 0), pack-reused 2991
Ricezione degli oggetti: 100% (2991/2991), 3.30 MiB | 2.02 MiB/s, fatto.
Risoluzione dei delta: 100% (2084/2084), fatto.
CMake Warning (dev) in CMakeLists.txt:
No project() command is present. The top-level CMakeLists.txt file must
contain a literal, direct call to the project() command. Add a line of
code such as

project(ProjectName)

near the top of the file, but after cmake_minimum_required().

CMake is pretending there is a “project(Project)” command on the first
line.
This warning is for project developers. Use -Wno-dev to suppress it.

– The C compiler identification is GNU 10.3.0
– The CXX compiler identification is GNU 10.3.0
– Detecting C compiler ABI info
– Detecting C compiler ABI info - done
– Check for working C compiler: /usr/bin/cc - skipped
– Detecting C compile features
– Detecting C compile features - done
– Detecting CXX compiler ABI info
– Detecting CXX compiler ABI info - done
– Check for working CXX compiler: /usr/bin/c++ - skipped
– Detecting CXX compile features
– Detecting CXX compile features - done
– Found PkgConfig: /usr/bin/pkg-config (found version “0.29.2”)
– Checking for module ‘libusb-1.0>=1.0.16’
– Found libusb-1.0, version 1.0.24
– Checking for module ‘libzip’
– No package ‘libzip’ found
CMake Error at /usr/share/cmake-3.18/Modules/FindPkgConfig.cmake:545 (message):
A required package was not found
Call Stack (most recent call first):
/usr/share/cmake-3.18/Modules/FindPkgConfig.cmake:733 (_pkg_check_modules_internal)
libuuu/CMakeLists.txt:8 (pkg_check_modules)

– Configuring incomplete, errors occurred!
See also “/home/ubuntu/librem5-devkit-tools-pureos-byzantium/build/mfgtools/CMakeFiles/CMakeOutput.log”.
make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
make: *** Nessuna regola per generare l’obiettivo «install». Arresto.
ubuntu@ubuntu:~/librem5-devkit-tools-pureos-byzantium$

[MV71]

[quote=“Quarnero, post:161, topic:16245, full:true”]

@MV71

Can I follow the procedure (which one? I see many adds…) using my desktop with Ubuntu distro?

@MV71, buongiorno, please reread this main post and start from the very first step:

[quote=“mladen, post:14, topic:16245”]
On your computer with GNU/Linux system:

1. Install the package uuu , on PureOS and other Debian based systems, from a terminal run the command: sudo apt install uuu

Impossible to find the package uuu

[Quarnero]

@MV71

Impossible to find the package uuu

Yes, I see now things that @irvinewade explained:
https://packages.ubuntu.com/hirsute/uuu
https://packages.ubuntu.com/impish/uuu

You might download one of above .deb files and proceed with:
sudo dpkg -i uuu_1.4.77-1_amd64.deb – by expecting that few dependencies might be needed to be added.

[MV71]

[quote=“7p5l, post:157, topic:16245, full:true”]
I’ve had the exact same problem and just reflashed the phone following the instructions that can easily be found in this forum. The instructions are technical, yes, but there’s nothing particularly difficult about them.

I’m sure… in your case…

Coming from the software development field myself, I have to say that s**t like this simply just happens. Especially when you have a niche product, the revenue of which can only support a small test team.

Well, I can accept many ‘errors’ but not of this ‘size’ and ‘duration’. Not all, have software development experience… me not at all

In this instance the update obviously wasn’t tested on a sufficiently “mature” phone and nobody was aware that space can run out when you’re performing many kernel updates in a row without reflashing. I can’t blame them, I’ve had similar stuff happen on my watch. Hindsight is always 20/20.

Doesn’t help me at all…

In think it is important to point out that, while expensive, the L5 overall is by far the best privacy-focused Linux phone money can buy. IMHO, Purism has been doing an amazing job. Could they improve? Sure, but at the same time it’s obvious that you can’t expect the same perfection you see with devices that are produced in the millions (the revenue of which can support orders of magnitude larger development & testing teams).

Never thought in a different way… but the problem is still in front of me and I have many doubts that I’ll be able to solve it ; an error of this ‘magnitude’ IMHO it is difficult to understand…

[Quarnero]

@MV71

but the problem is still in front of me and I have many doubts that I’ll be able to solve it ;

Now it is a bit late for myself but you’ll be able to solve things. Doesn’t need to be everything solved today.

[MV71]

@Quarnero

@MV71

Impossible to find the package uuu

Yes, I see now things that @irvinewade explained:
https://packages.ubuntu.com/hirsute/uuu
https://packages.ubuntu.com/impish/uuu

You might download one of above .deb files and proceed with:
sudo dpkg -i uuu_1.4.77-1_amd64.deb – by expecting that few dependencies might be needed to be added.

Thanks Quarnero but it’s too difficult for me to try to fix it. I don’t have enough knowledge
I cant’ do more than a copy and paste and if there is a problem I’m not able to go on.
hope to find here in Italy someone that will help me.

Anyway I learned a lesson. Never trust in new updates as I did on Librem5. I hope that even the developers will find a way to warn in time of any errors of this severity…

[Quarnero]

Please download this package: http://mirrors.kernel.org/ubuntu/pool/universe/m/mfgtools/uuu_1.4.77-1_amd64.deb and: cd /download_directory.

[MV71]

Do you mean this?

ubuntu@ubuntu:~$ cd Scaricati
ubuntu@ubuntu:~/Scaricati$ ls
libzip4_1.7.3-1ubuntu1_amd64.deb uuu_1.4.77-1_amd64.deb
ubuntu@ubuntu:~/Scaricati$

[Quarnero]

Now execute (copy from here): sudo dpkg -i uuu_1.4.77-1_amd64.deb and let us see result. Please copy/paste here result (if something missing).