Hi,
I have a PalmOS device (Sony Clié PEG-TH55) that I have been synchronizing with Fedora 8 flawlessly using KPilot. However, in Fedora 9, no /dev/ttyUSB device is created when the Clié is connected to the PC. I got the following in /var/log/messages:
Oct 7 15:48:35 home-01 kernel: usb 4-2: new full speed USB device using uhci_hcd and address 3 Oct 7 15:48:35 home-01 kernel: usb 4-2: configuration #1 chosen from 1 choice Oct 7 15:48:35 home-01 kernel: usb 4-2: New USB device found, idVendor=054c, idProduct=0144 Oct 7 15:48:35 home-01 kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 7 15:48:35 home-01 kernel: usb 4-2: Product: Palm Handheld Oct 7 15:48:35 home-01 kernel: usb 4-2: Manufacturer: Palm. Inc.
However, no device is created.
How do I get old /dev/ttyUSB0?
Thanks,
Marcelo
Marcelo Magno T. Sales wrote:
Hi,
I have a PalmOS device (Sony Clié PEG-TH55) that I have been synchronizing with Fedora 8 flawlessly using KPilot. However, in Fedora 9, no /dev/ttyUSB device is created when the Clié is connected to the PC. I got the following in /var/log/messages:
Oct 7 15:48:35 home-01 kernel: usb 4-2: new full speed USB device using uhci_hcd and address 3 Oct 7 15:48:35 home-01 kernel: usb 4-2: configuration #1 chosen from 1 choice Oct 7 15:48:35 home-01 kernel: usb 4-2: New USB device found, idVendor=054c, idProduct=0144 Oct 7 15:48:35 home-01 kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 7 15:48:35 home-01 kernel: usb 4-2: Product: Palm Handheld Oct 7 15:48:35 home-01 kernel: usb 4-2: Manufacturer: Palm. Inc.
However, no device is created.
How do I get old /dev/ttyUSB0?
Thanks,
Marcelo
You should be able to specify usb: as your port, and have it use usblib to talk to the PalmOS device without needing /dev/ttyUSB0.
Mikkel
Hi, Mikkel
You should be able to specify usb: as your port, and have it use usblib to talk to the PalmOS device without needing /dev/ttyUSB0.
Mikkel
I was not aware of this innovation :) Indeed, when I specified usb: as port, KPilot found the PalmOS device. However, the synchronization process was "done" in less than half a second and nothing was synchronized at all. Maybe I have to read more about usblib. Do I have to add something after usb: as port or is that all? Can you point me to some useful documentation about usblib?
Thanks,
Marcelo
Em Ter 07 Out 2008, Marcelo Magno T. Sales escreveu:
Hi, Mikkel
You should be able to specify usb: as your port, and have it use usblib to talk to the PalmOS device without needing /dev/ttyUSB0.
Mikkel
I was not aware of this innovation :) Indeed, when I specified usb: as port, KPilot found the PalmOS device. However, the synchronization process was "done" in less than half a second and nothing was synchronized at all. Maybe I have to read more about usblib. Do I have to add something after usb: as port or is that all? Can you point me to some useful documentation about usblib?
Never mind, for now on I'm sure it's a KPilot's problem. I'll dig it a little further.
Thanks for the usb: tip
[]'s Marcelo
Marcelo Magno T. Sales wrote:
Hi, Mikkel
You should be able to specify usb: as your port, and have it use usblib to talk to the PalmOS device without needing /dev/ttyUSB0.
Mikkel
I was not aware of this innovation :) Indeed, when I specified usb: as port, KPilot found the PalmOS device. However, the synchronization process was "done" in less than half a second and nothing was synchronized at all. Maybe I have to read more about usblib. Do I have to add something after usb: as port or is that all? Can you point me to some useful documentation about usblib?
Thanks,
Marcelo
That sounds like you don't have any conduits configured in KPilot, so there was nothing to synchronize.
Mikkel
Em Ter 07 Out 2008, Mikkel L. Ellertson escreveu:
Marcelo Magno T. Sales wrote:
Hi, Mikkel
You should be able to specify usb: as your port, and have it use usblib to talk to the PalmOS device without needing /dev/ttyUSB0.
Mikkel
I was not aware of this innovation :) Indeed, when I specified usb: as port, KPilot found the PalmOS device. However, the synchronization process was "done" in less than half a second and nothing was synchronized at all. Maybe I have to read more about usblib. Do I have to add something after usb: as port or is that all? Can you point me to some useful documentation about usblib?
Thanks,
Marcelo
That sounds like you don't have any conduits configured in KPilot, so there was nothing to synchronize.
I saw later it was claiming not to be able to detect if screensaver was running, so it could not synchronize. I disabled the "Do not synchronize while screensaver is active" option and it worked. Well... It crashes very often during synchronization, but this happened in F8 too.
Thanks,
Marcelo