[Solved] Mirrored Mint 19.3 install to new PC. Network interface won't startup until after login.

[hauser100]

Hello! I recently mirrored a Linux Mint 19.3 SSD and moved to a new system I built. Problem is the ethernet won't work until after I login with lightdm and then manually turn off and then turn back on the network connection with the network app. I did not have this problem before in the old system. Both wifi and ethernet work when manually turned on. Note that I dual-boot with windows 10 and that OS starts up the network just fine.

'inxi' output:

System:
Host: Vlad Kernel: 5.4.0-42-generic x86_64 bits: 64 Desktop: MATE 1.22.2
Distro: Linux Mint 19.3 Tricia
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <root required>
Mobo: ASUSTeK model: ROG STRIX Z490-I GAMING v: Rev 1.xx serial: <root required>
BIOS: American Megatrends v: 2005 date: 01/13/2021
CPU:
10-Core: Intel Core i9-10900K type: MT MCP speed: 800 MHz min/max: 800/5300 MHz
Graphics:
Device-1: NVIDIA driver: nvidia v: 460.39
Display: x11 server: X.Org 1.20.8 driver: nvidia resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce RTX 3070/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39
Network:
Device-1: Intel driver: iwlwifi
Device-2: Intel driver: igc
Drives:
Local Storage: total: 3.64 TiB used: 858.21 GiB (23.0%)
Info:
Processes: 404 Uptime: 16m Memory: 62.70 GiB used: 2.37 GiB (3.8%) Shell: bash
inxi: 3.0.32

---------------------------------------------------------------------------
'ip a' from console before lightdm login and switching on network shows the current state of the interface:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 24:4b:fe23:bc brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

After logging in and turning off then on the network, 'ip a' shows:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 24:4b:fe23:bc brd ff:ff:ff:ff:ff:ff
inet 10.66.77.7/24 brd 10.66.77.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::417b:d2d1:e290:76b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether bc:54:2f:60:4a:91 brd ff:ff:ff:ff:ff:ff

------------------------------------------------------------------------

Thanks for any help you may have!
Hauser

[txba516]

Hi Hauser,

It's a bit odd that your first inxi output doesn't list the hardware for the network devices. This probably means the driver is not getting loaded at boot time.
Can you post the inxi network output after you disable and enable the network to see what the hardware is identified as? Also, note what driver the kernel loaded for the ethernet connection.

Code: Select all

inxi -N

Cheers!

[hauser100]

Hey! Thanks for the fast response. Here you go (also done as sudo):

Network:
Device-1: Intel driver: iwlwifi
Device-2: Intel driver: igc

[hauser100]

Sorry for the 2nd rapid reply, however, the loaded driver is the igc driver...

[txba516]

Hmm...interesting. Let's try some additional info gathering commands please. I apologize if it seems redundant.

Code: Select all

inxi -M
lspci -knn
dmesg | grep igc
sudo lshw -C network

[hauser100]

inxi -M reveals:

Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: ROG STRIX Z490-I GAMING v: Rev 1.xx serial: 200771433601545
BIOS: American Megatrends v: 2005 date: 01/13/2021

lspci -knn:

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b33] (rev 05)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05)
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:06ed]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:06ef]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:14.3 Network controller [0280]: Intel Corporation Device [8086:06f0]
Subsystem: Intel Corporation Device [8086:0074]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:06e0]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:06d2]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: ahci
Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:06c0] (rev f0)
Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:06b8] (rev f0)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:06bc] (rev f0)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:06b0] (rev f0)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:0685]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:06c8]
Subsystem: ASUSTeK Computer Inc. Device [1043:87d6]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:06a3]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:06a4]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2484] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2617]
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:228b] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2617]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.0 Ethernet controller [0200]: Intel Corporation Device [8086:15f3] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:87d2]
Kernel driver in use: igc
Kernel modules: igc
05:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 [144d:a808]
Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
Kernel driver in use: nvme
Kernel modules: nvme

