[Solved] Net. Interf. visib. no more visible after broken pacman upd.

prgeorg · 2019-08-01 18:44:52

Context

So after using arch linux happily for almost a year it finally happened I run pacman -Syu and forgot to plugin the power cable.
After booting from an usb stick I managed to restore most of the system using the fabulous arch wiki
Pacman crashes during an update.
Partitions
Name FSTYPE MOUNTPOINT
nvme0n1p1 vfat /boot
nvme0n1p2
cryptlvm
main-vg-swap
main-vg-root /
main-vg-home /home
Main Steps taken

```
cryptsetup open /dev/nvme0n1p2 arch
```
```
mount /dev/mapper/main-vg-root /mnt
```

mount /dev/mapper/main-vg-home /mnt/home

```
mount /nvme0n1p1 /mnt/boot
```
```
arch-chroot /mnt
```
```
pacman -Syu linux
```
```
ip link
```
wlp2s0 visible

Problem

However when I start my system again normally and run

ip link

the network interface wlp2s0 is not visible
(Ethernet works fine though).
I read and tried a lot but I feel like I don't know what to do, can someone direct me in the right direction on
how to go about that?

Cheers Georg

Conclusion

Always do a

pacman -Qkk

after a broken update to check for broken packages.

Last edited by prgeorg (2019-08-02 11:19:34)

jasonwryan · 2019-08-01 18:57:59

Card and driver? Journal entries? dmesg?

ewaller · 2019-08-01 19:23:33

output of pacman -Q linux and of uname -a
?

Last edited by ewaller (2019-08-01 19:23:47)

prgeorg · 2019-08-01 19:54:49

Kernel

pacman -Q linux
linux 5.2.5.arch1-1

uname -a
Linux archlinux 5.2.5-arch1-1-ARCH #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019 x86_64 GNU/Linux

When booting using usb

ip link | grep Network
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether e8:6a:64:00:e3:83 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 48:a4:72:0b:e8:52 brd ff:ff:ff:ff:ff:ff

lspci -k | grep Network
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
    Subsystem: Lenovo Ethernet Connection (4) I219-LM
    Kernel driver in use: e1000e
    Kernel modules: e1000e
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
    Subsystem: Intel Corporation Dual Band Wireless-AC 8265
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi, wl

dmesg | grep iwlwifi
[   12.329093] iwlwifi 0000:02:00.0: loaded firmware version 36.9f0a2d68.0 op_mode iwlmvm
[   12.429219] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[   12.493093] iwlwifi 0000:02:00.0: base HW address: 48:a4:72:0b:e8:52
[   12.585212] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0

Normal boot

ip link | grep Network
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether e8:6a:64:00:e3:83 brd ff:ff:ff:ff:ff:ff

lspci -k | grep Network
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

Last edited by prgeorg (2019-08-01 20:43:34)

ewaller · 2019-08-01 19:59:21

I know what you think you are running. Let's make sure.

ewaller wrote:

output of pacman -Q linux and of uname -a
?

I have a feeling those two will give different answers.

Edit: I think you were editing whilst I was posting. Nevermind

Last edited by ewaller (2019-08-01 20:00:17)

prgeorg · 2019-08-01 20:19:20

