Disclaimer: This is not specific about siduction. Feel free to ignore it if.
I am having problems with USB devices disconnecting, resetting, and/or stop working.
Here is a brief history of what I tried (and has not solved the problem) in chronological order:
- BIOS update;
- different kernel (liquorix);
- replace the motherboard (which was a few months old only, from a ASUS TUF Gaming B850-PLUS to a MSI MAG X870 Tomahawk WiFi Gaming Motherboard);
- install Debian stable in a different partition;
- install Kubuntu (replacing Debian);
- replaced the video card (from ASRock RX 6600 8GB CLD Challenger D gddr6 to an older Radeon RX 5500 XT MECH 8G -- since it did not help, I put the newer one back);
- remove older USB-2 card (which provided 4 extra USB 2 ports);
- updated BIOS of new motherboard;
- replace the PSU (from MSI MAG A850GL PCIE5 to CORSAIR RM1000x ATX 3.1 PCIe 5.1);
- remove all hubs and USB extensions (noting that devices not attached to these were also affected).
(I tried running "memtest+" from the siduction installation, but I would not start... Is it deprecated?)
Removing the old USB-2 card seemed to have helped for a while, and maybe it was making it worse, but the problems remain.
In between, I also replaced some devices, such as Wacom tablet, and web camera.
A few times, some ports stopped working completely, some times unplugging and replugging would work. The non-working ports would start working after a reboot.
Here is some info on the system, currently on Ubuntu (I can log into siduction, if it would help):
$ inxi -v3
System:
Host: kubuntu Kernel: 7.0.0-31-generic arch: x86_64 bits: 64 compiler: gcc v: 15.2.0
Console: pty pts/8 Distro: Ubuntu 26.04.1 LTS (Resolute Raccoon)
Machine:
Type: Desktop System: Micro-Star product: MS-7E51 v: 1.0 serial: <superuser required>
Mobo: Micro-Star model: MAG X870 TOMAHAWK WIFI (MS-7E51) v: 1.0 serial: <superuser required>
Firmware: UEFI vendor: American Megatrends LLC. v: 1.A92 date: 06/30/2026
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 charge: 55% (should be ignored)
status: discharging
CPU:
Info: 8-core model: AMD Ryzen 7 9700X bits: 64 type: MT MCP arch: Zen 5 rev: 0 cache:
L1: 640 KiB L2: 8 MiB L3: 32 MiB
Speed (MHz): avg: 3618 min/max: 605/5582 boost: enabled cores: 1: 3618 2: 3618 3: 3618 4: 3618
5: 3618 6: 3618 7: 3618 8: 3618 9: 3618 10: 3618 11: 3618 12: 3618 13: 3618 14: 3618 15: 3618
16: 3618 bogomips: 121599
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: ASRock
driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 03:00.0
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 74:00.0 temp: 39.0 C
Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB bus-ID: 1-3.3:7
Display: unspecified server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.10 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu tty: 283x75
resolution: 1: 1920x1080 2: 1920x1080
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 26.0.8-1ubuntu0.3 note: console (EGL sourced)
renderer: llvmpipe (LLVM 21.1.8 256 bits), AMD Ryzen 7 9700X 8-Core Processor (radeonsi
raphael_mendocino ACO DRM 3.64 7.0.0-31-generic), AMD Radeon RX 6600 (radeonsi navi23 ACO DRM
3.64 7.0.0-31-generic)
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Network:
Device-1: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800] vendor: Foxconn Band
Simultaneous Wireless driver: ath12k_wifi7_pci v: N/A bus-ID: 09:00.0
IF: wlp9s0 state: up mac: ac:f2:3c:22:da:a3
Device-2: Realtek RTL8126 5GbE vendor: Micro-Star MSI driver: r8169 v: kernel port: e000
bus-ID: 0a:00.0
IF: enp10s0 state: up speed: 100 Mbps duplex: full mac: 34:5a:60:03:0a:a5
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
Local Storage: total: 19.1 TiB used: 7.27 TiB (38.0%)
Info:
Memory: total: 60 GiB note: est. available: 60.24 GiB used: 11.64 GiB (19.3%)
Processes: 535 Uptime: 9h 10m Init: systemd
Packages: 4031 Compilers: clang: 21.1.8 gcc: 15.2.0 Shell: Bash v: 5.3.9 inxi: 3.3.40
Here are some error from today, when the Wacom tablet kept disconnecting. From "journalctl -b -p err":
Sep 06 07:52:30 kubuntu kernel: usb 1-2-port2: disabled by hub (EMI?), re-enabling...
Sep 06 07:53:12 kubuntu sudo[3654]: pam_unix(sudo:auth): conversation failed
Sep 06 07:53:12 kubuntu sudo[3654]: pam_unix(sudo:auth): auth could not identify password for [finotti]
Sep 06 08:08:13 kubuntu kscreenlocker_greet[9175]: PAM unable to dlopen(pam_sss.so): /usr/lib/security/pam_sss.so: cannot open shared object file: No such file or directory
Sep 06 08:08:13 kubuntu kscreenlocker_greet[9175]: PAM adding faulty module: pam_sss.so
Sep 06 10:03:26 kubuntu kernel: usbhid 1-2.2:1.0: can't add hid device: -71
Sep 06 10:03:26 kubuntu kernel: usbhid 1-2.2:1.0: probe with driver usbhid failed with error -71
Sep 06 10:03:26 kubuntu kernel: usb 1-2-port2: disabled by hub (EMI?), re-enabling...
Sep 06 10:03:41 kubuntu kernel: usb 1-2-port2: disabled by hub (EMI?), re-enabling...
Sep 06 10:03:42 kubuntu kernel: usb 1-2.2: device descriptor read/64, error -71
Sep 06 10:03:42 kubuntu kernel: usb 1-2.2: device descriptor read/64, error -71
Sep 06 10:03:50 kubuntu kernel: usb 1-2-port2: Cannot enable. Maybe the USB cable is bad?
Sep 06 13:22:31 kubuntu kscreenlocker_greet[37555]: PAM unable to dlopen(pam_sss.so): /usr/lib/security/pam_sss.so: cannot open shared object file: No such file or directory
Sep 06 13:22:31 kubuntu kscreenlocker_greet[37555]: PAM adding faulty module: pam_sss.so
From "dmesg -H -T":
[Sun Sep 6 07:48:50 2026] usb 1-3.3: reset high-speed USB device number 7 using xhci_hcd
[Sun Sep 6 07:49:36 2026] usb 1-2.2: USB disconnect, device number 5
[Sun Sep 6 07:49:36 2026] usb 1-2.2: new full-speed USB device number 10 using xhci_hcd
[Sun Sep 6 07:49:37 2026] usb 1-2.2: New USB device found, idVendor=056a, idProduct=03c5, bcdDevice= 2.07
[Sun Sep 6 07:49:37 2026] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Sep 6 07:49:37 2026] usb 1-2.2: Product: Intuos BT S
[Sun Sep 6 07:49:37 2026] usb 1-2.2: Manufacturer: Wacom Co.,Ltd.
[Sun Sep 6 07:49:37 2026] usb 1-2.2: SerialNumber: 2CK00S1000751
[Sun Sep 6 07:49:37 2026] wacom 0003:056A:03C5.000C: hidraw7: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT S] on usb-0000:0d:00.0-2.2/input0
[Sun Sep 6 07:49:37 2026] input: Wacom Intuos BT S Pen as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000C/input/input31
[Sun Sep 6 07:49:37 2026] input: Wacom Intuos BT S Pad as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000C/input/input33
[Sun Sep 6 07:49:59 2026] usb 1-2.2: USB disconnect, device number 10
[Sun Sep 6 07:50:04 2026] usb 1-2.2: new full-speed USB device number 11 using xhci_hcd
[Sun Sep 6 07:50:04 2026] usb 1-2.2: New USB device found, idVendor=056a, idProduct=03c5, bcdDevice= 2.07
[Sun Sep 6 07:50:04 2026] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Sep 6 07:50:04 2026] usb 1-2.2: Product: Intuos BT S
[Sun Sep 6 07:50:04 2026] usb 1-2.2: Manufacturer: Wacom Co.,Ltd.
[Sun Sep 6 07:50:04 2026] usb 1-2.2: SerialNumber: 2CK00S1000751
[Sun Sep 6 07:50:04 2026] wacom 0003:056A:03C5.000D: hidraw7: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT S] on usb-0000:0d:00.0-2.2/input0
[Sun Sep 6 07:50:04 2026] input: Wacom Intuos BT S Pen as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000D/input/input34
[Sun Sep 6 07:50:04 2026] input: Wacom Intuos BT S Pad as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000D/input/input36
[Sun Sep 6 07:50:14 2026] usb 1-2.2: USB disconnect, device number 11
[Sun Sep 6 07:50:27 2026] usb 1-2.2: new full-speed USB device number 12 using xhci_hcd
[Sun Sep 6 07:50:27 2026] usb 1-2.2: New USB device found, idVendor=056a, idProduct=03c5, bcdDevice= 2.07
[Sun Sep 6 07:50:27 2026] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Sep 6 07:50:27 2026] usb 1-2.2: Product: Intuos BT S
[Sun Sep 6 07:50:27 2026] usb 1-2.2: Manufacturer: Wacom Co.,Ltd.
[Sun Sep 6 07:50:27 2026] usb 1-2.2: SerialNumber: 2CK00S1000751
[Sun Sep 6 07:50:28 2026] wacom 0003:056A:03C5.000E: hidraw7: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT S] on usb-0000:0d:00.0-2.2/input0
[Sun Sep 6 07:50:28 2026] input: Wacom Intuos BT S Pen as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000E/input/input37
[Sun Sep 6 07:50:28 2026] input: Wacom Intuos BT S Pad as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0d:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:056A:03C5.000E/input/input39
[Sun Sep 6 07:50:57 2026] usb 1-3.3: reset high-speed USB device number 7 using xhci_hcd
[Sun Sep 6 07:51:12 2026] usb 1-2.2: USB disconnect, device number 12
[Sun Sep 6 07:51:21 2026] usb 1-2.2: new full-speed USB device number 13 using xhci_hcd
[Sun Sep 6 07:51:22 2026] usb 1-2.2: New USB device found, idVendor=056a, idProduct=03c5, bcdDevice= 2.07
[Sun Sep 6 07:51:22 2026] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Sep 6 07:51:22 2026] usb 1-2.2: Product: Intuos BT S
[snip]
The complete output is here: https://luisfinotti.org/misc/dmes.txt
I am at the end of my rope, and considering installing Windows, since this is the computer that my wife uses for work, and the web cam and Wacom tablet are essential. Often, duriung Zoom calls the camera disconnects or the sound stops working, and we need it running reliably.
Any suggestions would be really
greatly appreciated!
Did I get this right? You replaced the motherboard and exactly the same
errors showed up? With completely different hardware? Your inxi report
doesn't mention any USB device and the error only showed up for the
CTL-4100WL [Intuos BT (S)] USB device. What happens if you connect
the tablet to another computer? Maybe the tablet is broken.
But one thing is for sure: Unless you correct the error, moving to Windows
will not save your day!
BTW: Though unrelated: Your system seems to miss pam_sss.so.
Quote from: Teriarch on Today at 00:05:21Did I get this right? You replaced the motherboard and exactly the same
errors showed up? With completely different hardware?
Yes, I replaced the motherboard. The CPU, GPU (later switched), memory, etc., remained the same.
Quote from: Teriarch on Today at 00:05:21Your inxi report
doesn't mention any USB device and the error only showed up for the
CTL-4100WL [Intuos BT (S)] USB device.
Sorry. Here is what we have:
$ inxi -J
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
Hub-2: 1-1:2 info: Genesys Logic Hub ports: 4 rev: 2.1
Hub-3: 1-2:3 info: Genesys Logic Hub ports: 4 rev: 2.1
Device-1: 1-2.2:26 info: Wacom CTL-4100 [Intuos (S)] type: HID rev: 2.0
Hub-4: 1-3:4 info: Genesys Logic Hub ports: 4 rev: 2.1
Device-1: 1-3.3:7 info: Logitech Webcam C270 type: video,audio rev: 2.0
Device-2: 1-5:6 info: Micro Star USB Audio type: audio,HID rev: 2.0
Device-3: 1-10:8 info: Micro Star MYSTIC LIGHT type: HID rev: 1.1
Device-4: 1-12:9 info: Foxconn / Hon Hai type: bluetooth rev: 1.1
Hub-5: 2-0:1 info: super-speed hub ports: 5 rev: 3.1
Hub-6: 2-1:2 info: Genesys Logic Hub ports: 4 rev: 3.2
Hub-7: 2-2:3 info: Genesys Logic GL3523 Hub ports: 4 rev: 3.2
Hub-8: 2-3:4 info: Genesys Logic GL3523 Hub ports: 4 rev: 3.2
Hub-9: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
Hub-10: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
Hub-11: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
Hub-12: 5-2:2 info: Genesys Logic Hub ports: 4 rev: 2.0
Device-1: 5-2.1:3 info: Cyber Power System CP1500 AVR UPS type: HID rev: 2.0
Device-2: 5-2.3:4 info: Logitech Unifying Receiver type: keyboard,mouse,HID rev: 2.0
Device-3: 5-2.4:5 info: Metadot Das Keyboard 4 type: keyboard,HID rev: 1.1
Hub-13: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
Hub-14: 7-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
Device-1: 7-1:2 info: Focusrite-Novation Scarlett 8i6 USB type: audio rev: 2.0
Hub-15: 7-2:3 info: Genesys Logic Hub ports: 4 rev: 2.1
Hub-16: 8-0:1 info: super-speed hub ports: 2 rev: 3.1
Hub-17: 8-2:2 info: Genesys Logic Hub ports: 4 rev: 3.2
Hub-18: 9-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
Quote from: Teriarch on Today at 00:05:21and the error only showed up for the
CTL-4100WL [Intuos BT (S)] USB device. What happens if you connect
the tablet to another computer? Maybe the tablet is broken.
I've replaced it once, and my son used it in his Mac without trouble. (Although not as extensively.) We did not use the camera today, so there are no errors from it. Here are some errors that occurred when using the camera with Zoom, and the sound (from the camera) failed:
Sep 05 15:40:44 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:44 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:40:49 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:49 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:49 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:49 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:40:54 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:54 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:54 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:54 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:40:59 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:59 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:59 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:40:59 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:41:04 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:04 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:04 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:04 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:41:09 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:09 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:09 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:09 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:41:14 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:14 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:14 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:14 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:41:19 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:19 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:19 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:19 kubuntu pipewire[2453]: pw.node: (alsa_input.usb-046d_0825_9737EF40-02.mono-fallback-67) suspended -> error (Start error: Device or resource busy)
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:21 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:24 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:24 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Sep 05 15:41:24 kubuntu pipewire[2453]: spa.alsa: 'hw:4': capture open failed: Device or resource busy
Here are some similar:
Sep 04 18:39:41 kubuntu kernel: usb 1-3.1.1: device not accepting address 12, error -71
Sep 04 18:39:57 kubuntu kernel: usb 1-3.1.1: device descriptor read/64, error -110
Sep 04 18:40:13 kubuntu kernel: usb 1-3.1.1: device descriptor read/64, error -110
Sep 04 18:40:43 kubuntu kernel: xhci_hcd 0000:0d:00.0: Abort failed to stop command ring: -110
Sep 04 18:40:43 kubuntu kernel: xhci_hcd 0000:0d:00.0: xHCI host controller not responding, assume dead
Sep 04 18:40:43 kubuntu kernel: xhci_hcd 0000:0d:00.0: HC died; cleaning up
Sep 04 18:40:44 kubuntu kernel: usb 1-3.1.1: device not accepting address 12, error -22
Sep 04 18:40:44 kubuntu pipewire[2470]: spa.alsa: hw:5c: snd_pcm_status error: No such device
Sep 04 18:40:44 kubuntu pipewire[2470]: spa.alsa: hw:5c: snd_pcm_drop: No such device
Sep 04 18:40:44 kubuntu pipewire[2470]: spa.alsa: hw:5c: snd_pcm_prepare error: No such device
Sep 04 18:40:44 kubuntu pipewire[2470]: spa.alsa: hw:5c: snd_pcm_drop: No such device
Here are the full errors (from "journalctl -p err") for the day: https://luisfinotti.org/misc/errors_2026_09_04.txt
When errors occur, even the mouse and keyboard stop working. Plugin in a different port sometimes solve the problem.
I will try to capture more errors if I can.
Quote from: Teriarch on Today at 00:05:21But one thing is for sure: Unless you correct the error, moving to Windows
will not save your day!
Probably... But if it continues, it will certainly not be a software/Linux problem. Maybe it will help pinpoint what piece of hardware is the problem. I just cannot think of what it could be, as I replaced most of the parts. :-(
Quote from: Teriarch on Today at 00:05:21BTW: Though unrelated: Your system seems to miss pam_sss.so.
Although I am not exactly sure what it is for, I've installed it now. :-) Thanks!
> Yes, I replaced the motherboard. The CPU, GPU (later switched), memory, etc., remained the same.
To be absolutely certain, since this is important: The same errors showed up before and after
you replaced the motherboard. There is only one way to find out: Remove everything from the
mainboard except PSU, keyboard, mouse and graphics card (I assume you have a USB keyboard and
mouse). Boot the system, stir up some activity and wait for a USB disconnect using
$ dmesg -w
If nothing happens, add some other USB devices at different USB ports or shuffle connected ones and
use different cables. USB disconnects are indicative for worn out ports, damaged cables or bad devices.
Add the USB devices one by one since USB ports sometimes get overloaded.
What I see is, the wacom device is connected via Bluetooth.
But what I also see is, that there is a sound problem, how many sound devices are running? Could it be that two different microphones are enabled, one from a Headset and one from the cam?
Quote from: Teriarch on Today at 01:06:31> Yes, I replaced the motherboard. The CPU, GPU (later switched), memory, etc., remained the same.
To be absolutely certain, since this is important: The same errors showed up before and after
you replaced the motherboard. There is only one way to find out: Remove everything from the
mainboard except PSU, keyboard, mouse and graphics card (I assume you have a USB keyboard and
mouse). Boot the system, stir up some activity and wait for a USB disconnect using
$ dmesg -w
If nothing happens, add some other USB devices at different USB ports or shuffle connected ones and
use different cables. USB disconnects are indicative for worn out ports, damaged cables or bad devices.
Add the USB devices one by one since USB ports sometimes get overloaded.
That's good advice. For now, since my wife has to work, I cannot disconnect the camera and tablet... But we have nothing else connected, except for the keyboard and mouse.
But, it made me think of one constant: the Wacon tablet. We've used three of them: the original, one we had for traveling both of the exact same model, and a new one we bought after the problems started to show up. (We've switched cameras, although they were all Logitech...) This last one was a slightly different model, but very similar. So, this morning I bought a Huion tablet, and so far everything is running perfectly! It is too early to say, but I am optimistic!
Quote from: hendrikL on Today at 08:15:59What I see is, the wacom device is connected via Bluetooth.
But what I also see is, that there is a sound problem, how many sound devices are running? Could it be that two different microphones are enabled, one from a Headset and one from the cam?
Thanks for the reply! Although the tablet (the most recent one) does have bluetooth, we never (intentionally, at least) connected it with bluetooth... I could only see USB connections on the logs... Did I miss something?
About the sound, I was worried about that as well, since there are many pipewire errors in the log, but we do have the correct connections.
I have the builtin audio card, a Focusrite interface which we use for playback, and the camera's audio input.
$ inxi -A
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio driver: snd_hda_intel
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio driver: snd_hda_intel
Device-4: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
Device-5: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB
Device-6: Focusrite-Novation Scarlett 8i6 USB driver: snd-usb-audio type: USB
API: ALSA v: k7.0.0-31-generic status: kernel-api
Server-1: PipeWire v: 1.6.2 status: active
But Zoom would give the error message that the Web Cam microphone, which was configured as the input, was not available, when we had failures. So, I am assuming that the pipewire errors came due to the USB failure, but I am not sure.
Anyway, I have my fingers crossed that the new tablet (or removing the Wacon one and its software) might solve the problem!