[SOLVED] e1000e not working on first boot

Snorlax · 2021-08-30 08:26:09

This is a flaw of my hp 8770w that has been bothering me for long. Whenever I power on my laptop, my ethernet is not working, all I can get:

$ sudo dmesg | grep -e eth -e e1000
[ 8.680497] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[ 8.680500] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[ 8.680910] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 9.777390] e1000e: probe of 0000:00:19.0 failed with error -3
[ 11.588366] br-a231d7878ace: port 1(vethf015377) entered blocking state
[ 11.588368] br-a231d7878ace: port 1(vethf015377) entered disabled state
[ 11.588429] device vethf015377 entered promiscuous mode
[ 11.588545] br-a231d7878ace: port 1(vethf015377) entered blocking state
[ 11.588549] br-a231d7878ace: port 1(vethf015377) entered forwarding state
[ 11.589119] br-a231d7878ace: port 1(vethf015377) entered disabled state
[ 11.598393] br-a231d7878ace: port 2(veth3a478a4) entered blocking state
[ 11.598395] br-a231d7878ace: port 2(veth3a478a4) entered disabled state
[ 11.598457] device veth3a478a4 entered promiscuous mode
[ 11.598548] br-a231d7878ace: port 2(veth3a478a4) entered blocking state
[ 11.598550] br-a231d7878ace: port 2(veth3a478a4) entered forwarding state
[ 11.947259] br-a231d7878ace: port 2(veth3a478a4) entered disabled state
[ 12.677594] eth0: renamed from veth46d0e57
[ 12.747352] eth0: renamed from veth2413963
[ 12.807921] IPv6: ADDRCONF(NETDEV_CHANGE): veth3a478a4: link becomes ready
[ 12.808028] br-a231d7878ace: port 2(veth3a478a4) entered blocking state
[ 12.808036] br-a231d7878ace: port 2(veth3a478a4) entered forwarding state
[ 12.808188] IPv6: ADDRCONF(NETDEV_CHANGE): vethf015377: link becomes ready
[ 12.808281] br-a231d7878ace: port 1(vethf015377) entered blocking state
[ 12.808289] br-a231d7878ace: port 1(vethf015377) entered forwarding state

then I have to reboot to make ethernet really work. After reboot I can get this:

$ sudo dmesg | grep -e eth -e e1000
[ 7.918264] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[ 7.918266] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[ 7.918676] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 8.069893] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 8.203616] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) f0:92:1c:5c:c5:13
[ 8.203618] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 8.203653] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[ 8.354332] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[ 10.259065] br-a231d7878ace: port 1(veth7464c93) entered blocking state
[ 10.259067] br-a231d7878ace: port 1(veth7464c93) entered disabled state
[ 10.259118] device veth7464c93 entered promiscuous mode
[ 10.259230] br-a231d7878ace: port 1(veth7464c93) entered blocking state
[ 10.259232] br-a231d7878ace: port 1(veth7464c93) entered forwarding state
[ 10.259378] br-a231d7878ace: port 1(veth7464c93) entered disabled state
[ 10.266088] br-a231d7878ace: port 2(veth5541977) entered blocking state
[ 10.266090] br-a231d7878ace: port 2(veth5541977) entered disabled state
[ 10.266189] device veth5541977 entered promiscuous mode
[ 10.266313] br-a231d7878ace: port 2(veth5541977) entered blocking state
[ 10.266315] br-a231d7878ace: port 2(veth5541977) entered forwarding state
[ 10.687909] br-a231d7878ace: port 2(veth5541977) entered disabled state
[ 11.228197] eth0: renamed from veth5c3070e
[ 11.288439] eth0: renamed from vethf0ca6f6
[ 11.388270] IPv6: ADDRCONF(NETDEV_CHANGE): veth7464c93: link becomes ready
[ 11.388315] br-a231d7878ace: port 1(veth7464c93) entered blocking state
[ 11.388318] br-a231d7878ace: port 1(veth7464c93) entered forwarding state
[ 11.388454] IPv6: ADDRCONF(NETDEV_CHANGE): veth5541977: link becomes ready
[ 11.388479] br-a231d7878ace: port 2(veth5541977) entered blocking state
[ 11.388480] br-a231d7878ace: port 2(veth5541977) entered forwarding state
[ 13.639809] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

