|
|
（为了高效，请按如下格式提问）
硬件主板型号：
固件名称/系统版本：
自编的或固件下载地址：
Log日志: (可以导出，用TXT附件上传)
问题描述及复现步骤:（为了高效，请按如下格式提问）
硬件主板型号：YY3588 SOM CV2
固件名称/系统版本：ubuntu 22.04.5
自编的或固件下载地址：https://pan.baidu.com/s/1aiCw6nv ... =1234#list/path=%2F
Log日志: (可以导出，用TXT附件上传)
这个固件全部升级后两个网卡都有问题，一个网卡找不到了，另一个网卡名称由eth1变成了enP3p49s0 ;可以获取IP，但是无法上网。enP3p49s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.117 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 2409:8a1e:9963:a830:5759:5aff:db2a:b34b prefixlen 64 scopeid 0x0<global>
inet6 fe80::42b1:9c13:745d:8041 prefixlen 64 scopeid 0x20<link>
inet6 2409:8a1e:9963:a830:2d1a:e055:cd0a:494 prefixlen 64 scopeid 0x0<global>
ether 92:45:09:b9:7c:9a txqueuelen 1000 (Ethernet)
RX packets 3788 bytes 349166 (349.1 KB)
RX errors 0 dropped 30 overruns 0 frame 0
TX packets 334 bytes 66032 (66.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enxf8e43b3be1bb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether f8:e4:3b:3b:e1:bb txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.3.155 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 2409:8a1e:9963:a830:8c38:1ff:fece:bf7f prefixlen 64 scopeid 0x0<global>
inet6 fe80::8c38:1ff:fece:bf7f prefixlen 64 scopeid 0x20<link>
ether 8e:38:01:ce:bf:7f txqueuelen 1000 (Ethernet)
RX packets 15289 bytes 1714174 (1.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 684 bytes 78977 (78.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 76
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 313 bytes 59143 (59.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 313 bytes 59143 (59.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@YY3588:/#实际上eth0是没连接的，网卡在界面上也找不到，不知IP是从哪儿来的；enP3p49s0可以获取Ip，但是无法连接，
root@YY3588:/# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.3.155 icmp_seq=1 Destination Host Unreachable
From 192.168.3.155 icmp_seq=2 Destination Host Unreachable
From 192.168.3.155 icmp_seq=3 Destination Host Unreachable
From 192.168.3.155 icmp_seq=4 Destination Host Unreachable
From 192.168.3.155 icmp_seq=5 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
8 packets transmitted, 0 received, +5 errors, 100% packet loss, time 7127ms
pipe 3
root@YY3588:/# reverse socket connection using:
tcp:<port> (<remote> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
reverse --remove REMOTE remove specific reverse socket connection
reverse --remove-all remove all reverse socket connections from device
mdns check check if mdns discovery is available
mdns services list all discovered services
scripting:
wait-for[-TRANSPORT]-STATE...
wait for device to be in a given state
STATE: device, recovery, rescue, sideload, bootloader, or disconnect
TRANSPORT: usb, local, or any [default=any]
get-state print offline | bootloader | device
get-serialno print <serial-number>
get-devpath print <device-path>
remount [-R]
remount partitions read-write. if a reboot is required, -R will
will automatically reboot the device.
reboot [bootloader|recovery|sideload|sideload-auto-reboot]
reboot the device; defaults to booting system image but
supports bootloader and recovery too. sideload reboots
into recovery and automatically starts sideload mode,
sideload-auto-reboot is the same but reboots after sideloading.
sideload OTAPACKAGE sideload the given full OTA package
root restart adbd with root permissions
unroot restart adbd without root permissions
usb restart adbd listening on USB
tcpip PORT restart adbd listening on TCP on PORT
internal debugging:
start-server ensure that there is a server running
kill-server kill the server if it is running
reconnect kick connection from host side to force reconnect
reconnect device kick connection from device side to force reconnect
reconnect offline reset offline/unauthorized devices to force reconnect
usb:
attach attach a detached USB device
detach detach from a USB device to allow use by other processes
environment variables:
$ADB_TRACE
comma-separated list of debug info to log:
all,adb,sockets,packets,rwx,usb,sync,sysdeps,transport,jdwp
$ADB_VENDOR_KEYS colon-separated list of keys (files or directories)
$ANDROID_SERIAL serial number to connect to (see -s)
$ANDROID_LOG_TAGS tags to be used by logcat (see logcat --help)
$ADB_LOCAL_TRANSPORT_MAX_PORT max emulator scan port (default 5585, 16 emus)
$ADB_MDNS_AUTO_CONNECT comma-separated list of mdns services to allow auto-connect (default adb-tls-connect)
PS E:\BaiduNetdiskDownload\RKDevTool_Release_v3.32\RKDevTool_v3.32_for_window\bin> adb shell
adb server version (40) doesn't match this client (41); killing...
* daemon started successfully
root@YY3588:/# ifconfig
enP3p49s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.117 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 2409:8a1e:9963:a830:5759:5aff:db2a:b34b prefixlen 64 scopeid 0x0<global>
inet6 fe80::42b1:9c13:745d:8041 prefixlen 64 scopeid 0x20<link>
inet6 2409:8a1e:9963:a830:2d1a:e055:cd0a:494 prefixlen 64 scopeid 0x0<global>
ether 92:45:09:b9:7c:9a txqueuelen 1000 (Ethernet)
RX packets 3788 bytes 349166 (349.1 KB)
RX errors 0 dropped 30 overruns 0 frame 0
TX packets 334 bytes 66032 (66.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enxf8e43b3be1bb: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether f8:e4:3b:3b:e1:bb txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.3.155 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 2409:8a1e:9963:a830:8c38:1ff:fece:bf7f prefixlen 64 scopeid 0x0<global>
inet6 fe80::8c38:1ff:fece:bf7f prefixlen 64 scopeid 0x20<link>
ether 8e:38:01:ce:bf:7f txqueuelen 1000 (Ethernet)
RX packets 15289 bytes 1714174 (1.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 684 bytes 78977 (78.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 76
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 313 bytes 59143 (59.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 313 bytes 59143 (59.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=111 time=35.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=111 time=34.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=111 time=35.2 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 34.746/35.016/35.198/0.195 ms
root@YY3588:/# ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
From 192.168.3.155 icmp_seq=1 Destination Host Unreachable
ping: sendmsg: No route to host
From 192.168.3.155 icmp_seq=2 Destination Host Unreachable
^C
--- 192.168.3.1 ping statistics ---
11 packets transmitted, 0 received, +9 errors, 100% packet loss, time 10246ms
pipe 3
root@YY3588:/# ip route show
default via 192.168.3.1 dev enP3p49s0 proto dhcp metric 100
169.254.0.0/16 dev eth0 scope link metric 1000 linkdown
192.168.3.0/24 dev eth0 proto kernel scope link src 192.168.3.155 linkdown
192.168.3.0/24 dev enP3p49s0 proto kernel scope link src 192.168.3.117 metric 100
root@YY3588:/# sudo ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
From 192.168.3.155 icmp_seq=1 Destination Host Unreachable
From 192.168.3.155 icmp_seq=2 Destination Host Unreachable
|
|
发表于 
