Wicked: device eth0: operation timed out

diophantus7 · January 31, 2021, 6:42pm

Hello,

Since recently I have problems to connect my intel nuc to the network. It was working well with the static setup, not sure what broke it.


systemctl status wicked

returns message of the title.


lspci | grep thernet
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03)

Pinging results in “connect: Network is unreachable”.

Any idea what might be wrong? I just don’t know where to look.

hcvv · January 31, 2021, 7:27pm

Please post

ip address

It will probably confirm that eth0 is down.

Is this after some update, or just “out of the blue”? In the latter case it could be a hardware problem (check cable connections, etc.)

BTW, please always post computer text complete in one copy/paste. Thus not the command without the prompt in the CODE block and (part of?) the output in thread title (of course you may also post that error in the thread title).

deano_ferrari · January 31, 2021, 10:22pm

Watch wicked logging in a terminal using

sudo journalctl -fu wicked

In another terminal do

sudo systemctl restart wicked

Observe/capture the output (you could also just redirect output to a text file if desired). Does that result in a working connection?

If not, examine link status with

ethtool eth0

*You may need to change the name of the interface to suit your system

dcurtisfra · February 1, 2021, 4:23pm

@diophantus7:

Some things to check – either “sudo” or, simply login as the user “root” …

Find the PCI address of the Ethernet controller –


 # lspci | grep -i 'ethernet'
**03:00.0** Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
 #

The PCI address is the left most field of the resulting output line – use the PCI address to gain some detailed information about the Ethernet controller – for example, on this machine – your machine will be different because, it ain’t an AMD machine …


 # lspci -s **03:00.0** -v
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: ASUSTeK Computer Inc. Device 8677
        Flags: bus master, fast devsel, latency 0, IRQ 31
        I/O ports at f000 [size=256]
        Memory at fcd04000 (64-bit, non-prefetchable) [size=4]
        Memory at fcd00000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [170] Latency Tolerance Reporting
        Capabilities: [178] L1 PM Substates
        Kernel driver in use: r8169
        Kernel modules: r8169

 #

The immediately needed information is, the “Kernel driver in use” and “Kernel modules” – the driver and module information is then checked as follows – a further example from this machine –


 # lsmod | grep -i 'r8169'
r8169                  94208  0
libphy                106496  2 r8169,realtek
 #

Then, search the systemd Journal of the current boot with:

 # journalctl --this-boot --output=short-monotonic | grep -iE 'r8169|realtek|eth0|wicked|network'

[HR][/HR]The examples here, are those of a running system – please check your system and post any errors and/or anomalies in this thread.

There’s no need to quote my examples in your reply – simply post the errors you find.

[/size][/size][/size]

tsu2 · February 1, 2021, 9:28pm

diophantus7:

Hello,

Since recently I have problems to connect my intel nuc to the network. It was working well with the static setup, not sure what broke it.
systemctl status wicked
returns message of the title.
lspci | grep thernet
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03)
Pinging results in “connect: Network is unreachable”.

Any idea what might be wrong? I just don’t know where to look.

“Returns message of the title” doesn’t mean anything to me.
You should see a standard output for this command,
First whether the service is running or not
A relevant snippet from the system log,
And more.

The error “network is unreachable” means that your configured network settings are likely incompatible with the network it’s on.
So, you need to start with basics, like how your interface is currently configured… DHCP client or static address? Did you change something in "YaST > Network Settings > Global configuration tab? And, of course the critical missing piece is what “systemctl status wicked” returns.

TSU

diophantus7 · February 2, 2021, 8:23pm

hcvv:

Please post
ip address
It will probably confirm that eth0 is down.

Is this after some update, or just “out of the blue”? In the latter case it could be a hardware problem (check cable connections, etc.)

BTW, please always post computer text complete in one copy/paste. Thus not the command without the prompt in the CODE block and (part of?) the output in thread title (of course you may also post that error in the thread title).

ip a

only shows the lo and wlan0 devices. I am not totally sure if it happened after an update.
Sorry about the CODE blog. I was just too lazy to type all the output since I am writing this from my laptop and the NUC doesn’t have a working access to the internet.

