USB storage devices are not detected and extremely slow

I tried to search the forum but I didn’t find a similar problem.
I need help with a couple of problems related to external USB storage devices.
I decided, a few days ago, to solve some problems of my OpenSUS 15.3 by installing a new 15.4, also formatting the Home partition which was the same for years.
A completely new and fresh installation then.
Since the first start of the new 15.4 I have had 2 problems.
All USB storage devices are not detected upon insertion or power on.
All USB storage devices are extremely slow in their operations.
I’ve done some testing, but I’m not very familiar with Linux.
1)
A 2.5-inch HDD, self-powered, on which I make scheduled backups, and with a 2-week history.
Until before the new 15.4 the backup lasted, as an execution time, between 23 and 25 minutes.
Under the new installation 15.4 the backup lasts at least 3 hours and 40/50 minutes…
2)
A 500Mb HDD, 3.5-inch, EXT-4, mounted in a docking station that contains aMule temporary files, if the program starts to work a lot, downloading many files at the same time, like a TV series, the program crashes continuously.
The more disk activity increases, the more likely the program will crash
3)
The 500Gb disk in the docking station is only seen by the system if the doking is on at boot time.
If I try to turn on the docking station when the computer is started it is not detected…
4)
A 32Gb Corsair Flash Voyager USB stick that I usually use to transfer data from one computer to another, so that I mount on occasion, is not recognized, even it, only if inserted at startup is it recognized.
The Corsair Flash Voyager USB stick has a blue LED that flashes with activity, and that usually flashes when inserted and mounted.
No flashing sign now in 15.4.
Even this, if inserted at startup and recognized and mounted, is very slow when used.
5)
To realize the slowness we are talking about.
Copy a file from the Corsair USB stick to the desktop.
The file is 84.2Mb in size
The copy in OpenSUSE 15.4 takes 4 minutes and 32 seconds.
I tried the copy of the Windows 7 system, dual boot on the same machine, and it lasted 3/4 seconds, I didn’t even have time to time.
The USB stick was attached to the same USB port in both tests.
6)
A ZIP file copied from the 500Gb EXT4 disk in the docking station to the desktop, the file size 400.2Mb.
Total copying time 21 minutes.
Under “normal” conditions I would have expected a copy time of no more than 2 minutes, maybe just 1.

I think you more or less understand the anomaly.
I am not very well versed in Linux, even though I have been using it for years, but I am open to testing of all kinds.
If you have any advice on how to proceed to understand what the anomaly is, thank you in advance.

@renedrive:

Sorry – I’m going to ask you to use the user “root” and, to use some system administration CLI tools – Terminal Window …

  • We need to see what happened when the system booted – please use the following example as a guide –

 # journalctl -b 0 --output=short-monotonic --no-hostname | grep 'kernel:' | grep -E ' USB |usbcore'
    2.188685] kernel: ACPI: bus type USB registered
    2.188711] kernel: usbcore: registered new interface driver usbfs
    2.188717] kernel: usbcore: registered new interface driver hub
    2.188747] kernel: usbcore: registered new device driver usb
    2.210327] kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
    2.266052] kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    2.266054] kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.266181] kernel: hub 1-0:1.0: USB hub found
    2.273102] kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
    2.273105] kernel: xhci_hcd 0000:01:00.0: Host supports USB 3.1 Enhanced SuperSpeed
    2.273199] kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
    2.273201] kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.273327] kernel: hub 2-0:1.0: USB hub found
    2.276817] kernel: xhci_hcd 0000:08:00.3: new USB bus registered, assigned bus number 3
    2.277441] kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    2.277443] kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.277565] kernel: hub 3-0:1.0: USB hub found
    2.278090] kernel: xhci_hcd 0000:08:00.3: new USB bus registered, assigned bus number 4
    2.278093] kernel: xhci_hcd 0000:08:00.3: Host supports USB 3.1 Enhanced SuperSpeed
    2.278152] kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
    2.278153] kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.278247] kernel: hub 4-0:1.0: USB hub found
    2.278885] kernel: xhci_hcd 0000:08:00.4: new USB bus registered, assigned bus number 5
    2.279435] kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    2.279436] kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.279534] kernel: hub 5-0:1.0: USB hub found
    2.279670] kernel: xhci_hcd 0000:08:00.4: new USB bus registered, assigned bus number 6
    2.279672] kernel: xhci_hcd 0000:08:00.4: Host supports USB 3.1 Enhanced SuperSpeed
    2.279725] kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
    2.279727] kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    2.279809] kernel: hub 6-0:1.0: USB hub found
    2.527221] kernel: usb 1-7: new low-speed USB device number 2 using xhci_hcd
    2.771820] kernel: usb 1-7: New USB device found, idVendor=046a, idProduct=0023, bcdDevice= 0.27
    2.771824] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    2.907260] kernel: usb 1-10: new low-speed USB device number 3 using xhci_hcd
    3.163852] kernel: usb 1-10: New USB device found, idVendor=046d, idProduct=c069, bcdDevice=56.01
    3.163856] kernel: usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    3.163858] kernel: usb 1-10: Product: USB Laser Mouse
    4.114725] kernel: usbcore: registered new interface driver usbhid
    4.114726] kernel: usbhid: USB HID core driver
    4.509926] kernel: input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-10/1-10:1.0/0003:046D:C069.0003/input/input0
    4.510017] kernel: hid-generic 0003:046D:C069.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] on usb-0000:01:00.0-10/input0
    4.571387] kernel: cherry 0003:046A:0023.0001: input,hidraw1: USB HID v1.11 Keyboard [HID 046a:0023] on usb-0000:01:00.0-7/input0
    4.635334] kernel: cherry 0003:046A:0023.0002: input,hidraw2: USB HID v1.11 Device [HID 046a:0023] on usb-0000:01:00.0-7/input1
 .
 .
 .
 #

The output above indicates what happened at boot time with respect to the USB devices on the system.
[INDENT=2]Hopefully your machine will indicate something similar.
[/INDENT]

  • Please install a package named “inxi
    ” which will supply access to a system information script and then, execute the command as in the following example to give us some more information about your USB device environment –

 # inxi --admin -x -xx -xx --filter --usb
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Device-1: 1-7:2 info: Cherry Keyboard type: Keyboard,HID driver: cherry,usbhid interfaces: 2 rev: 2.0 
           speed: 1.5 Mb/s chip ID: 046a:0023 
           Device-2: 1-10:3 info: Logitech M-U0007 [Corded Mouse M500] type: Mouse driver: hid-generic,usbhid interfaces: 1 
           rev: 2.0 speed: 1.5 Mb/s chip ID: 046d:c069 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 
           Device-3: 2-4:2 info: SanDisk Ultra Flair type: Mass Storage driver: usb-storage interfaces: 1 rev: 3.2 
           speed: 5 Gb/s chip ID: 0781:5591 serial: <filter> 
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Hub: 6-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 
 # 

I’ve coloured the output pasted from my Terminal session to make it easier for you to compare the output from your system to that provided by my machine.

  • You don’t need to colour your pasted output – we’ll be able to interpret the black & white pasted copy.

We’ll also need to peek into the Repositories you’re using –

  • Please post the output of “zypper repos --uri
    ” – you can execute this command from a normal user’s CLI in a Terminal Window.

@renedrive:

BTW, on this machine, when I plugged in a USB stick, the systemd Journal indicated the following –


