LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-08-2003, 08:29 AM   #1
slungu
LQ Newbie
 
Registered: Nov 2003
Location: Aschaffenburg, Germany
Distribution: RH,SUSE - the one that works with my hardware
Posts: 5

Rep: Reputation: 0
Unhappy Canon Powershot Pro 90IS on linux


Here is my newest problem :
I am trying to get my Canon Powershot Pro 90IS to work with Linux, but without succes. The camera is not a usb storage device, so it has to work with gphoto2. It is supported by the gphoto2 software, and the usb port is reported as available port in I try gphoto2 --list-ports, but gphoto2 --auto-detect does not see the camera. Also the camera is not listed under /proc/bus/usb/devices, regardles if I boot the linux box with the camera on or I go to transfer mode after I have booted the linux box.
A dmesg | grep "usb" after boot shows the following:
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-ohci.c: USB OHCI at membase 0xd8932000, IRQ 20
usb-ohci.c: usb-00:03.0, Silicon Integrated Systems [SiS] 7001
usb.c: new USB bus registered, assigned bus number 1
usb-ohci.c: USB OHCI at membase 0xd8934000, IRQ 21
usb-ohci.c: usb-00:03.1, Silicon Integrated Systems [SiS] 7001 (#2)
usb.c: new USB bus registered, assigned bus number 2
usb-ohci.c: USB OHCI at membase 0xd8936000, IRQ 22
usb-ohci.c: usb-00:03.2, Silicon Integrated Systems [SiS] 7001 (#3)
usb.c: new USB bus registered, assigned bus number 3
usbdevfs: remount parameter error
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=2 (error=-110)
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-110)
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout

Switching the camera on brings these new lines to dmesg:

usb.c: USB device not accepting new address=2 (error=-110)
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout

Trying to auto-detect the camera with gphoto2 brings the following to dmesg:
usb.c: USB device not accepting new address=3 (error=-110)

Trying to modprobe usb-uhci ( as explained in some other threads here ):
usb-uhci.c: $Revision: 1.275 $ time 15:32:56 Mar 14 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver

but the command line says the insmod failed, with a message like:
init_module: No such device

Can anyone help me with this one ?!?
 
Old 11-09-2003, 12:20 AM   #2
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
I may not be able to help, but you'll have to post the following for anyone else to help you:
output of 'uname -r'
output of 'lsusb -v' (with camera plugged in and 'on')
output of 'lspci -v'
Boot without camera plugged in.
Bring up a 'terminal/console' and do 'tail -f /var/log/messages'
plug camera in, watch console
turn camera on, watch console
post that along with the above outputs. Are you using the latest gphoto, ie gPhoto2 2.1.3 (probably not the problem though).

This part is spooky: http://www.gphoto.org/doc/manual/FAQ.html#FAQ-Canon-AC , see your camera, try running on battery power and do the same above, any difference??? Spooky.

Last edited by faheyd; 11-09-2003 at 12:28 AM.
 
Old 11-09-2003, 12:02 PM   #3
slungu
LQ Newbie
 
Registered: Nov 2003
Location: Aschaffenburg, Germany
Distribution: RH,SUSE - the one that works with my hardware
Posts: 5

Original Poster
Rep: Reputation: 0
Thank you for the input, I have tried to get the data, so here it is

lsusb -v gives the following output :

Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Root Hub
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 0.00
iManufacturer 0
iProduct 2 USB OHCI Root Hub
iSerial 1 d8936000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Root Hub
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0000 (null)((null))

Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Root Hub
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 0.00
iManufacturer 0
iProduct 2 USB OHCI Root Hub
iSerial 1 d8934000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Root Hub
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0000 (null)((null))

Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Root Hub
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 0.00
iManufacturer 0
iProduct 2 USB OHCI Root Hub
iSerial 1 d8932000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Root Hub
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0000 (null)((null))

the tail -f /var/log/messages gives the following output when switching the camera on:

Nov 9 18:50:32 pro kernel: hub.c: new USB device 00:03.0-1, assigned address 6
Nov 9 18:50:37 pro kernel: usb_control/bulk_msg: timeout
Nov 9 18:50:37 pro kernel: usb-ohci.c: unlink URB timeout
Nov 9 18:50:37 pro kernel: usb.c: USB device not accepting new address=6 (error=-110)
Nov 9 18:50:37 pro kernel: hub.c: new USB device 00:03.0-1, assigned address 7
Nov 9 18:50:42 pro kernel: usb_control/bulk_msg: timeout
Nov 9 18:50:42 pro kernel: usb-ohci.c: unlink URB timeout
Nov 9 18:50:42 pro kernel: usb.c: USB device not accepting new address=7 (error=-110)

The kernel is 2.4.21.
Anyone having any idea ?!?
 
Old 11-09-2003, 01:35 PM   #4
mlp68
Member
 
Registered: Jun 2002
Location: NY
Distribution: Gentoo,RH
Posts: 333

Rep: Reputation: 40
Are you sure you need the ohci and not the uhci driver? Go into the kernel config, usb, and enable the UHCI driver. Remake and install the modules.

Then in /etc/modules.conf you'll find some alias about the USB, try

alias usb-controller usb-uhci

I presume you have ohci in there now.

I have the Powershot s110 and it works great.

Hope it helps,

mlp
 
Old 11-09-2003, 04:02 PM   #5
slungu
LQ Newbie
 
Registered: Nov 2003
Location: Aschaffenburg, Germany
Distribution: RH,SUSE - the one that works with my hardware
Posts: 5

Original Poster
Rep: Reputation: 0
Thanks for the tip - unfortunately it didn't work :
modprobe usb-uhci stated :
init_module: "No such device"
The problem is after trying usb-uhci I don't have any /proc/bus/usb, and the usb-modules are not loaded ( since modprobe failed ).
I realy don't know how to handle this...
 
Old 11-09-2003, 06:56 PM   #6
mlp68
Member
 
Registered: Jun 2002
Location: NY
Distribution: Gentoo,RH
Posts: 333

Rep: Reputation: 40
Did you do this in the "warm" system while ohci was already loaded? Then uhci wouldn't load. If you did, either reboot or modprobe -r the ohci.

I'll break out my camera and see what I get and what loads how. Later.

Don't you have to specify the camera with gphoto2 --camera <your model> ?

mlp
 
Old 11-09-2003, 10:45 PM   #7
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
Two things, did you try plugging it directly into the motherboard usb port and second, are you using camera battery power, or the ac adapter?

And because you just never know, see http://www.canon.co.jp/Imaging/PSPRO...irmware-e.html for checking that you have the latest firmware.
 
Old 11-10-2003, 01:47 AM   #8
slungu
LQ Newbie
 
Registered: Nov 2003
Location: Aschaffenburg, Germany
Distribution: RH,SUSE - the one that works with my hardware
Posts: 5

Original Poster
Rep: Reputation: 0
Well, I changed the /etc/modules.conf as you poited out, and then rebooted. There was no ohci module around, but the uhci didn't load either, so I ended up with no USB support whatsoever. Manualy trying to modprobe usb-uhci brought me the same result. The camera is of course not detected by gphoto2, but this is not surprising since it does not appear in the /proc/bus/usb/devices...
Running the camera on battery or ac adapter didn't make any difference. The only thing I get with the ohci is the message about not accepting new address, as shown in the listings . This is a little bit odd, since on my former linux box, a Pentium I at 133, it worked, at least to the part where it should have been seen in /proc/bus/usb/devices. With usbview I get an "unknown device" that disappears -> don't know if that helps enybody in "debugging" this...
Any way, thanks a lot for the hints guys
 
Old 11-10-2003, 01:56 AM   #9
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
This might be a real long reach, but i saw it in another thread,
"or add 'noapic' to the 'append =' line in lilo.conf (then doing /sbin/lilo ), (or the 'kernel =' line in Grub)."
Can't hurt to try it.
Also, check to make sure you have PnP OS turned off in your bios if you have that setting.

Last edited by faheyd; 11-10-2003 at 02:00 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Canon Powershot a510 linux drivers needed dmneoblade Linux - Hardware 8 05-23-2005 06:31 PM
Canon powershot A75 & Linux Mikessu Linux - Hardware 20 01-18-2005 06:48 AM
Canon Powershot S10: remote capture linux nyk Linux - Hardware 0 10-25-2004 11:39 AM
Canon PowerShot S50 oskar_27de Linux - Hardware 0 11-03-2003 04:12 AM
Canon Powershot Cameras psx-dude Slackware 14 08-28-2003 09:28 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration