After software update, no WiFi or WWAN adapter found

Hardware Librem 5
21

Yes, this helped me already meanwhile. The laptop in question (of my son) came preinstalled with this Ubuntu. I’m not in the position to judge if it should have been installed.

22

Thanks! Is this already happening with the linux-image-5.16.0-1-librem5? It looks like to me that third apt upgrade to this particular Linux Kernel is already available (without leaving traces of the previously installed one):

23

Just for the record, building jumpdrive ended fine with#

...
cp src/boot-purism-librem5.sh boot-purism-librem5.sh
cp src/purism-librem5.txt purism-librem5.lst
All done! Switch your phone into flashing mode and run Jumpdrive with `./boot-purism-librem5.sh`
...

Now let’s wait for a situation where we do need it. hopefully never :slight_smile:

2 Likes
24

Great that you got through the build. I’ll update the wiki regarding the c++ issue in a day or so.

My advice: don’t wait. Don’t make it that the first time you are testing whether you have a working, bootable Jumpdrive is … when you need it !

I have used Jumpdrive to make a backup of the entire eMMC drive of my Librem 5. Everybody needs to do backup, right?

1 Like
25

If I run the above script, what will happen between the laptop and the L5 and what can I do then, i.e. how could I telnet into the L5 and how could I get/put files from/to the L5? Is there some guide?

26

When you run jumpdrive the Librem 5 storage unit is mounted on the laptop via USB as an external storage unit. You can access / the same way you would access an encrypted external hard drive. And the /boot partition will also show as a separate partition.

From that point on you can follow the instructions on Can't use L5 after update! to regain space in /boot for the device to boot again.

2 Likes
27

The Librem 5 will boot Jumpdrive. (It will be running a fairly complete Linux kernel that has been loaded over USB from the x86 host computer.)

  • The eMMC drive (and the uSD drive if applicable) will be exposed as USB disks that you can mount on the x86 host computer.
  • You can telnet in from the x86 host computer to the Librem 5.

Warning: Be careful if doing both. You don’t want to mount a Librem 5 disk on both the x86 host computer and on the Librem 5. In terms of mounting, one or the other but not both.

For clarity: The Librem 5 is exposing itself to the x86 host computer as a ‘composite’ USB device with one or two disks and a network connection.

The easiest way is probably to mount the Librem 5 disk on the x86 host computer, copy files from/to, then umount.

However other ways might be possible:

  • sneakernet using the uSD card (should work but would be a hassle)
  • transfer via some network protocol (but I am not sure what is included in the Jumpdrive kernel and what is not)

If you just want to rm and mv and the like then telnet may be easier. However I see that the other topic related to this still suggests mounting on the x86 host and carrying the commands out on the x86 host, which is fine too.

As @joao.azevedo perhaps implies … any option will need to take into account whether the root partition is encrypted if you need to access the root partition. (The other topic related to this is accessing the boot partition and hence does not need to be concerned with encryption.)

This forum? No, I don’t think so.

28

Removing files manually from /boot as described here: Can't use L5 after update! does not require dealing with LUKS partitions, as /boot is not encrypted.

However if someone wants to explore other options, then maybe you need to deal with LUKS

1 Like