Skip to content
Snippets Groups Projects

After software update, no WiFi or WWAN adapter found

    • Closed Issue created by Jan Vlug @janvlug

    Reported by someone on the forum and confirmed by me:

    I just updated my Librem 5’s PureOS Byzantium using the PureOS Store. Upon rebooting after the update, there is no WiFi or mobile/cellular/WWAN network connectivity. The icons don’t show in the top corner of the screen and the settings for WiFi/Mobile show “No (WiFi|WWAN) Adapter Found”.

    lsusb shows a device 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, which I presume is the modem.

    Have tried toggling kill switches on and off and rebooting.

    Phone is behaving almost as if in lockdown mode, as the rotation sensor is not active. No icons for camera or microphone either, though, so not quite the same mode.

    Designs

      Child items 0

      2. No child items are currently assigned. Use child items to break down this issue into smaller parts.

      Activity

      • Martin Kepplinger
        Martin Kepplinger @martin.kepplinger ·
        Owner

        I assume you toggled the hks and rebooted a few times already.

        Can you plug in USB, picocom -b 115200 /dev/ttyACM0, login and see what kernel you run now? dpkg --list | grep linux-image

        If it's the latest kernel 5.16.3pureos1, I'm running it without problems here, usually wifi disabled and modem enabled.

        • Jan Vlug
          Jan Vlug @janvlug ·
          Author

          Yes, I toggled hks and rebooted a few times, I did not try taking out the battery (yet).

          I have no USB cable that I can use, but I ran on the terminal on the phone: dpkg --list | grep linux-image

          It shows a list of four kernels:

          • linux-image-5.13.0-1-librem5 5.13.19pureos5
          • linux-image-5.15.0-1-librem5 5.15.9pureos1
          • linux-image-5.16.0-1-librem5 5.16.3pureos1
          • linux-image-librem5 5.16.3pureos1

          There seems something wrong with the versions above.

          uname -a shows:

          5.16.0-1-librem5

          Edited by Jan Vlug
        • Martin Kepplinger
          Martin Kepplinger @martin.kepplinger ·
          Owner

          to free up space in /boot it might make sense to run apt autoremove and reboot.

        • Please register or sign in to reply
      • Jan Vlug
        Jan Vlug @janvlug ·
        Author

        Thanks @martin.kepplinger running

        sudo apt autoremove

        and rebooting brought back the Wifi and WWAN adapters.

        Maybe apt autoremove should be done automatically somehow, to prevent users running into this problem.

      • Jan Vlug
        Jan Vlug @janvlug ·
        Author

        For info:

        I had to enable the ssh service again to be able to access my L5 with:

        sudo systemctl enable ssh

        Then I was able to ssh in again and ran:

        $ dpkg --list | grep linux-image
rc  linux-image-5.13.0-1-librem5          5.13.19pureos5                   arm64        Linux 5.13 for the Librem 5 and its devkit
ii  linux-image-5.15.0-1-librem5          5.15.9pureos1                    arm64        Linux 5.15 for the Librem 5 and its devkit
ii  linux-image-5.16.0-1-librem5          5.16.3pureos1                    arm64        Linux 5.16 for the Librem 5 and its devkit
ii  linux-image-librem5                   5.16.3pureos1                    arm64        Linux kernel for the Librem 5 and its devkit
      • Martin Kepplinger
        Martin Kepplinger @martin.kepplinger ·
        Owner

        ok. thanks for the details. we have an issue for that actually: OS-issues#153 so I guess we can close this?

      • Jan Vlug closed

        closed

        • Guido Gunther
          Guido Gunther @guido.gunther ·
          Owner

          As noted in matrix I suspect we get a new kernel with e.g. ABI 5.16.0-1 unpacked over old ABI (but also labeled as 5.16.0-1) and then the "low space" triggers the initramfs not getting updated. Just "low space" doesn't explain the symptoms to me.

          Reopening to reflect that (we can close in case the mitigation in other places are sufficient or if turns out my claims are completely off).

          @janvlug can you check if you had another 5.16.x kernel installed before (e.g. 5.16.1) ?

        • Jan Vlug
          Jan Vlug @janvlug ·
          Author

          can you check if you had another 5.16.x kernel installed before

          @guido.gunther: How do I have to check this?

          Is this enough information for you:

          ls -slrt /boot/dtbs
