I have a new Canon S1 camera that wants to talk in PTP mode. I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user. I get the wunnerful resmgr 501 and 502 errors. I've done the following: 1) Gone through google with site:suse and found a thread two years ago where I was trying to solve the same problem for a different camera. 2) I've done everything suggested in (1) 3) I've gone through the doc in /usr/share/packages/libgphoto2/linux-hotplug etc etc etc. 4) I've made changes to the /etc/hotplug/usb files suggested in (3). 5) I've made a change to fstab that is supposed to allow users access to any usb device..... yada yada yada. But I still can't access the camera through digikam as a user even though it does detect it. I've been here before.... but have lost the secrets of life. Can someone give me a clue? Thanks.
* Bruce Marshall <bmarsh@bmarsh.com> [03-03-05 18:50]:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
...
Can someone give me a clue?
I am not sure but seem to remember that all you need to do is add the device you connect the camera to /etc/resmgr.conf, examples there. PTP would be ?? serial, /dev/ttyS0 or S1.... disclaimer, I am not sure about this but that seems to be the type of error you are receiving. Try it. gud luk, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
On Thursday 03 March 2005 08:21 pm, Patrick Shanahan wrote:
* Bruce Marshall <bmarsh@bmarsh.com> [03-03-05 18:50]:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
...
Can someone give me a clue?
I am not sure but seem to remember that all you need to do is add the device you connect the camera to /etc/resmgr.conf, examples there. PTP would be ?? serial, /dev/ttyS0 or S1....
disclaimer, I am not sure about this but that seems to be the type of error you are receiving. Try it.
gud luk,
Thanks.... but I've discovered something new.... I have a 'lab-rat' machine with a quite unmodified 9.2 on it. I opened digikam on this machine, plugged in the Canon S1, let digikam detect the camera and add it to the list. Voila... it worked. Then I got out of digikam and unplugged the camera and tried the sequence again without doing the detect (since it was already a known camera). No worky. So I went through the sequence again and removed the camera from digikam and let it find it again. It worked again. I then tried this on my normal machine and it would work only by letting digikam detect the camera. Not a Good Thing (tm) but seems to show that the resmgr isn't really the problem. And I'm not sure what device PTP would use but I don't think it is a ttyxxx device. It is a USB device and shows up as such and resmgr.conf seems to allow the user access to any USB device with a few exceptions. PTP is the Photo Transfer Protocol which really shouldn't enter into the connection problems in my view. Still researching.... Strange stuff.
I then tried this on my normal machine and it would work only by letting digikam detect the camera.
Not a Good Thing (tm) but seems to show that the resmgr isn't really the problem.
And I'm not sure what device PTP would use but I don't think it is a ttyxxx device. It is a USB device and shows up as such and resmgr.conf seems to allow the user access to any USB device with a few exceptions. PTP is the Photo Transfer Protocol which really shouldn't enter into the connection problems in my view.
Still researching.... Strange stuff.
Might be gphoto2 related. Check "gphoto2 --list-ports" ... It should only report "usb:" Ciao, Marcus
On Friday 04 March 2005 08:38 am, Marcus Meissner wrote:
I then tried this on my normal machine and it would work only by letting digikam detect the camera.
Not a Good Thing (tm) but seems to show that the resmgr isn't really the problem.
And I'm not sure what device PTP would use but I don't think it is a ttyxxx device. It is a USB device and shows up as such and resmgr.conf seems to allow the user access to any USB device with a few exceptions. PTP is the Photo Transfer Protocol which really shouldn't enter into the connection problems in my view.
Still researching.... Strange stuff.
Might be gphoto2 related.
Check "gphoto2 --list-ports" ... It should only report "usb:"
Ciao, Marcus
gphoto2 --list-ports Devices found: 27 Path Description -------------------------------------------------------------- serial:/dev/ttyS0 Serial Port 0 serial:/dev/ttyS1 Serial Port 1 serial:/dev/ttyS2 Serial Port 2 serial:/dev/ttyS3 Serial Port 3 serial:/dev/ttyS4 Serial Port 4 serial:/dev/ttyS5 Serial Port 5 serial:/dev/ttyS6 Serial Port 6 serial:/dev/ttyS7 Serial Port 7 serial:/dev/ttyS8 Serial Port 8 serial:/dev/ttyS9 Serial Port 9 serial:/dev/ttyS10 Serial Port 10 serial:/dev/ttyS11 Serial Port 11 serial:/dev/ttyS12 Serial Port 12 serial:/dev/ttyS13 Serial Port 13 serial:/dev/ttyS14 Serial Port 14 serial:/dev/ttyS15 Serial Port 15 serial:/dev/ttyS16 Serial Port 16 serial:/dev/ttyS17 Serial Port 17 serial:/dev/ttyS18 Serial Port 18 serial:/dev/ttyS19 Serial Port 19 serial:/dev/ttyS20 Serial Port 20 serial:/dev/ttyS21 Serial Port 21 serial:/dev/ttyS22 Serial Port 22 serial:/dev/ttyS23 Serial Port 23 usb: Universal Serial Bus usb:001,010 Universal Serial Bus usb:001,003 Universal Serial Bus Doesn't seem to be the case. The above was with the camera attached. /var/log/messages shows: Mar 4 09:18:48 linux1 kernel: usb 1-2: new full speed USB device using address10 Mar 4 09:18:48 linux1 kernel: usb 1-2: Product: Canon Digital Camera Mar 4 09:18:48 linux1 kernel: usb 1-2: Manufacturer: Canon Inc. Mar 4 09:18:50 linux1 kernel: Device not ready. Make sure there is a disc in the drive. Mar 4 09:18:51 linux1 kernel: Device not ready. Make sure there is a disc in the drive. Mar 4 09:18:52 linux1 gphoto2: resmgr: server response code 502 Mar 4 09:18:52 linux1 last message repeated 71 times Mar 4 09:18:52 linux1 gphoto2: resmgr: server response code 501 Mar 4 09:18:52 linux1 last message repeated 26 times Mar 4 09:18:52 linux1 gphoto2: resmgr: server response code 200 and on and on............
On Fri, Mar 04, 2005 at 09:21:57AM -0500, Bruce Marshall wrote:
On Friday 04 March 2005 08:38 am, Marcus Meissner wrote:
I then tried this on my normal machine and it would work only by letting digikam detect the camera.
Not a Good Thing (tm) but seems to show that the resmgr isn't really the problem.
And I'm not sure what device PTP would use but I don't think it is a ttyxxx device. It is a USB device and shows up as such and resmgr.conf seems to allow the user access to any USB device with a few exceptions. PTP is the Photo Transfer Protocol which really shouldn't enter into the connection problems in my view.
Still researching.... Strange stuff.
Might be gphoto2 related.
Check "gphoto2 --list-ports" ... It should only report "usb:"
Ciao, Marcus
gphoto2 --list-ports usb: Universal Serial Bus usb:001,010 Universal Serial Bus usb:001,003 Universal Serial Bus
Doesn't seem to be the case. The above was with the camera attached.
If you unplug the camera, is only "usb:" shown? digikam probably added "usb:001,0xx" as port to the camera setting, which is wrong. Ciao, Marcus
On Friday 04 March 2005 09:23 am, Marcus Meissner wrote:
On Fri, Mar 04, 2005 at 09:21:57AM -0500, Bruce Marshall wrote:
On Friday 04 March 2005 08:38 am, Marcus Meissner wrote:
I then tried this on my normal machine and it would work only by letting digikam detect the camera.
Not a Good Thing (tm) but seems to show that the resmgr isn't really the problem.
And I'm not sure what device PTP would use but I don't think it is a ttyxxx device. It is a USB device and shows up as such and resmgr.conf seems to allow the user access to any USB device with a few exceptions. PTP is the Photo Transfer Protocol which really shouldn't enter into the connection problems in my view.
Still researching.... Strange stuff.
Might be gphoto2 related.
Check "gphoto2 --list-ports" ... It should only report "usb:"
Ciao, Marcus
gphoto2 --list-ports usb: Universal Serial Bus usb:001,010 Universal Serial Bus usb:001,003 Universal Serial Bus
Doesn't seem to be the case. The above was with the camera attached.
If you unplug the camera, is only "usb:" shown? bmarsh@linux1:~> gphoto2 --list-ports Devices found: 3 Path Description
serial:/dev/ttyS4 Serial Port 4 serial:/dev/ttyS6 Serial Port 6 usb: Universal Serial Bus Better. The S4 and S6 are special serialports on a moxa board.
digikam probably added "usb:001,0xx" as port to the camera setting, which is wrong.
Ciao, Marcus
On Thu, Mar 03, 2005 at 06:46:02PM -0500, Bruce Marshall wrote:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
Your SUSE Linux version is? What does "/sbin/resmgr list" show as the user after the camera is attached? Ciao, Marcus
On Thu, Mar 03, 2005 at 06:46:02PM -0500, Bruce Marshall wrote:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
Your SUSE Linux version is?
What does "/sbin/resmgr list" show as the
On Friday 04 March 2005 04:27 am, Marcus Meissner wrote: ulinux1:/pictures/linpha/albums/bruce # /sbin/resmgr list status code 200 server message follows: no devices available ser after the camera is
attached?
Ciao, Marcus
SuSE 9.2 (and up to date as of a couple of weeks ago) linux1:# /sbin/resmgr list status code 200 server message follows: no devices available (and I was hoping you would chime in here.... Thanks) See my earlier note about how digikam/camera will work if going through the autodetect process each time it is connected.
On Fri, Mar 04, 2005 at 09:15:31AM -0500, Bruce Marshall wrote:
On Thu, Mar 03, 2005 at 06:46:02PM -0500, Bruce Marshall wrote:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
Your SUSE Linux version is?
What does "/sbin/resmgr list" show as the
On Friday 04 March 2005 04:27 am, Marcus Meissner wrote: ulinux1:/pictures/linpha/albums/bruce # /sbin/resmgr list status code 200 server message follows: no devices available ser after the camera is
attached?
Ciao, Marcus
SuSE 9.2 (and up to date as of a couple of weeks ago)
linux1:# /sbin/resmgr list status code 200 server message follows: no devices available
(and I was hoping you would chime in here.... Thanks)
See my earlier note about how digikam/camera will work if going through the autodetect process each time it is connected.
Run /sbin/resmgr list as the logged in user, not as root. Ciao, Marcus
On Friday 04 March 2005 09:21 am, Marcus Meissner wrote:
On Fri, Mar 04, 2005 at 09:15:31AM -0500, Bruce Marshall wrote:
On Friday 04 March 2005 04:27 am, Marcus Meissner wrote:
On Thu, Mar 03, 2005 at 06:46:02PM -0500, Bruce Marshall wrote:
I have a new Canon S1 camera that wants to talk in PTP mode.
I can run digikam as root and the camera gets connected just fine. But I cannot for the life of me get it to run as a user.
I get the wunnerful resmgr 501 and 502 errors.
Your SUSE Linux version is?
What does "/sbin/resmgr list" show as the
ulinux1:/pictures/linpha/albums/bruce # /sbin/resmgr list status code 200 server message follows: no devices available ser after the camera is
attached?
Ciao, Marcus
SuSE 9.2 (and up to date as of a couple of weeks ago)
linux1:# /sbin/resmgr list status code 200 server message follows: no devices available
(and I was hoping you would chime in here.... Thanks)
See my earlier note about how digikam/camera will work if going through the autodetect process each time it is connected.
Run /sbin/resmgr list as the logged in user, not as root.
Ciao, Marcus
Sorry.... but I get the same thing. bmarsh@linux1:~> /sbin/resmgr list status code 200 server message follows: no devices available
Sorry.... but I get the same thing.
bmarsh@linux1:~> /sbin/resmgr list status code 200 server message follows: no devices available
You did not login via kdm or gdm, so resmgr did not see you login I suspect. How did you start your X session? Ciao, Marcus
On Friday 04 March 2005 09:51 am, Marcus Meissner wrote:
Sorry.... but I get the same thing.
bmarsh@linux1:~> /sbin/resmgr list status code 200 server message follows: no devices available
You did not login via kdm or gdm, so resmgr did not see you login I suspect. How did you start your X session?
Ciao, Marcus
Normal Suse login to init 5 level and to KDE. Don't believe I have made any changes at all to the normal SUSE login sequence. And as I stated earlier, I also tried this on a pristine install of 9.2. Hmm just tried /sbin/resmgr over on the pristine machine and I get (as user): rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any rw-- /proc/bus/usb/004/002 rw-- /proc/bus/usb/004/003 rw-- /proc/bus/usb/004/004 rw-- /proc/bus/usb/004/005 rw-- /proc/bus/usb/004/006 with the last item being the camera. So you are probably right that resmgr didn't see me login.... just wonder why...
On Friday 04 March 2005 10:11 am, Bruce Marshall wrote:
On Friday 04 March 2005 09:51 am, Marcus Meissner wrote:
Sorry.... but I get the same thing.
bmarsh@linux1:~> /sbin/resmgr list status code 200 server message follows: no devices available
You did not login via kdm or gdm, so resmgr did not see you login I suspect. How did you start your X session?
Ciao, Marcus
Ok, back to square one on this. I think what happened with my previous resmgr list results was that I had done a resmgr restart at some point, thus it hadn't seen me login after that. So I have done a reboot of the machine, and done the normal login. The resmgr list results look more normal. However, even with a fresh boot, going into digikam with the camera previously defined to it still does not allow the camera to connect. I can then go into the 'add camera' dialog, remove the S1, re-detect it, get out of the dialog, and I am good for that one session. The camera will connect. The camera is good only for the session where digikam is allowed to auto-detect it. Sounds like it might be a problem with digikam (or gphoto2) to me.
So I have done a reboot of the machine, and done the normal login. The resmgr list results look more normal. However, even with a fresh boot, going into digikam with the camera previously defined to it still does not allow the camera to connect.
I can then go into the 'add camera' dialog, remove the S1, re-detect it, get out of the dialog, and I am good for that one session. The camera will connect.
The camera is good only for the session where digikam is allowed to auto-detect it.
Sounds like it might be a problem with digikam (or gphoto2) to me.
Yes, it is. It originates from the multiple USB device support in gphoto2. I hope I fixed that for later gphoto2 versions. Ciao, Marcus
On Friday 04 March 2005 10:50 am, Marcus Meissner wrote:
So I have done a reboot of the machine, and done the normal login. The resmgr list results look more normal. However, even with a fresh boot, going into digikam with the camera previously defined to it still does not allow the camera to connect.
I can then go into the 'add camera' dialog, remove the S1, re-detect it, get out of the dialog, and I am good for that one session. The camera will connect.
The camera is good only for the session where digikam is allowed to auto-detect it.
Sounds like it might be a problem with digikam (or gphoto2) to me.
Yes, it is. It originates from the multiple USB device support in gphoto2.
I hope I fixed that for later gphoto2 versions.
Ciao, Marcus
Thanks for you help.. I can live with the work-around for now. (or the CF reader I have but don't really want to use) I've been playing with some of the gphoto2 commands and it sees the camera and I can download (--get-all-files) with it over and over. So gphoto2 doesn't really seem to have a problem..... Don't know where that leaves the problem.
On Fri, Mar 04, 2005 at 10:59:24AM -0500, Bruce Marshall wrote:
On Friday 04 March 2005 10:50 am, Marcus Meissner wrote:
So I have done a reboot of the machine, and done the normal login. The resmgr list results look more normal. However, even with a fresh boot, going into digikam with the camera previously defined to it still does not allow the camera to connect.
I can then go into the 'add camera' dialog, remove the S1, re-detect it, get out of the dialog, and I am good for that one session. The camera will connect.
The camera is good only for the session where digikam is allowed to auto-detect it.
Sounds like it might be a problem with digikam (or gphoto2) to me.
Yes, it is. It originates from the multiple USB device support in gphoto2.
I hope I fixed that for later gphoto2 versions.
Ciao, Marcus
Thanks for you help.. I can live with the work-around for now. (or the CF reader I have but don't really want to use)
I've been playing with some of the gphoto2 commands and it sees the camera and I can download (--get-all-files) with it over and over. So gphoto2 doesn't really seem to have a problem.....
Don't know where that leaves the problem.
The digikam app remembers the bad port "usb:xxx,yyy" instead of "usb:" ... Someone has to fix those apps ;) Ciao, Marcus
participants (3)
-
Bruce Marshall -
Marcus Meissner -
Patrick Shanahan