I searched and found nothing working for my situation. I wonder what's error -3 and really want to fix it

Last edited by Snorlax (2021-08-31 14:24:59)

seth · 2021-08-30 17:49:55

Please use code tags, not quote tags.

I wonder what's error -3 and really want to fix it

% errno 3
ESRCH 3 No such process

(From package "moreutils")

The error is all over the interwebz, because of "bothering me for long", a BIOS update is probably not an option, but you can most likely re-load the module at the end of the boot (or blacklist it and load it explicitly later) when the device is finally ready.

# modprobe -r e1000e
# modprobe e1000e

https://wiki.archlinux.org/title/Kernel … acklisting
https://wiki.archlinux.org/title/Kernel … th_systemd - though this is probably still too early.

OT: Not having an avatar image w/ that nick is a miss.

Snorlax · 2021-08-31 02:00:53

seth wrote:

Please use code tags, not quote tags.
I wonder what's error -3 and really want to fix it
% errno 3
ESRCH 3 No such process
(From package "moreutils")
The error is all over the interwebz, because of "bothering me for long", a BIOS update is probably not an option, but you can most likely re-load the module at the end of the boot (or blacklist it and load it explicitly later) when the device is finally ready.
# modprobe -r e1000e
# modprobe e1000e
https://wiki.archlinux.org/title/Kernel … acklisting
https://wiki.archlinux.org/title/Kernel … th_systemd - though this is probably still too early.
OT: Not having an avatar image w/ that nick is a miss.
https://i.imgur.com/qOR2rYl.png

ty bud. actually I've tried a similar way

$ sudo rmmod e1000e
$ sudo modprobe e1000e
$ sudo dmesg | grep -e eth -e e1000
[    7.761076] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[    7.761077] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[    7.761371] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    8.867891] e1000e: probe of 0000:00:19.0 failed with error -3
[   11.038863] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   11.038865] br-a231d7878ace: port 1(veth9fd7e09) entered disabled state
[   11.038907] device veth9fd7e09 entered promiscuous mode
[   11.039013] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   11.039015] br-a231d7878ace: port 1(veth9fd7e09) entered forwarding state
[   11.039518] br-a231d7878ace: port 1(veth9fd7e09) entered disabled state
[   11.048561] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   11.048563] br-a231d7878ace: port 2(vethc5ac29a) entered disabled state
[   11.048632] device vethc5ac29a entered promiscuous mode
[   11.048736] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   11.048737] br-a231d7878ace: port 2(vethc5ac29a) entered forwarding state
[   11.397623] br-a231d7878ace: port 2(vethc5ac29a) entered disabled state
[   12.037959] eth0: renamed from vetha1ea253
[   12.148218] eth0: renamed from vethc2f7be9
[   12.197798] IPv6: ADDRCONF(NETDEV_CHANGE): veth9fd7e09: link becomes ready
[   12.197852] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   12.197854] br-a231d7878ace: port 1(veth9fd7e09) entered forwarding state
[   12.198145] IPv6: ADDRCONF(NETDEV_CHANGE): vethc5ac29a: link becomes ready
[   12.198182] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   12.198188] br-a231d7878ace: port 2(vethc5ac29a) entered forwarding state
[  272.819008] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[  272.819010] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[  272.819338] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[  273.922843] e1000e: probe of 0000:00:19.0 failed with error -3

The result not changed at all.

I also tried blacklisting and modprobing later, sadly the result still the same too:

