Ryan Budney's questions

For the past few weeks I've been editing an Arduino device over USB. I performed a regular system update recently, and now the USB device is no longer recognised.

It's unclear to me what is at issue, since my other USB devices continue to be recognised. I have a USB external drive that is doing fine. A USB keyboard operates as usual, and a USB mouse.

But the Arduino isn't recognised. When I plug the Arduino in, regardless of which USB port I use, I get this in dmesg:

[  181.628764] usb 1-10.2: device descriptor read/64, error -32
[  181.816753] usb 1-10.2: device descriptor read/64, error -32
[  182.004728] usb 1-10.2: new full-speed USB device number 14 using xhci_hcd
[  182.084746] usb 1-10.2: device descriptor read/64, error -32
[  182.272745] usb 1-10.2: device descriptor read/64, error -32
[  182.380771] usb 1-10-port2: attempt power cycle
[  182.992684] usb 1-10.2: new full-speed USB device number 15 using xhci_hcd
[  182.992752] usb 1-10.2: Device not responding to setup address.
[  183.200753] usb 1-10.2: Device not responding to setup address.
[  183.408685] usb 1-10.2: device not accepting address 15, error -71
[  183.488682] usb 1-10.2: new full-speed USB device number 16 using xhci_hcd
[  183.488751] usb 1-10.2: Device not responding to setup address.
[  183.696738] usb 1-10.2: Device not responding to setup address.
[  183.904671] usb 1-10.2: device not accepting address 16, error -71
[  183.904753] usb 1-10-port2: unable to enumerate USB device

So it's clear the computer knows the USB device is there, it's just having trouble assigning the USB device an address.

As you might expect, the device does not appear in lsusb.

You may ask, perhaps it's the Arduino circuit. But I have tried several other Arduino devices that were working before today, and none of them are recognised over USB.

You mas ask, perhaps its the USB cable, or perhaps the USB port I'm using. But if I connect a USB keyboard to this cable and port, the keyboard works.

Similarly, my tablet that's running the same version of Ubuntu (20.04) and is also up to date, is having the same problem.

Ideas?

I have a little headless audio server runing LUbuntu. It always had the occasional wifi problem -- seemingly not able to connect. Usually I would reboot the system and the problem would go away. With the upgrade to LUbuntu 19.10, the problem seems to be more persistent. Maybe 1 out of 2 reboots the WIFI will not work.

Here is the output of wireless-info when the wifi is connected.

https://paste.ubuntu.com/p/wQnckTYmyw/

Any idea what might be causing this intermittent wifi? If the wifi is up, it stays up. If the machine boots and the wifi is down, there appears to be nothing I can do to get it to connect, other than a reboot.

Perhaps this is relevant: I have my wifi router assign a static IP address to this machine. Perhaps I need to tell the machine that?

lspci -knn | grep Net -A3 output:

01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179] (rev 01)
    Subsystem: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179]
    Kernel driver in use: rtl8188ee
    Kernel modules: rtl8188ee

02:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
    Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer I211 Gigabit Network Connection [1297:4034]
    Kernel driver in use: igb
    Kernel modules: igb

rfkill list output:

0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

I recently performed a kernel upgrade on my tablet, going from 4.15.0-50 to 4.15.0-51. On reboot, it dropped to busybox. The system did not seem to know about my encrypted hard drive -- i.e. it had nothing to do.

Does anyone know if this is a peculiarity of the new kernel, or what might have caused this boot up problem? I can still boot to 4.15.0-50, so my initial inclination is to wait out 0-51, and hope the problem is fixed in future kernel updates.

Does anyone know if this is a peculiarity of my own system, or perhaps the system update will break anyone's configuration that uses an encrypted hard drive?

I performed the most recent kernel update on my Dell 5290 2-in-1 earlier today. But moments after I plug it into its docking station, the screen flickers, blanks and freezes. The only item left on the screen is the mouse pointer, and it is stuck.

If I leave the tablet not plugged in, it runs just fine. It seems to be the docking station that triggers the freeze.

That said, I can log into the tablet via ssh even with the screen frozen. So the system is still running. But if I try to reboot the tablet via the reboot command, nothing appears to happen. sudo reboot -f will reboot the system, while sudo reboot will not.

Any ideas where I should start looking to identify this problem?

I've been having trouble getting gparted to run. I'd like to format a usb stick. . . but when I attempt to load gparted it endlessly cycles through "scanning all devices". This is a fresh Ubuntu 18.04 install on a Dell Latitude 5290, in case that helps.

Gparted does the same regardless of the usb stick being inserted or not.

When I run gparted from "sudo gparted" the output is:

Unit -.mount does not exist, proceeding anyway
Gtk-Message: 12:31:43.801: Failed to load module "canberra-gtk-module"
==============
libparted: 3.2
==============

The GUI comes up with the scanning animation on the bottom bar. And that's all that happens.

edit:

I should add, this is not just a gparted problem. When I run "sudo fdisk -l", fdisk starts listing my drives, but when it gets to /dev/sdc it freezes. Even a ^c won't get me out of fdisk. "sudo killall fdisk" does not kill the fdisk task.

The "Disks" GUI application often does not load. Attempting to run it from the command line results in the error message "GNOME-Disks-ERROR **: Error getting udisks client: Timeout was reached Trace/breakpoint trap"

When I use the gnome-disks utility to format the usb drive it gives me:

Error creating file system: Command-line `parted --script "/dev/sdd" mktable msdos' exited with non-zero exit status 1: Error: Input/output error during read on /dev/sdd
Error: Input/output error during write on /dev/sdd
 (udisks-error-quark, 0)

edit 2: I managed to get gparted to load with the usb drive inserted on one of my old LUbuntu 16.04 boxes. gparted spews out a lot of warnings. The "information" panel for /dev/sdd (it calls it sdd now) says:

/dev/sdd: unrecognised disk label
Input/output error during read on /dev/sdd

I recently installed Ubuntu 18.04 on a Dell Latitude 5290 2-in-1 tablet. The only element of the hardware I haven't been able to get Ubuntu to recognise is the video cameras. Judging from this thread my guess is perhaps there is no support at this time.

Is that right?

Here is my lspci

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
00:05.0 Multimedia controller: Intel Corporation Skylake Imaging Unit (rev 01)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:14.3 Multimedia controller: Intel Corporation Device 9d32 (rev 01)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:16.3 Serial controller: Intel Corporation Device 9d3d (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
02:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
02:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
02:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
02:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
37:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02)
6c:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
6d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)

and lsusb:

lsusb
Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. 
Bus 004 Device 002: ID 0424:5807 Standard Microsystems Corp. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 1532:0050 Razer USA, Ltd 
Bus 003 Device 003: ID 0bda:4014 Realtek Semiconductor Corp. 
Bus 003 Device 002: ID 0424:2807 Standard Microsystems Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 002: ID 044e:1218 Alps Electric Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

hwinfo --usb

03: USB 00.0: 10503 USB Mouse                                   
  [Created at usb.122]
  Unique ID: POWV.+uuvZOpekiC
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0
  SysFS BusID: 1-9:1.0
  Hardware Class: mouse
  Model: "USB Dongle for Razer Lancehead"
  Hotplug: USB
  Vendor: usb 0x1532 "Razer USA, Ltd"
  Device: usb 0x005a "USB Dongle for Razer Lancehead"
  Revision: "2.00"
  Compatible to: int 0x0210 0x0015
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event5, /dev/input/by-id/usb-Razer_USB_Dongle_for_Razer_Lancehead-event-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:9:1.0-event-mouse, /dev/input/by-id/usb-Razer_USB_Dongle_for_Razer_Lancehead-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:9:1.0-mouse
  Device Number: char 13:63 (char 13:32)
  Speed: 12 Mbps
  Module Alias: "usb:v1532p005Ad0200dc00dsc00dp00ic03isc01ip02in00"
  Driver Info #0:
    Buttons: 5
    Wheels: 1
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

04: USB 00.1: 0401 Multimedia audio controller
  [Created at usb.122]
  Unique ID: JKDt.A+UETb5j1v1
  Parent ID: KRJj.mzrV6H7iCbA
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb3/3-1/3-1.5/3-1.5:1.1
  SysFS BusID: 3-1.5:1.1
  Hardware Class: sound
  Model: "Realtek USB Audio"
  Hotplug: USB
  Vendor: usb 0x0bda "Realtek Semiconductor Corp."
  Device: usb 0x4014 "USB Audio"
  Revision: "0.05"
  Serial ID: "200901010001"
  Driver: "snd-usb-audio"
  Driver Modules: "snd_usb_audio"
  Speed: 480 Mbps
  Module Alias: "usb:v0BDAp4014d0005dc00dsc00dp00ic01isc02ip00in01"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #11 (Hub)

05: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: cLrx.E1ssW4L74M7
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
  SysFS BusID: 1-2:1.0
  Hardware Class: mouse
  Model: "Alps Electric Alps Touchpad"
  Hotplug: USB
  Vendor: usb 0x044e "Alps Electric Co., Ltd"
  Device: usb 0x1218 "Alps Touchpad"
  Revision: "6.05"
  Compatible to: int 0x0210 0x0001
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event12, /dev/input/by-id/usb-Alps_Alps_Touchpad-event-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:2:1.0-event-mouse, /dev/input/by-id/usb-Alps_Alps_Touchpad-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:2:1.0-mouse
  Device Number: char 13:63 (char 13:33)
  Speed: 12 Mbps
  Module Alias: "usb:v044Ep1218d0605dc00dsc00dp00ic03isc01ip02in00"
  Driver Info #0:
    Buttons: 1
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

06: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: uIhY.dFBsQFTOFD6
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb3/3-0:1.0
  SysFS BusID: 3-0:1.0
  Hardware Class: hub
  Model: "Linux Foundation 2.0 root hub"
  Hotplug: USB
  Vendor: usb 0x1d6b "Linux Foundation"
  Device: usb 0x0002 "2.0 root hub"
  Revision: "4.15"
  Serial ID: "0000:37:00.0"
  Driver: "hub"
  Driver Modules: "usbcore"
  Speed: 480 Mbps
  Module Alias: "usb:v1D6Bp0002d0415dc09dsc00dp01ic09isc00ip00in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

07: USB 00.0: 0200 Ethernet controller
  [Created at usb.122]
  Unique ID: EEKG.xnYl+YUVZVC
  Parent ID: PYMB.WSevIRkAXq9
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1.2/4-1.2:1.0
  SysFS BusID: 4-1.2:1.0
  Hardware Class: network
  Model: "Realtek RTL8153 Gigabit Ethernet Adapter"
  Hotplug: USB
  Vendor: usb 0x0bda "Realtek Semiconductor Corp."
  Device: usb 0x8153 "RTL8153 Gigabit Ethernet Adapter"
  Revision: "30.11"
  Serial ID: "000002000000"
  Driver: "r8152"
  Driver Modules: "r8152"
  Device File: enxe4b97ac6387a
  HW Address: e4:b9:7a:c6:38:7a
  Permanent HW Address: e4:b9:7a:c6:38:7a
  Link detected: no
  Module Alias: "usb:v0BDAp8153d3011dc00dsc00dp00icFFiscFFip00in00"
  Driver Info #0:
    Driver Status: r8152 is active
    Driver Activation Cmd: "modprobe r8152"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #15 (Hub)

08: USB 00.1: 0000 Unclassified device
  [Created at usb.122]
  Unique ID: sZmZ.F1ZquY2RN29
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1
  SysFS BusID: 1-9:1.1
  Hardware Class: unknown
  Model: "USB Dongle for Razer Lancehead"
  Hotplug: USB
  Vendor: usb 0x1532 "Razer USA, Ltd"
  Device: usb 0x005a "USB Dongle for Razer Lancehead"
  Revision: "2.00"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/event6
  Device Files: /dev/input/event6, /dev/input/by-id/usb-Razer_USB_Dongle_for_Razer_Lancehead-if01-event-kbd, /dev/input/by-path/pci-0000:00:14.0-usb-0:9:1.1-event-kbd
  Device Number: char 13:70
  Speed: 12 Mbps
  Module Alias: "usb:v1532p005Ad0200dc00dsc00dp00ic03isc00ip01in01"
  Driver Info #0:
    Driver Status: usbhid is active
    Driver Activation Cmd: "modprobe usbhid"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

10: USB 00.0: 11500 Bluetooth Device
  [Created at usb.122]
  Unique ID: X7GA.GS0ueMFUyi1
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0
  SysFS BusID: 1-7:1.0
  Hardware Class: bluetooth
  Model: "Intel Bluetooth Device"
  Hotplug: USB
  Vendor: usb 0x8087 "Intel Corp."
  Device: usb 0x0a2b 
  Revision: "0.10"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v8087p0A2Bd0010dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

11: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: KRJj.mzrV6H7iCbA
  Parent ID: uIhY.dFBsQFTOFD6
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb3/3-1/3-1:1.0
  SysFS BusID: 3-1:1.0
  Hardware Class: hub
  Model: "Standard Microsystems USB2807 Hub"
  Hotplug: USB
  Vendor: usb 0x0424 "Standard Microsystems Corp."
  Device: usb 0x2807 "USB2807 Hub"
  Revision: "2.04"
  Driver: "hub"
  Driver Modules: "usbcore"
  Speed: 480 Mbps
  Module Alias: "usb:v0424p2807d0204dc09dsc00dp02ic09isc00ip02in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #6 (Hub)

12: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: zPk0.WbJ3tCF4BRF
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-0:1.0
  SysFS BusID: 4-0:1.0
  Hardware Class: hub
  Model: "Linux Foundation 3.0 root hub"
  Hotplug: USB
  Vendor: usb 0x1d6b "Linux Foundation"
  Device: usb 0x0003 "3.0 root hub"
  Revision: "4.15"
  Serial ID: "0000:37:00.0"
  Driver: "hub"
  Driver Modules: "usbcore"
  Module Alias: "usb:v1D6Bp0003d0415dc09dsc00dp03ic09isc00ip00in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

14: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-0:1.0
  SysFS BusID: 1-0:1.0
  Hardware Class: hub
  Model: "Linux Foundation 2.0 root hub"
  Hotplug: USB
  Vendor: usb 0x1d6b "Linux Foundation"
  Device: usb 0x0002 "2.0 root hub"
  Revision: "4.15"
  Serial ID: "0000:00:14.0"
  Driver: "hub"
  Driver Modules: "usbcore"
  Speed: 480 Mbps
  Module Alias: "usb:v1D6Bp0002d0415dc09dsc00dp01ic09isc00ip00in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

15: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: PYMB.WSevIRkAXq9
  Parent ID: zPk0.WbJ3tCF4BRF
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1:1.0
  SysFS BusID: 4-1:1.0
  Hardware Class: hub
  Model: "Standard Microsystems USB5807 Hub"
  Hotplug: USB
  Vendor: usb 0x0424 "Standard Microsystems Corp."
  Device: usb 0x5807 "USB5807 Hub"
  Revision: "2.04"
  Driver: "hub"
  Driver Modules: "usbcore"
  Module Alias: "usb:v0424p5807d0204dc09dsc00dp03ic09isc00ip00in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (Hub)

16: USB 00.2: 10800 Keyboard
  [Created at usb.122]
  Unique ID: Jl0e.WwTgX0FrS+E
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2
  SysFS BusID: 1-9:1.2
  Hardware Class: keyboard
  Model: "USB Dongle for Razer Lancehead"
  Hotplug: USB
  Vendor: usb 0x1532 "Razer USA, Ltd"
  Device: usb 0x005a "USB Dongle for Razer Lancehead"
  Revision: "2.00"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/event7
  Device Files: /dev/input/event7, /dev/input/by-id/usb-Razer_USB_Dongle_for_Razer_Lancehead-if02-event-kbd, /dev/input/by-path/pci-0000:00:14.0-usb-0:9:1.2-event-kbd
  Device Number: char 13:71
  Speed: 12 Mbps
  Module Alias: "usb:v1532p005Ad0200dc00dsc00dp00ic03isc01ip01in02"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

19: USB 00.0: 10a00 Hub
  [Created at usb.122]
  Unique ID: pBe4.xYNhIwdOaa6
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb2/2-0:1.0
  SysFS BusID: 2-0:1.0
  Hardware Class: hub
  Model: "Linux Foundation 3.0 root hub"
  Hotplug: USB
  Vendor: usb 0x1d6b "Linux Foundation"
  Device: usb 0x0003 "3.0 root hub"
  Revision: "4.15"
  Serial ID: "0000:00:14.0"
  Driver: "hub"
  Driver Modules: "usbcore"
  Module Alias: "usb:v1D6Bp0003d0415dc09dsc00dp03ic09isc00ip00in00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

The webcam goes by the label
Realtek Semiconductor Co., Ltd. Integrated_Webcam_HD but I haven't found much regarding what drivers might be needed, or if drivers are needed at all. I don't see a key combination on the tablet to activate the camera.

Dell appears to have a guide for Ubuntu.

edit: I contacted Dell customer support and they believe there are no drivers for the 5290 2-in-1 webcams for Linux. Ah well. I'll use it without the webcams for now.

I'm attempting to build mpd from source to replace Ubuntu's rather old distribution of mpd. I've been having trouble with the recent upgrade to 0.19.12 in the Ubuntu distribution, and wanted to check if it was an old bug that has been fixed -- the current mpd is 0.20.15.

I can build mpd from source but now I'd like to install it using the same set-up that Ubuntu does, when its installed from the Ubuntu package. So I've been trying to read the package build log for the Ubuntu package and I've been having some trouble.

Where does one find in the package build log the items such as:

1. When the mpd user is created.
2. When the audio group is created.
3. When permissions are set on the new directories, and new directories created.
4. When the mpd daemon is set-up.

Where in the package log does one find that information? When I "sudo make install" from source it does not do any of these things, so I'm assuming these items must be elsewhere.

A natural thing one might consider is to read the mpd documentation. As far as I can tell, it does not go into these kinds of details.

I am attempting to control my stereo from my Android phone, using mpd. I have an Ubuntu 16.04 box hooked up to the stereo system, via a USB -> Toslink -> DSP -> amps route. I am trying to drive jackd through the mpd daemon. . . and I am having some troubles.

So far I have been able to:

1) Get mpd to play music locally on my Ubuntu box. MPDroid (on my phone) works fine with mpd at this level, driving the music on my Ubuntu box.

2) Drive my stereo system through jack from the Ubuntu box, using jack-plumbing and mplayer.

I strongly suspect my problem is I do not understand what mpd.conf needs to drive jack.

Here is my current mpd.conf audio_output section:

audio_output {
    type      "jack"
    name      "my JACK device"
    device    "hw:1,0"
    autostart "yes"
    destination_ports "playback_9, playback_10"
}

I chose destination_ports 9 and 10 because this is producing a Toslink signal. But I strongly suspect that's what I've formatted incorrectly.

and the version that plays locally:

audio_output {
    type            "alsa"
    name            "My ALSA Device"
    device          "hw:0,0"        # optional
    mixer_type      "hardware"      # optional
    mixer_device    "default"       # optional
    mixer_control   "PCM"           # optional
    mixer_index     "0"             # optional
}

Here are a few things that will likely help. jack-plumbing works fine for piping mplayer output to my usb-audio device. The .jack-plumbing file that works is:

(connect "MPlayer \[[0-9]+\]:out_0" "system:playback_9")
(connect "MPlayer \[[0-9]+\]:out_1" "system:playback_10")

aplay -l output:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]  
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: USBStreamer [USBStreamer], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I've found the documentation available for mpd online a little difficult to read, and it tends to get a little vague when it comes to using it with jackd. Any advice? I imagine I'm making a pretty simple mistake. Thanks for any help.

edit: with the "jack" version of mpd.conf in /etc/mpd.conf, I get this as output to the "sudo systemctl status mpd" command:

● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; disabled; vendor preset: enabled)
   Active: active (running) since Sun 2016-07-03 23:58:34 PDT; 52s ago
 Main PID: 3651 (mpd)
   CGroup: /system.slice/mpd.service
       └─3651 /usr/bin/mpd --no-daemon

Jul 03 23:58:34 rybu-ThinkPad-W530 systemd[1]: Started Music Player Daemon.
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: "channels=2"): initialization failed.
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] main.c: Module load failed.
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jul 03 23:58:38 rybu-ThinkPad-W530 pulseaudio[3665]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.177" (uid=122 pid=3665 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1018 comm="/usr/lib/bluetooth/bluetoothd ")

I suppose I should mention one other thing. After installing mpd, my system boot times have become significantly slower. Sometimes it looks like the computer is doing nothing, so I reboot the system again. Sometimes it takes 3 reboots before I can get to the login prompt.

edit 2: Perhaps I can solve this problem by avoiding jack entirely. Here is the /var/lib/alsa/asound.state file, the portion relevant to my usbaudio device:

state.USBStreamer {
control.1 {
    iface PCM
    name 'Playback Channel Map'
    value.0 0
    value.1 0
    value.2 0
    value.3 0
    value.4 0
    value.5 0
    value.6 0
    value.7 0
    value.8 0
    value.9 0
    comment {
        access read
        type INTEGER
        count 10
        range '0 - 36'
    }
}
control.2 {
    iface PCM
    name 'Capture Channel Map'
    value.0 0
    value.1 0
    value.2 0
    value.3 0
    value.4 0
    value.5 0
    value.6 0
    value.7 0
    value.8 0
    value.9 0
    comment {
        access read
        type INTEGER
        count 10
        range '0 - 36'
    }
}
control.3 {
    iface MIXER
    name 'USBStreamer Output Playback Switch'
    value.0 true
    value.1 true
    value.2 true
    value.3 true
    value.4 true
    value.5 true
    value.6 true
    value.7 true
    value.8 true
    value.9 true
    comment {
        access 'read write'
        type BOOLEAN
        count 10
    }
}
control.4 {
    iface MIXER
    name 'USBStreamer Output Playback Switch'
    index 1
    value true
    comment {
        access 'read write'
        type BOOLEAN
        count 1
    }
}
control.5 {
    iface MIXER
    name 'USBStreamer Output Playback Volume'
    value.0 255
    value.1 255
    value.2 255
    value.3 255
    value.4 255
    value.5 255
    value.6 255
    value.7 255
    value.8 255
    value.9 255
    comment {
        access 'read write'
        type INTEGER
        count 10
        range '0 - 255'
        dbmin -12750
        dbmax 0
        dbvalue.0 0
        dbvalue.1 0
        dbvalue.2 0
        dbvalue.3 0
        dbvalue.4 0
        dbvalue.5 0
        dbvalue.6 0
        dbvalue.7 0
        dbvalue.8 0
        dbvalue.9 0
    }
}
control.6 {
    iface MIXER
    name 'USBStreamer Output Playback Volume'
    index 1
    value 152
    comment {
        access 'read write'
        type INTEGER
        count 1
        range '0 - 255'
        dbmin -12750
        dbmax 0
        dbvalue.0 -5150
    }
}
control.7 {
    iface MIXER
    name 'USBStreamer Clock Selector'
    value 'USBStreamer Internal Clock'
    comment {
        access 'read write'
        type ENUMERATED
        count 1
        item.0 'USBStreamer Internal Clock'
        item.1 'USBStreamer TOSLINK Clock'
    }
}
control.8 {
    iface MIXER
    name 'Mic Capture Switch'
    value.0 true
    value.1 true
    value.2 true
    value.3 true
    value.4 true
    value.5 true
    value.6 true
    value.7 true
    value.8 true
    value.9 true
    comment {
        access 'read write'
        type BOOLEAN
        count 10
    }
}
control.9 {
    iface MIXER
    name 'Mic Capture Switch'
    index 1
    value true
    comment {
        access 'read write'
        type BOOLEAN
        count 1
    }
}
control.10 {
    iface MIXER
    name 'Mic Capture Volume'
    value.0 255
    value.1 255
    value.2 255
    value.3 255
    value.4 255
    value.5 255
    value.6 255
    value.7 255
    value.8 255
    value.9 255
    comment {
        access 'read write'
        type INTEGER
        count 10
        range '0 - 255'
        dbmin -12750
        dbmax 0
        dbvalue.0 0
        dbvalue.1 0
        dbvalue.2 0
        dbvalue.3 0
        dbvalue.4 0
        dbvalue.5 0
        dbvalue.6 0
        dbvalue.7 0
        dbvalue.8 0
        dbvalue.9 0
    }
}
control.11 {
    iface MIXER
    name 'Mic Capture Volume'
    index 1
    value 255
    comment {
        access 'read write'
        type INTEGER
        count 1
        range '0 - 255'
        dbmin -12750
        dbmax 0
        dbvalue.0 0
    }
}

If I'm reading that correctly it looks like perhaps the relevant audio output channels are muted? Channels 8 and 9 are the ones relevant for audio output over a Toslink cable, so I suspect I need to modify those values and perhaps I can do a direct ALSA output from mpd.

Strangely, if I delete asound.state and then re-create it with a "sudo alsactl store" command, the channel mapping is completely different:

state.USBStreamer {
    control.1 {
            iface PCM
            name 'Playback Channel Map'
            value.0 3
            value.1 4
            value.2 7
            value.3 8
            value.4 5
            value.5 6
            value.6 12
            value.7 13
            value.8 11
            value.9 9
            comment {
                    access read
                    type INTEGER
                    count 10 
                    range '0 - 36'
            }
    }

But it still produces no sound.

Another thing I'm considering is that since JACK can play to my usbstreamer, and it is using ALSA, so perhaps I can just figure out what settings its using with ALSA, and duplicate them. The /proc/asound/card1 directory has the current settings for this card, so I start it playing with jack and mplayer, and read off the files.

stream0:

miniDSP USBStreamer at usb-0000:00:14.0-2, high speed : USB Audio

Playback:
  Status: Running
    Interface = 1
    Altset = 1
    Packet Size = 280
    Momentary freq = 44100 Hz (0x5.8330)
    Feedback Format = 16.16
  Interface 1
    Altset 1
    Format: S32_LE
    Channels: 10
    Endpoint: 1 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000
    Data packet interval: 125 us

Capture:
  Status: Running
    Interface = 2
    Altset = 1
    Packet Size = 280
    Momentary freq = 44100 Hz (0x5.8333)
  Interface 2
    Altset 1
    Format: S32_LE
    Channels: 10
    Endpoint: 2 IN (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000
    Data packet interval: 125 us

usbbus:

003/005

usbmixer:

USB Mixer: usb_id=0x27520016, ctrlif=0, ctlerr=0
 Card: miniDSP USBStreamer at usb-0000:00:14.0-2, high speed
  Unit: 10
Control: name="USBStreamer Output Playback Volume", index=1
Info: id=10, control=2, cmask=0x0, channels=1, type="S16"
Volume: min=-32640, max=0, dBmin=-12750, dBmax=0
Unit: 10
Control: name="USBStreamer Output Playback Volume", index=0
Info: id=10, control=2, cmask=0x3ff, channels=10, type="S16"
Volume: min=-32640, max=0, dBmin=-12750, dBmax=0
Unit: 10
Control: name="USBStreamer Output Playback Switch", index=1
Info: id=10, control=1, cmask=0x0, channels=1, type="INV_BOOLEAN"
Volume: min=0, max=1, dBmin=0, dBmax=0
Unit: 10
Control: name="USBStreamer Output Playback Switch", index=0
Info: id=10, control=1, cmask=0x3ff, channels=10, type="INV_BOOLEAN"
Volume: min=0, max=1, dBmin=0, dBmax=0
Unit: 11
Control: name="Mic Capture Volume", index=1
Info: id=11, control=2, cmask=0x0, channels=1, type="S16"
Volume: min=-32640, max=0, dBmin=-12750, dBmax=0
Unit: 11
Control: name="Mic Capture Volume", index=0
Info: id=11, control=2, cmask=0x3ff, channels=10, type="S16"
Volume: min=-32640, max=0, dBmin=-12750, dBmax=0
Unit: 11
Control: name="Mic Capture Switch", index=1
Info: id=11, control=1, cmask=0x0, channels=1, type="INV_BOOLEAN"
Volume: min=0, max=1, dBmin=0, dBmax=0
Unit: 11
Control: name="Mic Capture Switch", index=0
Info: id=11, control=1, cmask=0x3ff, channels=10, type="INV_BOOLEAN"
Volume: min=0, max=1, dBmin=0, dBmax=0
Unit: 40
Control: name="USBStreamer Clock Selector", index=0
Info: id=40, control=1, cmask=0x0, channels=1, type="U8"
Volume: min=1, max=2, dBmin=0, dBmax=0

pcm0p/info:

card: 1
device: 0
subdevice: 0
stream: PLAYBACK
id: USB Audio
name: USB Audio
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0

pcm0p/sub0/hw_params:

access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 10
rate: 44100 (44100/1)
period_size: 1024
buffer_size: 2048

pcm0p/sub0/info

card: 1
device: 0
subdevice: 0
stream: PLAYBACK
id: USB Audio
name: USB Audio
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0

pcm0p/sub0/status

state: RUNNING
owner_pid   : 12545
trigger_time: 50245.966761737
tstamp      : 0.000000000
delay       : 2010
avail       : 72
avail_max   : 1029
----- 
hw_ptr      : 325870664
appl_ptr    : 325872640

pcm0p/sub0/sw_params:

tstamp_mode: NONE
period_step: 1
avail_min: 1024
start_threshold: 0
stop_threshold: 2048
silence_threshold: 0
silence_size: 0
boundary: 4611686018427387904

Hmm, if the information on channels is in there, it's cleverly hidden!

Volker Schatz describes setting up an ALSA device to switch channels. It looks like it's done a different way than just playing around with the playback channel map:

http://www.volkerschatz.com/noise/alsa.html

The ttable appears to be a device for channel mixing, and if you use integer entries (0 and 1), for channel switching. Finally this is starting to make sense. The i.j notation are pairs coordinates, describing the entries of a square matrix.

edit: Some progress. The "aplay -L" command gives a list of device names. For this usbstreamer, it gives:

sysdefault:CARD=USBStreamer
USBStreamer, USB Audio
Default Audio Device
front:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
Front speakers
surround21:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
Direct sample mixing device
dsnoop:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
Direct sample snooping device
hw:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
Direct hardware device without any conversions
plughw:CARD=USBStreamer,DEV=0
USBStreamer, USB Audio
Hardware device with all software conversions

These device names are very handy, from here you can run the command:

speaker-test -c 10 -t sin -F S32_LE -D front:USBStreamer

which runs through all the speakers on that device. Channels 8 and 9 (as expected) produce the sin wave sound on the left and right speakers respectively.

So I think this means I should be able to get direct ALSA output to my speakers using a ttable construction in asound.state. I would imagine the Playback Channel Map might allow for this as well, but after quite a bit of fiddling-around with it, it's unclear to me how to make it work.

update:

I modified the control.1 portion of the asound.state file to be:

control.1 {
            iface PCM
            name 'Playback Channel Map'
            value.0 0
            value.1 0
            value.2 0
            value.3 0
            value.4 0
            value.5 0
            value.6 0
            value.7 0
            value.8 3
            value.9 4
            comment {
                    access read
                    type INTEGER
                    count 10 
                    range '0 - 36'
            }
    }

and it almost works. Mplayer will not play to alsa:device=hw=1.0 but the error message is that I'm sending the wrong format to the device. ALSA thinks the device only accepts S32LE. Technically, I think it's an S24LE device. I'll contact the manufacturer to clear this up.

So I add -format s32le to the mplayer command line and stuff comes out of the speakers! Only, it's a bit of a jumble. It's playing too fast and. . . something else is going on. There's some kind of frequency distortion. I suspect what's happening is it's sending s16le data as if it's s32le data, so there's a bit of a shuffling (temporally) of the data, and a pitch-shift, and it's playing too fast.

So now to get this working I need to know how to convers the s16le data to proper s24le, and then format it as s32le so the usb device is happy.

update:

speaker-test -c 10 -t sin -D plughw:USBStreamer

works fine, and converts S16_LE to S32_LE.

Unfortunately,

aplay -Dplughw:USBStreamer ./blah.wav

does not work. Perhaps the channel mapping is off for this device?

The Deadbeef software plays to the usbstreamer with little effort. I give it the hw:USBStreamer device, and tell it to do all 8->16->24 bit conversions and it works like a charm.

Has anyone had success streaming music via a miniDSP usbstreamer b unit?

I'm attempting to cut out an extraneous digital->analogue conversion in my laptop-powered stereo system. The usbstreamer b unit would allow my stereo to do just a single digital to analogue conversion. Hopefully there is a way to make it compatible with Linux.

Ubuntu 16.04 recognises the unit and can be configured to send audio to it. But the usbstreamer does not appear to be generating a toslink signal, so I suspect Ubuntu is sending the wrong data to the usbstreamer.

I've set the firmware on the usbstreamer to toslink, using a windows box.

edit (July 1st 1016): I can get some sound to broadcast from my laptop. If I run the ALSA test wav files through aplay, they play. But I can't get any other sound to broadcast to the usbstreamer.

Does anyone know what this is a symptom of? aplay works, but no other system sounds get broadcast? In particular I would like to get to the point where I could get software like Rythmbox to play via the streamer. For example, in the "Sound Settings" dialogue (Ubuntu default) if I set output to USBStreamer, this results in none of the system sounds being sent to usbstreamer -- or at least, not in a way that the streamer can understand. Because they don't play.

Here is what I have done that has been successful:

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: USBStreamer [USBStreamer], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0

aplay -D plughw:1,0 /usr/share/sounds/alsa/Side_Left.wav

After some googling around it appears the usb-audio driver needs some setting up. ALSA sees the usbstreamer, but it looks like Ubuntu has no ready-made driver and ?perhaps? something can be cobbled-together with the usb-audio driver. It looks like I might have to set up an .asoundrc file. These pages seem particularly relevant:

https://help.ubuntu.com/community/UbuntuStudio/UsbAudioDevices

http://www.alsa-project.org/main/index.php/Matrix:Module-usb-audio

edit 2:

Finally, I'm playing music with mplayer, from my linux laptop to my speakers, via the usbstreamer and minidsp 4x10hd unit.

The key thing I did not understand is it's better not to use pulseaudio with high-end speakers. . . and the Linux community figured that out long ago. So they developed a distinct audio interface, called Jack.

I haven't figured out all the quirks yet, but the "Jack audio connection kit" has a nice GUI for setting up the audio interface. mplayer will stream straight to jack.

So all my music appears to play fine, now. Hmm, likely I'll have to rip all my music at a higher sample rate, now...

Once I have everything working smoothly I'll post something that is hopefully easier to follow, perhaps as an answer.

I have a USB device that is likely a CAN bus and I'm trying to interact with it. I'm wondering if anyone can offer any advice for probing and discovering what services are available. I suppose a good place to start would be to check whether or not its actually a CAN bus. I'm not certain how to do that, though.

Specifically, I'm plugged into the USB interface for a DJI Phantom quad copter. It's a small autonomous drone.

Here's what I have so far:

If I call lsusb with the drone plugged in and powered-up,

Bus 003 Device 003: ID fff0:0008

is new. lsusb -vvv gives the further details:

Bus 003 Device 003: ID fff0:0008
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0xfff0
  idProduct          0x0008
  bcdDevice            1.00
  iManufacturer           1 DJI  CONFIF
  iProduct                2 DJI    CONTROLLER
  iSerial                 3 0001A0000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           75
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       0 None
      iFunction               4 VCOM
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      0 None
      iInterface              4 VCOM
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               2
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface              4 VCOM
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

if I call udevadm and remove the quad copter's USB cable, I get:

UDEV  [41256.502177] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/tty/ttyACM0 (tty)
UDEV  [41256.502247] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1 (usb)
UDEV  [41256.502286] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0 (usb)
UDEV  [41256.502346] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-2 (usb)`

and when I plug it in...

`UDEV  [41261.068689] add      /devices/pci0000:00/0000:00:14.0/usb3/3-2 (usb)
UDEV  [41261.070265] add      /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0 (usb)
UDEV  [41261.071507] add      /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1 (usb)
UDEV  [41261.072843] add      /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/tty/ttyACM0 (tty)

So I try to treat it like a CAN bus interface. It seems okay with the command:

sudo slcand -o -s6 -t hw -S 1000000 /dev/ttyACM0

i.e. no error messages, and

sudo ip link set up slcan0

creates the network interface slcan0 and ifconfig now shows:

slcan0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

From this can anyone tell if this is really a CAN bus I'm interacting with? Or am I walking down the wrong path?

Possible Duplicate:
Software center not opening

I'd like to look at the Ubuntu Software Center configuration files, to check and see if there's a simple reason why the package appears to be partly broken. Does anyone know where they should be, on a standard, just-installed-yesterday from a formatted harddrive Ubuntu 12.04 install?

All the features of software-center work, except syncing between computers. I think there might be a user name or password problem, or some simple problem identifying my other computers. I can't tell without more information.

In short, sometimes my other computers appear on the list in the sync menu in software-center. Sometimes they don't. And when they do appear, I do not get a package list for the other installs when I click on them.

When running software-center from the command line I get this message:

software-center 2012-05-23 13:52:06,630 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 'None' 2012-05-23 13:52:06,637 - softwarecenter.db.database - INFO - open() database: path=None use_axi=True use_agent=True 2012-05-23 13:52:06,854 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file 2012-05-23 13:52:07,237 - softwarecenter.db.pkginfo_impl.aptcache - INFO - aptcache.open()

I suspect the "no username in config file" is pointing to the key problem. How do I fix it?

Other related discussions:

Ubuntu Forums Thread

How can I sync application between multiple computers?

edit: Going on Eliah Kagan's comments, I ran:

cd ~/.config; rm -r software-center

and

sudo apt-get --purge --reinstall install software-center 

on my computers... and everything is exactly the same. There are no other computers listed to sync with, the "no username in config file" message is still there, etc. No improvement with the symptoms.

And my ~/.config/software-center/softwarecenter.cfg file looks like this. Should it?

[general] 
maximized = False
size = 871, 536 
add_to_launcher = True
recommender_uuid =  
recommender_profile_id =

The more I google-around the more I see other people have the same blank entries in their softwarecenter.cfg file, so I suspect this isn't the problem. Perhaps its my user account on the Ubuntu servers. How would I check that this isn't the source of the problem?

edit2: Perhaps logging out of Ubuntu Software Center here https://login.ubuntu.com/+applications and re logging in might help, technically, "Deleting" then running Software Center to re-launch the Application. Hmm, no this doesn't seem to have any effect. Still only the local computer is listed.

It's strange because yesterday my other computers were listed before I clicked on the "stop syncing" option. I can't seem to get them to come back up.