Try to look for the right kmod for your adapter, looking for PCI ID and correspondant kmod.
If this hardware worked fine before, maybe it’s only a matter of finding the right driver.
I never worked with KMOD’s and PCI ID’s before, so I have no clue where to start looking.
This is a ‘new’ system and the NIC’s are new too, so it never worked before.
Not sure if this helps … but it means nothing to me.
lsmod
Module Size Used by
ifb 12974 0
udp_diag 12801 0
unix_diag 12601 0
tcp_diag 12591 0
inet_diag 18949 2 tcp_diag,udp_diag
br_netfilter 22256 0
xt_recent 18500 1
ipt_REJECT 12541 4
nf_reject_ipv4 13373 1 ipt_REJECT
xt_multiport 12798 8
xt_set 18141 78
xt_NFQUEUE 12697 28
xt_hashlimit 17569 34
xt_mac 12492 6
xt_TCPMSS 12707 1
xt_addrtype 12676 77
xt_mark 12563 144
xt_connmark 12755 32
xt_conntrack 12760 83
xt_REDIRECT 12757 1
nf_nat_redirect 12771 1 xt_REDIRECT
xt_nat 12681 4
ipt_MASQUERADE 12678 3
nf_nat_masquerade_ipv4 13463 1 ipt_MASQUERADE
xt_comment 12504 76
xt_CT 12956 22
sch_fq_codel 17571 0
ip6_tables 26912 0
xt_ndpi 488506 75
xt_NFLOG 12537 0
nfnetlink_log 17892 1 xt_NFLOG
nf_log_ipv4 12767 34
nf_log_common 13317 1 nf_log_ipv4
xt_LOG 12690 34
nf_nat_h323 17720 0
nf_nat_sip 17191 0
nf_conntrack_sip 33780 3 nf_nat_sip
nf_conntrack_h323 73865 5 nf_nat_h323
nf_conntrack_sane 12954 2
nf_conntrack_netlink 40492 0
nf_nat_tftp 12529 0
nf_nat_snmp_basic 17302 0
nf_conntrack_snmp 12857 3 nf_nat_snmp_basic
nf_nat_pptp 13115 0
nf_nat_proto_gre 13009 1 nf_nat_pptp
nf_nat_irc 12762 0
nf_nat_ftp 12809 0
nf_nat_amanda 12533 0
nf_conntrack_tftp 13121 3 nf_nat_tftp
nf_conntrack_pptp 19227 3 nf_nat_pptp
nf_conntrack_proto_gre 14434 1 nf_conntrack_pptp
nf_conntrack_netbios_ns 12665 2
nf_conntrack_broadcast 12589 2 nf_conntrack_netbios_ns,nf_conntrack_snmp
nf_conntrack_irc 13489 3 nf_nat_irc
nf_conntrack_ftp 18448 3 nf_nat_ftp
ts_kmp 12605 5
nf_conntrack_amanda 13041 3 nf_nat_amanda
xt_state 12578 0
iptable_raw 12678 1
iptable_mangle 12695 1
iptable_nat 12875 1
nf_conntrack_ipv4 19149 139
nf_defrag_ipv4 12729 1 nf_conntrack_ipv4
nf_nat_ipv4 14115 1 iptable_nat
nf_nat 26583 12 nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda, nf_nat_redirect,nf_nat_proto_gre,nf_nat_h323,nf_nat_ipv4,nf_nat_pptp,nf_nat_tftp ,xt_nat,nf_nat_masquerade_ipv4
nf_conntrack 143411 30 nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda, xt_ndpi,xt_CT,nf_nat_snmp_basic,nf_conntrack_netbios_ns,nf_conntrack_proto_gre,n f_nat,xt_state,nf_nat_h323,nf_nat_ipv4,nf_nat_pptp,nf_nat_tftp,xt_conntrack,nf_c onntrack_amanda,nf_nat_masquerade_ipv4,nf_conntrack_netlink,nf_conntrack_broadca st,xt_connmark,nf_conntrack_ftp,nf_conntrack_irc,nf_conntrack_sip,nf_conntrack_h 323,nf_conntrack_ipv4,nf_conntrack_pptp,nf_conntrack_sane,nf_conntrack_snmp,nf_c onntrack_tftp
bridge 155432 1 br_netfilter
stp 12976 1 bridge
llc 14552 2 stp,bridge
iptable_filter 12810 1
binfmt_misc 17468 1
nfnetlink_queue 18197 8
ip_set_hash_net 36021 3
ipmi_devintf 17459 0
ipmi_msghandler 56728 1 ipmi_devintf
ip_set_hash_ip 31658 24
ip_set 45799 3 ip_set_hash_net,ip_set_hash_ip,xt_set
overlay 91659 0
vboxnetadp 25813 0
vboxnetflt 27959 0
vboxdrv 499640 2 vboxnetadp,vboxnetflt
sunrpc 366617 1
vfat 17461 1
fat 65950 1 vfat
snd_hda_codec_realtek 116449 1
snd_hda_codec_generic 74631 1 snd_hda_codec_realtek
snd_hda_codec_hdmi 52340 1
snd_hda_intel 44486 6
snd_hda_codec 136355 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda _codec_generic,snd_hda_intel
snd_hda_core 91007 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda _codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep 17704 1 snd_hda_codec
intel_powerclamp 14451 0
coretemp 13444 0
intel_rapl 19451 0
crc32_pclmul 13133 0
snd_seq 62774 0
ghash_clmulni_intel 13273 0
aesni_intel 189456 1
lrw 13286 1 aesni_intel
gf128mul 15139 1 lrw
glue_helper 13990 1 aesni_intel
dell_wmi 13251 0
ablk_helper 13597 1 aesni_intel
sparse_keymap 13948 1 dell_wmi
cryptd 21190 3 ghash_clmulni_intel,aesni_intel,ablk_helper
snd_seq_device 14356 1 snd_seq
snd_pcm 109531 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,s nd_hda_core
dell_smbios 21539 1 dell_wmi
snd_timer 34110 2 snd_pcm,snd_seq
snd 83987 22 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_h da_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel, snd_seq_device
soundcore 15047 1 snd
dell_wmi_descriptor 13740 2 dell_smbios,dell_wmi
mei_wdt 13426 0
mei_me 32848 0
mei 95246 3 mei_wdt,mei_me
iTCO_wdt 13572 0
iTCO_vendor_support 13242 1 iTCO_wdt
dcdbas 15108 1 dell_smbios
wmi 21636 3 dell_smbios,dell_wmi_descriptor,dell_wmi
pcspkr 12718 0
sg 40719 0
i2c_i801 22736 0
lpc_ich 21086 0
ip_tables 27126 4 iptable_filter,iptable_mangle,iptable_nat,iptabl e_raw
xfs 1014152 2
libcrc32c 12644 3 xfs,nf_nat,nf_conntrack
sd_mod 46281 4
sr_mod 22416 0
cdrom 46696 1 sr_mod
crc_t10dif 12912 1 sd_mod
crct10dif_generic 12647 0
i915 1896341 2
i2c_algo_bit 13413 1 i915
iosf_mbi 15582 2 i915,intel_rapl
drm_kms_helper 186531 1 i915
syscopyarea 12529 1 drm_kms_helper
ahci 34056 3
sysfillrect 12701 1 drm_kms_helper
sysimgblt 12640 1 drm_kms_helper
fb_sys_fops 12703 1 drm_kms_helper
libahci 31992 1 ahci
e1000e 252695 0
drm 468454 4 i915,drm_kms_helper
libata 247190 2 ahci,libahci
serio_raw 13434 0
r8169 84623 0
crct10dif_pclmul 14307 1
crct10dif_common 12595 3 crct10dif_pclmul,crct10dif_generic,crc_t10dif
crc32c_intel 22094 1
ptp 23551 1 e1000e
pps_core 19057 1 ptp
drm_panel_orientation_quirks 17180 1 drm
video 24538 1 i915
dm_mirror 22326 0
dm_region_hash 20813 1 dm_mirror
dm_log 18411 2 dm_region_hash,dm_mirror
dm_mod 128595 8 dm_log,dm_mirror
fuse 100393 1
kvm_intel 188793 0
kvm 653976 1 kvm_intel
irqbypass 13503 1 kvm
So i uncorrecly assumed that the hardware you’re using was the same from ClearOS 7, shame on me.
With the command
lspci | grep Ethernet
you’ll have the output of all the devices that kernel and mods classify as Ethernet cards (mind the capital e!)
This is the output of my VM guest
lspci |grep Ethernet
02:02.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)
For every card recognized you’ll have a line, for every line, please type down
lspci -s **:**.* -v
with the numers of previous output replacing the * character.
Continuing with my example
lspci -s 02:02.0 -v
02:02.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)
Subsystem: VMware VMXNET3 Ethernet Controller
Physical Slot: 34
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe243000 (32-bit, non-prefetchable) [size=4K]
Memory at fe242000 (32-bit, non-prefetchable) [size=4K]
Memory at fe240000 (32-bit, non-prefetchable) [size=8K]
I/O ports at 0a20 [size=16]
Expansion ROM at fdd10000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [48] Express Endpoint, MSI 00
Capabilities: [84] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [9c] MSI-X: Enable+ Count=65 Masked-
Capabilities: [100] Device Serial Number 00-0c-29-ff-ff-33-0c-84
Kernel driver in use: vmxnet3
Kernel modules: vmxnet3
Please, post the output of these commands.
Last but not least: this is technically not Nethserver support, more CentOS 7 support. The older NS version mimic a linux distro, however still needs a working OS with drivers correctly interacting to hardware to have best performances.
These commands only enquiry info from your system, do not make any change.
Thanks for the info.
Currently the TP-Link card has been removed from my system and it is packed for shipment.
The Axagon card will arive tommorow in which I have more trust.
According to it’s specs, it at least is supported by Linux.
I will send the results of your commands after I have installed the Axagon card.
I still will have to compile a driver for it for optimum performance.
My clean installed NS7 box still is missing the dependencies, so I will have to yum install them first.
The Realtek source code for the RTL8111 version 8.052.01 (kernel 2.4.x and later) is from 2023.
So I have high hopes that my NS7 box is able to do that.
If you prefer compiling your own the drivers, go for it.
IMVHO i’d go the route of kmod with yum install kmod-r8168, which according to this archived wiki
https://wiki.centos.org/AdditionalResources(2f)HardwareList(2f)CentOS5(2f)RealTek(2f)r1000.html
should be the right kmod/driver for your NIC.
Elrepo might be a resource too
Why don’t you try network cards with Intel chips? Aside from the 2.5GB ones, I see that they are well supported and have never given me any problems.
I also confirm this!
Actually even the 2.5 GBE Intel NICs are fairly well supported!
And: They may cost a bit more than RealTek NICs, but they often get 10-30% more throughput than RealTek NICs…
My 2 cents
Andy
1 Like
Hi all,
I will take the time to reply to all your messages later, but first I need to solve this problem.
I physically installed the new NIC, but when I attempted to install the correct driver with yum in PuTTy this happened …
The first time this command produced a long list of dependencies that where about to be installed, but my workstation crashed.
I didn’t know what to do so I rebooted my NS7 box.
I did this to try to clean it up:
yum clean all
yum makecache
Now this is the result:
yum install kmod-r8168
Loaded plugins: changelog, fastestmirror, langpacks, nethserver_events
Loading mirror speeds from cached hostfile
- epel: mirrors.hostiserver.com
- rpmfusion-free-updates: fr2.rpmfind.net
No package kmod-r8168 available.
Error: Nothing to do
Please assist.
I had a failing SSD in my workstation that caused this problem.
I fixed it, so now I can finally try to install the correct driver.
I just wanted to say that there is no such thing as a yum install of this driver.
The only way I could find is by compiling it, so I have no choice.
It’s possible that some EL7 repos (like elrepo) are deprecated / being archived
result without elrepo
yum install kmod-r8168
Loaded plugins: changelog, fastestmirror, nethserver_events
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 5.1 kB 00:00:00
* epel: d2lzkl7pfhq30w.cloudfront.net
ce-base/7/x86_64/signature | 811 B 00:00:00
ce-base/7/x86_64/signature | 3.6 kB 00:00:00 !!!
ce-extras/7/x86_64/signature | 819 B 00:00:00
ce-extras/7/x86_64/signature | 2.9 kB 00:00:00 !!!
ce-sclo-rh | 3.0 kB 00:00:00
ce-sclo-sclo | 3.0 kB 00:00:00
ce-updates/7/x86_64/signature | 819 B 00:00:00
ce-updates/7/x86_64/signature | 2.9 kB 00:00:00 !!!
elasticsearch-7.x | 1.3 kB 00:00:00
mrmarkuz/7/signature | 490 B 00:00:00
mrmarkuz/7/signature | 2.9 kB 00:00:00 !!!
nethforge/7/x86_64/signature | 836 B 00:00:00
nethforge/7/x86_64/signature | 3.6 kB 00:00:00 !!!
nethserver-base/7/x86_64/signature | 836 B 00:00:00
nethserver-base/7/x86_64/signature | 2.9 kB 00:00:00 !!!
nethserver-updates/7/x86_64/signature | 836 B 00:00:00
nethserver-updates/7/x86_64/signature | 3.6 kB 00:00:00 !!!
zammad/x86_64/signature | 488 B 00:00:00
zammad/x86_64/signature | 1.3 kB 00:00:00 !!!
No package kmod-r8168 available.
Error: Nothing to do
After these commands
rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
yum install https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
(source, adapted, here start [ELRepo Wiki])
(which by the way… worked flawlessly)
Result was almost the same.
No package kmod-r8168 available.
Digging little further…
https://pkgs.org/search/?q=kmod-r8168
no version for CentOS 7.0 available here
So… scenario provided by @dnutan makes sense, reduce issues and bandwith consumption from mirrors avoiding to provide packages for distro no more supported (and forn an almost 12 years old kernel).
Then it’s eventually time for look for another brand or a mirror for the package… from network card chip provider or some reliable and confirmed source.
Strange is…
https://mirror.ihost.md/elrepo/archive/elrepo/el7/x86_64/RPMS/
- in this directory the package is available.*
This is my reply to @saitobenkei & @Andy_Wismer.
I chose Realtek, because Intel is too expensive and I already spend a lot upgrading most of my hardware and network.
Even when I know now that the following could have been prevented.
I attempted to compile and install the driver for my new NIC by following the instructions of the latest Realtek driver, but besides almost breaking my box and killing the 2 External NIC’s this was the result:
[root@system r8168-ring-lib-8.052.01] sudo ./autorun.sh
Check old driver and unload it.
rmmod r8169
Build the module and install
In file included from /tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:91:0:
/tmp/r8168-ring-lib-8.052.01/src/r8168.h:65:20: error: redefinition of ‘ether_addr_copy’
static inline void ether_addr_copy(u8 *dst, const u8 *src)
^
In file included from /tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:47:0:
include/linux/etherdevice.h:246:20: note: previous definition of ‘ether_addr_copy’ was here
static inline void ether_addr_copy(u8 *dst, const u8 *src)
^
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:28216:9: error: unknown field ‘ndo_change_mtu’ specified in initializer
.ndo_change_mtu = rtl8168_change_mtu,
^
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:28216:9: warning: missing braces around initializer [-Wmissing-braces]
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:28216:9: warning: (near initialization for ‘rtl8168_netdev_ops.’) [-Wmissing-braces]
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:28216:9: warning: initialization from incompatible pointer type [enabled by default]
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:28216:9: warning: (near initialization for ‘rtl8168_netdev_ops..ndo_get_stats64’) [enabled by default]
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c: In function ‘rtl8168_rx_interrupt’:
/tmp/r8168-ring-lib-8.052.01/src/r8168_n.c:31506:20: error: ‘struct net_device’ has no member named ‘last_rx’
dev->last_rx = jiffies;
^
make[3]: *** [/tmp/r8168-ring-lib-8.052.01/src/r8168_n.o] Error 1
make[2]: *** [module/tmp/r8168-ring-lib-8.052.01/src] Error 2
make[1]: *** [modules] Error 2
make: *** [modules] Error 2
I spend several hours trying to fix it, but a simple reboot did the job and made my NIC’s visible again.
[root@system ~]# lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
04:02.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
This is my onboard NIC (LAN - Green - Up):
[root@system ~]# lspci -s 00:19.0 -v
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
Subsystem: Dell Device 05a4
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7300000 (32-bit, non-prefetchable) [size=128K]
Memory at f7339000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f040 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
This is my old PCI NIC (WAN - Red - Up):
[root@system ~]# lspci -s 04:02.0 -v
04:02.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)
Subsystem: D-Link System Inc DGE-528T PCI Gigabit Ethernet Adapter
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
I/O ports at d000 [size=256]
Memory at f7220000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at f7200000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: r8169
Kernel modules: r8169
This is my new PCI-Express NIC (Unassigned - Down):
[root@system ~]# lspci -s 05:00.0 -v
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
Flags: bus master, fast devsel, latency 0, IRQ 16
I/O ports at c000 [size=256]
Memory at f7100000 (64-bit, non-prefetchable) [size=4K]
Memory at f2100000 (64-bit, prefetchable) [size=16K]
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: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Kernel driver in use: r8169
Kernel modules: r8169
As soon as I assigned the PCIe NIC my Internet connection broke, but because I had been unable to compile the correct driver for it, I could not use it.
I didn’t see your last post until a few moments ago, because I have been busy all day.
So what am I supposed to do now without breaking my Internet … ?!?
Or should I simply release the PCI NIC before configuring the PCIe NIC … ?!?
And how do I get the latest compatible driver for it … ?!?
Please assist.
Hi @misterjohn
I can not afford a NIC which costs more than 500 €!!!
None of my clients would accept this price!
Your Realtek would have cost me way too much!
(Yes, I charge more than 100€ / hour).
But taking something in operation is part of the Total Costs of Ownership (TCO) for me, I have to calculate this in, I am a professional…
PS: just see the lengh of this post, and the amount of posts in it…
My 2 cents
Andy
Hi @Andy_Wismer
Sure … when you charge over a € 100,- an hour you can afford an Intel NIC.
I still have the option to return it, but before I do that I would like a solution for this problem.
I already found a NIC that is supported by CentOS, but that’s also a Realtek NIC.
I currently have more time than money so if anyone has a solution, I could at least try it.
For me it’s a hobby so I don’t calculate like that, but I can understand where your coming from.
Please advice
Most generic Realtic NICs will work without issues, the standard driver will work. Newer chips are the issue…
At home, I use both Intel & Realtek. Some servers have Broadcom. My clients have expensive HPE servers, there it makes sense to get decent NICs (Mostly 2.5 or 10 GBE nowadays)…
Even if this is the case, it’s more than a bit extensive if it takes so long to solve…
Most of us have - at some time in life - been in a similiar situation. No biggie…
Don’t forget: it must be supported by Centos7 - not eg Centos8!
My 2 cents
Andy
Because it seems to be impossible to normally use a Realtek NIC with NS, can someone please inform me about affordable PCI-Express (up to x16) Gb Intel NIC’s I could use, because the cheapest I could find on one site is € 67,- which is too expensive.
On Amazon they sell this for under € 12,- … which makes no sense to me
I don’t want to spend time compiling a driver, because I don’t trust that process to work without errors.
All I am interested in is an affordable and stable NIC that I can yum install and that’s compatible with NS7, -8 & -9.
Please assist
Red Hat Hardware Compatibility List does no longer list Red Hat 7 (so EL7 support unknown):
According to some AI (not to be trusted 100%) some commonly used network cards that are generally known to be compatible with RHEL 7 are:
Intel Ethernet Cards:
- Intel Ethernet Server Adapter I350-T4
- Driver: Generally well-supported with built-in drivers; widely used in enterprise environments.
- Intel Ethernet Converged Network Adapter X520-DA2
- Driver: Supported with built-in drivers; suitable for high-performance applications.
- Intel Ethernet I210-T1
- Driver: Typically has good support; check for the latest firmware.
Broadcom Network Cards:
- Broadcom NetXtreme II 5709
- Driver: May require additional drivers; check for compatibility.
- Broadcom NetXtreme BCM5720
- Driver: Generally supported, but some users report needing proprietary drivers.
Mellanox Network Cards:
- Mellanox ConnectX-3
- Driver: Supported, but may require additional configuration for optimal performance.
- Mellanox ConnectX-4
- Driver: Generally well-supported; check for the latest drivers.
QLogic Network Cards:
- QLogic FastLinQ QL41162
- Driver: Supported, but verify driver availability for specific use cases.
- QLogic QL45262
- Driver: Generally compatible; check for any known issues.
For NS8, NS9… there shall be no much problem, as the underlying OS (debian, rocky linux et all) usually ship with a more recent kernel with most drivers built-in or it is easier to find supported drivers. Your card might perfectly work out of the box with them.
The problem is with the old way of LTS/EL distributions (like Centos7 and thus NS7, ClearOS…) with reliable/well-tested but old kernels and software, where mostly only security patches were being ported (additional support through third-party repos like ElRepo, but as EL7 and derivates reached EOL more difficulties arose).
As an example of the problems we have been referring too over the previous posts, here’s an excerpt from hetzner:
The Linux r8169 driver for the Realtek network chips does not always work correctly up to kernel version 4.16. There can be timeouts and/or frequent link up/link down state changes, bandwidth problems and even system crashes may occur.
One solution is to use the official Realtek r8168 driver (instead of r8169). It can be installed from external repositories or compiled by yourself. As an alternative, you can upgrade the kernel to version 4.17+.
Easy method for current network card, if default kernel driver is not working properly, you can install kmod-r8168 (assuming this one is the correct kmod version for your card) from any of the archived mirrors (@pike kind of pointed it out as an option):
yum install https://mirrors.coreix.net/elrepo/archive/elrepo/el7/x86_64/RPMS/kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64.rpm
reboot
There seems to be no problem with dependencies.
I successfully installed my new PCI-Express NIC with the r8168 driver.
I noticed that my old PCI NIC with r8169 was disabled after a reboot, so I will remove this NIC at a later time.
Now I can start testing to see if these interruptions are a thing of the past.
PS.
The test was short, because I still lost my Internet and LAN connection briefly.
Enough to stop a live stream and to kill the connection with my NS7 web interface.
It’s unworkable … I am going back to my old PCI NIC by uninstalling the r8168 driver.
[root@system ~]# yum install https://mirrors.coreix.net/elrepo/archive/elrepo/el7/x86_64/RPMS/kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64.rpm
Loaded plugins: changelog, fastestmirror, langpacks, nethserver_events
kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64.rpm | 93 kB 00:00
Examining /var/tmp/yum-root-rWCgvI/kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64.rpm: kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64
Marking /var/tmp/yum-root-rWCgvI/kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64.rpm to be installed
Resolving Dependencies
→ Running transaction check
—> Package kmod-r8168.x86_64 0:8.053.00-1.el7_9.elrepo will be installed
→ Finished Dependency Resolution
ce-base/7/x86_64/signature | 811 B 00:00
ce-base/7/x86_64/signature | 3.6 kB 00:00 !!!
ce-extras/7/x86_64/signature | 819 B 00:00
ce-extras/7/x86_64/signature | 2.9 kB 00:00 !!!
ce-sclo-rh/7/x86_64 | 3.0 kB 00:00
ce-sclo-sclo/7/x86_64 | 3.0 kB 00:00
ce-updates/7/x86_64/signature | 819 B 00:00
ce-updates/7/x86_64/signature | 2.9 kB 00:00 !!!
elrepo/x86_64 | 3.0 kB 00:00
epel/x86_64/metalink | 5.1 kB 00:00
nethforge/7/x86_64/signature | 836 B 00:00
nethforge/7/x86_64/signature | 3.6 kB 00:00 !!!
nethserver-base/7/x86_64/signature | 836 B 00:00
nethserver-base/7/x86_64/signature | 2.9 kB 00:00 !!!
nethserver-updates/7/x86_64/signature | 836 B 00:00
nethserver-updates/7/x86_64/signature | 3.6 kB 00:00 !!!
rpmfusion-free-updates/x86_64 | 3.7 kB 00:00
virtualbox/7/x86_64 | 2.9 kB 00:00Dependencies Resolved
================================================================================
Package Arch Version Repository SizeInstalling:
kmod-r8168 x86_64 8.053.00-1.el7_9.elrepo
/kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64 310 kTransaction Summary
Install 1 Package
Total size: 310 k
Installed size: 310 k
Is this ok [y/d/N]: y
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Installing : kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64 1/1
Working. This may take some time …
Done.
Verifying : kmod-r8168-8.053.00-1.el7_9.elrepo.x86_64 1/1Installed:
kmod-r8168.x86_64 0:8.053.00-1.el7_9.elrepoComplete!
If I uninstall r8168, r8169 is no longer on my system.
How can I restore my previous driver, because a yum install won’t work anymore … ?!?
I quickly installed r8168, so I won’t lose my Internet connection completely.
Please advice
if uninstall and reboot of kmod-… doesnt do it it is possible that the other driver is blacklisted by the module
search for blacklist or unblacklist linux driver