Re: what is sitting on USB device?
- Date: Tue, 23 Oct 2018 11:35:59 -0500
- From: Mark Copper <mcopper@xxxxxxxxxxxxxx>
- Subject: Re: what is sitting on USB device?
On Tue, Oct 23, 2018 at 11:13 AM <tomas@xxxxxxxxxx> wrote:
> On Tue, Oct 23, 2018 at 11:03:05AM -0500, Mark Copper wrote:
> > Trying to connect to a device, I get this error message:
> What are you trying to do while this error show up? How does it
> show up (e.g. desktop pop up, some log file...)?
> > *** Error ***
> > An error occurred in the io-library ('Could not claim the USB
> > device'): Could not claim interface 0 (Device or resource busy). Make
> > sure no other program (gvfs-gphoto2-volume-monitor) or kernel module
> > (such as sdc2xx, stv680, spca50x) is using the device and you have
> > read/write access to the device.
> > *** Error (-53: 'Could not claim the USB device') ***
> Things to try:
> - Issue (on a terminal, as root or sudo) "dmesg | tail", a short while
> after having inserted the USB device.
> - If the USB device poses as a storage device, issue "mount", to check
> whether something on your box (your DE, perhaps) has mounted the
> file system.
> - Look in /var/log/messages and/or /var/log/syslog (or however these
> things are called, should your init system be systemd: I'm not
> qualified for that, others will chime in, I guess).
> Note that USB devices can pose as different things "at the same
> -- tomás
The error is generated in response to this command:
The camera is recognized properly in dmesg. But it might be relevant
that the Chrome OS sees it as a storage device, and it's important not
to treat the camera as a storage device if one wants to use the
computer to control the camera. However, I cannot see that the device
is actually mounted. (the output of "mount" has become so complicated
I don't see either messages or syslog under the chroot.