[33044.140607] kernel: usb 2-4: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[33044.168023] kernel: usb 2-4: New USB device found, idVendor=0781, idProduct=5591, bcdDevice= 1.00
[33044.168027] kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33044.168029] kernel: usb 2-4: Product:  SanDisk 3.2Gen1
[33044.168031] kernel: usb 2-4: Manufacturer:  USB
[33044.168033] kernel: usb 2-4: SerialNumber: xxxx
[33044.215992] kernel: usb-storage 2-4:1.0: USB Mass Storage device detected
[33044.216153] kernel: scsi host10: usb-storage 2-4:1.0
[33044.216239] kernel: usbcore: registered new interface driver usb-storage
[33044.219955] kernel: usbcore: registered new interface driver uas
[33045.233150] kernel: scsi 10:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[33045.233527] kernel: sd 10:0:0:0: Attached scsi generic sg5 type 0
[33045.233801] kernel: sd 10:0:0:0: [sdd] 60088320 512-byte logical blocks: (30.8 GB/28.7 GiB)
[33045.234699] kernel: sd 10:0:0:0: [sdd] Write Protect is off
[33045.234703] kernel: sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00
[33045.235720] kernel: sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[33045.273756] kernel:  sdd: sdd1
[33045.276719] kernel: sd 10:0:0:0: [sdd] Attached SCSI removable disk

In other words, the system detected and activated the USB stick in 1.136112 seconds – 1,136.112 milliseconds …

First dcurtisfra thank you very much for your reply.

Here are the results of the commands you asked me, I hope. (I don’t know why, since this morning, my system won’t let me copy / paste without taking off all the LFs, so I have to manually edit all the carriage returns… I hope I have not made any mistakes)

# journalctl -b 0 --output=short-monotonic --no-hostname | grep 'kernel:' | grep -E ' USB |usbcore' 
    2.656912] kernel: ACPI: bus type USB registered 
    2.656958] kernel: usbcore: registered new interface driver usbfs 
    2.656969] kernel: usbcore: registered new interface driver hub 
    2.656987] kernel: usbcore: registered new device driver usb 
    2.666136] kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver 
    2.675887] kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver 
    2.678222] kernel: ehci-pci 0000:00:13.5: new USB bus registered, assigned bus number 1 
    2.678230] kernel: ehci-pci 0000:00:13.5: applying AMD SB600/SB700 USB freeze workaround 
    2.691459] kernel: ehci-pci 0000:00:13.5: USB 2.0 started, EHCI 1.00 
    2.691540] kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14 
    2.691544] kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.692062] kernel: hub 1-0:1.0: USB hub found 
    2.693846] kernel: ehci-pci 0000:05:05.2: new USB bus registered, assigned bus number 2 
    2.708139] kernel: ehci-pci 0000:05:05.2: USB 2.0 started, EHCI 1.00 
    2.708216] kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14 
    2.708220] kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.708385] kernel: hub 2-0:1.0: USB hub found 
    2.714656] kernel: ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 3 
    2.718854] kernel: uhci_hcd: USB Universal Host Controller Interface driver 
    2.719120] kernel: uhci_hcd 0000:05:05.0: new USB bus registered, assigned bus number 4 
    2.719259] kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.719263] kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.719473] kernel: hub 4-0:1.0: USB hub found 
    2.720018] kernel: uhci_hcd 0000:05:05.1: new USB bus registered, assigned bus number 5 
    2.720126] kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.720129] kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.720264] kernel: hub 5-0:1.0: USB hub found 
    2.775537] kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.775544] kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.775726] kernel: hub 3-0:1.0: USB hub found 
    2.780068] kernel: ohci-pci 0000:00:13.1: new USB bus registered, assigned bus number 6 
    2.843567] kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.843576] kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.843762] kernel: hub 6-0:1.0: USB hub found 
    2.844246] kernel: ohci-pci 0000:00:13.2: new USB bus registered, assigned bus number 7 
    2.911788] kernel: usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.911792] kernel: usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    2.919526] kernel: hub 7-0:1.0: USB hub found 
    2.959446] kernel: usb 1-3: new high-speed USB device number 2 using ehci-pci 
    3.276677] kernel: ohci-pci 0000:00:13.3: new USB bus registered, assigned bus number 8 
    3.343500] kernel: usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    3.343504] kernel: usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    3.343646] kernel: hub 8-0:1.0: USB hub found 
    3.343984] kernel: ohci-pci 0000:00:13.4: new USB bus registered, assigned bus number 9 
    3.411521] kernel: usb usb9: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    3.411528] kernel: usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 
    3.411687] kernel: hub 9-0:1.0: USB hub found 
    3.539473] kernel: usb 4-2: new full-speed USB device number 2 using uhci_hcd 
    3.743470] kernel: usb 4-2: New USB device found, idVendor=046d, idProduct=c52f, bcdDevice=22.01 
    3.743479] kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 
    3.743482] kernel: usb 4-2: Product: USB Receiver 
    3.759666] kernel: usbcore: registered new interface driver usbhid 
    3.759672] kernel: usbhid: USB HID core driver 
    3.762543] kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.4/0000:05:05.0/usb4/4-2/4-2:1.0/0003:046D:C52F.0001/input/input1 
    3.762684] kernel: hid-generic 0003:046D:C52F.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:05:05.0-2/input0 
    3.762998] kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.4/0000:05:05.0/usb4/4-2/4-2:1.1/0003:046D:C52F.0002/input/input2 
    3.823627] kernel: hid-generic 0003:046D:C52F.0002: input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:05:05.0-2/input1 
    3.887827] kernel: logitech-djreceiver 0003:046D:C52F.0001: hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:05:05.0-2/input0 
    3.988003] kernel: logitech-djreceiver 0003:046D:C52F.0002: hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:05:05.0-2/input1 
    3.998132] kernel: usb 1-3: New USB device found, idVendor=13fe, idProduct=3e00, bcdDevice= 1.00 
    3.998140] kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
    3.998142] kernel: usb 1-3: Product: USB DISK 2.0 
    4.060367] kernel: hid-generic 0003:046D:4009.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech Wireless Mouse PID:4009] on usb-0000:05:05.0-2/input1:1 
    4.106482] kernel: usb-storage 1-3:1.0: USB Mass Storage device detected 
    4.106868] kernel: usbcore: registered new interface driver usb-storage 
    4.109338] kernel: usbcore: registered new interface driver uas 
    4.195753] kernel: logitech-hidpp-device 0003:046D:4009.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech M315/M235] on usb-0000:05:05.0-2/input1:1 
    4.223449] kernel: usb 1-5: new high-speed USB device number 3 using ehci-pci 
    5.468474] kernel: usb 1-5: New USB device found, idVendor=1234, idProduct=5678, bcdDevice= 0.05 
    5.468484] kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
    5.468514] kernel: scsi 10:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 4 
    5.569551] kernel: usb-storage 1-5:1.0: USB Mass Storage device detected 
    5.695449] kernel: usb 1-8: new high-speed USB device number 4 using ehci-pci 
    6.478485] kernel: usb 1-8: New USB device found, idVendor=05e3, idProduct=0702, bcdDevice= 0.33 
    6.478494] kernel: usb 1-8: New USB device strings: Mfr=0, Product=1, SerialNumber=0 
    6.478497] kernel: usb 1-8: Product: USB TO IDE 
    6.579544] kernel: usb-storage 1-8:1.0: USB Mass Storage device detected 
   13.625280] kernel: usbcore: registered new interface driver usbtouchscreen
# inxi --admin -x -xx -xx --filter --usb 
USB:       Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
            class-ID: 0900
            Device-1: 1-3:2 info: Kingston Flash Drive type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
            speed: 480 Mb/s power: 200mA chip-ID: 13fe:3e00 class-ID: 0806 serial: <filter>
            Device-2: 1-5:3 info: Brain Actuated VLI Product String type: Mass Storage driver: usb-storage interfaces: 1
            rev: 2.1 speed: 480 Mb/s power: 2mA chip-ID: 1234:5678 class-ID: 0802 serial: <filter>
            Device-3: 1-8:4 info: Genesys Logic USB 2.0 IDE Adapter [GL811E] type: Mass Storage driver: usb-storage
            interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 96mA chip-ID: 05e3:0702 class-ID: 0806
            Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
            class-ID: 0900
            Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Device-1: 4-2:2 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid
            interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 98mA chip-ID: 046d:c52f class-ID: 0300
            Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-7: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-8: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-9: 9-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900

For the repository list, I know it’s a bit of a mess.
I added the -P option to see and sort the priority.
I work with many “strange” multimedia programs, to install them I have to activate many “special” repositories.
As often letting them run updates creates problems for the system so I use priorities to avoid the situation, I leave only the more “official” ones with higher priority so only those can upgrade.
Here they are. (In the next post…)