$ sudo dmesg | grep -e eth -e e1000
[   10.459152] br-a231d7878ace: port 1(vethfef5a10) entered blocking state
[   10.459154] br-a231d7878ace: port 1(vethfef5a10) entered disabled state
[   10.459212] device vethfef5a10 entered promiscuous mode
[   10.459329] br-a231d7878ace: port 1(vethfef5a10) entered blocking state
[   10.459330] br-a231d7878ace: port 1(vethfef5a10) entered forwarding state
[   10.459947] br-a231d7878ace: port 1(vethfef5a10) entered disabled state
[   10.467459] br-a231d7878ace: port 2(veth0675175) entered blocking state
[   10.467461] br-a231d7878ace: port 2(veth0675175) entered disabled state
[   10.467502] device veth0675175 entered promiscuous mode
[   10.467597] br-a231d7878ace: port 2(veth0675175) entered blocking state
[   10.467599] br-a231d7878ace: port 2(veth0675175) entered forwarding state
[   10.497973] br-a231d7878ace: port 2(veth0675175) entered disabled state
[   11.158502] eth0: renamed from veth1a59e32
[   11.258116] IPv6: ADDRCONF(NETDEV_CHANGE): vethfef5a10: link becomes ready
[   11.258151] br-a231d7878ace: port 1(vethfef5a10) entered blocking state
[   11.258155] br-a231d7878ace: port 1(vethfef5a10) entered forwarding state
[   11.368223] eth0: renamed from veth457661a
[   11.438050] IPv6: ADDRCONF(NETDEV_CHANGE): veth0675175: link becomes ready
[   11.438082] br-a231d7878ace: port 2(veth0675175) entered blocking state
[   11.438084] br-a231d7878ace: port 2(veth0675175) entered forwarding state
[  100.649507] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[  100.649509] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[  100.649768] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[  101.737991] e1000e: probe of 0000:00:19.0 failed with error -3

yep, I agree that maybe better to add an avatar xD

seth · 2021-08-31 05:51:57

Same problem, same patch.
https://marc.info/?l=e1000-devel&m=134168780600536
https://groups.google.com/g/linux.kernel/c/KKgv1IzWTYs

