我正在尝试将一些音乐文件从文件服务器复制到我的三星手机的内部存储卡。
当我插入手机时,我可以通过 Nautilus 中的 MTP 访问存储卡。但是,当我尝试复制任何文件时,我只是得到“不支持操作”。
它似乎仍然能够创建新文件夹,但不能创建文件。
我很确定这之前已经与其他 Ubuntu-Android 组合一起工作过。这里似乎有什么问题?
三星 Galaxy A52s (Android 14) 和 Ubuntu 22.04 LTS。
我正在尝试将一些音乐文件从文件服务器复制到我的三星手机的内部存储卡。
当我插入手机时,我可以通过 Nautilus 中的 MTP 访问存储卡。但是,当我尝试复制任何文件时,我只是得到“不支持操作”。
它似乎仍然能够创建新文件夹,但不能创建文件。
我很确定这之前已经与其他 Ubuntu-Android 组合一起工作过。这里似乎有什么问题?
三星 Galaxy A52s (Android 14) 和 Ubuntu 22.04 LTS。
我在使用充当 hidraw 设备通过 USB 发送定期数据的传感器时遇到问题。我有一个 Udev 规则,它创建一个符号链接,供 docker 容器与 Azure IoT Edge 使用。
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="e025", SYMLINK+="temper" MODE="0660"
事情通常是,在一段时间(可能是几分钟或几小时)之后,它开始在屏幕上写入,并且 docker 无法再检测到它(程序发送错误)。
我已经尝试在 udev 规则中设置 GROUP="docker" 。我正在使用带有 LXDE 的 Ubuntu 20.04。
设备是 TemperHUM: https: //www.amazon.fr/Temp%C3%A9rature-Doluteur-Enregistreur-Thermo-hygrom%C3%A8tre-Surveillance/dp/B0B7SJL3C7/ref=sr_1_5 希望链接有效
USB (NTFS) 文件传输遇到的挑战:初始写入速度异常导致数据丢失
目前,我在将文件传输到 NTFS 格式的 USB 驱动器时遇到了一个令人困惑的问题。启动传输后,进度条会显示预期的 USB 总写入速度为 13-26 MB/s。然而,当传输开始时,出现了异常情况,数据以 170+ MB/s 的意外速度发送到 USB。这种异常行为会导致数据完全丢失;弹出并重新插入 USB 后,文件将无处可寻。
此外,如果我选择对 USB 进行剪切和粘贴方法,原始文件也会丢失。为了缓解这个问题,我发现自己必须多次复制同一个文件。有趣的是,经过两三次尝试后,USB 的数据传输稳定下来,以预期的正常速度运行,然后成功保留数据。
值得注意的是,我目前使用的是 Ubuntu 18.04,但这个问题在版本 20.04 和 23.04 中仍然存在。我正在询问社区内的其他人是否遇到了类似的问题,以及是否已经找到了任何解决方案或见解。
我有一个无线 USB 鼠标,直到两天前才可以正常工作,然后我的笔记本电脑没电了,当我充电并重新打开它时,它不再工作了。
我正在运行 Ubuntu 22.04,当我运行时lsusb
,USB 在总线 002 设备 003 上被识别
~ lsusb
Bus 001 Device 005: ID 13d3:5a07 IMC Networks VGA UVC WebCam
Bus 001 Device 004: ID 13d3:3526 IMC Networks Bluetooth Radio
Bus 001 Device 003: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 3151:3020 YICHIP Wireless Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
但是,它没有出现在 上xinput
,并且不起作用。我给鼠标充电,更换了USB端口,并重新启动了计算机,但没有任何效果。
我正在尝试从 .iso 文件制作 Ubuntu 可启动 USB 驱动器。
我正在关注ubuntu.com上的教程
此时,它拒绝写入驱动器。我以为我的 U 盘已经旧了,所以我买了一个全新的,但行为还是一样。
我尝试过 SE 或论坛上建议的各种咒语,建议诸如“umount”等。
最终,我尝试从 18.04 进行后期升级,并且由于不再安装软件包而使我的系统陷入不稳定状态(没有可用的 gparted),因此我打算进行全新安装,因为/ home/stewart 位于完全独立的磁盘上。
帮助!
我有一台运行 Ubuntu 23.10 的笔记本电脑,运行 VirtualBox 图形用户界面版本 7.0.10_Ubuntu r158379
当我启动Virtual Box界面时,它立即弹出错误:
Failed to enumerate host USB devices.
Could not load the Host USB Proxy service: VERR_DISK_FULL.
Result Code:
NS_ERROR_FAILURE (0X00004005)
Component:
HostWrap
Interface:
IHost {e54f6256-97a7-4947-8a78-10c013ddf4b8}
该笔记本电脑设置了 ZFS 文件系统,可用空间超过 1 TB:
$ zfs list
NAME USED AVAIL REFER MOUNTPOINT
UbuntuZFS 6.10T 1.02T 192K none
UbuntuZFS/home 1.93T 1.02T 1.84T /home
UbuntuZFS/replicant 4.10T 1.02T 4.10T /mnt/replicant
UbuntuZFS/root 78.7G 1.02T 58.6G /
我尝试删除并重新安装 VBox 扩展包,但这并没有改变错误。
在打开任何虚拟机之前会弹出此错误。
Syslog 有以下信息:
023-11-15T14:44:07.550689-05:00 fafnir kernel: [12360.888264] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/common/log/log.c:551:41
2023-11-15T14:44:07.582740-05:00 fafnir kernel: [12360.921116] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:861:45
2023-11-15T14:44:07.582757-05:00 fafnir kernel: [12360.921373] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:930:19
2023-11-15T14:44:07.582766-05:00 fafnir kernel: [12360.921529] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:931:19
2023-11-15T14:44:07.587163-05:00 fafnir kernel: [12360.921679] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:937:19
2023-11-15T14:44:07.587179-05:00 fafnir kernel: [12360.921827] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1213:9
2023-11-15T14:44:07.587187-05:00 fafnir kernel: [12360.921998] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:917:15
2023-11-15T14:44:07.587228-05:00 fafnir kernel: [12360.922224] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:918:15
2023-11-15T14:44:07.587240-05:00 fafnir kernel: [12360.922404] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:919:15
2023-11-15T14:44:29.942888-05:00 fafnir kernel: [12383.281184] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:943:19
2023-11-15T14:44:29.942918-05:00 fafnir kernel: [12383.281600] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:944:19
2023-11-15T14:44:29.946752-05:00 fafnir kernel: [12383.281976] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:945:19
2023-11-15T14:44:58.114804-05:00 fafnir kernel: [12411.453334] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:951:23
2023-11-15T14:44:58.114817-05:00 fafnir kernel: [12411.453681] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:952:23
2023-11-15T14:44:58.118746-05:00 fafnir kernel: [12411.453981] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:958:23
2023-11-15T14:44:58.118774-05:00 fafnir kernel: [12411.454281] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1222:13
2023-11-15T14:52:00.059611-05:00 fafnir dbus-daemon[2333]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.182' (uid=1000 pid=45623 comm="/usr/lib/virtualbox/VirtualBox" label="unconfined")
2023-11-16T08:25:23.667358-05:00 fafnir kernel: [76038.004783] input: BM20X-5.0 as /devices/virtual/misc/uhid/0005:000E:3412.0008/input/input34
2023-11-16T08:25:23.739025-05:00 fafnir /usr/libexec/gdm-x-session[4725]: (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:000E:3412.0008/input/input34/event4"
2023-11-16T12:32:34.048520-05:00 fafnir kernel: [90867.964254] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/common/log/log.c:1558:29
2023-11-16T12:37:05.988567-05:00 fafnir kernel: [91139.906740] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.c:648:59
2023-11-16T12:37:05.988587-05:00 fafnir kernel: [91139.906898] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.c:647:59
2023-11-16T12:38:40.046438-05:00 fafnir dbus-daemon[2333]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.263' (uid=1000 pid=45623 comm="/usr/lib/virtualbox/VirtualBox" label="unconfined")
2023-11-16T12:53:44.923189-05:00 fafnir systemd[4532]: app-gnome-virtualbox-86937.scope: Failed to add control inotify watch descriptor for control group /user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-virtualbox-86937.scope: No space left on device
2023-11-16T12:53:44.923464-05:00 fafnir systemd[4532]: app-gnome-virtualbox-86937.scope: Failed to add memory inotify watch descriptor for control group /user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-virtualbox-86937.scope: No space left on device
2023-11-16T12:53:44.944988-05:00 fafnir systemd[4532]: Started app-gnome-virtualbox-86937.scope - Application launched by gnome-shell.
2023-11-16T12:53:45.002296-05:00 fafnir virtualbox.desktop[86937]: Qt CRITICAL: inotify_add_watch(/home/alan/.config/ibus/bus/4ac0e7f5903b1e1023748f9563b86a21-unix-1) failed: (No space left on device)
关于如何解决的任何想法?
我正在编写嵌入式 STMicro.com STM32 处理器代码并使用 STMicro.com 的 USB 驱动程序。STM32处理器上没有运行其他软件。这有点不寻常,但我们已经成功地将 STM32 处理器配置为根据命令从 USB/CDC 设备切换到 USB/MSC 设备。问题是找到一种方法从 USB/MSC 切换回 USB/CDC。
为了解决这个问题,我相信我可以使用 USB 电缆将基于 STM32 的设备连接到 Ubuntu 计算机并发送 SCSI 弹出命令。然而这并不总是有效。我发现我必须至少发送两次 SCSI 弹出命令。有时,在我的 STM32 代码看到 1 个弹出事件之前,有多达 5 次。为什么?
为了验证 STM32 代码是否有效,我将基于 STM32 的设备连接到 Windows 10 计算机。使用 Windows 文件资源管理器中的弹出功能,我能够看到 Windows 10 计算机发送到基于 STM32 的设备的每个弹出事件。因此,STM32 代码和 STMicro.com USB 驱动程序似乎可以工作(适用于 Windows 10)。
更深入...
当基于 STM32 的设备连接到 Ubuntu 计算机时,我运行了 STM32 处理器调试器。在调试 STMicro.com 的 USB 驱动程序时,我观察到可以看到所有 USB/MSC SCSI Eject 命令。但是,在我的代码看到 EJECT 状态之前,驱动程序会用其他 USB/MSC 状态(例如 LOCK 和 UNLOCK)重写弹出标志。以下是可以在 github.com 上找到的 STMicro.com 代码片段:
if ((params[4] & 0x3U) == 0x1U) /* START=1 */
{
hmsc->scsi_medium_state = SCSI_MEDIUM_UNLOCKED;
}
else if ((params[4] & 0x3U) == 0x2U) /* START=0 and LOEJ Load Eject=1 */
{
hmsc->scsi_medium_state = SCSI_MEDIUM_EJECTED;
}
else if ((params[4] & 0x3U) == 0x3U) /* START=1 and LOEJ Load Eject=1 */
{
hmsc->scsi_medium_state = SCSI_MEDIUM_UNLOCKED;
}
else
{
/* .. */
}
当出现以下情况时,Ubuntu 是否发送的不仅仅是 SCSI 弹出命令:
eject -s /dev/sdx
...使用命令?有没有办法只从 Ubuntu 通过 USB/MSC 连接发送 SCSI 弹出命令?
我的 USB 网络摄像头一直工作正常,直到我从 20.04 升级到 23.04。
网络摄像头仍然可以在 Ubuntu 22.04 上运行(我刚刚在另一台机器上测试过)。
更新:我也在23.10中测试过,它不起作用
当我将网络摄像头连接到 Ubuntu 23.04 计算机时,我在日志 ( ) 中收到以下错误消息journalctl -f
:
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: new high-speed USB device number 18 using xhci_hcd
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: New USB device found, idVendor=046d, idProduct=082b, bcdDevice=28.26
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: Product: Webcam C170
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: Manufacturer:
Sep 18 12:59:33 HOST-NAME kernel: usb 3-5: Found UVC 1.00 device Webcam C170 (046d:082b)
Sep 18 12:59:33 HOST-NAME kernel: input: Webcam C170: Webcam C170 as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0/input/input38
Sep 18 12:59:34 HOST-NAME mtp-probe[996248]: checking bus 3, device 18: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-5"
Sep 18 12:59:34 HOST-NAME mtp-probe[996248]: bus: 3, device: 18 was not an MTP device
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.1: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.1 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996254]: 3-5:1.3: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.3 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996254]: 3-5:1.3: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.3 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.1: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.1 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.2: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.2 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.2: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.2 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0 0:0' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME mtp-probe[996302]: checking bus 3, device 18: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-5"
Sep 18 12:59:34 HOST-NAME mtp-probe[996302]: bus: 3, device: 18 was not an MTP device
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:14.0/usb3/3-5 189:273' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME systemd-udevd[996251]: 3-5: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:14.0/usb3/3-5 189:273' failed with exit code 1.
Sep 18 12:59:34 HOST-NAME wireplumber[901535]: <WpPortalPermissionStorePlugin:0x564ee8807980> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
它提到了“快照”和“杯子”。我不知道杯子和网络摄像头有什么关系。即使是“突然”对我来说也是一个惊喜,但我知道这可能是有牵连的。但是杯子呢?
无论如何,你能发现问题吗?我还可以在这里分享其他内容来寻找解决方案吗?
当我在 23.10 中测试它时,我得到:
Sep 21 19:31:58 ubuntu systemd[1]: systemd-localed.service: Deactivated successfully.
Sep 21 19:32:04 ubuntu kernel: usb 3-8: new high-speed USB device number 6 using xhci_hcd
Sep 21 19:32:04 ubuntu kernel: usb 3-8: New USB device found, idVendor=046d, idProduct=082b, bcdDevice=28.26
Sep 21 19:32:04 ubuntu kernel: usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 21 19:32:04 ubuntu kernel: usb 3-8: Product: Webcam C170
Sep 21 19:32:04 ubuntu kernel: usb 3-8: Manufacturer:
Sep 21 19:32:04 ubuntu mtp-probe[4921]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-8"
Sep 21 19:32:04 ubuntu mtp-probe[4921]: bus: 3, device: 6 was not an MTP device
Sep 21 19:32:04 ubuntu kernel: mc: Linux media interface: v0.10
Sep 21 19:32:04 ubuntu kernel: videodev: Linux video capture interface: v2.00
Sep 21 19:32:04 ubuntu kernel: usbcore: registered new interface driver snd-usb-audio
Sep 21 19:32:04 ubuntu kernel: usb 3-8: Found UVC 1.00 device Webcam C170 (046d:082b)
Sep 21 19:32:04 ubuntu kernel: usbcore: registered new interface driver uvcvideo
Sep 21 19:32:04 ubuntu mtp-probe[4931]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-8"
Sep 21 19:32:04 ubuntu mtp-probe[4931]: bus: 3, device: 6 was not an MTP device
Sep 21 19:32:04 ubuntu (udev-worker)[4920]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 99.
Sep 21 19:32:04 ubuntu systemd[2463]: Reached target sound.target - Sound Card.
Sep 21 19:32:04 ubuntu wireplumber[2474]: <WpPortalPermissionStorePlugin:0x55ba448edf30> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.squashfs...................................../casper/minimal.squashfs: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.es.squashfs.gpg..../casper/minimal.enhanced-secureboot.es.squashfs.gpg: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.en.squashfs..../casper/minimal.enhanced-secureboot.en.squashfs: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.es.manifest..../casper/minimal.standard.es.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.ru.manifest..../casper/minimal.ru.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.es.manifest..../casper/minimal.enhanced-secureboot.es.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.en.squashfs...../casper/minimal.standard.en.squashfs: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.pt.manifest..../casper/minimal.pt.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.fr.size..../casper/minimal.fr.size: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.de.squashfs.gpg..../casper/minimal.standard.de.squashfs.gpg: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.manifest..../casper/minimal.enhanced-secureboot.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.fr.manifest..../casper/minimal.fr.manifest: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.squashfs.gpg..../casper/minimal.squashfs.gpg: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.en.size..../casper/minimal.enhanced-secureboot.en.size: OK
Sep 21 19:32:04 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.enhanced-secureboot.ru.manifest..../casper/minimal.standard.enhanced-secureboot.ru.manifest: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.enhanced-secureboot.squashfs........./casper/minimal.standard.enhanced-secureboot.squashfs: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.fr.size..../casper/minimal.standard.fr.size: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.es.squashfs.gpg..../casper/minimal.es.squashfs.gpg: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.standard.es.size..../casper/minimal.standard.es.size: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.no-languages.manifest..../casper/minimal.no-languages.manifest: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.it.size..../casper/minimal.enhanced-secureboot.it.size: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.no-languages.squashfs..../casper/minimal.no-languages.squashfs: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./casper/minimal.enhanced-secureboot.de.squashfs.gpg..../casper/minimal.enhanced-secureboot.de.squashfs.gpg: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./.disk/cd_type..../.disk/cd_type: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./.disk/base_installable..../.disk/base_installable: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./.disk/info..../.disk/info: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./.disk/casper-uuid-generic..../.disk/casper-uuid-generic: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Checking ./.disk/release_notes_url...../.disk/release_notes_url: OK
Sep 21 19:32:10 ubuntu casper-md5check[3451]: Check finished: no errors found.
Sep 21 19:32:10 ubuntu systemd[1]: Finished casper-md5check.service - casper-md5check Verify Live ISO checksums.
Sep 21 19:32:10 ubuntu systemd[1]: Startup finished in 8.401s (kernel) + 3min 13.015s (userspace) = 3min 21.416s.
我买了一个 USB 灯,我想使用命令打开/关闭它(我的目的是设置一些 CRON 作业以在特定时间打开它)。
我研究了几个答案,但没有一个有效。
我尝试使用所有 USB 端口(包括 USB 集线器中的端口等)输出到/sys/bus/usb/drivers/usb/unbind
、/sys/bus/usb/devices/usb1/power/level
工具uhubctl
,但没有任何效果。
该灯是一个哑设备,当它插入端口时它就会打开。
我的电脑是MouseComputer Co.,Ltd. MB-R500
.
灯就是这个。
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
sudo lsusb
Bus 002 Device 004: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 123: ID 13d3:56af IMC Networks USB2.0 HD UVC WebCam
Bus 001 Device 121: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 119: ID 2808:9338 Focal-systems.Corp FT9201Fingerprint.̚
Bus 001 Device 054: ID 19d2:1405 ZTE WCDMA Technologies MSM ZTE Technologies MSM
Bus 001 Device 053: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 052: ID 046d:c548 Logitech, Inc. USB Receiver
Bus 001 Device 051: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 125: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sudo uhubctl
Current status for hub 2-2 [2109:0813 VIA Labs, Inc. USB3.0 Hub, USB 3.00, 4 ports, ppps]
Port 1: 02a0 power 5gbps Rx.Detect
Port 2: 02a0 power 5gbps Rx.Detect
Port 3: 02a0 power 5gbps Rx.Detect
Port 4: 02a0 power 5gbps Rx.Detect
Current status for hub 1-2 [2109:2813 VIA Labs, Inc. USB2.0 Hub, USB 2.10, 4 ports, ppps]
Port 1: 0100 power
Port 2: 0103 power enable connect [046d:c548 Logitech USB Receiver]
Port 3: 0103 power enable connect [046d:c52b Logitech USB Receiver]
Port 4: 0503 power highspeed enable connect [19d2:1405 ZTE,Incorporated ZTE Technologies MSM MF9751ZTED000000]
这是输出的片段lsusb -v
,然后搜索Anker
哪个是我的HUB的名称。
Bus 001 Device 068: ID 291a:8365 Anker Anker USB-C Hub Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01
bDeviceClass 17
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x291a
idProduct 0x8365
bcdDevice 0.01
iManufacturer 1 Anker
iProduct 2 Anker USB-C Hub Device
iSerial 3 0000000000000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0012
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 0000000000000001
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 17
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 3 0000000000000001