No ethernet connection: hardware fault?

English Hardware
#1

Hi,

On my HTPC running Leap 15 my network connection has gone. Yast gives “Not connected” for the ethernet device, does permit configuring of it, but no connection is made.
I added a second Ethernet adapter, but that also gives the same result.

It’s not the cable: if I connect that to a raspberry, the connection is fine.

I don’t see anything regarding this in dmesg, apart from the finding that the connection is not available.

I’ve configured network devices through Yast many times, and never encountered this. Can I have overlooked something, or is it definitively a hardware thing?
Something that affects both the Ethernet device on the mb itself, and the second device in the PCI-slot?

Like to have your opinion!

regards, jehojakim

#2

Some hardware information would be useful to start with…

/usr/sbin/hwinfo --netcard

Observe the kernel output from

dmesg --follow

when first plugging in an ethernet cable.

#3

The result of hwinfo --netcard is

18: PCI 500.0: 0200 Ethernet controller
  [Created at pci.378]
  Unique ID: JNkJ.qQIprdItMR3
  Parent ID: Rgik.DFXWmiC9JE1
  SysFS ID: /devices/pci0000:00/0000:00:15.0/0000:05:00.0
  SysFS BusID: 0000:05:00.0
  Hardware Class: network
  Model: "Intel Gigabit CT Desktop Adapter"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x10d3 "82574L Gigabit Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0xa01f "Gigabit CT Desktop Adapter"
  Driver: "e1000e"
  Driver Modules: "e1000e"
  Device File: eth1
  Memory Range: 0xfeac0000-0xfeadffff (rw,non-prefetchable)
  Memory Range: 0xfea00000-0xfea7ffff (rw,non-prefetchable)
  I/O Ports: 0xc000-0xcfff (rw)
  Memory Range: 0xfeae0000-0xfeae3fff (rw,non-prefetchable)
  Memory Range: 0xfea80000-0xfeabffff (ro,non-prefetchable,disabled)
  IRQ: 16 (1497 events)
  HW Address: 68:05:ca:16:37:7b
  Permanent HW Address: 68:05:ca:16:37:7b
  Link detected: no
  Module Alias: "pci:v00008086d000010D3sv00008086sd0000A01Fbc02sc00i00"
  Driver Info #0:
    Driver Status: e1000e is active
    Driver Activation Cmd: "modprobe e1000e"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #15 (PCI bridge)

36: PCI 100.0: 0200 Ethernet controller
  [Created at pci.378]
  Unique ID: rBUF.5rbhBgx50x4
  Parent ID: 8otl.G5Dfw+ssufC
  SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: network
  Model: "Gigabyte Onboard Ethernet"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xe000 "Onboard Ethernet"
  Revision: 0x06
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: eth0
  I/O Ports: 0xe000-0xefff (rw)
  Memory Range: 0xd0004000-0xd0004fff (ro,non-prefetchable)
  Memory Range: 0xd0000000-0xd0003fff (ro,non-prefetchable)
  IRQ: 43 (no events)
  HW Address: 94:de:80:06:30:cf
  Permanent HW Address: 94:de:80:06:30:cf
  Link detected: no
  Module Alias: "pci:v000010ECd00008168sv00001458sd0000E000bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #34 (PCI bridge)

dmesg --follow gives nothing when plugging in an ethernet cable, on neither of the interfaces.

I’ve tried it after booting without the cable attached (which is I think you mean by “first plugging in”), and after booting with the cable already attached, then removing and re-inserting it.

In all cases the result is the same.

#4

What happens if you boot a previous kernel?

#5

Alas, there is no previous kernel, since it’s a fresh install of Leap 15.0 And, since I don’t have internet connection, update is not possible…

There’s a hole in the bucket, dear Liza…

#6

So never had network connection???

What NIC chip do you have some realtek chips require a special driver.

lspci as root should show you the hardware

#7

Please post:

ping -c1 8.8.8.8

ping -c1 google.com
#8

Both ethernet devices show no link detected. In any case, when you connect a known good ethernet cable between your router and one of the NICs, observe the output from

  1. For the Gigabyte Onboard Ethernet (Realtek chipset)
/usr/sbin/ethtool eth0
  1. For the Intel NIC
/usr/sbin/ethtool eth1
#9

Your Realtek NIC is currently using the r8169 driver…

Model: "Gigabyte Onboard Ethernet"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
SubDevice: pci 0xe000 "Onboard Ethernet"
Revision: 0x06
Driver: "r8169"
Driver Modules: "r8169"
Device File: eth0

Instead, install the r8168 Realtek driver (for Leap 15)…

https://software.opensuse.org/package/r8168

#10

Name or service unkknown

#11

Not on Leap 15, but I did have a connection on various Leap 42.x releases. Did not try those this time, though.

lspci sees net network hardware as follows:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

#12 
Settings for eth1:
    Supported ports:  TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Speed: Unknown!
    Duplex: Unknown! (255)
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown (auto)
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: no
#13

The packages shown there are all source rpm’s from the community; I suppose I have to compile them.
Any advice how to do that? Of course I can install a development environment (gcc, linker, etc.) from the install usb-stick.

Edit: The development environment is installed by default, I see…

#14

They are not at all src.rpms…

Do you try to install one of them before?
Do you restart your Router?

#15

The required packages are available from the packman repo…

# zypper se -s r8168
Loading repository data...
Reading installed packages...

S | Name                        | Type       | Version                                  | Arch   | Repository
--+-----------------------------+------------+------------------------------------------+--------+-----------
  | r8168                       | srcpackage | 8.045.08-lp150.4.13                      | noarch | packman   
  | r8168-blacklist-r8169       | package    | 8.045.08-lp150.4.13                      | x86_64 | packman   
  | r8168-debugsource           | package    | 8.045.08-lp150.4.13                      | x86_64 | packman   
  | r8168-kmp-default           | package    | 8.045.08_k4.12.14_lp150.12.28-lp150.4.13 | x86_64 | packman   
  | r8168-kmp-default-debuginfo | package    | 8.045.08_k4.12.14_lp150.12.28-lp150.4.13 | x86_64 | packman
#16

I do not know, if the package is working for the kernel, shipped with openSUSE Leap 15.0.

v  | kernel-default                   | package    | 4.12.14-lp150.11.4          | x86_64 | openSUSE-Leap-15.0-Oss

Because there was no Update up to now…

Maybe these from my OSS Repo are right:
https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15.0/x86_64/r8168-kmp-default-8.046.00_k4.12.14_lp150.11-lp150.61.1.x86_64.rpm
https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15.0/x86_64/r8168-blacklist-r8169-8.046.00-lp150.61.1.x86_64.rpm

But that does not show, why the Intel LAN has also no connect…

#17

The OP has not verified that the ethernet cable and/or router port is ok. Even connecting between two hosts (PC, switch, or other network device) should result in an active link and correctly negotiated speed/duplex.

#18

Well, as I said in my original post, if I insert the cable in a raspberry, the network connection is fine. So I think that would be enough verification that the cable and router port are OK…

#19

I’m sorry, I really only see .src.rpm’s there… No, I didn’t try to install them before.
And no, I didn’t restart my router, but, as I said in my OP, when inserted to a rasperry, the same cable gives a fine connection.
So I would thing the cable/router combination is OK.

#20

Please post the output of

dmesg | grep -i "eth0|eth1"

Also, with respect to your Intel NIC…

dmesg | grep e1000e