This seems to happen in many different drivers but it happened more often in newer versions such as 530 vs 525. Then nvidia-modeset goes to 100% There are many reports of this appearing since driver 4.70 and I can confirm I've seen this in various machines. https://forums.de........

So say you happen to have 2 NICs of the exact same chipset, they will generally show up as the same name, with possibly a different revision in lspci. Normally this is not an issue if you have a server with 4 NICs, generally the eth0 to eth3 appears from left to the right (or right to left on some vendors) so it doesn't take much figuring out. Generally if you have different chipsets for different NICs, it should be easy to know which one is eth0 or the first NIC in the OS.........

The easiest way for the 8821AU Realtek Wifi chipset / TP-Link T2U Plus: Bus 002 Device 003: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU] First install your kernel headers/source/other required tools: sudo apt install linux-headers-`uname -r` make gcc bc Clone this github repo with the driver: git clone https://github.com/morrownr/8821au-20210708 Run the compile/ins........

Interestingly enough Windows 2000 works fine on QEMU 64-bit but you have to specify Pentium as your CPU otherwise it doesn't complete the install (it will not pass the detecting/setting up devices phase). -vga cirrus is wise because it is supported by Windows 2000 and allows higher resolutions and 24-bit color. -cpu Pentium emulates an old computer and is necessary for install to complete -device rtl8139 is important as this oldschool Realtek 8139 NIC is supported by W........

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) For whatever reason it seems the r8169 driver that ships and has shipped with most Linux distros for years is still flawed and does not work properly on these cards, causing 100mbit connectivity when it should be 1gbit and even worse, causing random network dropouts. The r8169 driver in Linux kernels is simply not meant to be used on th........

That is pinging to the gateway IP on the same switch, the same IP is pingable externally without any problems which makes me think the switch is fine. 64 bytes from 55.55.55.55: icmp_seq=4 ttl=255 time=1.07 ms 64 bytes from 55.55.55.55: icmp_seq=1 ttl=255 time=3536 ms 64 bytes from 55.55.55.55: icmp_seq=2 ttl=255 time=2536 ms 64 bytes from 55.55.55.55: icmp_seq=3 ttl=255 time=1536 ms 64 bytes from 55.55.55.55: icmp_seq=8 ttl=255 time=1.20 ms 64 by........

This is obviously a bug in the r8169 kernel module and it seems to affect a lot of people. I upgraded to the latest kernel and hope this won't happen anymore, as it is a very serious error. This is especially serious for those who are running servers with this chipset, who can afford for the NIC to randomly go off-line for no apparent reason? [655548.189113] type=1505 audit(1277067560.902:5): operation="profile_load" name="/usr/bin/freshclam&q........

Basically the two main types of distros are Debian and RHEL/Centos based. I'm just going to give a quick overview of how the configuration of IP interfaces works in Debian/Centos based distros. *Just one thing to remember, when setting IPs statically you have to manually specify a DNS server in /etc/resolv.conf (since DHCP is what normally does it automatically) Debian/Ubuntu/Kubuntu/MEPIS The IP (DHCP &........

Here are the results, it is Sempron 3000+ AMD Mobile, 500Gig HDD, 512MB RAM with shared ATI Radeon graphics. # # # # # # # ##### ###### # # #### # # # # ## # # # #&nb........

This is the Intel Atom 330 motherboard with integrated Realtek Gigabit NIC (Intel Desktop Board D945GCLF2 Motherboard W/ Atom 330 1.6 GHz Dual Core Processor - Mini-ITX) I cannot achieve more than 15 MB/s, even doing a local transfer through eth0 to it's own IP. 100% 95MB 15.9MB/s 00:06 So this is not a cabling, switch or hardware issue, it seems like a driver or chipset limitation problem. Here is my........