![无法在华硕 TUF FX504 上的 Ubuntu 19.04 中使用以太网](https://linux22.com/image/1014053/%E6%97%A0%E6%B3%95%E5%9C%A8%E5%8D%8E%E7%A1%95%20TUF%20FX504%20%E4%B8%8A%E7%9A%84%20Ubuntu%2019.04%20%E4%B8%AD%E4%BD%BF%E7%94%A8%E4%BB%A5%E5%A4%AA%E7%BD%91.png)
首先,我不是一注意到这个问题就问的。但问题是我 3 个月前购买了这款华硕 tuf fx504,它与正版 Windows 配合使用时一切正常。第二天我安装了 ubuntu 19.04(开发分支)并注意到了这个问题。我知道这个硬件是新的,即使触摸板也存在问题,而且传感器也无法检测到 acpi 风扇。所以,我等待更新的内核以获得更好的驱动程序支持。
我在主线内核的 driver>net>ethernet 下看到了 r8169 相关文件,所以我全新安装了 ubuntu 19.04 LTS 并将内核更新为5.2.0-050200rc7。
有什么改变?
- 以前在设置/网络中没有以太网(有线)选项,但更新内核后我得到了该选项。
- 然后我得到了如下图所示的连接状态 ->通知面板下的连接状态
- 有时连接失败后会显示此警告框 ->激活网络连接失败陷入无限循环。
uname 输出
$ uname -r
5.2.0-050200rc7-generic
ifconfig 输出
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet6 fe80::898a:1463:6579:97e0 prefixlen 64 scopeid 0x20<link>
ether 04:92:26:6e:ab:1b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1371 bytes 178614 (178.6 KB)
TX errors 606 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1968 bytes 168097 (168.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1968 bytes 168097 (168.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.43.80 netmask 255.255.255.0 broadcast 192.168.43.255
inet6 fe80::3488:9802:814c:3f07 prefixlen 64 scopeid 0x20<link>
inet6 2409:4062:2296:2aa8:9659:df17:a617:ab55 prefixlen 64 scopeid 0x0<global>
inet6 2409:4062:2296:2aa8:f43b:ea6e:838f:13c3 prefixlen 64 scopeid 0x0<global>
ether 18:1d:ea:36:2f:7c txqueuelen 1000 (Ethernet)
RX packets 23196 bytes 19937226 (19.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15628 bytes 4134485 (4.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
当我搜索现有问题时,我发现所有以太网接口都命名为,eth0
但正如你所看到的enp3s0
,为什么?后来我发现它在 dmesg 中从 eth0 重命名为 enp3s0。
[ 1.638046] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 10.305777] r8169 0000:03:00.0 enp3s0: Link is Down
[ 11.773703] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 11.773720] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 11.873260] r8169 0000:03:00.0 enp3s0: Link is Down
[ 13.458759] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 13.534198] r8169 0000:03:00.0 enp3s0: Link is Down
[ 15.151133] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 15.226573] r8169 0000:03:00.0 enp3s0: Link is Down
[ 16.814176] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 16.887538] r8169 0000:03:00.0 enp3s0: Link is Down
[ 18.475925] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 18.548917] r8169 0000:03:00.0 enp3s0: Link is Down
[ 20.181428] r8169 0000:03:00.0 enp3s0: Link is Up - 10Mbps/Full - flow control rx/tx
[ 20.264971] r8169 0000:03:00.0 enp3s0: Link is Down
在 dmesg 日志中您可以看到,有时它会记录链接已准备就绪,然后它会一直处于关闭-打开-关闭的状态并永远持续下去。
我原本计划安装内核 5.2,因为在提出这个问题的时候,它在 r8169 主源中得到了一些更新,但是由于构建失败https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/,无法安装。
如果有人描述该问题的原因/解决方法/修复方法,将会非常有帮助。