dmesg | grep igc shows:

[ 1.312837] igc 0000:04:00.0 eth0: MAC: 24:4b:fe23:bc
[ 1.319555] igc 0000:04:00.0 enp4s0: renamed from eth0
[ 233.498249] igc 0000:04:00.0 enp4s0: igc: enp4s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 233.611837] igc 0000:04:00.0: Force mode currently not supported
[ 236.974284] igc 0000:04:00.0 enp4s0: igc: enp4s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

and lastly, sudo lshw -C network displays:

*-network DISABLED
description: Wireless interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
logical name: wlo1
version: 00
serial: bc:54:2f:60:4a:91
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-42-generic firmware=48.13675109.0 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: iomemory:400-3ff irq:16 memory:4000114000-4000117fff
*-network
description: Ethernet interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: enp4s0
version: 01
serial: 24:4b:fe23:bc
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igc driverversion=0.0.1-k duplex=full ip=10.66.77.7 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:16 memory:a3100000-a31fffff memory:a3200000-a3203fff

[txba516]

Ok, this confirms one of my thoughts. You may be experiencing a similar issue to this thread. https://askubuntu.com/a/1251669

However you are running an ASUS board so you may need to download an update for the Intel I225-V network card (based on available Windows drivers on the ASUS site for your board).

Cheers!

[hauser100]

Thanks. Are you suggesting that I download windows driver code and then put into linux's driver in "whatever folder" for said driver?

- Hauser

[hauser100]

So, I just updated the firmware as the instructions dictated but the issue remains. Its not a firmware item. Would you suspect its something related to either network-manager or lower level hardware not powering up soon enough?

- Thanks
Hauser

[txba516]

It is interesting that in the dmesg output you posted the NIC is recognized early but the link is not initialized until 233 seconds after booting (almost 4 minutes). I'm betting you are getting to the desktop login well before that time mark. And the dmesg info about the NIC coming up is probably from when you are forcing it manually.
Looking at my system's dmesg outputs related to the NIC, it brings up the interface in about 35 seconds.

Just for giggles, let's make sure NetworkManager is responsible for this interface. In this file, the line under [ifupdown] should say "managed=true"

Code: Select all

cat /etc/NetworkManager/NetworkManager.conf

Let's also see what NM knows about for connections:

Code: Select all

nmcli connection show

There's more that can be done as part of this effort but instead of duplicating everything, I'll refer you.
I'm pulling this info from a thread here: https://askubuntu.com/questions/71159/n ... ot-managed
and here: https://devconnected.com/network-manage ... -examples/

Cheers!

[hauser100]

Hi! Pardon the late response, but I do live in Germany... Haha.

So, here is the output of 'cat /etc/NetworkManager/NetworkManager.conf'

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no

Interestingly, managed=false is set.

Next, nmcli connection show:

Ethernet connection 1 087b532b-b8da-4f15-a7ef-9fe600758985 ethernet enp4s0

Maybe we're onto something. I'll try changing the first 'managed = false' to true and see what happens.

[hauser100]

Changing managed to true did not solve the problem... Very confusing.

However, after running 'sudo cat /var/log/boot.log | grep network' I noticed this:

Starting Raise network interfaces...
Starting Dispatcher daemon for systemd-networkd...
[ OK ] Started Raise network interfaces.
[ OK ] Started Dispatcher daemon for systemd-networkd.
Starting Raise network interfaces...
Starting Dispatcher daemon for systemd-networkd...
[ OK ] Started Raise network interfaces.
[ OK ] Started Dispatcher daemon for systemd-networkd.
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
Starting Dispatcher daemon for systemd-

Now I need to figure out why the interface is not starting...

So, after rebooting again, but now running two additional network commands, I get the following data, which may help:

sudo service network-manager status:

● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-03-10 06:47:59 CET; 30s ago
Docs: man:NetworkManager(8)
Main PID: 1376 (NetworkManager)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
└─1376 /usr/sbin/NetworkManager --no-daemon

Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0925] wifi-nl80211: (wlo1): using nl80211 for WiFi device control
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0926] device (wlo1): driver supports Access Point (AP) mode
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0931] manager: (wlo1): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devic
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0934] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-i
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0937] device (wlo1): set-hw-addr: set MAC address to 62:7C:00:22:4B:F2 (scanning)
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.0999] bluez: use BlueZ version 5
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.1002] supplicant: wpa_supplicant running
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.1002] modem-manager: ModemManager available
Mar 10 06:48:02 Vlad NetworkManager[1376]: <info> [1615355282.1010] bluez5: NAP: added interface BC:54:2F:60:4A:95
Mar 10 06:48:08 Vlad NetworkManager[1376]: <info> [1615355288.0902] manager: startup complete

sudo service networking status
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: active (exited) since Wed 2021-03-10 06:47:59 CET; 1min 31s ago
Docs: man:interfaces(5)
Process: 1268 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Process: 1265 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevad
Main PID: 1268 (code=exited, status=0/SUCCESS)

Mar 10 06:47:59 Vlad systemd[1]: Starting Raise network interfaces...
Mar 10 06:47:59 Vlad systemd[1]: Started Raise network interfaces.

The interface is not getting raised during boot. Also, appears as if its trying wifi which I am not using.


After switching on ethernet manually, network-manager status shows:

● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-03-10 06:47:59 CET; 3min 32s ago
Docs: man:NetworkManager(8)
Main PID: 1376 (NetworkManager)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
├─1376 /usr/sbin/NetworkManager --no-daemon
└─8103 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-enp4s0.pid -lf /var/lib/NetworkManager/dhclient-087b532b-b8da-4f15-a7ef-

Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3281] dhcp4 (enp4s0): state changed unknown -> bound
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3289] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3294] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3296] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3297] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 10 06:51:31 Vlad dhclient[8103]: bound to 10.66.77.7 -- renewal in 38656 seconds.
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3342] manager: NetworkManager state is now CONNECTED_SITE
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3342] policy: set 'Ethernet connection 1' (enp4s0) as default for IPv4 routing and DNS
Mar 10 06:51:31 Vlad NetworkManager[1376]: <info> [1615355491.3344] device (enp4s0): Activation: successful, device activated.
Mar 10 06:51:32 Vlad NetworkManager[1376]: <info> [1615355492.5678] manager: NetworkManager state is now CONNECTED_GLOBAL

Everything is now assigned properly but it should not be this way. I've read many other posts related to this such as:
https://www.linux.org/threads/failed-to ... ces.22500/
https://neurotechnics.com/blog/linux-fa ... nterfaces/

Lots of reading to do!

[hauser100]

Anyone have any further ideas?

[hauser100]

Gents, I still have this problem. Its not sorted out. Any ideas? I've played around with /etc/network/interfaces systemd files, and so on. No luck.

- thanks

[SMG]

Have you updated your kernel higher than the 5.4.0-42 you originally posted? The most recent is 5.4.0-66.

Looking through the changelog, I see the following was added to 5.4.0-55 which means it should be available in 5.4.0-66.

Code: Select all

  * Ethernet no link lights after reboot (Intel i225-v 2.5G) (LP: #1902578)
    - igc: Add PHY power management control

[hauser100]

Team, I'm astonished. If it wasn't for you taking time to inform me of a recent kernel update that potentially had a fix, I'd still be trouble-shooting to no avail. It worked! The 5.4.0-66 update fixed the NIC. I think it was a power-status issue based on other sources tackling something similar.

Thanks guys! We can close this one out.

[SMG]

Thanks guys! We can close this one out.

Glad it worked.
To close it out, please edit your very first post in the thread by clicking the pencil icon and add [SOLVED] to the beginning of the title.