LEAP 42.2 and Realtek

English Network/Internet
#1

Since my upgrade frome 42.1 to 42.2, my ethernet card Realtek doesn’t work:

lspci -v

09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
Subsystem: Lenovo Device 21dd
Flags: bus master, fast devsel, latency 0, IRQ 10
I/O ports at 4000 [size=256]
Memory at f0a04000 (64-bit, prefetchable) [size=4]
Memory at f0a00000 (64-bit, 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: [ac] MSI-X: Enable- Count=4 Masked-
Capabilities: [cc] Vital Product Data
Kernel modules: r8169

lspci -vv

09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
Subsystem: Lenovo Device 21dd
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at 4000 [size=256]
Region 2: Memory at f0a04000 (64-bit, prefetchable) [size=4]
Region 4: Memory at f0a00000 (64-bit, prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [cc] Vital Product Data
pcilib: sysfs_read_vpd: read failed: Input/output error
Not readable
Kernel modules: r8169

Where can I found the driver?

I don’t find this for Kernel 4
Linux 4.4.27-2-default #1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c) x86_64 x86_64 x86_64 GNU/Linux

[LEFT]LINUX driver for kernel 3.x and 2.6.x and 2.4.x[/LEFT]

8.043 2016/10/25

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

#2

Please post:

zypper se -si r8168 kmp

Did you install the r8168 Driver under 42.1?
Is there a Blacklist File for r8169?

grep 'blacklist r816' /etc/modprobe.d/*
#3

I just found your repo on my config :
http://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_42.2/x86_64/

It was disabled before upgrade to 42.2.

The new version is installed now.
I will try.

#4

If you have enabled my Repo in 42.1 and installed r8168, the kmp will not loaded anymore after Upgrade to 42.2.
But the blacklist-File (Package r8168.rpm) will take still Effect and will stop r8169 from loading in 42.2.

#5

With your repo for 4.2, that works fine after package update
Thx

#6

Thx for the solution

#7

PS:
Mostly you do not need the r8168 Driver from Realtek (build f.e. in my Repo), the Driver r8169 from Kernel works.

3 Computers here works with r8169 without any Problems.
I have build r8168 only to see, if there is anything running better…

#8

Am Wed, 23 Nov 2016 17:46:01 GMT
schrieb Sauerland <Sauerland@no-mx.forums.microfocus.com>:

> PS:
> Mostly you do not need the r8168 Driver from Realtek (build f.e. in my
> Repo), the Driver r8169 from Kernel works.
>

> 3 Computers here works with r8169 without any Problems.

Confirmed, I have two machines with respective realtek cards and both work as
well as with the vendor driver.

> I have build r8168 only to see, if there is anything running
> better…
>
>

Ditto, see above.

However, for some extra value to my otherwise rather useless post, there is one
suggestion I would like to add which has to be considered by any packager of
an external kernel module.

If you are planning to keep this driver package in your home project, you should
also add openSUSE_Leap_42.2_Update as a build target, otherwise your
“customers” might run into the same issue if the kernel for 42.2 gets updated.

This only happens if there is a non-compatible ABI change in a future kernel
package, as then the typical “symlink the
module to /lib/modules/KERBELVERSION/weak-updates” would fail while the
blacklisting of r8169 is still in effect.

(This of course applies to all openSUSE verson you are publishing kernel module
packages for.)

AK

Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

#9

Am Wed, 23 Nov 2016 18:16:18 GMT
schrieb AK <Akoellh@no-mx.forums.microfocus.com>:

>
> If you are planning to keep this driver package in your home project, you
> should also add openSUSE_Leap_42.2_Update as a build target, otherwise your
> “customers” might run into the same issue if the kernel for 42.2 gets updated.

> (This of course applies to all openSUSE verson you are publishing kernel
> module packages for.)
>

Addendum:

Just saw that you have “Update”-repos activated for 13.2 and 42.1, so 42.2
is probably only missing at the moment and you are obviously aware of the
issue.

So my last comment might be only useful for other potential packagers reading
this thread and hopefully adapt this to their home repos.

AK

–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

#10

Forgotten up to now…

Will do it on Weekend…