Can't use L5 after update!

[dos]

@Marts

And there is THREE eject button to unplug the Librem5 (I have a memory card). I clic on anyone to unmount?

Yup.

@Marts

How can I erease de file? I right clic on initrd.img and I don’t have the delete option!

You will have to do that with administrator’s privileges - but unfortunately I don’t know how to do that from the GUI. Maybe someone else can chime in on how to easily do that in GNOME.

[Marts]

Ok I hope a response of someone tomorow to erease this evil initrd.img!! Thanks very much every one!

[irvinewade]

@dos

You will have to do that with administrator’s privileges - but unfortunately I don’t know how to do that from the GUI. Maybe someone else can chime in on how to easily do that in GNOME.

That looks awkward because it seems to be broken right now for me. So it is going to depend on precisely what distro and version @Marts is running.

For a Ubuntu install that is completely up to date, it will fail with:

and the workaround seems worse than just attempting to delete the files from the command line. Just my opinion of course.

The internet says that the problematic package version is: gvfs 1.47.91
whereas the following works: gvfs 1.48.1

[pure_fede]

Install the package uuu , on PureOS and other Debian based systems
It should be noted that uuu in Debian is only available from Bullseye.

[angus.ainslie]

Only erase the initrd.img and vmlinuz on the 488 MB drive. Not on the other drives.

[Quarnero]

@Marts

And I hope it will work tomorrow!

After connecting your Librem 5 over Jumpdrive again, you’ll need to trust me on this post (explaining anything in writing isn’t field I familiar with and would take too long anyway, with too many grammatical mistakes), therefore:
sudo fdisk -l
sudo umount /dev/sdb1
sudo mount /dev/sdb1 /mnt
cd /mnt

Now please post your output within this thread with:
ls -lh

I’m expecting you to list/see following files:

@guru

-rw-r--r-- 1 root root  62M Jan 23 02:18 initrd.img
-rw-r--r-- 1 root root  62M Dec 10 07:55 initrd.img-5.13.0-1-librem5
-rw-r--r-- 1 root root  62M Jan  9 08:14 initrd.img-5.15.0-1-librem5
-rw-r--r-- 1 root root  62M Jan 23 02:17 initrd.img-5.16.0-1-librem5
-rw-r--r-- 1 root root  62M Jan  9 08:14 initrd.img.bak

If no other proposal here, I expect that you might free just about enough space by (should do to power/log on into your phone):
sudo rm initrd.img −− will free cca. 62 MiB within your Librem 5 /boot partition.
sudo rm vmlinuz
sudo apt update −− if PureOS in use.
sudo apt install rename
sudo rename initrd.img.bak initrd.img −− not tested by myself, still hope this works for you (or something similar).
sudo rename vmlinuz.bak vmlinuz

As mentioned already, before disconnecting your Librem 5 from USB Type-C cable you’ll need to:
cd /
umount /dev/sdb1
umount /dev/sdb2 −− actually not sure as it is encrypted and I cannot see through my crystal … time to take your Librem 5 battery out.

@mladen

Once you get the device booted you should clean up the failed parts, so run these commands in terminal, one by one:

13. sudo apt remove linux-image-5.13.0-1-librem5
14. sudo flash-kernel

@Marts, keep us informed, please. Also hope this time no mistakes from my side.

[Marts]

I have only done that and I can reopen my Librem5 with many bugs (no wifi, no power off, it’s write « dummy output » when I volume up or down…). Must I do all this things you said like :
sudo fdisk -l
sudo umount /dev/sdb1
sudo mount /dev/sdb1 /mnt
cd /mnt

Now please post your output within this thread with:
ls -lh

OR can I do only that?
sudo apt remove linux-image-5.13.0-1-librem5
sudo flash-kernel

[Marts]

when I say done that i forgot to say what I’ve done. It’s this :
You need to do this as root user. Steps:

1. press Ctrl+L shortcut when in file manager to view and copy full folder path
2. in terminal run command: “cd folder_path”, where “folder_path” is the folder path, location of these files
3. verify that you are in correct folder, run “ls” to list all files, check if “initrd.img” and “vmlinuz” are there
4. if yes, run:

sudo rm initrd.img

sudo rm vmlinuz

sudo mv initrd.img.bak initrd.img

sudo mv vmlinuz.bak vmlinuz

one by one.

[Quarnero]

@Marts

OR can I do only that?
sudo apt remove linux-image-5.13.0-1-librem5

NO. Please don’t do this when connected under Jumpdrive. Will not bring anything useful anyway.

[Marts]