zypper repos --uri -P 
#  | Alias                                | Name                                                                                        | Enabled   | GPG Check     | Refresh       | Priority | URI ---+--------------------------------------+---------------------------------------------------------------------------------------------+-----------+---------------+---------------+----------+------------------------------------------------------------------------------------------------  1 | KDE-Applications                     | KDE-Applications                                                                            | Sì        | (r ) Sì       | Sì            |   97     | https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.4   
2 | KDE-Extra                            | KDE-Extra                                                                                   | Sì        | (r ) Sì       | Sì            |   97     | https://download.opensuse.org/repositories/KDE:/Extra/KDE_Applications_openSUSE_Leap_15.4   
3 | KDE-Frameworks5                      | KDE-Frameworks5                                                                             | Sì        | (r ) Sì       | Sì            |   97     | https://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_15.4   
4 | KDE-Qt5                              | KDE-Qt5                                                                                     | Sì        | (r ) Sì       | Sì            |   97     | https://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_15.4   
5 | Mozilla                              | Mozilla                                                                                     | Sì        | (r ) Sì       | Sì            |   97     | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.4/   
6 | Packman                              | Packman                                                                                     | Sì        | (r ) Sì       | Sì            |   97     | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/   
9 | http-ftp.gwdg.de-75c0c450            | Packman Repository                                                                          | Sì        | (r ) Sì       | Sì            |   97     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/ 
10 | http-opensuse-guide.org-180c17de     | libdvdcss repository                                                                        | Sì        | (r ) Sì       | Sì            |   97     | http://opensuse-guide.org/repo/openSUSE_Leap_15.4/ 
35 | repo-backports-debug-update          | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No        | ----          | ----          |   97     | http://download.opensuse.org/update/leap/15.4/backports_debug/ 
36 | repo-backports-update                | Update repository of openSUSE Backports                                                     | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/update/leap/15.4/backports/ 
37 | repo-debug                           | Debug Repository                                                                            | No        | ----          | ----          |   97     | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/ 
38 | repo-debug-non-oss                   | Debug Repository (Non-OSS)                                                                  | No        | ----          | ----          |   97     | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/ 
39 | repo-debug-update                    | Update Repository (Debug)                                                                   | No        | ----          | ----          |   97     | http://download.opensuse.org/debug/update/leap/15.4/oss/ 
40 | repo-debug-update-non-oss            | Update Repository (Debug, Non-OSS)                                                          | No        | ----          | ----          |   97     | http://download.opensuse.org/debug/update/leap/15.4/non-oss/ 
41 | repo-non-oss                         | Repository Non-OSS                                                                          | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/ 
42 | repo-oss                             | Repository principale                                                                       | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/distribution/leap/15.4/repo/oss/ 
43 | repo-sle-debug-update                | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | No        | ----          | ----          |   97     | http://download.opensuse.org/debug/update/leap/15.4/sle/ 
44 | repo-sle-update                      | Update repository with updates from SUSE Linux Enterprise 15                                | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/update/leap/15.4/sle/ 
45 | repo-source                          | Source Repository                                                                           | No        | ----          | ----          |   97     | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/ 
46 | repo-update                          | Repository principale degli aggiornamenti                                                   | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/update/leap/15.4/oss 47 | repo-update-non-oss                  | Repository degli aggiornamenti (Non-Oss)                                                    | Sì        | (r ) Sì       | Sì            |   97     | http://download.opensuse.org/update/leap/15.4/non-oss/   
7 | Scrivania                            | Scrivania                                                                                   | Sì        | ( p) Sì       | No            |  100     | dir:/home/renedrive/Scrivania   
8 | http-download.opensuse.org-95f9f161  | openSUSE:Leap:15.4:Update                                                                   | Sì        | (r ) Sì       | Sì            |  101     | http://download.opensuse.org/update/leap/15.4/oss/ 
11 | https-download.opensuse.org-0d8f8518 | SUSE:SLE-15-SP2:Update                                                                      | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP2:/Update/pool-leap-15.4/ 
12 | https-download.opensuse.org-31c6c55d | SUSE:SLE-15-SP3:GA                                                                          | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP3:/GA/pool/ 
13 | https-download.opensuse.org-3970ca89 | SUSE:SLE-15-SP4:GA                                                                          | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP4:/GA/pool/ 
16 | https-download.opensuse.org-4f42c887 | SUSE:SLE-15-SP1:Update                                                                      | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP1:/Update/pool-leap-15.4/ 
17 | https-download.opensuse.org-583b3679 | multimedia:libs                                                                             | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/multimedia:/libs/15.4/ 
18 | https-download.opensuse.org-5aed10e9 | openSUSE:Backports:SLE-15-SP4                                                               | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP4/standard/ 
19 | https-download.opensuse.org-6cdbd2f5 | SUSE:SLE-15-SP2:GA                                                                          | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP2:/GA/pool/ 
20 | https-download.opensuse.org-71f598dd | multimedia:apps                                                                             | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/multimedia:/apps/15.4/ 
21 | https-download.opensuse.org-79906b29 | openSUSE:Backports:SLE-15-SP4:Checks                                                        | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP4:/Checks/standard/ 
22 | https-download.opensuse.org-926f180d | network                                                                                     | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/network/15.4/ 
23 | https-download.opensuse.org-9ae95431 | SUSE:SLE-15:Update                                                                          | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15:/Update/pool-leap-15.4/ 
25 | https-download.opensuse.org-a0b6961e | SUSE:SLE-15-SP1:GA                                                                          | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP1:/GA/pool/ 
30 | https-download.opensuse.org-d0364270 | X11:Drivers:Video                                                                           | Sì        | (r ) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/X11:/Drivers:/Video/openSUSE_Leap_15.4/ 
32 | https-download.opensuse.org-e86f44bc | SUSE:SLE-15-SP3:Update                                                                      | Sì        | ( p) Sì       | Sì            |  101     | https://download.opensuse.org/repositories/SUSE:/SLE-15-SP3:/Update/pool-leap-15.4/ 
34 | openSUSE-Leap-15.4-1                 | openSUSE-Leap-15.4-1                                                                        | No        | ----          | ----          |  101     | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_408D5C1653D621918908TLEC-0:0-part2 
14 | https-download.opensuse.org-3e9ac455 | home:phoenix.os:playmarket                                                                  | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/phoenix.os:/playmarket/15.4/ 
15 | https-download.opensuse.org-3f2f6735 | home:txutxifel                                                                              | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/txutxifel/15.4/ 
24 | https-download.opensuse.org-9d25e209 | home:dliw:multimedia                                                                        | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/dliw:/multimedia/15.4/ 
26 | https-download.opensuse.org-c42587d4 | home:mpoleur:KDE:Extra                                                                      | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/mpoleur:/KDE:/Extra/15.4/ 
27 | https-download.opensuse.org-c76b335a | home:dfaure                                                                                 | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/dfaure/15.4/ 
28 | https-download.opensuse.org-cfd55b64 | home:phoenix.os:dup                                                                         | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/phoenix.os:/dup/15.4/ 
29 | https-download.opensuse.org-cfde6ea4 | home:jmairboeck                                                                             | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/jmairboeck/15.4/ 
31 | https-download.opensuse.org-da676403 | home:ahjolinna                                                                              | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/ahjolinna/15.4/ 
33 | https-download.opensuse.org-f8571fbc | home:simotek:base                                                                           | Sì        | (r ) Sì       | Sì            |  104     | https://download.opensuse.org/repositories/home:/simotek:/base/15.4/ 

Now I am looking for the command, which I do not remember, of systemctl to make it wait for the insertion of the USB key and I will write it to you in the next post.
If nothing has changed in the meantime, it didn’t show anything at the time of insertion, but I’ll try again anyway as soon as I find the right syntax.