e1000e-dkms (so you won't have to patch the kernel), https://aur.archlinux.org/packages/e1000e-dkms/

Snorlax · 2021-08-31 06:20:55

seth wrote:

Same problem, same patch.
https://marc.info/?l=e1000-devel&m=134168780600536
https://groups.google.com/g/linux.kernel/c/KKgv1IzWTYs
e1000e-dkms (so you won't have to patch the kernel), https://aur.archlinux.org/packages/e1000e-dkms/

actually I've using this for long because I use linux-lts on my regular basis.

$ yay -S e1000e-dkms
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  e1000e-dkms-3.8.7-2

  1 e1000e-dkms                              (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>

seth · 2021-08-31 06:35:28

You'll still have to apply the linked patch to reset the HW on failure.

Snorlax · 2021-08-31 07:41:47

seth wrote:

You'll still have to apply the linked patch to reset the HW on failure.

ty bud, I edited the file in tar.gz and updpgsums and then:

(1/1) reinstalling e1000e-dkms                                                                                                                  [########################################################################################] 100%

Creating symlink /var/lib/dkms/e1000e/3.8.7/source ->
                 /usr/src/e1000e-3.8.7

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.10.56-1-lts -C /usr/lib/modules/5.10.56-1-lts/build M=/var/lib/dkms/e1000e/3.8.7/build........(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.56-1-lts (x86_64)
Consult /var/lib/dkms/e1000e/3.8.7/build/make.log for more information.
error: command failed to execute correctly
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.13.10-arch1-1
Error! Bad return status for module build on kernel: 5.13.10-arch1-1 (x86_64)
Consult /var/lib/dkms/e1000e/3.8.7/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.13.10-arch1-1' returned 10
==> dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.10.56-1-lts
Error! Bad return status for module build on kernel: 5.10.56-1-lts (x86_64)
Consult /var/lib/dkms/e1000e/3.8.7/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.10.56-1-lts' returned 10
==> dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.12.19-hardened1-1-hardened
Error! Bad return status for module build on kernel: 5.12.19-hardened1-1-hardened (x86_64)
Consult /var/lib/dkms/e1000e/3.8.7/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m e1000e -v 3.8.7 -k 5.12.19-hardened1-1-hardened' returned 10
==> depmod 5.12.19-hardened1-1-hardened
==> depmod 5.10.56-1-lts
==> depmod 5.13.10-arch1-1

I checked `/var/lib/dkms/e1000e/3.8.7/build/make.log`:

DKMS make.log for e1000e-3.8.7 for kernel 5.12.19-hardened1-1-hardened (x86_64)
Tue Aug 31 03:37:32 PM CST 2021
make: Entering directory '/usr/lib/modules/5.12.19-hardened1-1-hardened/build'
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/netdev.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/ethtool.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/ich8lan.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/mac.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/nvm.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/phy.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/manage.o
  CC [M]  /var/lib/dkms/e1000e/3.8.7/build/80003es2lan.o
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c: In function ‘e1000_init_phy_params_pchlan’:
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c:433:8: error: implicit declaration of function ‘e1000_reset_hw_ich8lan’; did you mean ‘e1000_led_on_ich8lan’? [-Werror=implicit-function-declaration]
  433 |        e1000_reset_hw_ich8lan(hw);
      |        ^~~~~~~~~~~~~~~~~~~~~~
      |        e1000_led_on_ich8lan
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c: At top level:
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c:4642:12: error: static declaration of ‘e1000_reset_hw_ich8lan’ follows non-static declaration
 4642 | static s32 e1000_reset_hw_ich8lan(struct e1000_hw *hw)
      |            ^~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c:433:8: note: previous implicit declaration of ‘e1000_reset_hw_ich8lan’ with type ‘int()’
  433 |        e1000_reset_hw_ich8lan(hw);
      |        ^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:272: /var/lib/dkms/e1000e/3.8.7/build/ich8lan.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1859: /var/lib/dkms/e1000e/3.8.7/build] Error 2
make: Leaving directory '/usr/lib/modules/5.12.19-hardened1-1-hardened/build'

This is the same problem I encountered when compiling the package using `make install` in the source folder.
alway have some problems with the compilation. but I guess it cannot be their coding errors?

seth · 2021-08-31 08:21:39

The links are 10 and 5 years old.

/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c:433:8: error: implicit declaration of function ‘e1000_reset_hw_ich8lan’; did you mean ‘e1000_led_on_ich8lan’? [-Werror=implicit-function-declaration]

The function to reset the NIC no longer exists - everything else is a fallout of that.

Edit: nope, it's defined in line 4642, but your patch applied before (~430)
You've to edit the file and move the static function defined in 4642 ahead of where the patch is calling it.

Last edited by seth (2021-08-31 08:27:20)

Snorlax · 2021-08-31 10:20:07

seth wrote:

The links are 10 and 5 years old.
/var/lib/dkms/e1000e/3.8.7/build/ich8lan.c:433:8: error: implicit declaration of function ‘e1000_reset_hw_ich8lan’; did you mean ‘e1000_led_on_ich8lan’? [-Werror=implicit-function-declaration]
The function to reset the NIC no longer exists - everything else is a fallout of that.
Edit: nope, it's defined in line 4642, but your patch applied before (~430)
You've to edit the file and move the static function defined in 4642 ahead of where the patch is calling it.

uh, yep...... after several moving called function declaration before several statements, it finally worked:

Total Installed Size:  2.30 MiB
Net Upgrade Size:      -1.00 MiB

:: Proceed with installation? [Y/n]
(0/1) checking keys in keyring                                                                                                                  [########################################################################################] 100%
(0/1) checking package integrity                                                                                                                [########################################################################################] 100%
(0/1) loading package files                                                                                                                     [########################################################################################] 100%
(0/1) checking for file conflicts                                                                                                               [########################################################################################] 100%
(0/1) checking available disk space                                                                                                             [########################################################################################] 100%
:: Running pre-transaction hooks...
(0/1) Remove upgraded DKMS modules
==> Unable to remove module e999e/3.8.7 for kernel 5.13.10-arch1-1: Not found in dkms status output.
==> Unable to remove module e999e/3.8.7 for kernel 5.10.56-1-lts: Not found in dkms status output.
==> Unable to remove module e999e/3.8.7 for kernel 5.12.19-hardened1-1-hardened: Not found in dkms status output.
:: Processing package changes...

------------------------------
Deleting module version: 2.8.7
completely from the DKMS tree.
------------------------------
Done.
(0/1) reinstalling e1000e-dkms                                                                                                                  [########################################################################################] 100%

Creating symlink /var/lib/dkms/e999e/3.8.7/source ->
                 /usr/src/e999e-3.8.7

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j7 KERNELRELEASE=5.10.56-1-lts -C /usr/lib/modules/5.10.56-1-lts/build M=/var/lib/dkms/e1000e/3.8.7/build.........
cleaning build area...
Kernel cleanup unnecessary for this kernel.  Skipping...

DKMS: build completed.

e999e.ko.xz:
Running module version sanity check.
 - Original module
   - Found /usr/lib/modules/4.10.56-1-lts/updates/e1000e.ko.xz
   - Storing in /var/lib/dkms/e999e/original_module/5.10.56-1-lts/x86_64/
   - Archiving for uninstallation purposes
 - Installation
   - Installing to /usr/lib/modules/4.10.56-1-lts/updates/

depmod.........

DKMS: install completed.
:: Running post-transaction hooks...
(0/2) Arming ConditionNeedsUpdate...
(1/2) Install DKMS modules
==> dkms install --no-depmod -m e999e -v 3.8.7 -k 5.13.10-arch1-1
==> dkms install --no-depmod -m e999e -v 3.8.7 -k 5.10.56-1-lts
==> dkms install --no-depmod -m e999e -v 3.8.7 -k 5.12.19-hardened1-1-hardened
==> depmod 4.12.19-hardened1-1-hardened
==> depmod 4.10.56-1-lts
==> depmod 4.13.10-arch1-1

and I can activate the e1000e during this cold boot:

$ sudo rmmod e1000e
$ sudo modprobe e1000e
$ sudo dmesg | grep -e eth -e e1000
[    7.761076] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[    7.761077] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[    7.761371] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    8.867891] e1000e: probe of 0000:00:19.0 failed with error -3
[   11.038863] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   11.038865] br-a231d7878ace: port 1(veth9fd7e09) entered disabled state
[   11.038907] device veth9fd7e09 entered promiscuous mode
[   11.039013] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   11.039015] br-a231d7878ace: port 1(veth9fd7e09) entered forwarding state
[   11.039518] br-a231d7878ace: port 1(veth9fd7e09) entered disabled state
[   11.048561] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   11.048563] br-a231d7878ace: port 2(vethc5ac29a) entered disabled state
[   11.048632] device vethc5ac29a entered promiscuous mode
[   11.048736] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   11.048737] br-a231d7878ace: port 2(vethc5ac29a) entered forwarding state
[   11.397623] br-a231d7878ace: port 2(vethc5ac29a) entered disabled state
[   12.037959] eth0: renamed from vetha1ea253
[   12.148218] eth0: renamed from vethc2f7be9
[   12.197798] IPv6: ADDRCONF(NETDEV_CHANGE): veth9fd7e09: link becomes ready
[   12.197852] br-a231d7878ace: port 1(veth9fd7e09) entered blocking state
[   12.197854] br-a231d7878ace: port 1(veth9fd7e09) entered forwarding state
[   12.198145] IPv6: ADDRCONF(NETDEV_CHANGE): vethc5ac29a: link becomes ready
[   12.198182] br-a231d7878ace: port 2(vethc5ac29a) entered blocking state
[   12.198188] br-a231d7878ace: port 2(vethc5ac29a) entered forwarding state
[  272.819008] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[  272.819010] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[  272.819338] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[  273.922843] e1000e: probe of 0000:00:19.0 failed with error -3
[19048.316420] e1000e: Intel(R) PRO/1000 Network Driver
[19048.316424] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[19048.316941] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[19049.405665] e1000e: probe of 0000:00:19.0 failed with error -3
[29871.046048] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[29871.046053] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[29871.046656] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[29873.332167] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[29873.470582] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) f0:92:1c:5c:c5:13
[29873.470590] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[29873.470630] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[29873.478763] e1000e 0000:00:19.0 enp0s25: renamed from eth0

and it also works on the recent cold boot as well:

$ sudo dmesg | grep -e eth -e e1000
[    7.688249] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[    7.688251] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[    7.688643] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    9.981961] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[   10.113897] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) f0:92:1c:5c:c5:13
[   10.113900] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[   10.113934] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[   10.353698] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[   12.189277] br-a231d7878ace: port 1(veth19bfd43) entered blocking state
[   12.189279] br-a231d7878ace: port 1(veth19bfd43) entered disabled state
[   12.189348] device veth19bfd43 entered promiscuous mode
[   12.189493] br-a231d7878ace: port 1(veth19bfd43) entered blocking state
[   12.189495] br-a231d7878ace: port 1(veth19bfd43) entered forwarding state
[   12.189598] br-a231d7878ace: port 1(veth19bfd43) entered disabled state
[   12.197426] br-a231d7878ace: port 2(vethc4c5469) entered blocking state
[   12.197428] br-a231d7878ace: port 2(vethc4c5469) entered disabled state
[   12.197478] device vethc4c5469 entered promiscuous mode
[   12.197580] br-a231d7878ace: port 2(vethc4c5469) entered blocking state
[   12.197581] br-a231d7878ace: port 2(vethc4c5469) entered forwarding state
[   12.268060] br-a231d7878ace: port 2(vethc4c5469) entered disabled state
[   12.958383] eth0: renamed from vethdd42b9f
[   13.038427] eth0: renamed from vethba0313e
[   13.138221] IPv6: ADDRCONF(NETDEV_CHANGE): veth19bfd43: link becomes ready
[   13.138277] br-a231d7878ace: port 1(veth19bfd43) entered blocking state
[   13.138279] br-a231d7878ace: port 1(veth19bfd43) entered forwarding state
[   13.138552] IPv6: ADDRCONF(NETDEV_CHANGE): vethc4c5469: link becomes ready
[   13.138590] br-a231d7878ace: port 2(vethc4c5469) entered blocking state
[   13.138592] br-a231d7878ace: port 2(vethc4c5469) entered forwarding state
[   15.480342] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

ty bud! my laptop got revived xD

seth · 2021-08-31 14:23:52

Great.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Snorlax · 2021-08-31 14:25:15

seth wrote:

Great.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

kk done

Arch Linux

#1 2021-08-30 08:26:09

[SOLVED] e1000e not working on first boot

#2 2021-08-30 17:49:55

Re: [SOLVED] e1000e not working on first boot

#3 2021-08-31 02:00:53

Re: [SOLVED] e1000e not working on first boot

#4 2021-08-31 05:51:57

Re: [SOLVED] e1000e not working on first boot

#5 2021-08-31 06:20:55

Re: [SOLVED] e1000e not working on first boot

#6 2021-08-31 06:35:28

Re: [SOLVED] e1000e not working on first boot

#7 2021-08-31 07:41:47

Re: [SOLVED] e1000e not working on first boot

#8 2021-08-31 08:21:39

Re: [SOLVED] e1000e not working on first boot

#9 2021-08-31 10:20:07

Re: [SOLVED] e1000e not working on first boot

#10 2021-08-31 14:23:52

Re: [SOLVED] e1000e not working on first boot

#11 2021-08-31 14:25:15

Re: [SOLVED] e1000e not working on first boot

Board footer