What i must do now to remove the bugs and have the librem5 fully functional? I Jumpdrive back the Librem 5 and follow your post #75-76? or I only sudo flash-kernel on terminal of Librem5?

[Quarnero]

@Marts

I Jumpdrive back the Librem 5 and follow your post #75-76?

Perhaps to post your output with:
ls -lh

[Quarnero]

@Marts

sudo rm initrd.img

sudo rm vmlinuz

sudo mv initrd.img.bak initrd.img

sudo mv vmlinuz.bak vmlinuz

Is this done under the Jumpdrive usage?

[Marts]

Yes! It’s done under Jumpdrive.

I Jumpdrive back the librem5 and I ll try ls -1h And I tell you what happen

[Quarnero]

@Marts

ls -1h

This command is more like “LS -LH”, therefore please use: ls -lh.

[Marts]

@Quarnero

ls -lh

This is the new response of terminal :
ls -lh
total 312M
-rw-r–r-- 1 root root 2.3K Feb 6 21:54 boot.scr
-rw-r–r-- 1 root root 2.3K Feb 2 11:57 boot.scr.bak
-rw-r–r-- 1 root root 182K Nov 29 03:31 config-5.13.0-1-librem5
-rw-r–r-- 1 root root 182K Dec 20 11:34 config-5.15.0-1-librem5
-rw-r–r-- 1 root root 184K Jan 31 10:35 config-5.16.0-1-librem5
lrwxrwxrwx 1 root root 53 Feb 6 21:54 dtb -> dtbs/5.16.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
lrwxrwxrwx 1 root root 53 Dec 9 18:56 dtb-5.13.0-1-librem5 -> dtbs/5.13.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
lrwxrwxrwx 1 root root 53 Jan 10 08:23 dtb-5.15.0-1-librem5 -> dtbs/5.15.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
lrwxrwxrwx 1 root root 53 Feb 6 21:54 dtb-5.16.0-1-librem5 -> dtbs/5.16.0-1-librem5/freescale/imx8mq-librem5-r4.dtb
drwxr-xr-x 5 root root 1.0K Jan 22 21:48 dtbs
drwxr-xr-x 2 root root 1.0K Jul 13 2021 grub
-rw-r–r-- 1 root root 62M Feb 2 11:57 initrd.img
-rw-r–r-- 1 root root 62M Dec 9 18:56 initrd.img-5.13.0-1-librem5
-rw-r–r-- 1 root root 62M Jan 10 08:23 initrd.img-5.15.0-1-librem5
-rw-r–r-- 1 root root 62M Jan 22 21:48 initrd.img-5.16.0-1-librem5
drwx------ 2 root root 12K Sep 11 01:31 lost+found
-rw-r–r-- 1 root root 4.7M Nov 29 03:31 System.map-5.13.0-1-librem5
-rw-r–r-- 1 root root 4.7M Dec 20 11:34 System.map-5.15.0-1-librem5
-rw-r–r-- 1 root root 4.8M Jan 31 10:35 System.map-5.16.0-1-librem5
-rw-r–r-- 1 root root 24M Feb 2 11:57 vmlinuz
-rw-r–r-- 1 root root 8.3M Nov 29 03:31 vmlinuz-5.13.0-1-librem5
-rw-r–r-- 1 root root 8.4M Dec 20 11:34 vmlinuz-5.15.0-1-librem5
-rw-r–r-- 1 root root 8.5M Jan 31 10:35 vmlinuz-5.16.0-1-librem5

[Quarnero]

With reason. Thanks for your post! Now is time to disconnect your Librem 5:

@Quarnero

cd /
umount /dev/sdb1
umount /dev/sdb2

I’ll prepare my next post when your phone runs on itself again.

[Marts]

@Quarnero

umount /dev/sdb2

I’ve tryed many many times to unmount and Terminal respond this :
martin@Ephemere:~$ cd /
martin@Ephemere:/$ umount /dev/sdb1
umount: /mnt: umount failed: Opération non permise.
martin@Ephemere:/$ umount /dev/sdb2
umount: /dev/sdb2: not mounted.
martin@Ephemere:/$

[Quarnero]

Sorry, I’m not aware of Librem 5 mounted location, but you might use your File manager (Nautilus?) to umount …

sudo fdisk --list will show you all of your mounted partitions.

[Marts]

When I clic like a USB key, he say that I can’t eject

[irvinewade]

@Marts

umount /dev/sdb1
umount: /mnt: umount failed: Opération non permise.

You need sudo i.e.

sudo umount /dev/sdb1

@Marts

umount /dev/sdb2
umount: /dev/sdb2: not mounted.

That’s fine. If it’s not mounted then it doesn’t need to be umounted!