Can't connect to 230 with ops for linux

Can't connect to 230 with ops for linux
I have unlocked and used my Rite Aid/Pure Digital 230 camera with ops 20 in Window$ XP. I can't seem to get it to work in linux (Fedora core 5 X86_64). When I plug in the camera the following shows up in /var/log/messages: Oct 21 23:28:26 emet kernel: usb 4-3: new high speed USB device using ehci_hcd and address 8 Oct 21 23:28:26 emet kernel: usb 4-3: configuration #1 chosen from 1 choice When I start ops this is added to /var/log/messages: Oct 21 23:29:59 emet kernel: usb 4-3: usbfs: interface 0 claimed by usbfs while 'ops' sets config #1 Oct 21 23:30:30 emet last message repeated 2 times Oct 21 23:30:30 emet kernel: ops<12958>: segfault at 0000000000000001 rip 00000000459748ea rsp 00000000ffa07900 error 4 Oct 21 23:30:36 emet kernel: usb 4-3: usbfs: interface 0 claimed by usbfs while 'ops' sets config #1 Oct 21 23:32:01 emet kernel: usb 4-3: usbfs: interface 0 claimed by usbfs while 'ops' sets config #1 When I start ops and click on "open camera" I get dialog box that says: "Camera can be found but can't be opened. Maybe you're not running as superuser (root)?" I am most definitely running ops as root! Anyone have any ideas how to fix this? Do I need to load a module manually? Help! The following is the output to standard out: Closing device No device to close Camcorder found! Found camcorder. Connected to camcorder. Challenge Key: 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 Response Key: 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 ERROR: (unlock_camcorder.c, 117): failed to unlock camcorder Closing device No device to close Camcorder found! Found camcorder. ERROR: (open_camcorder.c, 39): Couldn't connect to camcorder. ERROR: (open_camcorder.c, 159): Open() == FALSE ERROR: (open_camcorder.c, 160): Camera can be found but can't be opened. ERROR: (open_camcorder.c, 161): Maybe you're not running as superuser (root)? ERROR: (update_directory_listing.c, 240): change directory to / failed Closing device No device to close Camcorder found! Found camcorder. ERROR: (open_camcorder.c, 39): Couldn't connect to camcorder. ERROR: (open_camcorder.c, 159): Open() == FALSE ERROR: (open_camcorder.c, 160): Camera can be found but can't be opened. ERROR: (open_camcorder.c, 161): Maybe you're not running as superuser (root)? And yes, once again, I am running as superuser. Software versions: (rpm) ops-for-linux-1 libusb-0.1.11-2.2

the .rpm one is old, i'll package up my most current one (not 100% my work, more like 5%) into a .tar.gz, just uninstall the .rpm

I have the same problem: it works just fine with OPS20 in WinXP but not in Linux (ubuntu 6.10) using OPS v0.13 (https://sourceforge.net/project/showfiles.php?group_id=145193). Where can I get the la-*test*-('") one? Thanks

there is a thread in this forum specifically named "ops-for-linux". start from the end of that thread and work your way back and i'm sure you'll find it. look around first, please, before asking.

If there was an up to date package...
If there was an up to date package... It shouldn't be kept secret. If it is in that topic why didn't you post the link to help others? Why does it bother you when people ask a simple question? That's because you don't even know if there is an up to date link in that thread. I'll save you the time. There isn't one.

http://ryandavid773.googlepages.com/ops-linux-1.4-new.tar.tar wow...i started at the end, and worked my way back. this is the version that i've been using the whole time. and it works. people should be able to find it themselves, because i have too. using their brains and their browsers helps build themselves up. and they should be able to find the tab that references "ops" and "linux"...because it's in the name of the topic. newest versions should be in the newest posts...this also makes sense. if they looked, they could find it. they didn't want to look. i at least pointed them in the right direction. now you're giving them false information. that link works with both m200s and m220/m230s. i know, because i've used it with my 3.7 and 33.04. EDIT: he's referencing ops v.13, when there's two links to ops v.14. he's not using the newest version. if you weren't so cocky, you would have helped him with that.

http://ryandavid773.googlepages.com/ops-linux-1.4-new.tar.tar wow...i started at the end, and worked my way back. this is the version that i've been using the whole time. and it works. people should be able to find it themselves, because i have too. using their brains and their browsers helps build themselves up. and they should be able to find the tab that references "ops" and "linux"...because it's in the name of the topic. newest versions should be in the newest posts...this also makes sense. if they looked, they could find it. they didn't want to look. i at least pointed them in the right direction. now you're giving them false information. that link works with both m200s and m220/m230s. i know, because i've used it with my 3.7 and 33.04. EDIT: he's referencing ops v.13, when there's two links to ops v.14. he's not using the newest version. if you weren't so cocky, you would have helped him with that. Saturnnights: I know this is following up on an old thread, but as you know from my other post I have problems using ops-for-linux and pv2tools-linux. I saw this post and thought I would mention that the software referenced on the link here also does not work with my model 230 - the firmware is newer than what you have listed, so that probably has something to do with it. This is why I've questioned the diff's between ops21 and ops-for-linux - the Windows version works fine with the 230 and newer firmware, but the Linux version doesn't. Has the code been kept a match on the "key stuff", as I know from reading elsewhere in the forums that some of the challenge keys, etc., be it format or something, changed with the newer releases of firmware. The firmware on my model 230 is 53.18. Perhaps this is why the LInux version can find the camcorder, connect to it, then fail on the read of the challenge keys, which in turn results in the "are you root?" message, even when you have logged on as root and are running the application from the root home folder. :)

nah, i'm about 90 percent positive that the unlocker code is correct. i know that the deb package at the end of the thread is one of the newest builds available, and that's long after i made unlocker changes to the source tree. if the unlocker was malfunctioning, you should be getting an output of all "00"s as the challenge and response. that would be an indicator of an old build. but you're not even getting that far, which leaves me to think that it's indicative of an earlier problem.

anewguy, you may want to try that on a different USB port or through a USB hub on your Linux box. The USB hardware on these cams is fairly dodgy, and sometimes a marginal cable will allow you to enumerate, connect, but when you start really pulling data (like the challenge) it fails. I realize the cam works fine through your Windows box, but that hardware may be more tolerant. Even with the same computer, lots of people have reported a difference when going through the ports on the back of their computer, instead of the front. It's worth trying, anyway. Sidenote, someone may want to add a check for geteuid() before that message. (and a setgid/setuid after making the libusb connection, in case PD is trying to root our boxes!!! :wink: )

anewguy, you may want to try that on a different USB port or through a USB hub on your Linux box. The USB hardware on these cams is fairly dodgy, and sometimes a marginal cable will allow you to enumerate, connect, but when you start really pulling data (like the challenge) it fails. I realize the cam works fine through your Windows box, but that hardware may be more tolerant. Even with the same computer, lots of people have reported a difference when going through the ports on the back of their computer, instead of the front. It's worth trying, anyway. Sidenote, someone may want to add a check for geteuid() before that message. (and a setgid/setuid after making the libusb connection, in case PD is trying to root our boxes!!! :wink: ) Thanks for the reply! I know you and SaturnNights are the 2 big players in this project, so I am flattered that you guys would answer me! I've been a little suspicious since last night - I read where someone had gotten USB cables at the Dollar Store and everyone said to stay away from them. Guess what? I'm on disability so I went for the cheapest cable I could find - you guessed it - at the Dollar Store. I'm going to see if someone else has a good cable I can borrow, and if that fixes the problem I'll save up some pennies (quite literally! :) ) until I can get a better cable. Wouldn't you know - I thought the model 200 was somehow bad, so I actually soldered one of those cables straight to camera (not to brag, but it was a good solder job!) and right away when the cable was connected to one of the built-in USB ports it got REALLY hot (obviously an internal short) and proceeded to overdraw the USB port, so the 2 built-in ports are fried. Good thing I got the 4 port PCI USB card!! Now for even worse news - the cable going to my hub is from (gulp!!) the Dollar Store as well. All of this would sure explain some strange things that have happened through the hub as well!!! I guess I missed the cabling when thinking about hardware problems as SaturnNights had mentioned! It may be a while before I have a cable to -*test*-('") with, but THANK YOU BOTH SO MUCH!!!! Your willingness to do all of this is just amazing. I came from back in the pre-CPM days when you populated all your boards, set up the buss, etc., all on your own, and the truth is I have been away from "playing" for a LONG time. These cameras have me ready to dig back into C and C++ and start going again (at least both of those are easier than the old hand-assembly poke into memory days!!) Thanks so much! :) EDIT: Forgot to mention - if the USB interface on the camera is touchy, then these cables could very well be to blame - there is NO shielding at all!

You're welcome - always glad to lend an answer when I can. Sorry to hear about your port-short. A good source for free cables may be USB mice that family/friends may have replaced or discarded. Welcome back to the playground! :wink:

Well, I got a brand new decent USB 2 cable, and I get the same results. Ops for Linux won't unlock the camera and pv2tool-linux won't unlock the camera. This is on the same cable on the same port on the same computer (a 4-port USB card) that works with Windows. Is it okay to just use the binary from the packages, or do I need to do something like compile from the source in order for this to work? Thanks! :)

the binary should be sufficient, and before you get disgruntled with the camera, the unlocking for it is so ridiculous, that it fails very often even for me. what happens when you power on the camera, let it stay on, then plug in the cable?

next
I turned on the camera, waited about a minute, then plugged in the USB cable. The camera stayed on. I started ops for Linux and got the same result: dave@dave-desktop:~/ops-for-linux$ gksudo ./ops No device to close usb device with VID==167b PID==0101 Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded ERROR: (unlock_camcorder.c, 151): Failed at 0xff read (read 4 bytes of response) ERROR: (unlock_camcorder.c, 208): Failed to retrieve challenge key Closing device Camcorder USB device closed. dave@dave-desktop:~/ops-for-linux$ The saturnkeys.txt file is a copy of the file that works in Windows - I copied and pasted it into a file, then deleted the default saturnkeys.txt, then renamed my file to saturnkeys.txt. All in the ops-for-linux directory since I run ops while "in" that directory. I hope you can understand it's getting a little frustrating. :) As I'm sure it is with you as well. My biggest thing is I don't understand how it can be anything but either the libusb in LInux (I'm running Ubuntu 7.04 - do I need a different version of libusb?) or else ops itself, since everything - same camera, same cable, same port, same PC works in Windows. Perhaps something has changed in Ubuntu such that ops doesn't work right. Just grasping at straws here! :) As mentioned in my reply to Billw, I know you 2 are the key players in this entire thing, and I am flattered that you are taking the time to work with me - it is GREATLY appreciated!! :) Any ideas on what to try next? They have a couple more model 230's at our local CVS and I'd like to pick them up, but at the same time I REALLY want to stay with Linux if I can, so I need this all to work in Linux. PV2TOOLS-LINUX gives the exact same error with the model 410 digital camera as well, if that helps any.

try using the cam with a livecd on a different machine. there's some odd idiosyncrasies that people only note with certain conditions. it's not real easy diagnosing remotely. umm...well, i'll take a copy of the avidownload source, make it really verbose with the debugging, and give you a download link off of my server. it will take a little bit, but it shouldn't be long at all. heck, i'll ssh into my house and get to work on it.

View Full Version: Can't connect to 230 with ops for linux