AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / user-156821

retrodans's questions

Martin Hope
retrodans
Asked: 2025-02-15 23:23:00 +0800 CST

外部 DVD 驱动器已安装,但插入光盘后会失效

  • 5

我有一个外部驱动器,并已检查 Ubuntu 在使用 lsusb 插入时是否能识别它

MediaTek Inc. 三星 SE-S084 Super WriteMaster Slim 外置 DVD 刻录机

我还可以可靠地看到“磁盘”应用程序中列出的 CD/DVD 驱动器。

但遗憾的是,只要我把光盘放入其中(无论是 CD 还是 DVD),它就会:

  1. 开始像预期的那样发出呼呼声
  2. 然后它就会停止旋转
  3. 该驱动器将从“磁盘”应用程序中消失
  4. 然后它将重新出现在“磁盘”中
  5. 循环回到 1 并重复

我确信这在过去一两个月内是有效的,所以想知道升级或权限更改是否会影响这一点。

插入光盘后运行 dmesg 会输出如下内容:

[ +20.097292] usb 3-3: USB disconnect, device number 71
[  +0.159147] [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:20:ff:5b:7d:81:00:11:32:df:df:e9:08:00 SRC=192.168.1.54 DST=192.168.1.48 LEN=1365 TOS=0x00 PREC=0x00 TTL=64 ID=48489 DF PROTO=UDP SPT=3702 DPT=55889 LEN=1345 
[  +3.494338] usb 3-3: new high-speed USB device number 72 using xhci_hcd
[  +0.130560] usb 3-3: New USB device found, idVendor=0e8d, idProduct=1836, bcdDevice= 0.00
[  +0.000005] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000001] usb 3-3: Product: SES084D
[  +0.000001] usb 3-3: Manufacturer: TSST Inc    
[  +0.000000] usb 3-3: SerialNumber: R96X911 
[  +0.004014] usb-storage 3-3:1.0: USB Mass Storage device detected
[  +0.000209] scsi host0: usb-storage 3-3:1.0
[  +1.034492] scsi 0:0:0:0: CD-ROM            TSSTcorp CDDVDW SE-S084F  TS00 PQ: 0 ANSI: 0
[  +0.011374] sr 0:0:0:0: Power-on or device reset occurred
[  +0.018203] sr 0:0:0:0: [sr0] scsi3-mmc drive: 8x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[  +0.011453] sr 0:0:0:0: Attached scsi CD-ROM sr0
[  +0.000084] sr 0:0:0:0: Attached scsi generic sg0 type 5
[  +5.048998] usb 3-3: USB disconnect, device number 72

谢谢你提供的任何建议,丹

20.04
  • 1 个回答
  • 34 Views
Martin Hope
retrodans
Asked: 2023-02-27 22:12:21 +0800 CST

由于 nvidia 驱动程序,更新 ubuntu 22.04 中断了更新

  • 5

大约一个月前,我将 Ubuntu 更新到 22.04,从那时起我就意识到,每当我尝试安装任何类似的东西时,sudo apt update && sudo apt install signal-desktop我都会遇到以下错误:

Setting up nvidia-dkms-470 (470.161.03-0ubuntu0.22.04.1) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Removing old nvidia-470.161.03 DKMS files...
Deleting module nvidia-470.161.03 completely from the DKMS tree.
Loading new nvidia-470.161.03 DKMS files...
Building for 5.15.0-60-generic
Building for architecture x86_64
Building initial module for 5.15.0-60-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-470.0.crash'
Error! Bad return status for module build on kernel: 5.15.0-60-generic (x86_64)
Consult /var/lib/dkms/nvidia/470.161.03/build/make.log for more information.
dpkg: error processing package nvidia-dkms-470 (--configure): 
installed nvidia-dkms-470 package post-installation script subprocess
returned error exit status 10 dpkg: dependency problems prevent
configuration of nvidia-driver-470:  nvidia-driver-470 depends on
nvidia-dkms-470 (<= 470.161.03-1); however:
Package nvidia-dkms-470 is not configured yet.
nvidia-driver-470 depends on nvidia-dkms-470 (>= 470.161.03); however:
Package nvidia-dkms-470 is not configured yet.

