<---- template headericclude ----->
Setting up a Palm Device [m505]
FedoraForum.org - Fedora Support Forums and Community
Page 1 of 3 123 LastLast
Results 1 to 15 of 38
  1. #1
    ammar Guest

    Setting up a Palm Device [m505]

    Hi there,

    How does one go about setting up a palm device? I tried the Pilot app from within gnome, but it didnt recieve any notification of the hotsync (last step of the setup process: press hotsync). I think the pda is not detected.

    Is there a step-by-step process of how to get this to work?

  2. #2
    tchung Guest
    Hello,

    Here is an old tutorial I wrote back in December 2003.

    http://fedoranews.org/tchung/gnome-pilot/

    Thomas

  3. #3
    ammar Guest
    Thanks. This is the output I get after following the steps:
    No $PILOTPORT specified and no -p <port> given.
    Defaulting to '/dev/pilot'

    Unable to bind to port: /dev/pilot
    Please use --help for more information

  4. #4
    Join Date
    Oct 2004
    Location
    Saskatchewan
    Age
    56
    Posts
    35
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    /dev/pilot should point to the port your pilot is connected to for example mine is a serial system so /dev/pilot is symbolically linked to /dev/ttyS0 I see yours is a m505 which I believe is USB based you may have to create a /dev/pilot

    see http://pilot-link.org/README.usb

  5. #5
    ammar Guest
    Thanks a bunch, it works great now =)

  6. #6
    ahoyt Guest
    Hello,

    I can connect to my Palm Zire21 with the #pilot-xfer -l with no problem. However when I try to use the "Palm OS devices" GUI, it has no response. It just times out after awhile.

    ahoyt

  7. #7
    ahoyt Guest
    Oops,

    a reply to my own post. I needed to change the port designation from tty/usb/01 to ttyUSB1. It works good now. There are occasional glitches, but exiting J-Pilot and then going back in seems to fix it.

    ahoyt

  8. #8
    Join Date
    Aug 2004
    Location
    WV
    Age
    47
    Posts
    107
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Okay, following the tutorial, I get this:

    [root@localhost scott]# ln -s /dev/ttyUSB1 /dev/pilot
    [root@localhost scott]# pilot-xfer -l
    No $PILOTPORT specified and no -p <port> given.
    Defaulting to '/dev/pilot'

    Unable to bind to port: /dev/pilot
    Please use --help for more information

    So, I try to specify a port and get:

    [root@localhost scott]# pilot-xfer -p --ttyUSB1
    Time elapsed: 0:00:00

    ??

    I'm trying to sync with my palm m515.

    Thanks

  9. #9
    ahoyt Guest
    Did you make a symbollic link?

    ln -s /dev/ttyUSB1 /dev/pilot

    Something like that.

    ahoyt

  10. #10
    marcus-cat Guest
    Quote Originally Posted by ahoyt
    Did you make a symbollic link?

    ln -s /dev/ttyUSB1 /dev/pilot

    Something like that.

    ahoyt
    I also found that I had to add the devices by hand after installing FC3.

    From a terminal I entered:
    mknod /dev/ttyUSB1 c 188 1
    mknod /dev/ttyUSB0 c 188 0
    chmod 666 /dev/ttyUSB1

    To see the devices type:
    ls -al /dev/ttyUSB?

    I then ran Jpilot, hit the synch button and then pressed the palm synch button.

  11. #11
    imdeemvp Guest
    You are correct something changed in fedora core 3 that you have to add it manually. I think tchung has to update his tutorial.

  12. #12
    marcus-cat Guest
    Quote Originally Posted by imdeemvp
    You are correct something changed in fedora core 3 that you have to add it manually. I think tchung has to update his tutorial.
    One other oddity with FC3: After the synch is complete in Jpilot the usb system appears to lose the devices /dev/ttyUSB1 /dev/ttyUSB0. I haven't found a way to make them 'stick'. Currently I run a script that adds the palm devices, changes privs, and starts a synch each time I want to synch -- messy but it works for now.

  13. #13
    marcus-cat Guest
    Quote Originally Posted by marcus-cat
    Currently I run a script that adds the palm devices, changes privs, and starts a synch each time I want to synch -- messy but it works for now.
    In case anybody wants it here is the desktop script I run before using Jpilot on FC3 -- as I said before, it is ugly but it works for now.

    #!/bin/bash
    # palm-devices FC3 shell script hack

    # place in text file and set to 'execute'
    # in Gnome or KDE set the file to run as user 'root' -- run it
    # Start up gpilot or jpilot and then click synch on palm

    # make palm devices, pilot link, change privs
    mknod /dev/ttyUSB1 c 188 1
    chmod 666 /dev/ttyUSB1
    rm /dev/pilot
    ln -s /dev/ttyUSB1 /dev/pilot
    chmod 666 /dev/pilot

  14. #14
    Scoob_E Guest
    Found out how to avoid using your script... after googling I cam across this page:

    http://www.clasohm.com/blog/one-entry?entry_id=12096

    gpilot works like a charm after creating the two files...

    hat's off to the blog's author

    Scoob

  15. #15
    elgeeko Guest
    I got my T3 working with FC3 and Gnome-Pilot, here's what I discovered (from memory):

    FC3 now uses udev which dynamically creates device files, so that's why you can't see them in dev. They only exists when you synch.

    Use ln -s ttyUSB1 /etc/udev/devices/pilot

    Then go into /etc/udev/permissons.d/ and change the entries for pilot and ttyUSB1 so that udev creates the files with 0666 permissions rather than 0660.

    RH advise not to change the permissions file, but it worked for me.

    elgeeko...

Page 1 of 3 123 LastLast

Similar Threads

  1. FedCore6 - Setting up a trusted device (such as eth0)
    By dupies in forum Servers & Networking
    Replies: 0
    Last Post: 27th February 2007, 05:30 PM
  2. Replies: 0
    Last Post: 18th October 2005, 11:21 PM
  3. Replies: 1
    Last Post: 3rd January 2004, 09:07 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]