I can no longer find the correct syntax to put the systemctl command on hold while inserting the USB memory.
Maybe if you tell me, I’ll do it first.
Yesterday, doing tests, I had found it, and used it, today I can’t find it anymore.
I should have written it down.

Meanwhile, I don’t know if it’s useful, I used dmesg.
These are the last two lines of dmesg before inserting the USB memory.

 3015.715530] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0  
 3015.715542] floppy: error 10 while reading block 0

Then I plugged in, and left plugged in, the USB stick for more than 20 minutes and nothing changed.
(I was looking for systemctl syntax in the meantime, that’s why 20 minutes)

 3015.715530] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0   
 3015.715542] floppy: error 10 while reading block 0

In the meantime, I keep looking for the correct systemctl syntax.
Corsair Flash Voyager USB stick, she’s the one I’m rehearsing with now.
The same one I mentioned in the first description and which still behaves the same way.

I also redo the inxi command from root user with the USB memory inserted

inxi --admin -x -xx -xx --filter --usb 
USB:       Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
            class-ID: 0900
            Device-1: 1-3:2 info: Kingston Flash Drive type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
            speed: 480 Mb/s power: 200mA chip-ID: 13fe:3e00 class-ID: 0806 serial: <filter>
            Device-2: 1-5:3 info: Brain Actuated VLI Product String type: Mass Storage driver: usb-storage interfaces: 1
            rev: 2.1 speed: 480 Mb/s power: 2mA chip-ID: 1234:5678 class-ID: 0802 serial: <filter>
            Device-3: 1-8:4 info: Genesys Logic USB 2.0 IDE Adapter [GL811E] type: Mass Storage driver: usb-storage
            interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 96mA chip-ID: 05e3:0702 class-ID: 0806
            Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
            class-ID: 0900
            Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Device-1: 4-2:2 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid
            interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 98mA chip-ID: 046d:c52f class-ID: 0300
            Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-7: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-8: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900
            Hub-9: 9-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
            class-ID: 0900 

It seems to me that nothing has changed.

@renedrive:

Looking at your list of repositories used, you seem to have added a number of Community repositories –

  • Please note that, these are private repositories used by community members – they are not subject to the rigours of OpenQA and, therefore, the quality of the software being built there can not be quantified.

Please, reduce the list of repositories being used to, only those of the openSUSE factory plus, known reliable repositories.

  • My current list of repositories is as follows – you will, possibly, not be needing the “debug
    ” repositories unless, you’re submitting Bug Reports with Crash Dumps and, the “Source Repository” is only of interest for those people who need the source code packages or, the Linux Kernel documentation –

 > LANG=C zypper repos
Repository priorities in effect:                                                                                                                                                                                                                                                                                           (See 'zypper lr -P' for details)
      99 (default priority) : 14 repositories
     102 (lowered priority) :  2 repositories
     103 (lowered priority) :  2 repositories
     110 (lowered priority) :  1 repository

#  | Alias                            | Name                                                                                        | Enabled | GPG Check | Refresh
---+----------------------------------+---------------------------------------------------------------------------------------------+---------+-----------+--------
 1 | Build_Service:_PHP:_Applications | openSUSE BuildService - PHP:Applications                                                    | Yes     | (r ) Yes  | Yes
 2 | Essentials                       | Packman Repository - Essentials                                                             | Yes     | (r ) Yes  | Yes
 3 | Hardware:Tools                   | Hardware tools                                                                              | Yes     | (r ) Yes  | Yes
 4 | KDE:Extra                        | KDE: Extra                                                                                  | Yes     | (r ) Yes  | Yes
 5 | Multimedia:Apps                  | Multimedia: Apps                                                                            | No      | ----      | ----
 6 | Multimedia:Libs                  | Multimedia: Libs                                                                            | Yes     | (r ) Yes  | Yes
 7 | VideoLAN_libdvdcss               | VideoLAN - libdvdcss                                                                        | Yes     | (r ) Yes  | Yes
 8 | openSUSE-Leap-15.3-1             | openSUSE-Leap-15.3-1                                                                        | No      | ----      | ----
 9 | openSUSE_Virtulization           | openSUSE Virtualization                                                                     | No      | ----      | ----
10 | repo-backports-debug-update      | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No      | ----      | ----
11 | repo-backports-update            | Update repository of openSUSE Backports                                                     | Yes     | (r ) Yes  | Yes
12 | repo-debug                       | Debug Repository                                                                            | Yes     | (r ) Yes  | Yes
13 | repo-debug-backports-update      | Update repository of openSUSE Backports (Debug)                                             | Yes     | (r ) Yes  | Yes
14 | repo-debug-non-oss               | Debug Repository (Non-OSS)                                                                  | Yes     | (r ) Yes  | Yes
15 | repo-debug-sle-update            | Update repository with updates from SUSE Linux Enterprise 15 (Debug)                        | Yes     | (r ) Yes  | Yes
16 | repo-debug-update                | Update Repository (Debug)                                                                   | Yes     | (r ) Yes  | Yes
17 | repo-debug-update-non-oss        | Update Repository (Debug, Non-OSS)                                                          | Yes     | (r ) Yes  | Yes
18 | repo-non-oss                     | Non-OSS Repository                                                                          | Yes     | (r ) Yes  | Yes
19 | repo-oss                         | Main Repository                                                                             | Yes     | (r ) Yes  | Yes
20 | repo-sle-debug-update            | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | No      | ----      | ----
21 | repo-sle-update                  | Update repository with updates from SUSE Linux Enterprise 15                                | Yes     | (r ) Yes  | Yes
22 | repo-source                      | Source Repository                                                                           | Yes     | (r ) Yes  | Yes
23 | repo-update                      | Update Repository                                                                           | Yes     | (r ) Yes  | Yes
24 | repo-update-non-oss              | Update Repository (Non-OSS)                                                                 | Yes     | (r ) Yes  | Yes
 > 

May I suggest that, you reduce your list of repositories to only the bare essentials then –

  • Execute “zypper refresh --force” and “zypper verify” – take care to note the messages, warnings and errors issued during the verification process.
  • Then execute “zypper update --allow-downgrade” and then, use the YaST Software Management to forcibly reinstall all the remaining packages which you have installed from wherever.
  • Then, check for any orphaned packages and, forcibly reinstall them from the main openSUSE repositories.
  • Then reboot.

Please note the need to forcibly re-install the packages you have installed from wherever – the contents of those packages have to be replaced by the contents from the main openSUSE repositories.

As I mentioned in the comment with the list of repositories I am aware that I have many additional repositories and also many not fully officially certified.
As I have also mentioned, I use my machine as a system for producing multimedia files, audio, video, presentations and documents from OCR scans etc …, especially videos.
Typically I install all the software I need with “1clickinstall” systems and, as you know, these bring with them the addition of repoitories that they eventually need.
As soon as a possible package is installed, every time, I immediately enter the repository management and I lower the priority to all the new repositories acquired, in this way the system should never make automatic upgrades from non-standard and non-certified repositories.
Since I initially left all certified repositories at standard level 99, I initially made mistakes by not correctly identifying “new arrivals”, so some non-standard ones could remain active and cause upgrades and therefore possible damage.
I solved this problem with a trick, that is, as soon as I installed the base system, from the DVD, I lower all the standard repositories to the level of priority 97, in this way I am able to understand very clearly which are the standard and certified ones compared to the “new ones arrivals”
As far as I understand, and obviously I could be wrong, in this way the system will update automatically only and only from the most standard repositories, those with priority raised to 97 and, theoretically, never from any other repository that was not present after the first installation.
Apart from the “few” repositories present after a fresh installation, the only repositories that I manually add and that I raise to level 97 are additional repositories that I find in an OpenSUSE wiki page as recommended additional repositories, and therefore, I guess, certified, and no one else.
Over time I found myself observing that this system I used by managing priorities gave me a more stable machine, preventing “experimental” and malfunctioning updates from arriving in the system, corrupting its functioning.
I don’t know, I’m not sure, but I think it is possible that if I have additional repositories, even with lower priority, and a new program requires, as dependencies, newer, and perhaps experimental libraries, these can, during the installation phase, be brought into the system precisely because you find it in the non-standard repositories present.
Or at least I think it works this way, I’m not sure.
This, I believe, is a weak point of having such repositories active, even if at low priority, and that is that, if required by the installation of some program, some “non-standard” packages or libraries can “dirty” the system.
This is what I think, and I seem to have understood, possibly correct me if something escapes me.
Now to the question of cleaning up repositories and packages from removed repositories.
I could, of course, easily remove all repositories that are not standard and certified.
I did it, some time ago, when installing new particular software when I understood that he would try to use non-standard repositories, during the installation phase I asked him to “NOT” keep the repositories used active after the installation.
This was my previous strategy to not “litter” the system with unwanted automatic updates.
In this case, however, I could not possibly keep these additional installed programs manually updated, and from this situation I studied the system of repository priorities and I replaced this strategy with the one I explained above.
In this way the sources of the additional programs are active but do not automatically “dirty” the system.
Obviously this leads to pay attention, during the installation of a new “strange” program, to what is installed, which does not “seem” suspicious, for example by never activating the “automatic supplier change” in Yast, in this way it is me that I have to check if some “non-standard” library wants to overwrite the standard ones and eventually give up the installation of this package.
It’s not a perfect strategy, some non-standard updates can always escape me, of course.
But I need such additional programs for the multimedia work I do, and we come to the matter of removing the packages you mentioned.
So when you say …

May I suggest that, you reduce your list of repositories to only the bare essentials

…I believe that from the point of view of system updates I am, thanks to the priority strategy, in a relatively clean and standard system.
I think I have a “relatively clean and standard” system, not only because I try to pay attention to what I install and dependencies, but also because typically the programs I install tend to need “particular” libraries only in the multimedia field, not it often happens that they want to change standard system libraries.
Although of course it can happen, and it could be out of my control.
Now, I understand that …

“zypper refresh --force” and “zypper verify”

… would lead, once removed the “unofficial” repositories, to go back to a standard system.
But, I guess, it would also mean breaking all the multimedia dependencies that are necessary for the programs I need and use daily and that reside in the removed repositories, correct?
In this way I would be in a position of not being able to have a functioning machine for the specific purposes in which I use it.
Same goes with …

“zypper update --allow-downgrade”

… which would lead to the same situation.
So also this valuable and valid advice …

Then, check for any orphaned packages and, forcibly reinstall them from the main openSUSE repositories

… would not give valid results because obviously all the “special” multimedia programs that I have installed, and that I need, and that require the repositories eventually removed, would no longer work and would be considered orphaned and could not be “fixed” precisely because in the repositories standards do not exist the necessary requirements to make them work properly.
Now, having said that, if you have understood my situation, I understand that the situation is complex.
It is certainly more difficult to understand what is wrong with a non-standard system.
Unfortunately, however, I do not need a standard system but a system that is suitable for creating multimedia files, from many different sources and with many and different processing possibilities, is my “job”.
For this reason it is complex for me, but it is in general, to understand what is badly functioning.
Keeping in mind, however, as I mentioned previously, that the USB malfunction and weakness was present even when the system was just installed, before the addition of the various additional repositories and various necessary programs, therefore also present in a freshly installed “standard system”.
I doubt that “weird” multimedia programs are going to mess with the libraries, and drivers, device management standards.
I think I have to understand how “the detection of USB devices during connection or power on” works, as well as “the management of these devices during use” and understand if there is any anomaly in those systems, which for some reason has failed to be correctly configured or installed during the new system installation.
I have no idea if it will be possible, if it will be easy, maybe it will not be, but to have a working multimedia machine I think I will have to try.
I thought that I could eventually remove the repositories to have a report, typically I see it in Yast in red, of orphans, and start from there to understand if something standard has been polluted and correct it.
But I should then know “what” to check, so what has to do with the anomaly I find.
One thing that, of course, is not useful for me to do is make my machine unusable by uninstalling everything that is not standard, because it would not be a useful machine for my multimedia activity.
I don’t know if I’ve made myself clear.
I don’t know if at this point it is possible to debug the malfunctions.
I hope so.
And I will try.

One thing I occasionally do if I run into glitches that I don’t know how to fix is an “upgrade” installation, of the same system version, from the original DVD.
I think it causes something very similar to what you ask me to do.
When I start it I let it delete all pre-existing repositories.
So when it’s done I find myself with my “special” programs orphaned or not working.
Typically from that situation I start from scratch and get everything I need to work again.
Maybe by installing everything with more caution and attention, and maybe only one program at a time doing tests between one installation and another.
But even if this system often works, it doesn’t always work, it often doesn’t work if, I believe, the problem could be in the configurations saved in the home partition that are not changed except slightly.
I don’t know, it’s a tough job to do, long and tedious, and that may not solve, but maybe I’ll try.

Otherwise the only alternative would be to understand and debug the system as it is to understand what is not working well and solve that single problem, which is perhaps not easy.

I don’t know, tell me what you think and if you see, from your experience, a system to fix without making the machine unusable?
In the meantime, I still thank you very much for the help and information you have provided me so far.
I await your opinion on this, I’m curious to hear your opinion.

systemctl disable systemd-udevd-control.socket isn’t it. I tried, from among the following group:

# systemctl list-unit-files | grep udev
dracut-pre-udev.service                static          -
initrd-udevadm-cleanup-db.service      static          -
systemd-udev-settle.service            static          -
systemd-udev-trigger.service           static          -
systemd-udevd.service                  static          -
systemd-udevd-control.socket           static          -
systemd-udevd-kernel.socket            static          -

Maybe disabling one of the others is the ticket. I don’t feel like risking that one of the wrong others would necessitate a reboot to fix ATM.

inxi --admin -x -xx -xx --filter --usb 

A lot of unnecessary typing there. cf.:

# inxi -az --usb
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:8008 class-ID: 0900
  Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:8000 class-ID: 0900
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-4:2 info: Pixart Imaging Optical Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
    power: 100mA chip-ID: 093a:2510 class-ID: 0301
  Device-2: 3-6:3 info: Fitipower Integrated All-in-1 Card Reader
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s power: 250mA chip-ID: 18e3:9101 class-ID: 0806
    serial: <filter>
  Hub-6: 4-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 4-1:11 info: Kingston USB DISK 3.2 type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 3.2 speed: 5 Gb/s power: 504mA
    chip-ID: 13fe:6700 class-ID: 0806 serial: **<filter>**
# inxi -S
System:
  Host: 00srv Kernel: 5.3.18-150300.59.68-default arch: x86_64 bits: 64
    Console: pty pts/0 Distro: openSUSE Leap 15.3

-xx incorporates -x. -xxx incorporates -xx. -a incorporates -xxx. -a == --admin. -z == --filter.

I’m sorry, my bad English prevents me from fully understanding what you mean me to do.
The command …

systemctl list-unit-files | grep udev

… returns me exactly the same result as it returns to you.

> systemctl list-unit-files | grep udev 
dracut-pre-**udev**.service                                                   static          - 
initrd-**udev**adm-cleanup-db.service                                         static          - 
systemd-**udev**-settle.service                                               static          - 
systemd-**udev**-trigger.service                                              static          - 
systemd-**udev**d.service                                                     static          - 
systemd-**udev**d-control.socket                                              static          - 
systemd-**udev**d-kernel.socket                                               static          -

The command …

systemctl disable systemd-udevd-control.socket

… do you want me to run it to disable the udev system?
So what then?
Some test?
Can you explain better what you mean by the phrase …

Maybe disabling one of the others is the ticket. I don’t feel like risking that one of the wrong others would necessitate a reboot to fix ATM.

If with the phrase …

A lot of unnecessary typing there. cf.:

… you mean that …

inxi --admin -x -xx -xx --filter --usb

… the syntax is wrong, I’m sorry, I don’t know the inxi command and so I limited myself to copying it exactly as I saw it in your post number 5, without knowing what I was doing, precisely because I don’t know what inxi does.
If, on the other hand, you are interested in the result of the inxi command with the syntax you posted above, that is …

inxi -az --usb

… here is the result.

> inxi -az --usb 
**USB:       Hub-1:** 1-0:1 **info:** Full speed (or root) Hub **ports:** 10 **rev:** 2.0 **speed:** 480 Mb/s **chip-ID:** 1d6b:0002 **class-ID:** 0900 
           **Device-1:** 1-3:2 **info:** Kingston Flash Drive **type:** Mass Storage **driver:** usb-storage **interfaces:** 1 **rev:** 2.0 
           **speed:** 480 Mb/s **power:** 200mA **chip-ID:** 13fe:3e00 **class-ID:** 0806 **serial:** <filter> 
           **Device-2:** 1-5:3 **info:** Brain Actuated VLI Product String **type:** Mass Storage **driver:** usb-storage **interfaces:** 1 
           **rev:** 2.1 **speed:** 480 Mb/s **power:** 2mA **chip-ID:** 1234:5678 **class-ID:** 0802 **serial:** <filter> 
           **Device-3:** 1-8:4 **info:** Genesys Logic USB 2.0 IDE Adapter [GL811E] **type:** Mass Storage **driver:** usb-storage 
           **interfaces:** 1 **rev:** 2.0 **speed:** 480 Mb/s **power:** 96mA **chip-ID:** 05e3:0702 **class-ID:** 0806 
           **Hub-2:** 2-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Device-1:** 2-2:2 **info:** Logitech Unifying Receiver **type:** Mouse,HID **driver:** logitech-djreceiver,usbhid **interfaces:** 2 
           **rev:** 2.0 **speed:** 12 Mb/s **power:** 98mA **chip-ID:** 046d:c52f **class-ID:** 0300 
           **Hub-3:** 3-0:1 **info:** Full speed (or root) Hub **ports:** 4 **rev:** 2.0 **speed:** 480 Mb/s **chip-ID:** 1d6b:0002 **class-ID:** 0900 
           **Hub-4:** 4-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Hub-5:** 5-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Hub-6:** 6-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Hub-7:** 7-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Hub-8:** 8-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900 
           **Hub-9:** 9-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 **class-ID:** 0900

Also in this part …

-xx incorporates -x. -xxx incorporates -xx. -a incorporates -xxx. -a == --admin. -z == --filter.

… I don’t really understand what you mean and what I have to do with it, can you explain me better?

Sorry for being so poor in both English and Linux system, I hope you will forgive me.

No. I tried that. It failed.

So what then?
Some test?
Can you explain better what you mean by the phrase …

[quote]Maybe disabling one of the others is the ticket. I don’t feel like risking that one of the wrong others would necessitate a reboot to fix ATM.
[/quote]I meant that enabling others, one at a time, as an experiment or “test”, might switch your networking on, and that I didn’t want to make the tests myself at that moment and risk a need to reboot in order to undo any possible interference with other things I was working on.

If with the phrase …

[quote]A lot of unnecessary typing there. cf.:

… you mean that …

inxi --admin -x -xx -xx --filter --usb

… the syntax is wrong, I’m sorry, I don’t know the inxi command and so I limited myself to copying it exactly as I saw it in your post number 5, without knowing what I was doing, precisely because I don’t know what inxi does.[/quote]I didn’t write post number 5. Someone else used it in post number 2. I meant you didn’t need to type so much to produce equivalent results from running inxi. Inxi is a hardware and configuration collection and reporting tool.

Also in this part …

[quote] -xx incorporates -x. -xxx incorporates -xx. -a incorporates -xxx. -a == --admin. -z == --filter.

… I don’t really understand what you mean and what I have to do with it, can you explain me better?[/QUOTE]Menu

  1. asparagus
  2. asparagus, beets
  3. asparagus, beets, carrots
  4. asparagus, beets, carrots, dill
  5. eggplant
  6. fish
    -x equates to menu item 1.
    -xx equates to menu item 2.
    -xxx equates to menu item 3.
    Both -a and --admin equate to menu item 4.
    Both -z and --filter equate to menu item 5.
    –usb equates to menu item 6.
    The waitress, needing to be fast but accurate, will write 4, 5, 6 (-az --usb) to get the cook to make you every food on the menu.

Not only am I poor at English and concerned with Linux, I realize now that I am also poor at using forums.
Maybe rust due to the long period of non-use of the forums.

True, you are right, I did not notice that a different user had written that post and having replied in general, without quoting, it seemed I was replying to you.
In fact, through my own fault, through distraction, I didn’t realize I was dealing with two different users who were helping me.
I apologize to you for my mistake.
Also, as you seem to have already understood very well, I didn’t even understand the use of inxi at all and therefore I didn’t understand what I was doing, I just repeated what I had read.

You are absolutely right, I read the man of inxi a little bit and I realized that it is a great tool.
I believe I will use it more often from now on.
I will write it down with some useful examples ready to start.
Thank you very much also for the explanation of the “Menu”, it took me a little while, but I think I have better understood the command you recommended.

In the meantime I have also noticed something else, but that perhaps it will not add anything to you as information.
In my first post I mentioned a backup I make every day, which keeps a 14 day history.
For this backup I read data, 2.1Gb, from a USB stick, then copy it to an external 2.5 inch USB drive, first using an “mv” command on this, to create the history.
There are also 2 compression processes involved, luckily, to speed things up, I do them on partitions on internal drives, not USB, the “desktop” partition.
I had initially written that the process had gone from a time of realization of 23/25 minutes to a time of over 3 hours.
Instead I realized, last night, that the backup takes more than 5 hours.
I also realized, again last night, that the backup is no longer making it “valid” for more than a week, because I realized that all the files are corrupt, not recoverable.
What happens is that the last operation that performs the backup procedure is a copy of the last “final” compressed file on the external USB disk that contains the history, this copy command ends around 3 hours and 50/60 minutes from start of backup.
But after this, and I hadn’t thought about it, the process of committing the changes to that disk starts, committing the last copy operation.
When I saw ending the backup, close luckybackup which I use for this, waiting a little, I turned off the machine (the backup is the last operation before finishing the “work” day).
I had noticed a lot of slowness in shutting down the computer, and sometimes I had forced the shutdown with the power button, doing so then I would stop committing the last command to copy the backup to the external USB drive, on the next reboot, the following morning, I found the file of the backup truncated in size and therefore corrupted.
Last night, in fact, I realized it and waiting for the end of the copy, or rather the commit of the copy, I realized the actual duration of the backup, including the commit, of more than 5 hours, perhaps around 5 hours and 20 /30 minutes.
I noticed this last night before turning off the computer at the end of the work day, using the plasma widget to safely eject that disk, and wait, whether the disk disappeared from the widget list, or that the hard drive LED stopped blinking.
Also last night, in extreme delay, I shut down the computer forcibly, so no valid backup.
But this morning I have already changed the backup schedule in order to anticipate the start time a lot, maybe tonight it will be able to finish before the computer shutdown time, at least I hope.
But this backup is just my problem, I just wanted to tell you all that even the commit of the last copy command of the last backup step takes hours to complete.
For sure it makes complete sense to you, but it took me a moment to understand it.

In the meantime, I am continuing to search the Internet for possible solutions but for now nothing relevant or suitable.
I will obviously continue to search.
Thanks, however, again to all those who try to help me.

I have now found an information and have done the verification.
Maybe this check is useful for you to understand the anomaly more, and maybe you avoid telling me to do it later.
I have found that it looks like, in OpenSUSE, the kernel module …
usb_storage
… is responsible for recognizing and mounting USB devices.
He was then advised to use the command …
lsmod | grep usb
… to verify that it was loaded.
I have checked and this is the result.

> lsmod | grep usb 
**usb**touchscreen         32768  0 
**usb**_storage            81920  4 uas 
**usb**hid                 61440  1 hid_logitech_dj 
**usb**core               319488  9 **usb**touchscreen,ohci_hcd,ehci_pci,**usb**hid,**usb**_storage,ehci_hcd,ohci_pci,uas,uhci_hcd 
scsi_mod              266240  10 scsi_dh_emc,sd_mod,dm_multipath,scsi_dh_alua,**usb**_storage,uas,libata,sg,scsi_dh_rd
ac,sr_mod

Then in the procedure you were asked to insert the USB memory and check if the operations on that peripheral appeared in dmesg.
But nothing has changed.
As already mentioned, no message is shown in dmesg when inserting the USB memory.
I don’t know if this information will be useful to you in any way.

On 15.3 (running KDE3 desktop on a PC with Intel CPU) I get the same result before and after USB stick insertion and mounting:

# lsmod | grep usb | sort
scsi_mod              262144  11 st,scsi_dh_emc,sd_mod,dm_multipath,scsi_dh_alua,usb_storage,uas,libata,sg,scsi_dh_rdac,sr_mod
usb_storage            81920  3 uas
usbcore               311296  7 xhci_hcd,ehci_pci,usbhid,usb_storage,ehci_hcd,xhci_pci,uas
usbhid                 61440  0

On 15.4 (running TDE desktop on a PC with AMD CPU), before and after differ:

# lsmod | grep usb | sort
usbcore               319488  7 xhci_hcd,ohci_hcd,ehci_pci,usbhid,ehci_hcd,xhci_pci,ohci_pci
usbhid                 61440  0
<insert stick>
<click yes in do you wish to mount popup>
# lsmod | grep usb | sort
scsi_mod              266240  10 scsi_dh_emc,sd_mod,dm_multipath,scsi_dh_alua,usb_storage,uas,libata,sg,scsi_dh_rdac,sr_mod
usb_storage            81920  2 uas
usbcore               319488  9 xhci_hcd,ohci_hcd,ehci_pci,usbhid,usb_storage,ehci_hcd,xhci_pci,ohci_pci,uas
usbhid                 61440  0

I may have found something else interesting, and maybe useful.
I have taken a look at the features of systemctl, just a quick glance.
I understood the question of units a little and found that there are units such as mount and automount.
In the guide I read it was not clear what exactly the unit mounts are, or maybe it’s just me who doesn’t fully understand, but I think it’s the mount that systemd manages, so already mounted.
I asked for a list and from the content I see all the USB devices, which being connected and turned on at startup, which have been mounted.

> sudo systemctl list-units --type=mount   
UNIT                                    LOAD   ACTIVE SUB     DESCRIPTION                          
-.mount                                 loaded active mounted Root Mount   
dev-hugepages.mount                     loaded active mounted Huge Pages File System   
dev-mqueue.mount                        loaded active mounted POSIX Message Queue File System   
home.mount                              loaded active mounted /home   
media-DATI_2_NTFS.mount                 loaded active mounted /media/DATI_2_NTFS   
media-NAS_NG_01.mount                   loaded active mounted /media/NAS_NG_01   
media-Win.mount                         loaded active mounted /media/Win   
run-media-renedrive-Gatto4Gb.mount      loaded active mounted /run/media/renedrive/Gatto4Gb   
run-media-renedrive-Lacie500_Ext4.mount loaded active mounted /run/media/renedrive/Lacie500_Ext4   
run-media-renedrive-NTFS40Gb.mount      loaded active mounted /run/media/renedrive/NTFS40Gb   
run-user-1000-gvfs.mount                loaded active mounted /run/user/1000/gvfs   
run-user-1000.mount                     loaded active mounted /run/user/1000   
sys-fs-fuse-connections.mount           loaded active mounted FUSE Control File System   
sys-kernel-config.mount                 loaded active mounted Kernel Configuration File System   
sys-kernel-debug.mount                  loaded active mounted Kernel Debug File System   
sys-kernel-tracing.mount                loaded active mounted Kernel Trace File System 

Those in red are precisely those that are active at boot time.
So I asked for the list of automount units, perhaps thinking of finding something about USB peripherals in general.
This is the result.

> sudo systemctl list-units --type=automount   
UNIT                              LOAD   ACTIVE SUB     DESCRIPTION                                            >   
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount>

I assumed I had to find something related to USB, but it was just a try.
However, the autofs service is active.

> sudo systemctl list-units --all|grep -i .automount 
● boot.automount                                                                                                not-found inactive dead      boot.automount   
proc-sys-fs-binfmt_misc.automount                                                                             loaded    active   waiting   Arbitrary Executable File Formats File System Automount Point   
autofs.service                                                                                                loaded    active   running   Automounts filesystems on demand 

On another computer, the situation is identical, and on that computer, the detection of new USB drives works fine.
Maybe in the end all this control was not so useful, but I have learned something new.
I do not know!?!?

Possibly one of two causes –

  1. Broken hardware – the hardware which deals with USB has reached it’s end-of-life …
  2. Something in the code retrieved from the repositories you need for producing multimedia files, audio, video, presentations and documents from OCR scans, etc, doesn’t match up to the USB hardware of the machine suffering this issue …

The 2nd point can only be proved if, the machine suffering the issue you’re experiencing is tested with a basic openSUSE installation.

  • Ideally, you’ll have to replace your current system disk with a spare, empty, disk and, install from scratch with the scratch drive and then, check if the USB issue you’re experiencing still occurs – this will also prove if, the USB hardware is dying, or not …
  • And then, add the packages you need for multimedia etc. one by one, checking at each step for the USB issue.

Initially I also thought about the possibility of a hardware USB system failure.
For this reason I booted with a dual boot partition that I have with an old version of Windows 7 on it and did the test I mentioned in my first comment.
The test not only proved that the USB 2.0 add-in card works, but also that the precise USB port I used to test works, and also that it works at the correct speed one would expect from a USB 2.0 port.

Initially I also thought about the possibility of a hardware USB system failure.
For this reason I booted with a dual boot partition that I have with an old version of Windows 7 on it and did the test I mentioned in my first comment.
The test not only proved that the USB 2.0 add-in card works, but also that the precise USB port I used to test works, and also that it works at the correct speed one would expect from a USB 2.0 port.

As I mentioned in one of my comments the 2 problems with the USB ports were already present in the newly installed system, before installing the rest of the software I need.
However your suggestion reminds me of an easy and painless test to do.
Make a temporary boot from a DVD.
I don’t remember, because I don’t often try it, if OpenSUSE 15.4 also has boot mode in addition to installing and updating.
But a test with another distribution is also an interesting test just in case.

This other advice of yours reminded me of another test I can take.
Using unetbootin to make a bootable USB right from OpenSUSE 15.4, from the same ISO I used for the DVD I used to install, and boot the system from that USB, and see if the problems remain.
If the problem persists then there is something wrong with the ISO, either the burning to the DVD, or the DVD itself.
If the problem does not recur, it means that the support is correct but perhaps something went wrong during the installation, perhaps the download of updates.
Thanks to your advice, I have a bit of testing to do.
Taken from trying to study and understand the problem, the most banal and simple and non-destructive tests that can be done had slipped my mind.
It will take a while, I run, and then update on the results.

Yesterday afternoon I did a boot test with a CD of one of the Puppy Linux versions.
Everything was ok with regards to USB functionality.
USB drives mounted very quickly as soon as they are inserted or turned on.
Speed in copy operations in the norm.
I made the copy of that same file I mentioned, from the same USB memory, connected to the same USB port, the exact same file copied the first time, mentioned in the first comment, size 84.2Mb, copied to the Puppy desktop, and the copy lasted 2/3 seconds.

So I did another test, with a slightly more performing and modern system.
A 20.x version of Linux Mint that I had around.
I got exactly the same results as with the Puppy.
All USB disks mounted quickly and without problems when inserted or turned on, and when mounted they operate within the normal range of speed.
Even copying the exact same file, from the same USB memory, into the same USB port, copied to the Mint desktop took 2/3 seconds, exactly as expected.

Then, again from Mint, I started unetbootin and wrote the OpenSUSE 15.4 ISO on a USB stick.
I was thinking of starting OpenSUSE from there, but when I tried it I noticed that it is not a Live, but only for installation or upgrade (I didn’t remember it anymore).
So, still in Mint, I burned OpenSUSE 15.4 to a DVD.
Keep in mind that the ISO file resides on another USB drive and that both unetbootin and burning went perfectly smooth and fast reading directly from that disc.

