http://qa.mandrakesoft.com/show_bug.cgi?id=3381
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From [EMAIL PROTECTED] 2003-04-01 13:03 -------
Ok, let me guess : you have a Clié N6x0C or something like that :((
(I have one)..
These devices needs to use /dev/usb/tts/0 instead of 1 but unfortunately, there
is no way to autodetect if a particular Palm devices needs 1 or 0 USB port :
>From /usr/share/doc/pilot-link-0.11.7/README.usb :
(as of the time of this README, two Sony models use /dev/ttyUSB0, and the rest
of the Sony and Palm models use /dev/ttyUSB1)
Current workaround is to use /dev/usb/tts/0 instead of /dev/pilot.
FredL, could we try to modify /etc/dynamic/scripts/visor.script to try to handle
this "switch" more dynamically ? I seem a compatibility table is available in
/usr/share/doc/pilot-link-0.11.7/README.usb but it is still incomplete..
Anyway, this won't be completely fixed until Mdk 9.2 ..
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
Having read the pilot-link web pages, how-tos, man pages etc. I was expecting
to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is
usbcore and usb-uhci.
Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop.
Pressing this launches KPilot which reports:
22:11:53 Trying to open device...
22:11:53 Could not open device: /dev/pilot (will retry)
`lsmod' output is usbcore and usb-uhci
/dev/pilot is a symbolic link to /dev/usb/tts/1
`modprobe'ing usbserial and visor make no difference at all
`lsmod' produces the output:
visor 10440 0
usbserial 21468 0 [visor]
usb-uhci 24652 0 (unused)
usbcore 72992 1 [usbdnet visor usbserial usb-uhci]
The Pilot is connected via the cradle cable into the USB port. It makes no difference
if
"Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before
doing the Hot Sync.
Running `addresses' outputs:
No $PILOTPORT specified and no -p <port> given.
Defaulting to '/dev/pilot'
ERROR: No such device (19)
Press the HotSync button first and relaunch this conduit..
Unable to bind to port: /dev/pilot
None of the pilot-link programs can contact it.
How does KDE pick up the fact that there is a Palm attached when none of
the USB modules know about it ?!?!
