No network connection at boot

in terminal:

diff sudo_dmesg_cold_start.txt sudo_dmesg_hot_reboot.txt

1c1
< sudo dmesg (cold start)

sudo dmesg (hot re-boot)
3,11c3,11
< [ 258.651625] audit: type=1130 audit(1624817148.831:112): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1658-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
< [ 261.326179] audit: type=1131 audit(1624817151.507:113): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1658-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
< [ 261.442106] audit: type=1334 audit(1624817151.624:114): prog-id=22 op=UNLOAD
< [ 261.442110] audit: type=1334 audit(1624817151.624:115): prog-id=21 op=UNLOAD
< [ 261.442112] audit: type=1334 audit(1624817151.624:116): prog-id=20 op=UNLOAD
< [ 264.687928] audit: type=1100 audit(1624817154.867:117): pid=1661 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“gatu” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
< [ 264.689997] audit: type=1101 audit(1624817154.871:118): pid=1661 uid=1000 auid=1000 ses=2 msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“gatu” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
< [ 264.690376] audit: type=1110 audit(1624817154.871:119): pid=1661 uid=1000 auid=1000 ses=2 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
< [ 264.691486] audit: type=1105 audit(1624817154.871:120): pid=1661 uid=1000 auid=1000 ses=2 msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’


[ 185.125361] audit: type=1130 audit(1624817030.003:114): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1339-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 186.993351] audit: type=1131 audit(1624817031.870:115): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1339-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 187.105242] audit: type=1334 audit(1624817031.983:116): prog-id=22 op=UNLOAD
[ 187.105250] audit: type=1334 audit(1624817031.983:117): prog-id=21 op=UNLOAD
[ 187.105268] audit: type=1334 audit(1624817031.983:118): prog-id=20 op=UNLOAD
[ 191.806619] audit: type=1100 audit(1624817036.683:119): pid=1354 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“gatu” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 191.808538] audit: type=1101 audit(1624817036.686:120): pid=1354 uid=1000 auid=1000 ses=2 msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“gatu” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 191.808882] audit: type=1110 audit(1624817036.686:121): pid=1354 uid=1000 auid=1000 ses=2 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 191.809740] audit: type=1105 audit(1624817036.686:122): pid=1354 uid=1000 auid=1000 ses=2 msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
13,14d12
<

/ Hans Gatu

If this is the only difference, then try to grep for e1000e in both outputs. And in the journal. Also check the journal for errors the -p4 for both boots. There need to be a difference.

Sorry, @xabbu , how do I grep for e1000e, and how do I check the journal for errors the -p4?
Shall I do a certain command in the terminal? If so, what are the commands?

/ Hans Gatu

For the current boot

journalctl --no-pager --no-hostname -b -p4

for the boot before

journalctl  --no-pager --no-hostname -b-1 -p4

Grep either your dmesd (Keep in mind that you need to do that before your reboot to get the cold boot)

sudo dmesg | grep e1000e

or the journal

journalctl --no-pager --no-hostname -b -g e1000e

and

journalctl --no-pager --no-hostname -b-1 -g e1000e

journalctl --no-pager --no-hostname -b -p4
and
journalctl --no-pager --no-hostname -b-1 -p4
gave a lot of output, maybe too much to post, or?
but the other two is here:

in the terminal:

journalctl --no-pager --no-hostname -b -g e1000e
– Journal begins at Thu 2021-05-13 21:36:24 CEST, ends at Mon 2021-06-28 06:35:27 CEST. –
jun 28 05:12:59 kernel: e1000e: Intel(R) PRO/1000 Network Driver
jun 28 05:12:59 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
jun 28 05:12:59 kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
jun 28 05:12:59 kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
jun 28 05:12:59 kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 18:03:73:ba:69:be
jun 28 05:12:59 kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
jun 28 05:12:59 kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: E041FF-0FF
jun 28 05:12:59 kernel: e1000e 0000:00:19.0 eno1: renamed from eth0
jun 28 05:13:09 kernel: e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
jun 28 05:13:15 kernel: e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

and

journalctl --no-pager --no-hostname -b-1 -g e1000e
– Journal begins at Thu 2021-05-13 21:36:24 CEST, ends at Mon 2021-06-28 06:37:19 CEST. –
jun 28 05:09:31 kernel: e1000e: Intel(R) PRO/1000 Network Driver
jun 28 05:09:31 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
jun 28 05:09:31 kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
jun 28 05:09:31 kernel: e1000e: probe of 0000:00:19.0 failed with error -3

/ Hans Gatu

If you search for this error, you will find a lot. Make sure you look only at search results with -3, there are others with different numbers. Some are really old.

Most reports end with an BIOS/UEFI update, that fixed the problem. Sometimes changing some BIOS/UEFI settings helped, often just to disable fast boot if available. Many don’t have a solution. In one, a new CMOS battery helped.
I only found one with an OS Level fix, you might want to try it.

sudo rmmod e1000e && sudo modprobe e1000e
1 Like

I have checked the BIOS settings.
Fast boot was disabled already, so I didn’t find anything to change.
I think I can live with re-booting, even though it is a bit annoying.
Thank you all, for trying to help me out.

/ Hans Gatu

Hello Hans,

I’m a newbie and I do not know if your problem is similar to what I had. So kindly ignore, if my solution is too dumb.

I faced a kind of similar problem last month when my Ethernet connection disconnected (during a powercut) and then onward refused to even recognise the connection. Rebooting seemed to fix it once or twice. Post that, this also stopped working.

Did a bit of digging and the issue seemed to be my open network drivers being an incompatible version (How was it working before and then suddenly stopped, I don’t know)

A simple reinstall of the correct drivers fixed the issue.
I’m on KDE, so I just had to go to Hardware Configuration in settings, right click network controller and clicked install. Reboot and Voila… solved…

Yes, @Ace_Mcloud , it sounds very much like the same problem.
So far, the re-boot works for me.
I use XFCE and doesn’t have that same hardware setting.
I can look at the hardware setting, but it I cannot choose to re-install.
I looked through everything ‘network’ in Pamac, though,
and reinstalled all network-related applications, but it didn’t help.
The problem is still there.
Thank you anyway, for the tip.

/ Hans Gatu

@_HG
You can access the same from Manjaro settings manager (the tool to change kernel, locale and sorts), there is a hardware configuration tool in there. Click on that. It is essentially the same tool that I used on KDE. You may try reinstalling from there.

Unfortunately your fix can’t be used by @_HG . The driver (e1000e) for his network card (Intel 82579LM) is a inline Kernel driver. It is not a third party driver that can be installed via the Manjaro settings Manager, it is integrated in the Linux Kernel.

Of course there are way to switch to a different version of inline Kernel driver. The easiest is to switch the Kernel Version, for example try 5.12 or 5.4. Since Manjaro supports a lot of different Kernels, after install, a different Kernel can be it can be selected via grub at boot time.

For a little bit more advanced users, compile an own version the Linux Kernel. A specific version can be selected or the source code can be patched. But is is not that easy and take some time to compile.

After the latest upgrade of Manjaro (including upgrade to kernel 5.10.49) the problem disappeared.

/ Hans Gatu

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.