[Barry-devel] Re: Barry

[Chris F. <cd...@fo...>]

On Wed, Dec 28, 2005 at 04:44:03PM -0500, Chris Frey wrote:
> On Wed, Dec 28, 2005 at 03:46:14PM -0500, Ron Gage wrote:
> >   Configuration Descriptor:
> >     bLength                 9
> >     bDescriptorType         2
> >     wTotalLength           46
> >     bNumInterfaces          1
> >     bConfigurationValue     1
> >     iConfiguration          0 
> >     bmAttributes         0x80
> >     MaxPower              100mA
> >     Interface Descriptor:
> >       bLength                 9
> >       bDescriptorType         4
> >       bInterfaceNumber        0
> >       bAlternateSetting       0
> 
> These are the same as the devices I have to test with.  The "device or
> resource busy" error you are getting may be due to a USB module loaded in
> the kernel.
> 
> Check lsmod and see if there is anything loaded that might conflict.
> libusb only needs usbcore, which might not be a module.  Check dmesg too...
> it might have useful error messages.

Quoting from: http://if2a.free.fr/documentation/FAQWTO.html#AEN339

	2.4.2. I get the annoying message 'Device or resource busy' !

	This happens under Linux with some distributions that include
	the usbtest module in the kernel configuration. This module is
	automatically loaded by hotplug when the linker renumerates,
	and prevents if2a from using the cable.

	The error message looks like this:

	usb_set_configuration: could not set config 1: Device or resource busy

	To check if it is really usbtest that messes things up, try the
	command dmesg|tail, here it says:

	usb 1-2.4: usbfs: interface 0 claimed by usbtest while 'if2a' sets config #1

	This module can be unloaded (as root) with the command rmmod
	usbest then if2a can be restarted. For future use, you can add
	the word usbtest at the end of the file /etc/hotplug/blacklist,
	this will prevent hotplug from loading this module.

- Chris