deano_ferrari:

Watch wicked logging in a terminal using
sudo journalctl -fu wicked
In another terminal do
sudo systemctl restart wicked
Observe/capture the output (you could also just redirect output to a text file if desired). Does that result in a working connection?

If not, examine link status with
ethtool eth0
*You may need to change the name of the interface to suit your system

That is the message I posted above. The more detailed message is


Starting wicked managed network interfaces...
device eth0: operation timed out
lo                  up
eth0             no-device


# ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
No data available

Doesn’t show anything new I would say. I will post it once I find a usb stick to get the data.

malcolmlewis · February 2, 2021, 8:32pm

Hi
@OP, did you see this thread?
https://forums.opensuse.org/showthread.php/547936-Update-today-broke-wired-network-connection

diophantus7 · February 6, 2021, 10:43am

As mentioned in my original post, it is configured with a static address. I haven’t changed anything when it broke.

diophantus7 · February 6, 2021, 10:46am

dcurtisfra:

@diophantus7:
search the systemd Journal of the current boot with:
 # journalctl --this-boot --output=short-monotonic | grep -iE 'r8169|realtek|eth0|wicked|network'
[HR][/HR]The examples here, are those of a running system – please check your system and post any errors and/or anomalies in this thread.

There’s no need to quote my examples in your reply – simply post the errors you find.

Here is the requested output

# journalctl --this-boot --output=short-monotonic | grep -iE 'r8169|realtek|eth0|wicked|network'
    1.605755] antigone kernel: drop_monitor: Initializing network drop monitor service 
    2.236229] antigone systemd-udevd[267]: Network interface NamePolicy= disabled by default. 
    4.053065] antigone systemd-udevd[430]: Network interface NamePolicy= disabled by default. 
    4.559746] antigone kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k 
    4.559747] antigone kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. 
    4.560041] antigone kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode 
    5.132616] antigone kernel: e1000e: probe of 0000:00:19.0 failed with error -2 
    5.466449] antigone kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC283: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp 
    5.466452] antigone kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) 
    5.466454] antigone kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=0 (0x0/0x0/0x0/0x0/0x0) 
    5.466456] antigone kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0 
    5.466458] antigone kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs: 
    5.466460] antigone kernel: snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19 
    6.293975] antigone systemd[1]: Starting wicked AutoIPv4 supplicant service... 
    6.297702] antigone systemd[1]: Starting wicked DHCPv6 supplicant service... 
    6.300273] antigone systemd[1]: Reached target Host and Network Name Lookups. 
    6.303209] antigone systemd[1]: Starting wicked DHCPv4 supplicant service... 
    6.396092] antigone systemd[1]: Started wicked AutoIPv4 supplicant service. 
    6.396703] antigone systemd[1]: Started wicked DHCPv6 supplicant service. 
    6.397039] antigone systemd[1]: Started wicked DHCPv4 supplicant service. 
    6.411461] antigone systemd[1]: Starting wicked network management service daemon... 
    6.463025] antigone systemd[1]: Started wicked network management service daemon. 
    6.465548] antigone systemd[1]: Starting wicked network nanny service... 
    6.510965] antigone systemd[1]: Started wicked network nanny service. 
    6.512880] antigone systemd[1]: Starting wicked managed network interfaces... 
   36.586854] antigone wicked[904]: device eth0: operation timed out 
   36.587801] antigone wicked[904]: device eth1: operation timed out 
   36.589881] antigone wicked[904]: lo              up 
   36.589881] antigone wicked[904]: eth0            no-device 
   36.589881] antigone wicked[904]: eth1            no-device 
   36.590715] antigone systemd[1]: Started wicked managed network interfaces. 
   36.591225] antigone systemd[1]: Reached target Network. 
   36.627021] antigone ntpd[1060]: ntp-4 is maintained by Network Time Foundation, 
   36.634407] antigone start-ntpd[1046]: Starting network time protocol daemon (NTPD)

diophantus7 · February 6, 2021, 11:28am

Ok sorry guys. While I checked if the cable is working, I just booted a live USB system and it doesn’t work there either. So probably the port is malfunctioning…
Thanks anyway!