FS#78619 - [linux] Missing network devices with linux 6.3.4.arch1-1
            Attached to Project:
            Arch Linux
            
Opened by Lukas Fleischer (lfleischer) - Friday, 26 May 2023, 19:57 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 27 May 2023, 18:34 GMT
          Opened by Lukas Fleischer (lfleischer) - Friday, 26 May 2023, 19:57 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 27 May 2023, 18:34 GMT
| 
 | Details
                    Description: After upgrading to linux 6.3.4.arch1-1 and
                    rebooting, network devices are missing on my T480s: $ ip link 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 The issue persists after multiple reboots. After downgrading to 6.3.3.arch1-1 (from pacman package cache) and another reboot, the issue is resolved: $ ip link 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: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 8c:16:45:72:a3:a9 brd ff:ff:ff:ff:ff:ff 3: wlp61s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether b4:6b:fc:3e:62:73 brd ff:ff:ff:ff:ff:ff | 
              This task depends upon
              
              
            
            
          
            Closed by  Lukas Fleischer (lfleischer)
Saturday, 27 May 2023, 18:34 GMT
Reason for closing: Not a bug
          
          
        Saturday, 27 May 2023, 18:34 GMT
Reason for closing: Not a bug
 Comment by
            Lukas Fleischer (lfleischer) -
            Saturday, 27 May 2023, 18:34 GMT
            
            Comment by
            Lukas Fleischer (lfleischer) -
            Saturday, 27 May 2023, 18:34 GMT
          
           
          
              After investigating more, it turns out this was caused by faulty
              configuration on my end (wrong partition mounted at `/boot`,
              resulting in discrepancy between kernel and module versions). My
              apologies - marking as resolved.
            
          