The newest update to the r8168 driver prevents me from using zen kernel as i can’t use my wired connection, it simply wont connect to the internet, i had to revert to using lts kernel or main to use the r8168 driver which allows my wired connection to connect again, what are the changes to the driver or is it a known bug?
Edit
Does this mean the new zen kernel do not have the required patch to use this driver?
Just tested on both main & lts kernel works, seems like the new zen kernel is missing the required kernel patches, i guess its not a driver issue, will have to wait for upstream to fix. Added additional screenshots below to compare with the zen one at the first post.
Main kernel
Lts kernel
Edit - Anyone that can help verify this would be awesome.
Thank you for sharing your findings with us, this is often the case with the modified kernels, I think the best and direct way is to notify the Linux-zen team of this issue. It might be a case of them overlooking this bug.
Be aware: If r8168 is installed it will create a blacklist file and blacklist r8169 so that the r8169 kernel module will never run automatically. But I believe you could test with a simple modprobe r8169. And if that works you should find the blacklisting and remove it.
I guess this will be changed in all kernels in the future, can there be a distro side intervention for people who are already using 8168 to load the new driver when updating to the new kernels?
if r8169 is working for your hardware you should deinstall r8168.
What do you mean with that? What will change? Most distros install the extra r8168 module because it supports more of the newer hardware. This will not change in the future,
Since you’ve got it working without any workaround in the main kernel, I still think it is a small overlooked bug in the zen kernel, both those kernels use the same version.
Thank you there is a blacklist file on modprobe folder, its why i cant get it working when i uninstalled it earlier when @Kresimir suggested it, after removing 8168 + blacklist file, now all is working.
I guess its not a bug with zen or eos, just something users have to keep watch on.