There is, yes but that seems confusing as well.
Thanks for the response. Trying to figure out how to revert to a previous kernel.
Apologies to all for posting all over the place. I was a bit frayed yesterday and had multiple open windows and laptop with same.
So this is the readme file. Hope I'm not breaking any rules by submitting it like this.
This is the Linux device driver released for Realtek 2.5 Gigabit Ethernet controllers with PCI-Express interface.
- Kernel source tree (supported Linux kernel 2.6.x and 2.4.x)
- For linux kernel 2.4.x, this driver supports 2.4.20 and latter.
- Compiler/binutils for kernel compilation
Change to the directory:
# cd r8125-9.aaa.bb
If you are running the target kernel, then you should be able to do :
# ./autorun.sh (as root or with sudo)
You can check whether the driver is loaded by using following commands.
# lsmod | grep r8125
# ifconfig -a
If there is a device name, ethX, shown on the monitor, the linux
driver is loaded. Then, you can use the following command to activate
the ethX.
# ifconfig ethX up
,where X=0,1,2,...
# ifconfig ethX "the IP address of your machine"
b. Set the IP address of DNS.
Insert the following configuration in /etc/resolv.conf.
nameserver "the IP address of DNS"
c. Set the IP address of gateway.
# route add default gw "the IP address of gateway"
2. Set by doing configurations in /etc/sysconfig/network-scripts
/ifcfg-ethX for Redhat and Fedora, or /etc/sysconfig/network
/ifcfg-ethX for SuSE. There are two examples to set network
configurations.
a. Fixed IP address:
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=ethernet
NETMASK=255.255.255.0
IPADDR=192.168.1.1
GATEWAY=192.168.1.254
BROADCAST=192.168.1.255
b. DHCP:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
# ifconfig ethX hw ether YY:YY:YY:YY:YY:YY
,where X is the device number assigned by Linux kernel, and
YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.
2. Use ip:
# ip link set ethX address YY:YY:YY:YY:YY:YY
,where X is the device number assigned by Linux kernel, and
YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.
1. Force the link status when insert the driver.
If the user is in the path ~/r8125, the link status can be forced
to one of the 5 modes as following command.
# insmod ./src/r8125.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = 0 for half-duplex
= 1 for full-duplex
NWAY_OPTION = 0 for auto-negotiation off (true force)
= 1 for auto-negotiation on (nway force)
For example:
# insmod ./src/r8125.ko speed=100 duplex=0 autoneg=1
will force PHY to operate in 100Mpbs Half-duplex(nway force).
2. Force the link status by using ethtool.
a. Insert the driver first.
b. Make sure that ethtool exists in /sbin.
c. Force the link status as the following command.
2.5G before kernel v4.10
# ethtool -s eth0 autoneg on advertise 0x802f
2.5G for kernel v4.10 and later
# ethtool -s eth0 autoneg on advertise 0x80000000002f
# ethtool -s eth0 autoneg on advertise 0x002f (1G)
# ethtool -s eth0 autoneg on advertise 0x000f (100M full)
# ethtool -s eth0 autoneg on advertise 0x0003 (10M full)
# ifconfig ethX mtu MTU
, where X=0,1,2,..., and MTU is configured by user.
RTL8125 supports Jumbo Frame size up to 9 kBytes.
Get EEE device status
# ethtool --show-eee enp1s0
Set EEE device status
# ethtool --set-eee enp1s0 eee on tx-lpi on tx-timer 1546 advertise 0x0008 (100M full)
# ethtool --set-eee enp1s0 eee on tx-lpi on tx-timer 1546 advertise 0x0020 (1G)
# ethtool --set-eee enp1s0 eee on tx-lpi on tx-timer 1546 advertise 0x8000 (2.5G)
Very confusing I think. I won't bother you folks any more about this. All this was in the middle of building a new desktop and keeping my 'work at home' better half from accidentally bumping her offline. Tough to do sometimes.
Understood and thanks. Pro version produces the same result. Very frustrating.
You should not need to jump through the realtek website, given that these have been added to the Linux Kernel:
After downloading the firmware, move them to /lib/firmware/rtl_nic/ using sudo elevated permissions.
Then run in terminal:
sudo update-initramfs -u
Thanks for the help! I guess I download all of the 8125's I see?
You can. I am not sure which you are missing, either so grabbing them all may be a safer than sorry option.
So I can get it to work with Win11 but not Zorin, which leads me to believe the issue is inherent to Zorin. I've also read that Mint has the same issue. I'm committed to Zorin at this point as I bought the pro version and I'm going to use it (soon as I figure out how to help the Linux problem. Different opinions on folks with the same problem and also different fixes. Damn frustrating. That's all I know. Thnx for the responses just the same. I appreciate you taking the time. Be back, hopefully.
I'm wondering if there are ANY working Linux distros that don't exhibit this issue?
I'd be happy to run with one till the bug(s) get worked out on Zorin.
Did you perform this action?
I don't know how to move to this file. I can't locate it. Like I said earlier, I'm a Linux noob. Been wrestling with trying to figure out how to do so, if that counts for anything. Sorry for the whining.
How do I find that?
When you downloaded them, they should have landed in your Downloads folder.
To move them, you must elevate to root using terminal:
sudo -i
Then you can launch your file manager:
nautilus
and navigate to "Other locations" > Computer > double click on the folder named lib, then firmware and lastly rtl_nic. If rtl_nic does not exist, right click, select 'create new folder' and click that - then name it rtl_nic. Once made, open it with double click and drag and drop the downloaded firmware files into the rtl_nic folder.
Thank you once again. I'm pooped for tonight. I'll look forward to trying this tomorrow. I'd try it tonight but I've had too many brain squeezes for today. If it works, I'll be sure and let you and others know. Much appreciated!
1 Like
The newer the hardware, the lower the chances that drivers exist for Linux. This boils down to the fact that manufacturers don't want to spend time and money supporting an operating system with a low desktop market share.
In this case, the X870 seems to be fairly recent as it was released about a year ago.
I've missed quite a few replies here but in case it hasn't been suggested, you can try to upgrade the Linux kernel versiopn that comes with Zorin OS. That might help with hardware compatibility but you should test it in case it introduces other issues.
There are some Linux distributions that are constantly updated, unlike Zorin OS and other Debian derivatives which focus more on stability, and that might work best for you in this case.
I'd recommend checking out Fedora, Endeavour OS or OpenSUSE Tumbleweed. There are others but these are the ones that follow a "rolling release model" i.e., faster release schedule, that I've personally tested and liked.
I appreciate the input. Thank you.
I'm still dead on ethernet. Thank you for follow ups. I hate to say it but man, I might have to go back to click hell with Microsuck.