I’m experiencing an issue on my Manjaro system where a “ghost” USB device keeps reconnecting and disconnecting, causing an annoying sound every time it happens. The device is not physically connected, but it appears to show up in the system and causes these constant notifications.
I’ve tried various methods to resolve the issue, including:
Adding udev rules to ignore the device
Trying to disable the device using commands like echo '3-7' | sudo tee /sys/bus/usb/drivers/usb/unbind
Adjusting notification settings and audio preferences to mute the sound
However, the device still keeps connecting and disconnecting, and the sound persists. I would like to know if there’s a way to permanently disable this “phantom” device or stop it from causing these disconnect sounds.
Has anyone encountered a similar issue or found a solution to prevent this from happening?
If the device is not physically connected - understood as a physical port - depending on your system - it could be an internal device becoming defective.
That is a guess - as you have provided no usable intel.
Please provide output from - copy the text from your terminal and past it into your original topic - please ensure you select the text and format it using the code tags </> button in the topic toolbar
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
01:00.1 Audio device: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 11)
lsusb
Summary
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID c0f3:02a1 USB HCT Keyboard
Bus 003 Device 003: ID 046d:c246 Logitech, Inc. Gaming Mouse G300
Bus 003 Device 026: ID 14cd:168a Super Top Elecom Co., Ltd MR-K013 Multicard Reader
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
In any case, from what I understand the problematic device is this: Bus 003 Device 026: ID 14cd:168a Super Top Elecom Co., Ltd MR-K013 Multicard Reader
Please let me know if you need any more details or if you have further suggestions on how to resolve this.
Thank you so much for your help! Disconnecting the card reader physically did indeed resolve the issue, and the device no longer connects and disconnects constantly.
I do wonder though, if there’s any way to achieve the same result from software? In Windows, I can simply eject the device from the Device Manager, and that resolves the issue. Is there a similar solution on Linux or Manjaro to disable the device without physically disconnecting it?
I suppose one could attempt to write an udev rule to ignore the device, but since the device is in a loop of connect/disconnect the best approach is to remove the device.
It could be one of the reader slots having a short which causes the loop - I don’t know - simply disconnecting will remove the issue - but not the cause of defect.