Due to a filesystem issue (Let this be a lesson to you, don't 
fsck.reiserfs a ext3 filesystem, even though it does not seem to know 
the difference) I've reinstalled my karmic xubuntu system.

I noticed a few strange things that certainly show there is something 
going wrong.

1. The first time I tried to sync jpilot did not complain, but the 
attempt crashed my Clie. (hard reset required)

2. Due such an extreme failure I unloaded and reloaded the visor module:
sudo modprobe -r visor && sudo modprobe visor

3. Looking at the visor output I see two bindings, for both USB0 and
USB1:

Feb 22 10:39:02 aporia kernel: [48501.368174] usb 2-1: new full speed 
USB device using uhci_hcd and address 7
Feb 22 10:39:02 aporia kernel: [48501.534433] usb 2-1: configuration #1 
chosen from 1 choice
Feb 22 10:39:02 aporia kernel: [48501.555258] visor 2-1:1.0: Handspring 
Visor / Palm OS converter detected
Feb 22 10:39:02 aporia kernel: [48501.555611] usb 2-1: Handspring Visor 
/ Palm OS converter now attached to ttyUSB0
Feb 22 10:39:02 aporia kernel: [48501.556302] usb 2-1: Handspring Visor 
/ Palm OS converter now attached to ttyUSB1

I noticed that /dev/pilot only points to /dev/ttyUSB0.

4. I changed the jpilot settings to use /dev/ttyUSB0. The result is that 
both jpilot and the clie sit there waiting to communicate, but neither 
able to do so. Jpilot prints "press hotsync button" (already pressed to 
initiate the USB connection), and the clie says waiting to connect.

5. I changed the jpilot settings to /dev/ttyUSB1. And guess what, all 
works as it did in Jaunty.

Jan-Willem, can you see if this procedure works for you? (unload, 
reload, change settings to use ttyUSB1 (if your /var/log/messages says 
its being bound like mine does) and then sync?

It appears to me that there visor should only see one converter 
attached, there is only one converter, and only one ttyUSB should be 
bound, not two.

.b.


Jan-Willem van de Meent wrote:
> I have exactly the same problem with a palm m515. I used to be able to
> sync just fine under Jaunty. Under Karmic, the palm device does not even
> show up under lsusb when I press the hotsync button, and dmesg shows
> nothing. I have the visor module loaded.
>

-- 
visor module no works with Palm device after Jaunty to Karmic upgrade on older 
HW.
https://bugs.launchpad.net/bugs/510498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to