Hello,
There is some evolution.
I still use the r8169 module in the 5.19.0 kernel, r8168 and dkms are not
present anymore. Neither r8169 nor r8168 are blacklisted.
lsmod shows that the r8169 module is loaded in memory.
dmesg | grep r81 shows that the eth0 link is up at startup of the laptop.
I
Hello,
I came back to the r8169 module with the 5.19.0-40-generic #41~22.04.1-Ubuntu
module.
I removed the r8168 module and dkms.
The bug is still here, but now the ethernet link eth0 works only if i
reboot the remote device connected to the ethernet link.
Why is this regression? The 5.10.0
Hello,
I solved this problem by switching to the r8168 module, instead of the buggy
r8169 module.
Now, the ethernet tethering works fine!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Some additional information: when installing to a bare new installation
of 16.04.3 LTS upgraded to the new kernel (4.13.xxx), installation of
NVIDIA's CUDA 9 packages fails due to a module build failure, similar to
the description of bug 1742160 https://bugs.launchpad.net/ubuntu/+source
I confirm this with 4.13.0-26. Does not occur after reversion to
4.10.0-42 or earlier kernels.
I have not tested the new 390 series driver. 387.26 + 4.10.0-42
combination works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
i have the same problem with my Acer Aspire VN7-792G.
Iv installed ubuntu 14.04 with the upstream kernel 4.2
If you need any more information from my side as well please let me
know.
what I have already tried can be found here:
http://ubuntuforums.org/showthread.php?t=2304154=13398554
--
You
6 matches
Mail list logo