dpkg: error processing package nvidia-driver-470 (--configure): 
dependency problems - leaving unconfigured dpkg:
dependency problems prevent configuration of nvidia-driver-460:
nvidia-driver-460 depends on nvidia-driver-470; however:
Package nvidia-driver-470 is not configured yet.

dpkg: error processing package nvidia-driver-460 (--configure): 
dependency problems - leaving unconfigured No apport report written
because the error message indicates it's a follow-up error from a
previous failure.
                                                                                                            No apport report written because the error message indicates it's a
follow-up error from a prev ious failure.
             Processing triggers for initramfs-tools (0.140ubuntu13.1) ... update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic

如果我查看 /var/lib/dkms/nvidia/470.161.03/build/make.log,我可以看到:

DKMS make.log for nvidia-470.161.03 for kernel 5.15.0-60-generic
(x86_64) Mon 27 Feb 14:04:55 GMT 2023 make[1]: Entering directory
'/usr/src/linux-headers-5.15.0-60-generic' test -e
include/generated/autoconf.h -a -e include/config/auto.conf || (        \
echo >&2;                           \
echo >&2 "  ERROR: Kernel configuration is invalid.";       \
echo >&2 "  include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "  Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2;                           \
/bin/false)

ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.
make[1]: *** [Makefile:750: include/config/auto.conf] Error 1 make[1]:
Leaving directory '/usr/src/linux-headers-5.15.0-60-generic' make: ***
[Makefile:80: modules] Error 2

我在网上看过,并尝试过卸载/重新安装步骤,但没有成功。我也看不到“配置”的方法。

如果我尝试运行,make oldconfig && make prepare我得到的是:

make: *** No rule to make target 'oldconfig'. Stop.

任何人都有类似的问题,或者有什么想法可以尝试吗?


uname -r

5.15.0-60-generic

sudo apt 安装 linux-headers-$(uname -r)

Reading package lists...
Done Building dependency tree...
Done Reading
state information...
Done linux-headers-5.15.0-60-generic is already the newest version (5.15.0-60.66). 0 to upgrade, 0 to newly install, 0 to remove and 42 not to upgrade. 3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used. Do
you want to continue? [Y/n] y
Setting up nvidia-dkms-470 (470.161.03-0ubuntu0.22.04.1) ...
update-initramfs: deferring update
(trigger activated)
INFO:Enable nvidia DEBUG:Parsing
/usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad 
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Removing old nvidia-470.161.03 DKMS files...
Deleting module nvidia-470.161.03 completely from the DKMS tree.
Loading new nvidia-470.161.03 DKMS files...
Building for 5.15.0-60-generic
Building for architecture x86_64
Building initial module for 5.15.0-60-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-kernel-source-470.0.crash' Error! Bad return status for module build on kernel: 5.15.0-60-generic (x86_64)
Consult /var/lib/dkms/nvidia/470.161.03/build/make.log for more information.
dpkg: error processing package nvidia-dkms-470 (--configure): 
installed nvidia-dkms-470 package post-installation script subprocess
returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-470:  nvidia-driver-470 depends on nvidia-dkms-470 (<= 470.161.03-1); however:   Package nvidia-dkms-470
is not configured yet.  nvidia-driver-470 depends on nvidia-dkms-470
(>= 470.161.03); however:   Package nvidia-dkms-470 is not configured yet.

dpkg: error processing package nvidia-driver-470 (--configure): 
dependency problems - leaving unconfigured dpkg: dependency problems
prevent configuration of nvidia-driver-460:  nvidia-driver-460 depends
on nvidia-driver-470; however:   Package nvidia-driver-470 is not
configured yet.

dpkg: error processing package nvidia-driver-460 (--configure): 
dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.

No apport report written because the error message indicates it's a follow-up error from a prev ious failure.

