ab2ms Posted January 20, 2005 Report Share Posted January 20, 2005 For starters I've read every how-to and scrap of info I could find. I am running mdk 10.1 official, and want it to talk to my tungsten t2. I tried and tried and gave up last week. Being the stubborn guy I am, I try to sync every now n then just for the heck of it. Well I tried it today and heard that nice little tweedle-dee! j-pilot had successfully talked to /dev/ttyUSB2 so I do know where my palm likes to hang out. Problem is...... it synced that once. That's it. I tried several times since, but no go. I try different timing schemes, push sync on the palm, wait 5,10,25 etc. seconds but I can't figure out what sort of voodoo black magic I used that once. It worked, so I know it CAN work, but there must be some weird/obscure variable that just isn't cooperating. So basically I am hoping this little dilemma I have will pique someones interest that may be able to shed some light on this situation and allow me to hear that happy little sound again and save me from having to boot to the dark side. I haven't changed a single thing since the one success, just tried to sync so it "should" be all set with no APIC, udev entry etc. thanks Todd Quote Link to comment Share on other sites More sharing options...
ab2ms Posted January 20, 2005 Author Report Share Posted January 20, 2005 (edited) OK so I successfully synced repeatedly. When I pushed hotsync ttyUSB1 and 2 were the 2 devices created. so...... 2 supposedly is the one I want. It even worked once. I kept trying 1 and 2 just to see. /dev/pilot was set up by udev to be my palm (whenever I tried to sync kpilot did pop up, but wouldn't do anything other than say /dev/pilot was ready) For some reason it kept being created pointing to ttyUSB3. and lo n behold I just got frustrated and tried ttyUSB0 and it worked repeatedly. Who knows if this will continue, but can anyone explain what the heck my mix-up is? I did uninstall kpilot to keep it from competing with jpilot. Edited January 20, 2005 by ab2ms Quote Link to comment Share on other sites More sharing options...
Guest jglen490 Posted January 24, 2005 Report Share Posted January 24, 2005 You noted that udev created the /dev/pilot entry. In my experience, the only way the jpilot works is if /dev/pilot is created as a soft link for the actual device (USB, serial) where the handheld's cable connects to the PC. Quote Link to comment Share on other sites More sharing options...
ab2ms Posted January 29, 2005 Author Report Share Posted January 29, 2005 I just keep jpilot pointed at /dev/ttyUSB0, I gave up dealing with /dev/pilot. It just seems that the device number is a different value than it is "supposed" to be for some reason, but at least it is working. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.