Problems with usb and digital camera
Hi...
I have a Canon Powershot A70 and it used to work nicely with linux and gnome. But now it has stopped working.
When I plug the camera, gthumb pops and try to import photos. But I get a window with this message:
An error occurred in the io-library ('Error updating the port settings'): Could not set config 0/1 (Device or resource busy)
syslog shows this:
Jun 6 23:43:04 werewolf kernel: usb 5-2: new full speed USB device using uhci_hcd and address 6 Jun 6 23:45:38 werewolf kernel: usb 5-2: usbfs: interface 0 claimed by usbfs while 'gthumb' sets config #1
I have now 2.6.12-rc6-mm1. My USB pendrive works nicely.
Are you aware of any strange behaviour of USB in this kernel ? What means the syslog message ? The kernel grabs the device to show in usbfs and nobody can open it ?
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.11-jam23 (gcc 4.0.0 (4.0.0-3mdk for Mandriva Linux release 2006.0))
Quoted 8 lines · J.A. Magallon
Hi...
I have a Canon Powershot A70 and it used to work nicely with linux and gnome. But now it has stopped working.
When I plug the camera, gthumb pops and try to import photos. But I get a window with this message:
Quoted 6 lines
An error occurred in the io-library ('Error updating the port settings'): Could not set config 0/1 (Device or resource busy)
syslog shows this:
Jun 6 23:43:04 werewolf kernel: usb 5-2: new full speed USB device using uhci_hcd and address 6 Jun 6 23:45:38 werewolf kernel: usb 5-2: usbfs: interface 0 claimed by usbfs while 'gthumb' sets config #1
That looks fine.
Quoted 3 lines
I have now 2.6.12-rc6-mm1. My USB pendrive works nicely.
Are you aware of any strange behaviour of USB in this kernel ?
Nope :)
Quoted 2 lines
What means the syslog message ? The kernel grabs the device to show in usbfs and nobody can open it ?
No, gthumb uses libusb to grab it (thats the usbfs bind message.)
How about enabling CONFIG_USB_DEBUG in your kernel and posting the results of your syslog to the linux-usb-devel mailing list when you try this?
thanks,
greg k-h