Processing triggers for initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic
Errors were encountered while processing:  nvidia-dkms-470 
nvidia-driver-470  nvidia-driver-460
E: Sub-process /usr/bin/dpkg returned an error code (1)
nvidia
  • 1 个回答
  • 77 Views
Martin Hope
retrodans
Asked: 2018-07-24 04:46:10 +0800 CST

大约 10 秒后连接到家庭网络会断开互联网(Ubuntu 16.04)

  • 0

我今天遇到了一个非常奇怪(且令人困惑)的问题,我似乎无法解决。当我连接到本地网络(使用以太网或 wifi)时,网络似乎连接正常,并且网页加载。但是大约 10 秒后,页面似乎无法再加载,并且我看到了 chrome 的“没有互联网连接”错误。

请注意,尽管互联网仍处于连接状态。

我发现了其他提到类似事情的博客,我可以从中收集到一些有用的信息。

  1. ping 8.8.8.8 这实际上不起作用,它只是返回以下内容,然后冻结

    PING 8.8.8.8 (8.8.8.8) 56(84) 字节数据。

  2. 我禁用了以太网/wifi 以查看另一个是否有效,但它没有。

  3. 在运行 wifi 的情况下,我运行了 ifconfig,它返回了预期的块,包括 ip 地址行

    inet 地址:192.168.0.1 广播:192.168.0.255 掩码:255.255.255.0

我不确定下一步该在哪里尝试,我正在考虑升级(就像在 Ubuntu 16.04 上一样),但我认为如果没有互联网连接我就做不到(请注意,尽管我确实有其他可以下载和使用 USB 的计算机)。

任何帮助将不胜感激,因为到目前为止这已经是半天的问题,我真的需要知道如何解决它(希望没有完全格式化我的机器)。

编辑 1

dmesg

[ 4738.843326] wlan0: authenticate with 9c:3d:cf:2d:2a:23
[ 4738.857852] wlan0: send auth to 9c:3d:cf:2d:2a:23 (try 1/3)
[ 4739.194588] wlan0: send auth to 9c:3d:cf:2d:2a:23 (try 2/3)
[ 4739.253551] wlan0: send auth to 9c:3d:cf:2d:2a:23 (try 3/3)
[ 4739.305312] wlan0: authentication with 9c:3d:cf:2d:2a:23 timed out
[ 4747.214155] wlan0: authenticate with 9c:3d:cf:2d:2a:23
[ 4747.228846] wlan0: send auth to 9c:3d:cf:2d:2a:23 (try 1/3)
[ 4747.244260] wlan0: authenticated
[ 4747.249426] wlan0: associate with 9c:3d:cf:2d:2a:23 (try 1/3)
[ 4747.262179] wlan0: RX AssocResp from 9c:3d:cf:2d:2a:23 (capab=0x1411 status=0 aid=4)
[ 4747.262285] wlan0: associated
[ 4803.391017] wlan0: deauthenticating from 9c:3d:cf:2d:2a:23 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 4803.409988] cfg80211: World regulatory domain updated:
[ 4803.409992] cfg80211:  DFS Master region: unset
[ 4803.409994] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 4803.409999] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 4803.410003] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 4803.410006] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 4803.410009] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 4803.410013] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 4803.410016] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 4803.410019] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 4803.410022] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 4806.968013] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4807.009667] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4813.836418] wlan0: authenticate with 9c:3d:cf:2d:2a:23
[ 4813.851747] wlan0: send auth to 9c:3d:cf:2d:2a:23 (try 1/3)
[ 4813.853849] wlan0: authenticated
[ 4813.855503] wlan0: associate with 9c:3d:cf:2d:2a:23 (try 1/3)
[ 4813.859434] wlan0: RX AssocResp from 9c:3d:cf:2d:2a:23 (capab=0x1411 status=0 aid=4)
[ 4813.859594] wlan0: associated
[ 4813.859619] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

journalctl --follow | grep 错误

我首先禁用了wifi,运行了这个命令,然后重新启动它。cli 中没有出现任何内容,网页可以正常工作,但在刷新约 15 秒后,它再次停止工作。

编辑002

添加我进入网络的其他 DNS 域 ,然后选择我连接到的 wifi 网络,并将下面的行添加到“附加 DNS 服务器”。然后重新启动网络管理器再次测试,遗憾的是没有变化。

8.8.8.8, 8.8.4.4

跑步路线

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         XPSbadger.local 0.0.0.0         UG    600    0        0 wlan0
link-local      *               255.255.0.0     U     1000   0        0 br-e83ec14e5fe6
172.17.0.0      *               255.255.0.0     U     0      0        0 docker0
172.18.0.0      *               255.255.0.0     U     0      0        0 br-2af86a86bdb0
172.19.0.0      *               255.255.0.0     U     0      0        0 br-5b58772b6da5
172.20.0.0      *               255.255.0.0     U     0      0        0 br-f76aa0c2dc58
172.21.0.0      *               255.255.0.0     U     0      0        0 br-27966f3ea248
172.22.0.0      *               255.255.0.0     U     0      0        0 br-cbda173ee6bd
172.23.0.0      *               255.255.0.0     U     0      0        0 br-65df59f4d93f
172.24.0.0      *               255.255.0.0     U     0      0        0 br-6d514edfb8e2
172.25.0.0      *               255.255.0.0     U     0      0        0 br-14e3dea71a99
172.26.0.0      *               255.255.0.0     U     0      0        0 br-48746990b42c
172.27.0.0      *               255.255.0.0     U     0      0        0 br-450e7e405a9b
172.28.0.0      *               255.255.0.0     U     0      0        0 br-002104caf6be
172.29.0.0      *               255.255.0.0     U     0      0        0 br-97fdbde621a5
172.30.0.0      *               255.255.0.0     U     0      0        0 br-831de9f3d506
172.31.0.0      *               255.255.0.0     U     0      0        0 br-9f1441b318f1
182.18.18.0     *               255.255.255.0   U     0      0        0 br-86b7b5bb37a1
182.18.19.0     *               255.255.255.0   U     0      0        0 br-f2bc890d9461
182.18.20.0     *               255.255.255.0   U     0      0        0 br-6a9feb1c2cde
192.168.0.0     *               255.255.255.0   U     600    0        0 wlan0
192.168.0.0     *               255.255.240.0   U     0      0        0 br-e83ec14e5fe6
192.168.16.0    *               255.255.240.0   U     0      0        0 br-157d68c1ba49
192.168.32.0    *               255.255.240.0   U     0      0        0 br-20c38da9b3d5
192.168.48.0    *               255.255.240.0   U     0      0        0 br-e36061771a1a
192.168.64.0    *               255.255.240.0   U     0      0        0 br-d4e0712eb056
192.168.80.0    *               255.255.240.0   U     0      0        0 br-515288084e48

编辑003

须藤IP链接

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:1f:af:4c:06:42 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 70:18:8b:2b:ef:3d brd ff:ff:ff:ff:ff:ff
4: br-14e3dea71a99: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e1:a8:cc:a9 brd ff:ff:ff:ff:ff:ff
5: br-27966f3ea248: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e8:fd:54:48 brd ff:ff:ff:ff:ff:ff
6: br-48746990b42c: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:fa:e4:3a:45 brd ff:ff:ff:ff:ff:ff
7: br-65df59f4d93f: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:23:c7:1a:7b brd ff:ff:ff:ff:ff:ff
8: br-6a9feb1c2cde: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:67:e9:46:84 brd ff:ff:ff:ff:ff:ff
9: br-cbda173ee6bd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:24:91:e6:c6 brd ff:ff:ff:ff:ff:ff
10: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:7e:b7:b5:03 brd ff:ff:ff:ff:ff:ff
11: br-002104caf6be: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:99:be:40:87 brd ff:ff:ff:ff:ff:ff
12: br-450e7e405a9b: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:57:a0:ad:97 brd ff:ff:ff:ff:ff:ff
13: br-5b58772b6da5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:3a:8d:61:de brd ff:ff:ff:ff:ff:ff
14: br-f2bc890d9461: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:ce:f8:7d:a1 brd ff:ff:ff:ff:ff:ff
15: br-f76aa0c2dc58: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:bc:b0:c5:e4 brd ff:ff:ff:ff:ff:ff
16: br-157d68c1ba49: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:10:b5:5f:09 brd ff:ff:ff:ff:ff:ff
17: br-2af86a86bdb0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:7e:25:da:fb brd ff:ff:ff:ff:ff:ff
18: br-515288084e48: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:5d:3e:a5:de brd ff:ff:ff:ff:ff:ff
19: br-6d514edfb8e2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:b8:39:16:80 brd ff:ff:ff:ff:ff:ff
20: br-831de9f3d506: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:5c:81:8c:8c brd ff:ff:ff:ff:ff:ff
21: br-9f1441b318f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:b3:7e:4f:d2 brd ff:ff:ff:ff:ff:ff
22: br-e36061771a1a: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e0:47:7f:11 brd ff:ff:ff:ff:ff:ff
23: br-e83ec14e5fe6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:7d:21:a9:00 brd ff:ff:ff:ff:ff:ff
24: br-20c38da9b3d5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:9b:3b:9c:5b brd ff:ff:ff:ff:ff:ff
25: br-97fdbde621a5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:a5:6c:db:87 brd ff:ff:ff:ff:ff:ff
26: br-d4e0712eb056: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e5:02:57:77 brd ff:ff:ff:ff:ff:ff
27: br-86b7b5bb37a1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e2:b1:ee:65 brd ff:ff:ff:ff:ff:ff
29: vetha46a4db@if28: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-cbda173ee6bd state UP mode DEFAULT group default 
    link/ether 0e:a4:64:96:f0:a4 brd ff:ff:ff:ff:ff:ff link-netnsid 2
31: veth8d800d2@if30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-831de9f3d506 state UP mode DEFAULT group default 
    link/ether 2a:f1:a5:39:e7:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0
33: veth38cfe67@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-831de9f3d506 state UP mode DEFAULT group default 
    link/ether 5e:c2:18:b2:4b:02 brd ff:ff:ff:ff:ff:ff link-netnsid 3
35: veth0e87fcd@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-cbda173ee6bd state UP mode DEFAULT group default 
    link/ether fe:53:90:21:56:cb brd ff:ff:ff:ff:ff:ff link-netnsid 1

编辑003

lspci -vv | egrep 内核 | 尾-5

Kernel modules: ath9k
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci

编辑004

我在下面找到了一个诊断脚本,因此运行并粘贴输出以提供帮助。

https://ubuntuforums.org/showthread.php?t=370108

结果在 pastebin 中:https ://pastebin.com/uA74APda

networking network-manager internet
  • 1 个回答
  • 820 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    如何运行 .sh 脚本?

    • 16 个回答
  • Marko Smith

    如何安装 .tar.gz(或 .tar.bz2)文件?

    • 14 个回答
  • Marko Smith

    如何列出所有已安装的软件包

    • 24 个回答
  • Marko Smith

    无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗?

    • 25 个回答
  • Martin Hope
    Flimm 如何在没有 sudo 的情况下使用 docker? 2014-06-07 00:17:43 +0800 CST
  • Martin Hope
    Ivan 如何列出所有已安装的软件包 2010-12-17 18:08:49 +0800 CST
  • Martin Hope
    La Ode Adam Saputra 无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗? 2010-11-30 18:12:48 +0800 CST
  • Martin Hope
    David Barry 如何从命令行确定目录(文件夹)的总大小? 2010-08-06 10:20:23 +0800 CST
  • Martin Hope
    jfoucher “以下软件包已被保留:”为什么以及如何解决? 2010-08-01 13:59:22 +0800 CST
  • Martin Hope
    David Ashford 如何删除 PPA? 2010-07-30 01:09:42 +0800 CST

热门标签

10.10 10.04 gnome networking server command-line package-management software-recommendation sound xorg

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve