Devices on Konqueror

As it happens in Konqueror 5.0.97 there is no sidebar which was earlier toggled by F9, which is sad, because it was very useful. Still, is it possible to view the attached devices (harddrive, usb) as separate links as it was earlier or as it is in Dolphin? Or maybe it is possible somehow to use an earlier version of Konqueror with the sidebar? I am using Ubuntu 18.

Thanks you.

Dual boot from two separate physical storage devices [migrated]

I have a new laptop that has a 256GB NVMe SSD drive with Windows 10 currently installed. The laptop has 2 NVMe SSD slots, so I plan to move the 256GB SSD to the second slot, and insert a new 1TB SSD drive into the first slot.

Summary:

  • Slot 1: 1TB SSD with Linux
  • Slot 2: 256GB SSD with Windows

I plan to dual boot. Is there anything special I need to be aware of in order to make this possible? Can I simply move the first SSD into the second slot, install Linux on the new 1TB SSD, configure the Grub2 boot loader and go? Is there anything I’m missing?

As I type this out I’m feeling like it’s a dumb question. I’ve done plenty of dual-booting in the past but I believe it was on separate partitions and not often on separate drives — or at least it’s been a while since I’ve done this. 😀

multiple /dev/video devices for 1 camera causing issue with udev rules

Since upgrading from ubuntu 16.04 (kernel 4.15.0-60-generic) to 18.04 (kernel 5.0.0-27-generic) v4l now returns multiple /dev/video devices per physical device. This causes issues when trying to map video devices to aliases using udev rules. One of the /dev/video devices can stream video, the other cannot. The udev alias I’ve created does not seem to consistently choose the correct /dev/video index (the one with streaming capabilities).

I know this post is very similar to this:

Four /dev/video entries but just one camera

However, the accepted answer (bug with skype) does not adequately address the udev issue I’m experiencing.

I see someone has a similar question on stack exchange:

https://unix.stackexchange.com/questions/512759/multiple-dev-video-for-one-physical-device

However, no answer has been accepted.

Additional Information:

Computer make/model: Asus ROG GL503V

Webcam make/model: Genius WideCam F100, Logitech C920, and more.

v4l2-ctl --list-devices

returns:

USB2.0 PC CAMERA: USB2.0 PC CAM (usb-0000:00:14.0-11):  /dev/video4  /dev/video5  USB_Camera: USB_Camera (usb-0000:00:14.0-3):  /dev/video0  /dev/video1  HD Pro Webcam C920 (usb-0000:00:14.0-4.1):  /dev/video6  /dev/video7  USB2.0 HD UVC WebCam: USB2.0 HD (usb-0000:00:14.0-7):  /dev/video2  /dev/video3 

Here’s a detailed look at the Genius WideCam F100:

user@AsusROG:~$   sudo v4l2-ctl --list-devices USB_Camera: USB_Camera (usb-0000:00:14.0-3):     /dev/video0     /dev/video1  USB2.0 HD UVC WebCam: USB2.0 HD (usb-0000:00:14.0-7):     /dev/video2     /dev/video3  user@AsusROG:~$   sudo v4l2-ctl --device=/dev/video0 --all Driver Info (not using libv4l2):     Driver name   : uvcvideo     Card type     : USB_Camera: USB_Camera     Bus info      : usb-0000:00:14.0-3     Driver version: 5.0.21     Capabilities  : 0x84A00001         Video Capture         Metadata Capture         Streaming         Extended Pix Format         Device Capabilities     Device Caps   : 0x04200001         Video Capture         Streaming         Extended Pix Format Priority: 2 Video input : 0 (Camera 1: ok) Format Video Capture:     Width/Height      : 640/480     Pixel Format      : 'YUYV'     Field             : None     Bytes per Line    : 1280     Size Image        : 614400     Colorspace        : sRGB     Transfer Function : Default (maps to sRGB)     YCbCr/HSV Encoding: Default (maps to ITU-R 601)     Quantization      : Default (maps to Limited Range)     Flags             :  Crop Capability Video Capture:     Bounds      : Left 0, Top 0, Width 640, Height 480     Default     : Left 0, Top 0, Width 640, Height 480     Pixel Aspect: 1/1 Selection: crop_default, Left 0, Top 0, Width 640, Height 480 Selection: crop_bounds, Left 0, Top 0, Width 640, Height 480 Streaming Parameters Video Capture:     Capabilities     : timeperframe     Frames per second: 30.000 (30/1)     Read buffers     : 0                      brightness 0x00980900 (int)    : min=-64 max=64 step=1 default=0 value=0                        contrast 0x00980901 (int)    : min=0 max=95 step=1 default=32 value=32                      saturation 0x00980902 (int)    : min=0 max=100 step=1 default=55 value=55                             hue 0x00980903 (int)    : min=-2000 max=2000 step=1 default=0 value=0  white_balance_temperature_auto 0x0098090c (bool)   : default=1 value=1                           gamma 0x00980910 (int)    : min=100 max=300 step=1 default=165 value=165            power_line_frequency 0x00980918 (menu)   : min=0 max=2 default=1 value=1       white_balance_temperature 0x0098091a (int)    : min=2800 max=6500 step=10 default=4600 value=4600 flags=inactive                       sharpness 0x0098091b (int)    : min=1 max=7 step=1 default=2 value=2          backlight_compensation 0x0098091c (int)    : min=0 max=1 step=1 default=0 value=0                   exposure_auto 0x009a0901 (menu)   : min=0 max=3 default=3 value=3               exposure_absolute 0x009a0902 (int)    : min=50 max=10000 step=1 default=166 value=166 flags=inactive user@AsusROG:~$   sudo v4l2-ctl --device=/dev/video1 --all Driver Info (not using libv4l2):     Driver name   : uvcvideo     Card type     : USB_Camera: USB_Camera     Bus info      : usb-0000:00:14.0-3     Driver version: 5.0.21     Capabilities  : 0x84A00001         Video Capture         Metadata Capture         Streaming         Extended Pix Format         Device Capabilities     Device Caps   : 0x04A00000         Metadata Capture         Streaming         Extended Pix Format Priority: 2 

Here’s the versions of various v4l packages I have installed:

ii libv4l-0:amd64 1.14.2-1 amd64 Collection of video4linux support libraries ii libv4l-dev:amd64 1.14.2-1 amd64 Collection of video4linux support libraries (development files) ii libv4l2rds0:amd64 1.14.2-1 amd64 Video4Linux Radio Data System (RDS) decoding library ii libv4lconvert0:amd64 1.14.2-1 amd64 Video4linux frame format conversion library ii v4l-utils 1.14.2-1 amd64 Collection of command line video4linux utilities 

here’s an excerpt from lsusb:

Bus 001 Device 017: ID 0458:708c KYE Systems Corp. (Mouse Systems) Genius WideCam F100

and the associated udev rule:

KERNEL=="video?", SUBSYSTEM=="video4linux", ATTRS{idVendor}=="0458", ATTRS{index}=="0", ATTRS{idProduct}=="708c", SYMLINK+="v4l/hd_cam" 

Any input would be greatly appreciated

Having a different design and interactions between mobile and tablet devices can have a big impact from overall UX?

I have 2 design approach for a specific module 1 is for mobile and 1 is for tablet. The goal of this is for analyzation of the historical dates of the financial data.

A. Mobile phone design – Straight forward horizontal bar chart to differentiate each data from the previous periods.

Mobile screen

B. Tablet Design – This is to increase users interactions by providing more relevant information for analysis to filter the data and period based on their preferences. enter image description here

Does it make sense from the users perspective do have different designs from the different screen? Does it not affect the learnability and familiarity on the app?

Thank you

How to interpret a device’s USB location (i.e. 1-3.2.1)

I have a script that needs to unbind/bind a device and to do that, I need to retrieve the USB location. When I enumerate the ports using pyserial, I get the following:

ttyACM3 Numato 1-3.2.1:1.1 

But when I do the unbind/bind, I believe what I want to use is just this portion of it:

1-3.2.1

That got me wondering what the “:1.1” was, so I went to /sys/bus/usb/devices and I noticed that I have the following:

lrwxrwxrwx 1 root root 0 Sep  3 12:53 1-3.2.1 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2.1/ lrwxrwxrwx 1 root root 0 Sep  3 12:53 1-3.2.1:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2.1/1-3.2.1:1.0/ lrwxrwxrwx 1 root root 0 Sep  3 12:53 1-3.2.1:1.1 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2.1/1-3.2.1:1.1/ lrwxrwxrwx 1 root root 0 Sep  3 12:53 1-3.2.1:1.2 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2.1/1-3.2.1:1.2/ lrwxrwxrwx 1 root root 0 Sep  3 12:53 1-3.2.1:1.3 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2.1/1-3.2.1:1.3/ 

I know the beginning of the location has to do with the hierarchy of the USB bus and the hubs, etc – what is the stuff after the colon (1.0, 1.1, 1.2, and 1.3)? It seems like /sys/bus/usb/devices/1-3.2.1 contains all the main details for the device, but I was curious what all the other folders are.

The other reason I ask is because when I use pyserial to list all the devices and their USB locations, is it safe to just truncate everything after the colon when I want the device location?

Received email from ISP saying one of my devices has malware

My dad received a suspicious email from our ISP (mtnl.net.in) The email was from noreply@mtnl.net.in and it had our userid (xxxxxxxx@a i masked it) in the email so it must have come from the ISP itself.

Email details below:

Subject:

“Intimation Regarding Malware/ Virus Infected Systems”

Body:

Dear Sir/Madam, Greetings! It is observed that your device connected with MTNL Mumbai broadband network with broadband number xxxxxxxx@a is infected with Malware. This is as per the analysis of Computer Emergency Response Team -INDIA (Cert-IN), under the Ministry of Electronics and Information Technology. Malware (CNC) is unwanted software that is installed in users system without users consent while user is surfing on the Internet. An attacker or cybercriminal can remotely send commands to such systems which are compromised by malware. These compromised machines can be used to create powerful networks (botnet) of infected devices capable of carrying out distributed denial-of-service (DDoS) attacks, stealing data, deleting data or encrypting data in order to carry out an extortion scheme. The device becomes part of the botnet due to malware/virus installed on it. To secure your devices , Kindly check your devices for malware/ botnet using Antivirus S/w. For more information on malware/botnets and the counter measures kindly visit https://www.cyberswachhtakendra.gov.in. You can also download "Free botnet removal tools". Thanks & Warm Regards, MTNL, Mumbai 

I extracted all links from the email and scanned them via https://www.virustotal.com/ url scanner but all were reported as safe.

Links:

  • http://www.cert-in.org.in/
  • https://www.cyberswachhtakendra.gov.in/
  • https://www.quickheal.co.in/bot-removal-tool
  • http://mtnlmumbai.in/index.php/broadband/triband/promotional-plans#unlimited-high-speed-plans
  • https://selfcare.mtnl.net.in/mumbai/TribandRegistrationInstn.aspx

Looking online there is a similar question on Quora but different scenario.

NETWORK AT HOME

  • Two mobile phones (Android)
  • One laptop (Windows 10 with Avira antivirus)

QUESTION:

  • Can an ISP really detect this?

  • Should I action on this and what to do?

After rebooting all of my existing usb devices stopped working

I rebooted my system today and discovered that my existing usb keyboard, mouse, and webcam stopped working. Oddly plugging a spare keyboard and mouse I had lying around works fine!!!

Failing devices

Aug 25 19:04:25 tower kernel: [  460.225605] usb 1-3: USB disconnect, device number 11 Aug 25 19:04:27 tower kernel: [  461.975324] usb 1-3: new high-speed USB device number 12 using xhci_hcd Aug 25 19:04:27 tower kernel: [  462.141834] usb 1-3: New USB device found, idVendor=148f, idProduct=3070, bcdDevice= 1.01 Aug 25 19:04:27 tower kernel: [  462.141840] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 25 19:04:27 tower kernel: [  462.141843] usb 1-3: Product: 802.11 n WLAN Aug 25 19:04:27 tower kernel: [  462.141846] usb 1-3: Manufacturer: Ralink Aug 25 19:04:27 tower kernel: [  462.141849] usb 1-3: SerialNumber: 1.0 Aug 25 19:04:27 tower mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 25 19:04:27 tower mtp-probe: bus: 1, device: 12 was not an MTP device Aug 25 19:04:27 tower mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 25 19:04:27 tower mtp-probe: bus: 1, device: 12 was not an MTP device Aug 25 19:04:32 tower kernel: [  467.175835] usb 1-5.3: USB disconnect, device number 7 Aug 25 19:04:35 tower kernel: [  470.011325] usb 1-5.3: new low-speed USB device number 13 using xhci_hcd Aug 25 19:04:35 tower kernel: [  470.169576] usb 1-5.3: New USB device found, idVendor=056e, idProduct=00fe, bcdDevice= 1.20 Aug 25 19:04:35 tower kernel: [  470.169581] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Aug 25 19:04:35 tower kernel: [  470.169585] usb 1-5.3: Product: ELECOM TrackBall Mouse Aug 25 19:04:35 tower kernel: [  470.169587] usb 1-5.3: Manufacturer: ELECOM Aug 25 19:04:35 tower mtp-probe: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3" Aug 25 19:04:35 tower mtp-probe: bus: 1, device: 13 was not an MTP device Aug 25 19:04:35 tower mtp-probe: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3" Aug 25 19:04:35 tower mtp-probe: bus: 1, device: 13 was not an MTP device Aug 25 19:04:37 tower kernel: [  472.295818] usb 1-5.1: USB disconnect, device number 5 Aug 25 19:04:40 tower kernel: [  474.831304] usb 1-5.1: new full-speed USB device number 14 using xhci_hcd Aug 25 19:04:40 tower kernel: [  474.947631] usb 1-5.1: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.03 Aug 25 19:04:40 tower kernel: [  474.947634] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Aug 25 19:04:40 tower kernel: [  474.947635] usb 1-5.1: Product: USB Receiver Aug 25 19:04:40 tower kernel: [  474.947637] usb 1-5.1: Manufacturer: Logitech Aug 25 19:04:40 tower mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1" Aug 25 19:04:40 tower mtp-probe: bus: 1, device: 14 was not an MTP device Aug 25 19:04:40 tower mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1" Aug 25 19:04:40 tower mtp-probe: bus: 1, device: 14 was not an MTP device 

This works:

Aug 25 19:09:26 tower kernel: [  761.299152] usb 1-5.2: new full-speed USB device number 21 using xhci_hcd Aug 25 19:09:27 tower kernel: [  761.414478] usb 1-5.2: New USB device found, idVendor=062a, idProduct=4102, bcdDevice=81.13 Aug 25 19:09:27 tower kernel: [  761.414483] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Aug 25 19:09:27 tower kernel: [  761.414486] usb 1-5.2: Product: 2.4G Wireless Mouse Aug 25 19:09:27 tower kernel: [  761.414489] usb 1-5.2: Manufacturer: MOSART Semi. Aug 25 19:09:27 tower kernel: [  761.420321] input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.0/0003:062A:4102.0013/input/input20 Aug 25 19:09:27 tower kernel: [  761.479523] input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.0/0003:062A:4102.0013/input/input21 Aug 25 19:09:27 tower kernel: [  761.481521] hid-generic 0003:062A:4102.0013: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Wireless Mouse] on usb-0000:00:14.0-5.2/input0 Aug 25 19:09:27 tower mtp-probe: checking bus 1, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2" Aug 25 19:09:27 tower mtp-probe: bus: 1, device: 21 was not an MTP device Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/mouse0) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) No input driver specified, ignoring this device. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) This device may have been added with another device file. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/mouse0) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) No input driver specified, ignoring this device. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) This device may have been added with another device file. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/event4) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: Applying InputClass "evdev pointer catchall" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: Applying InputClass "libinput pointer catchall" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Wireless Mouse' Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/event4) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (**) MOSART Semi. 2.4G Wireless Mouse: Applying InputClass "evdev pointer catchall" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (**) MOSART Semi. 2.4G Wireless Mouse: Applying InputClass "libinput pointer catchall" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Wireless Mouse' Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 47 paused 0 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: always reports core events Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) Option "Device" "/dev/input/event4" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) Option "_source" "server/udev" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 1 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) systemd-logind: releasing fd for 13:68 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: is tagged by udev as: Mouse Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: device is a pointer Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: device removed Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.0/0003:062A:4102.0013/input/input20/event4" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Wireless Mouse" (type: MOUSE, id 10) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) Option "AccelerationScheme" "none" Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: (accel) selected scheme none/0 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: (accel) acceleration factor: 2.000 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (**) MOSART Semi. 2.4G Wireless Mouse: (accel) acceleration threshold: 4 Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: is tagged by udev as: Mouse Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: device is a pointer Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/event5) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) No input driver specified, ignoring this device. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[3935]: (II) This device may have been added with another device file. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/event5) Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) No input driver specified, ignoring this device. Aug 25 19:09:27 tower /usr/lib/gdm3/gdm-x-session[2026]: (II) This device may have been added with another device file. Aug 25 19:09:27 tower mtp-probe: checking bus 1, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2" Aug 25 19:09:27 tower mtp-probe: bus: 1, device: 21 was not an MTP device 

Usb devices:

 T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=10 D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1 P:  Vendor=1d6b ProdID=0002 Rev=05.00 S:  Manufacturer=Linux 5.0.0-25-generic xhci-hcd S:  Product=xHCI Host Controller S:  SerialNumber=0000:00:14.0 C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub  T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh= 0 D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1 P:  Vendor=0bc2 ProdID=2100 Rev=00.00 S:  Manufacturer=Seagate S:  Product=FreeAgent S:  SerialNumber=2GE3CT36 C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I:  If#=0x0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage  T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  3 Spd=12  MxCh= 0 D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1 P:  Vendor=0d8c ProdID=0014 Rev=01.00 S:  Manufacturer=C-Media Electronics Inc. S:  Product=VTIN VNPA081AB C:  #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA I:  If#=0x0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none) I:  If#=0x1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none) I:  If#=0x2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none) I:  If#=0x3 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid  T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=03 Dev#=  4 Spd=480 MxCh= 4 D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1 P:  Vendor=2109 ProdID=2813 Rev=90.11 S:  Manufacturer=VIA Labs, Inc. S:  Product=USB2.0 Hub C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub  T:  Bus=01 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 14 Spd=12  MxCh= 0 D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1 P:  Vendor=046d ProdID=c52b Rev=12.03 S:  Manufacturer=Logitech S:  Product=USB Receiver C:  #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=98mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid I:  If#=0x2 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid  T:  Bus=01 Lev=02 Prnt=04 Port=01 Cnt=02 Dev#= 21 Spd=12  MxCh= 0 D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1 P:  Vendor=062a ProdID=4102 Rev=81.13 S:  Manufacturer=MOSART Semi. S:  Product=2.4G Wireless Mouse C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid  T:  Bus=01 Lev=02 Prnt=04 Port=02 Cnt=03 Dev#= 13 Spd=1.5 MxCh= 0 D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1 P:  Vendor=056e ProdID=00fe Rev=01.20 S:  Manufacturer=ELECOM S:  Product=ELECOM TrackBall Mouse C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid  T:  Bus=01 Lev=02 Prnt=04 Port=03 Cnt=04 Dev#= 18 Spd=1.5 MxCh= 0 D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1 P:  Vendor=413c ProdID=2113 Rev=01.08 S:  Product=Dell KB216 Wired Keyboard C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4 D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1 P:  Vendor=1d6b ProdID=0003 Rev=05.00 S:  Manufacturer=Linux 5.0.0-25-generic xhci-hcd S:  Product=xHCI Host Controller S:  SerialNumber=0000:00:14.0 C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub