Ubuntu - usb interface claimed or not

536 views
Skip to first unread message

Henning Skoglund

unread,
Feb 1, 2014, 6:57:20 AM2/1/14
to chromi...@chromium.org
I'm struggelig getting connection of the usb interface in Ubuntu 13.10. The application has called the onClaimed callback, but inspecting the

tail -f /var/log/syslog

gives

ThinkPad-T60 kernel: [ 8781.137407] usb 2-2: usbfs: process 7832 (Chrome_FileThre) did not claim interface 0 before use

lsusb | grep Dynastream

Bus 002 Device 017: ID 0fcf:1008 Dynastream Innovations, Inc. Mini stick Suunto

lsusb -v | grep Dynastream gives

ThinkPad-T60:~$ lsusb -v | grep Dynastream
Couldn't open device, some information will be missing
(repeated 6 times)
Bus 002 Device 017: ID 0fcf:1008 Dynastream Innovations, Inc. Mini stick Suunto
  idVendor           0x0fcf Dynastream Innovations, Inc.
  iManufacturer           1 Dynastream Innovations
Couldn't open device, some information will be missing


console.log from web app:

1391254636885 "Interface number 0 claimed" "in"
Object {address1direction"in"maximumPacketSize64pollingInterval1type"bulk"}
  1. address1
  2. direction"in"
  3. maximumPacketSize64
  4. pollingInterval1
  5. type"bulk"
  6. usage"data"
  7. __proto__Object
"out"
Object {address1direction"out"maximumPacketSize64pollingInterval1type"bulk"}


I've tried with usbmon and starting the app

sudo cat /sys/kernel/debug/usb/usbmon/2u >2u.mon.out

but the file is 0 bytes, so there is apparently nothing happening on bus 2

So I am in a situation where the interface seems to be claimed by the app, but really it not claimed libusbx/os. Anyone knows what might be the problem here, is there something about security (root vs normal user access to the device)?



Henning Skoglund

unread,
Feb 5, 2014, 3:14:06 AM2/5/14
to chromi...@chromium.org

After inspecting the log with dmesg I found that the linux kernel module suunto was loaded by default and somehow had claimed the interface. I added 'blacklist suunto' to /etc/modprobe.d/blacklist.conf and rebooted.


I've also added a check in the onClaimed callback for chrome.runtime.lastError which in this case the message was 'error claiming interface'

Reply all
Reply to author
Forward
0 new messages