No ethernet connection: hardware fault?

[nrickert]

Like to have your opinion!

Hmm, I have not been looking closely enough at this thread.

There is a possibility that your problem is the one reported in Bug 1080832. Pay particular attention to comment #5 in that bug report.

[dcurtisfra]

@jehojakim:

Back to the very beginning:

1. Your Ethernet controller is a Realtek RTL8111/8168/8411
2. The Kernel driver is the r8169 (Leap 15.0 default for these cards).
3. It has been suggested that, you should change to the “r8168” driver.

And that's where a couple of points came up.

AFAICS, the current Leap 15.0 r8168 driver on Packman has the following package properties:

• Package Name: r8168-kmp-default
• Version: 8.045.08_k4.12.14_lp150.12.45-lp150.4.14

The current Leap 15.0 Kernel version is 4.12.14-lp150.12.45 — if I'm reading the Packman version correctly, the current r8168 Driver should work with “4.12.14” Kernels back to “lp150.4.14” and up to “lp150.12.45” …

BTW, you'll have to also install the “r8168-blacklist-r8169” package …

---

A DuckDuckGo search for r8168 drivers revealed that, there are various problems occurring with Realtek RTL8111/8168/8411 hardware and the current Linux Kernel r8169 driver.
Currently I'm lucky but, I don't know for how long:

 # ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version: rtl8168e-3_0.0.4 03/27/12
expansion-rom-version: 
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
 #

Maybe it's time that I purchase a new Motherboard – the current one is labelled “Windows 7 ready” …

[jehojakim]

Hmm, I have not been looking closely enough at this thread.

There is a possibility that your problem is the one reported in Bug 1080832. Pay particular attention to comment #5 in that bug report.

Thanks for the advise. I'm not running TW on this system, but Leap 15, so it is doubtful if this bug bites me.
Would run the scripts advised in 1080832#5 anyhow, if not my problem was solved, see my answer @dcurtisfra just below.

[jehojakim]

@jehojakim:

Back to the very beginning:

1. Your Ethernet controller is a Realtek RTL8111/8168/8411
2. The Kernel driver is the r8169 (Leap 15.0 default for these cards).
3. It has been suggested that, you should change to the “r8168” driver.

And that's where a couple of points came up.

AFAICS, the current Leap 15.0 r8168 driver on Packman has the following package properties:

• Package Name: r8168-kmp-default
• Version: 8.045.08_k4.12.14_lp150.12.45-lp150.4.14

The current Leap 15.0 Kernel version is 4.12.14-lp150.12.45 — if I'm reading the Packman version correctly, the current r8168 Driver should work with “4.12.14” Kernels back to “lp150.4.14” and up to “lp150.12.45” …

BTW, you'll have to also install the “r8168-blacklist-r8169” package …

---

A DuckDuckGo search for r8168 drivers revealed that, there are various problems occurring with Realtek RTL8111/8168/8411 hardware and the current Linux Kernel r8169 driver.
Currently I'm lucky but, I don't know for how long:

 # ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version: rtl8168e-3_0.0.4 03/27/12
expansion-rom-version: 
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
 #

Maybe it's time that I purchase a new Motherboard – the current one is labelled “Windows 7 ready” …

Well, things are becoming very funny.
Installing those drivers didn't help, BUT: de-installing them (so the old drivers became active again, I suppose) did.... after a long time I have this system connected again!

Thanks to you, and to all of you who gave effort on solving this!

[nrickert]

Thanks for the advise. I'm not running TW on this system, but Leap 15, so it is doubtful if this bug bites me.

I'm running Leap 15.0, and it bit me. However, I recently replaced the home network router and the problem no longer exists here.

I'll note that you seem to have solved your problem.