These were my tests last night.
This morning I succumbed to temptation.
Since last night I had burned 15.4 to DVD, I started it and did the system update procedure.
I use this system, do the system upgrade procedure, on the same version, because sometimes if problems occur that seem related to the base system this procedure could solve them.
Unfortunately, however, it did not give good results.
Some data, with the computer started after the update and the USB disks turned off or disconnected at startup, is therefore turned on and connected after the start, the automount does not work, they are not “heard” by the system.

-x-x-x- to the next post -x-x-x-

The data.

> sudo journalctl -b 0 --output=short-monotonic --no-hostname | grep 'kernel:' | grep -E ' U
SB |usbcore' 
[sudo] password di root:  
    2.676440] kernel: ACPI: bus type** USB **registered 
    2.676481] kernel: **usbcore**: registered new interface driver usbfs 
    2.676493] kernel: **usbcore**: registered new interface driver hub 
    2.676509] kernel: **usbcore**: registered new device driver usb 
    2.682137] kernel: ehci_hcd:** USB **2.0 'Enhanced' Host Controller (EHCI) Driver 
    2.685841] kernel: ohci_hcd:** USB **1.1 'Open' Host Controller (OHCI) Driver 
    2.687665] kernel: ehci-pci 0000:00:13.5: new** USB **bus registered, assigned bus number 1 
    2.687679] kernel: ehci-pci 0000:00:13.5: applying AMD SB600/SB700** USB **freeze workaround 
    2.702737] kernel: ehci-pci 0000:00:13.5:** USB **2.0 started, EHCI 1.00 
    2.702846] kernel: usb usb1: New** USB **device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14 
    2.702850] kernel: usb usb1: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.703090] kernel: hub 1-0:1.0:** USB **hub found 
    2.703766] kernel: ehci-pci 0000:05:05.2: new** USB **bus registered, assigned bus number 2 
    2.703808] kernel: uhci_hcd:** USB **Universal Host Controller Interface driver 
    2.719032] kernel: ehci-pci 0000:05:05.2:** USB **2.0 started, EHCI 1.00 
    2.719233] kernel: usb usb2: New** USB **device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14 
    2.719238] kernel: usb usb2: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.719441] kernel: hub 2-0:1.0:** USB **hub found 
    2.719713] kernel: uhci_hcd 0000:05:05.0: new** USB **bus registered, assigned bus number 3 
    2.721095] kernel: usb usb3: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.721102] kernel: usb usb3: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.722739] kernel: hub 3-0:1.0:** USB **hub found 
    2.722943] kernel: ohci-pci 0000:00:13.0: new** USB **bus registered, assigned bus number 4 
    2.723129] kernel: uhci_hcd 0000:05:05.1: new** USB **bus registered, assigned bus number 5 
    2.723241] kernel: usb usb5: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.723244] kernel: usb usb5: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.726962] kernel: hub 5-0:1.0:** USB **hub found 
    2.790787] kernel: usb usb4: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.790797] kernel: usb usb4: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.790995] kernel: hub 4-0:1.0:** USB **hub found 
    2.791549] kernel: ohci-pci 0000:00:13.1: new** USB **bus registered, assigned bus number 6 
    2.854762] kernel: usb usb6: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.854768] kernel: usb usb6: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.858979] kernel: hub 6-0:1.0:** USB **hub found 
    2.865198] kernel: ohci-pci 0000:00:13.2: new** USB **bus registered, assigned bus number 7 
    2.926750] kernel: usb usb7: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    2.926754] kernel: usb usb7: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    2.930998] kernel: hub 7-0:1.0:** USB **hub found 
    3.252232] kernel: ohci-pci 0000:00:13.3: new** USB **bus registered, assigned bus number 8 
    3.314749] kernel: usb usb8: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    3.314754] kernel: usb usb8: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    3.314899] kernel: hub 8-0:1.0:** USB **hub found 
    3.315252] kernel: ohci-pci 0000:00:13.4: new** USB **bus registered, assigned bus number 9 
    3.382763] kernel: usb usb9: New** USB **device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.14 
    3.382770] kernel: usb usb9: New** USB **device strings: Mfr=3, Product=2, SerialNumber=1 
    3.382927] kernel: hub 9-0:1.0:** USB **hub found 
    3.514699] kernel: usb 3-2: new full-speed** USB **device number 2 using uhci_hcd 
    3.732717] kernel: usb 3-2: New** USB **device found, idVendor=046d, idProduct=c52f, bcdDevice=22.01 
    3.732727] kernel: usb 3-2: New** USB **device strings: Mfr=1, Product=2, SerialNumber=0 
    3.732730] kernel: usb 3-2: Product:** USB **Receiver 
    3.749916] kernel: **usbcore**: registered new interface driver usbhid 
    3.749920] kernel: usbhid:** USB **HID core driver 
    3.752894] kernel: input: Logitech** USB **Receiver as /devices/pci0000:00/0000:00:14.4/0000:05:05.0/usb3/3-2/3-2:
1.0/0003:046D:C52F.0001/input/input1 
    3.753060] kernel: hid-generic 0003:046D:C52F.0001: input,hidraw0:** USB **HID v1.11 Mouse [Logitech[b] USB Receiver]
 on usb-0000:05:05.0-2/input0 
    3.753420] kernel: input: Logitech** USB **Receiver Consumer Control as /devices/pci0000:00/0000:00:14.4/0000:05:0
5.0/usb3/3-2/3-2:1.1/0003:046D:C52F.0002/input/input2 
    3.814833] kernel: hid-generic 0003:046D:C52F.0002: input,hiddev96,hidraw1:** USB **HID v1.11 Device [Logitech[b] USB
 Receiver] on usb-0000:05:05.0-2/input1 
    3.847045] kernel: logitech-djreceiver 0003:046D:C52F.0001: hidraw0:** USB **HID v1.11 Mouse [Logitech[b] USB Receive
r] on usb-0000:05:05.0-2/input0 
    3.963401] kernel: logitech-djreceiver 0003:046D:C52F.0002: hiddev96,hidraw1:** USB **HID v1.11 Device [Logitech[b] U
SB Receiver] on usb-0000:05:05.0-2/input1 
    4.027066] kernel: hid-generic 0003:046D:4009.0003: input,hidraw2:** USB **HID v1.11 Mouse [Logitech Wireless Mous
e PID:4009] on usb-0000:05:05.0-2/input1:1 
    4.109985] kernel: logitech-hidpp-device 0003:046D:4009.0003: input,hidraw2:** USB **HID v1.11 Mouse [Logitech M31
5/M235] on usb-0000:05:05.0-2/input1:1

> inxi -az --usb 
**USB:       Hub-1:** 1-0:1 **info:** Full speed (or root) Hub **ports:** 10 **rev:** 2.0 **speed:** 480 Mb/s **chip-ID:** 1d6b:0002 
           **class-ID:** 0900 
           **Hub-2:** 2-0:1 **info:** Full speed (or root) Hub **ports:** 4 **rev:** 2.0 **speed:** 480 Mb/s **chip-ID:** 1d6b:0002 
           **class-ID:** 0900 
           **Hub-3:** 3-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Device-1:** 3-2:2 **info:** Logitech Unifying Receiver **type:** Mouse,HID **driver:** logitech-djreceiver,usbhid 
           **interfaces:** 2 **rev:** 2.0 **speed:** 12 Mb/s **power:** 98mA **chip-ID:** 046d:c52f **class-ID:** 0300 
           **Hub-4:** 4-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Hub-5:** 5-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Hub-6:** 6-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Hub-7:** 7-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Hub-8:** 8-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900 
           **Hub-9:** 9-0:1 **info:** Full speed (or root) Hub **ports:** 2 **rev:** 1.1 **speed:** 12 Mb/s **chip-ID:** 1d6b:0001 
           **class-ID:** 0900