[jp] Sync problems - further developments

  • Previous message: [jp] Sync problems - further developments
  • Next message: [jp] Sync problems - no "user" name
  • Eamann O Ruairc e.oruairc at skynet.be
    Sun Dec 3 15:11:26 EST 2006

     

    Thank you once more David for the time you are spending trying to help 
    me! I am conscious of how precious time is and appreciate your efforts 
    accordingly!
    
    David A. Desrosiers wrote:
    > I think your sync problems are MUCH more fundamental than what we're
    > making of them here. Let's forget everything you've done, and start from
    > scratch, from the bottom up and see where things begin to fail. 
    >
    > You're doing this using the standard USB path, right? Not using libusb
    > or any of the "new" methods to sync? (Bluetooth, PPP, libusb, and so
    > on). 
    >   
    That's right: standard USB path using a cable directly attached to a USB 
    port on my laptop.
    > When you do nothing, Palm uncradled, and type 'ps -afux | grep -i
    > pilot', do you see anything peculiar? 
    >   
    With Palm uncradled, but the cradle connected to the laptop, this is 
    what I get:
    
    root at eamann-laptop:/home/eamann# ps -afux | grep -i pilot
    Warning: bad ps syntax, perhaps a bogus '-'? See 
    http://procps.sf.net/faq.html
    root      6765  0.0  0.1   2808   768 pts/0    S+   20:58   
    0:00              \_ grep -i pilot
    eamann    6146  0.1  1.8  47288  9712 ?        S    20:47   0:00 jpilot
    > When you do an 'lsmod | grep visor', do you see the visor module
    > loaded? 
    >   
    root at eamann-laptop:/home/eamann# lsmod | grep visor
    visor                  19724  0
    usbserial              32616  1 visor
    usbcore               130304  6 visor,usbserial,usbhid,ehci_hcd,uhci_hcd
    > Can you rmmod and insmod the visor module manually? Or do you get an
    > error when you try to do so? 
    >   
    rmod and modprobe seem to work, but insmod didn't:
    
    root at eamann-laptop:/home/eamann# rmmod visor
    root at eamann-laptop:/home/eamann# insmod visor
    insmod: can't read 'visor': No such file or directory
    root at eamann-laptop:/home/eamann# modprobe visor
    root at eamann-laptop:/home/eamann#
    > Are you using your Palm through a USB port on the computer itself
    > (physically attached to the motherboard), or are you going through a USB
    > hub? 
    >   
    Cable to USB port on the side of the laptop, presumably into the 
    motherboard.
    > Let's start there, and diagnose further.. 
    >   
    This evening I opened JP, did modprobe visor, pressed the button on the 
    Zire and then on JP and got this message. As you can see, there doesn't 
    seem to be a user name. But in File / Install user, my name is there.
    
    Syncing on device /dev/ttyUSB1
     Press the HotSync button now
    ****************************************
    Username is ""
    User ID is 65536
    lastSyncPC = 0
    This PC = 413396775
    Doing a slow sync.
    Syncing DatebookDB
    Error reading appinfo block for AddressDB
    Syncing AddressDB
    slow_sync_application: Unable to open file: AddressDB
    sync_categories: Unable to open file: ToDoDB
    Syncing ToDoDB
    slow_sync_application: Unable to open file: ToDoDB
    sync_categories: Unable to open file: MemoDB
    Syncing MemoDB
    slow_sync_application: Unable to open file: MemoDB
    ReadDBList returned = -204
    palmos_error = 0
    dlp_strerror is No error
    Finished.
    
    
    Best wishes and thanks!
    
    Eamann
    > ------------------------------------------------------------------------
    >
    > _______________________________________________
    > jpilot mailing list
    > jpilot at jpilot.org
    > http://www.jpilot.org/mailman/listinfo/jpilot
    >   
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.jpilot.org/pipermail/jpilot/attachments/20061203/e6b5e231/attachment.htm 
    

     

     

    More information about the jpilot mailing list