Before I answer Yedidyah's latest post on this subject, I'd like to ask if Bluetooth might be a solution to my Hotsync problem. The Zire 72 has built-in Bluetooth and I know MDK10.1 supports Bluetooth. I've Googled and found that connecting Palm to Linux via Bluetooth is do-able. My questions: 1 - Is it worth trying? 2 - Does anyone have hands-on experience? 3 - What Bluetooth dongle do you reccomend with good Linux support?
On Friday 08 July 2005 21:50, Yedidyah Bar-David wrote: > I am very happy about your progress. I started feeling really bad The only **good** thing about my progress is that it's proof this thing can work. But 2 successes out of about 20 tries is next to useless. And since then I've tried many more tries with no success :-( > about this. For the record - I did see differences between the > connection reliability of different palms connected to the same usb > cable. Tungsten T3 was more problematic than Tungsten T and m130. But > the problems are occasional, not systematic or as frequent as yours. I I can accept **occasional** but this is ridiculous > am also pretty sure it's a (partly) physical problem of the connection, > not (only) a software one. I doubt that. I've tried different USB plugs (back panel, front panel and via a Hub) and 2 different cables. I think I already wrote that I have no problems with my printer, scanner, web-cam, disk-on-key or mouse (all USB). > There is no point in doing Ctrl-Z. If you want to shoot - shoot, don't > talk. Ctrl-C. Of course you're right - silly of me. > I did not thoroughly read all your tests and results. I do have two > points to make, some of them I already said in earlier posts. > 1. There is no magic in /dev/pilot. The hotplug scripts choose the Although on the tests I sent yesterday I tried /dev/pilot, I do know that this is only a pointer and might not point correctly. So I did do several test directly to the ttyUSB* devices and had no better results. In fact, it seems to me that /dev/pilot IS being correctly defined. Look at the following test: ----- before connecting the cable ------- [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot ls: /dev/pilot: No such file or directory [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* ls: /dev/ttyU*: No such file or directory ---- connect the cable ------ [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot lrwxrwxrwx 1 root root 12 Jul 9 21:14 /dev/pilot -> /dev/ttyUSB1 [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw---- 1 solomon uucp 188, 0 Jul 9 21:14 /dev/ttyUSB0 crw-rw---- 1 solomon uucp 188, 1 Jul 9 21:14 /dev/ttyUSB1 [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/ttyUSB0 -l Listening to port: /dev/ttyUSB0 Please press the HotSync button now... ---- Ctrl-C to stop this ------ [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/ttyUSB1 -l Listening to port: /dev/ttyUSB1 Please press the HotSync button now... Error accepting data on /dev/ttyUSB1 [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/pilot -l Listening to port: /dev/pilot Please press the HotSync button now... Error accepting data on /dev/pilot Notice that both /dev/pilot and /dev/ttyUSB1 give the data error message (not surprising since they're really the same device). I interpret this to mean that some attempt to communicate is being made and failing while the USB0 device gets no reaction. Am I wrong? After writing the above and (obviously) before sending this message, I succeeded once more - using /dev/pilot - so I do think /dev/pilot IS pointing to the correct port (ttyUSB1). But after the one success, again no luck :-( > 2. The behaviour you describe is definitely different from what I see > here (with all 3 devices) - none of them cause the creation of any > /dev/ttyUSB device on connection, and all cause creation of 2 devices (0 > and 1 if it's the only device connected) when pressing hotsync in the > palm. They differ in which of the two devices actually work. again - I do think /dev/pilot is being created correctly, but I have tried all the other created devices. > I never tried connecting through a hub, as far as I recall. I do not > think a hub should matter, assuming it's otherwise working well. I agree, but I tried various plugs (my box has 6) so I tried the hub too. -- Shlomo Solomon http://the-solomons.net Sent by KMail 1.7.1 (KDE 3.2.3) on LINUX Mandrake 10.1 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