They are unfortunately the same:(
Here is the journalctl

journalctl -b

https://pastebin.com/embed_js/jfXx5VYC

loqs · 2019-08-01 20:22:32

Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-8265-36.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-36.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-35.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-8265-34.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-34.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-33.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-32.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-8265-31.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-31.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-30.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-29.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-28.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-8265-27.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-27.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-8265-22.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-22.ucode failed with error -22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: no suitable firmware found!
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: minimum version required: iwlwifi-8265-22
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-8265-36
Aug 01 21:42:26 archlinux kernel: iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

Was linux-firmware corrupted / is very outdated?

pacman -Qi linux-firmware
pacman -Qkk linux-firmware

prgeorg · 2019-08-01 20:29:06

Yes basically I ran a

pacman -Syu

and had a power loss.

pacman -Qi linux-firmware
Name            : linux-firmware
Version         : 20190717.bf13a71-1
Description     : None
Architecture    : None
URL             : None
Licenses        : None
Groups          : None
Provides        : None
Depends On      : None
Optional Deps   : None
Required By     : linux
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 0.00 B
Packager        : None
Build Date      : None
Install Date    : None
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Unknown

pacman -Qkk linux-firmware
error: error while reading file /var/lib/pacman/local/linux-firmware-20190717.bf13a71-1/mtree: Unrecognized archive format
linux-firmware: no mtree file

Should I simply run a:

pacman -S --force linux-firmware

?
I guess there may be more corrupted packages and if so how to find and fix them?
Cheers Georg and thanks a lot for the help

Last edited by prgeorg (2019-08-01 20:44:11)

loqs · 2019-08-01 20:34:19

The following will detect other such corrupted packages. It will also detect some changes that are expected so please post the output.

pacman -Qkk

Last edited by loqs (2019-08-01 20:34:36)

jasonwryan · 2019-08-01 20:36:35

Please wrap all of the output in code tags, not just the command: that defeats the purpose

prgeorg · 2019-08-01 20:41:26

pacman -Qkk

https://pastebin.com/embed_js/VVTynZ1P

loqs · 2019-08-01 20:52:22

error: error while reading file /var/lib/pacman/local/i3lock-2.12-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/i3status-2.13-2/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/jupyter-notebook-6.0.0-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/lib32-bzip2-1.0.8-2/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/lib32-glibc-2.29-4/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/lib32-libpciaccess-0.16-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/lib32-llvm-libs-8.0.1-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/lib32-mesa-19.1.3-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/libheif-1.4.0-3/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/libnm-glib-1.18.2-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/libqalculate-3.3.0-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/linux-firmware-20190717.bf13a71-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/python-ipywidgets-7.5.0-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/python-jupyter_client-5.3.1-1/mtree: Unrecognized archive format
error: error while reading file /var/lib/pacman/local/python-pyrsistent-0.15.4-1/mtree: Unrecognized archive format
python-pyrsistent: no mtree file

Edit:
If you update the database first then can you reinstall the package e.g.

pacman -D linux-firmware
pacman -S linux-firmware

Last edited by loqs (2019-08-01 20:54:32)

prgeorg · 2019-08-01 21:01:25

One more question, when doing this I get a loooot of "exists in filesystem" would you then check for each of them if it is owned by another package:

pacman -Qo

or simply use a

pacman -S --force <package>

?
I guess otherwise one could write a script as there are so many of them.

Last edited by prgeorg (2019-08-01 21:07:32)

loqs · 2019-08-01 21:21:55

prgeorg wrote:

One more question, when doing this I get a loooot of "exists in filesystem" would you then check for each of them if it is owned by another package:

When doing what produces "exists in filesystem"?

prgeorg · 2019-08-01 21:28:30

When running:

pacman -D linux-firmware

and then

pacman -S linux-firmware

I get around 2000 "exists in filesyste" but when running

pacman -Qo <package>

for each of them I get "error: No package owns",
So I can either delete all of them or run

 pacman -S --force linux-firmware

correct?

loqs · 2019-08-01 21:43:38

Yes although --force is intended to be replaced by --overwrite

pacman -S --overwrite glob package

the issue would be finding the matching glob, possibly for linux-firmware

pacman -S --overwrite /usrlib/firmware*,/usr/share/licenses/linux-firmware* linux-firmware

Last edited by loqs (2019-08-01 21:43:59)

prgeorg · 2019-08-02 11:20:57

Thank you sooo much for all the help!!!!
I managed to resolve all broken packages and my system is running as smooth as ever and I learned a lot.

Best Georg:)

Last edited by prgeorg (2019-08-02 11:21:19)

Arch Linux

#1 2019-08-01 18:44:52