total 3
1 drwxr-xr-x 3 root root 1024 Dec 27 09:25 5.13.0-1-librem5
1 drwxr-xr-x 3 root root 1024 Jan  9 12:44 5.15.0-1-librem5
1 drwxr-xr-x 3 root root 1024 Feb  7 12:16 5.16.0-1-librem5
          Edited by Jan Vlug
        • Guido Gunther
          Guido Gunther @guido.gunther ·
          Owner

          /var/log/dpkg.log should have the necessary information. Full file would be great (send via private mail if you deem it sensitive data). (add @puri.sm to my gitlab handle).

        • Please register or sign in to reply
      • Guido Gunther reopened

        reopened

      • Guido Gunther mentioned in merge request !545 (merged)

        mentioned in merge request !545 (merged)

      • Jan Vlug
        Jan Vlug @janvlug ·
        Author

        These are the logs: dpkg.log.tar.bz2

      • Guido Gunther mentioned in merge request flash-kernel!25 (merged)

        mentioned in merge request flash-kernel!25 (merged)

        • Guido Gunther
          Guido Gunther @guido.gunther ·
          Owner

          Thanks @janvlug this helps!. This

          dpkg.log.1:2022-01-23 14:39:48 status installed linux-image-5.16.0-1-librem5:arm64 5.16.1pureos1

          shows you were able to update to 5.15.x -> 5.16.0 (which would bring in a new kernel and initramfs to /boot hence eating more space) but everything installed and configured fine. The update to 5.16.1 then fails (never goes to installed state) with a half-configured (due to insufficient space) 5.16.1:

          dpkg.log.1:2022-01-31 00:43:20 configure linux-image-5.16.0-1-librem5:arm64 5.16.2pureos1 <none>
...
dpkg.log.1:2022-01-31 00:43:14 upgrade linux-image-5.16.0-1-librem5:arm64 5.16.1pureos1 5.16.2pureos1

          but since modules are supposed to be ABI compatible (package is still 5.16.0-1 you could still boot (and had network) to try the upgrade to 5.16.2:

          dpkg.log:2022-02-06 22:35:13 status half-installed linux-image-5.16.0-1-librem5:arm64 5.16.2pureos1

          which means modules where ABI compatible up to here. But then it stopped with 5.16.3:

          dpkg.log:2022-02-06 22:35:13 upgrade linux-image-5.16.0-1-librem5:arm64 5.16.2pureos1 5.16.3pureos1
dpkg.log:2022-02-06 22:35:17 status unpacked linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1
dpkg.log:2022-02-06 22:35:18 configure linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1 <none>
dpkg.log:2022-02-06 22:35:18 status unpacked linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1
dpkg.log:2022-02-06 22:35:18 status half-configured linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1
dpkg.log:2022-02-07 12:14:10 configure linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1 <none>
dpkg.log:2022-02-07 12:14:10 status half-configured linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1
dpkg.log:2022-02-07 12:15:12 status installed linux-image-5.16.0-1-librem5:arm64 5.16.3pureos1

          I assume the 22:35 is the installation and the next day at 12:14 you booted but had no wifi/wwan. This would also match the bug report date.

          For me this confirms the theory that kernel ABI broke between 5.16.2 and 5.16.3 (you got old kernel and initramfs (hence could still boot to unlock) but then the rootfs had the ABI incompatible modules of 5.16.2).

          Kernel ABI change would have required the package name to change to linux-image-5.16.0-2-librem5.

          So for me this means 4 things

          • free up space on boot OS-issues#153
          • make sure we always run with the correct initramfs (flash-kernel!25 (merged)) - i've marked this MR as fixing this issue since that would have prevented that (as soon as we can create the initramfs we can switch to the new kernel since there's no additional copy anymore).
          • Improve ABI breackage detection (we could just bump the ABI with every minor release but that would fill up /boot quickly or if we prune old kernels quickly mean we don't have a fallback to an old kernel version that is 5.15 in this case.
          • Now that flash-kernel boots a versioned kernel by default consider having a rescue kernel as /boot/{vmlinuz,initrd.img} that we fall back to (/boot/boot.scr does this already) (#397 (moved) )

          @martin.kepplinger we could try to redo this locally by rebuilding the old packages but I think the logs are enough to assume we're not chasing another problem. If my logic is flawed somewhere please let me know.

        • Martin Kepplinger
          Martin Kepplinger @martin.kepplinger ·
          Owner

          could we find a test for ABI compatibility that will tell me whether I need to increment the ABI version before releasing?

        • Guido Gunther
          Guido Gunther @guido.gunther ·
          Owner

          A web search brings some matches:

        • Please register or sign in to reply
      • Sebastian Krzyszkowiak mentioned in commit flash-kernel@7091179d

        mentioned in commit flash-kernel@7091179d

      • Sebastian Krzyszkowiak closed with merge request flash-kernel!25 (merged)

        closed with merge request flash-kernel!25 (merged)

      Please register or sign in to reply