Palm-Linux-Bluetooth (was Re: my new Palm Zire 72)
As I already wrote, I'm now able to Hotsync. However, I'm still interested in answers to the following Bluetooth questions. BTW - as I understand it, Bluetooth would also be useful for Internet connection and e-mail. On Saturday 09 July 2005 21:31, Shlomo Solomon wrote: > 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? -- 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]
Re: my new Palm Zire 72
On Sat, Jul 09, 2005 at 09:31:53PM +0300, Shlomo Solomon wrote: (Snipped Bluetooth question - I never used Bluetooth) I already read your later message about 95% success. So ":-)". > > 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). I did not tend to imply you had a hardware problem, only said I think I did. Hardware problems are easier to solve by cross-checking, as you did, and I assume you came to the correct conclusion that it's not hardware. > > 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? You did not say if these messages are before pressing hotsync, or after, or both. Can you try again both before and after, on all 4 devices? My guess is that connecting the cable creates two devices (0 and 1) that do not work, and pressing hotsync creates another two (2 and 3), and one of them works. I guess my guess isn't accurate, but I can't check it. I did see, though, a USB-to-Palm cable that was also a simple card reader (only for the palm's cards). The card reader was active only if you toggled a switch on it, and was (obviously) active on connection, without pressing hotsync. Maybe yours is somewhat similar? > > > 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 :-( Did you check that when it worked, /dev/pilot really linked to USB1? You could try dlpsh instead of pilot-xfer if you want time for checks (it finishes the connection only when you tell it). > > > > 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. Maybe. I don't know. 95% is good, but not enough. The two tungstens here connect few times a day for few months, and rarely have problems. Or at least the rarely tell me they have (they aren't mine). -- Didi = 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]
Re: my new Palm Zire 72
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]
Re: my new Palm Zire 72 - resnd
I sent this over 2 hours ago and it didn't reach the list. On Saturday 09 July 2005 21:31, Shlomo Solomon wrote: > 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? I'd still like an answer to the above questions, BUT my Palm ZIRE 72 is now hotsyncing 95% of the time. I wish I could say what I did or changed - it's driving me crazy, because as far as I know I didn't make any changes. And the syslog entries look exactly as they did before. -- 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]
Re: my new Palm Zire 72
On Saturday 09 July 2005 21:31, Shlomo Solomon wrote: > 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? I'd still like an answer to the above questions, BUT my Palm ZIRE 72 is now hotsyncing 95% of the time. I wish I could say what I did or changed - it's driving me crazy, because as far as I know I didn't make any changes. And the syslog entries look exactly as they did before. -- 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]
Re: my new Palm Zire 72
Yedidyah Bar-David wrote: > > There is no point in doing Ctrl-Z. If you want to shoot - shoot, don't > talk. Ctrl-C. and if this does not work, you can also try Crtl-\ (backslash) (sometimes progs stop responding to SIGINT, but they still respond to this - it sends SIGQUIT) = 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]
Re: my new Palm Zire 72
On Fri, Jul 08, 2005 at 02:36:59PM +0300, Shlomo Solomon wrote: > On Friday 08 July 2005 10:05, Shlomo Solomon wrote: > > > I now intend to clean everything up and make a few more tries. I'll try to > > keep acurate records of what I do and see if the log entries can be of any > > help. > > OK - I did several experiments. Unfortunately, I was unable to reproduce the > situation I mentioned befor when pilot-xfer worked 2 times in about 20 tries. > But here are the results of my experiments. I tried 3 different USB sockets > on my machine. Below I've written what I did each time and included syslog > entries. I am very happy about your progress. I started feeling really bad 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 am also pretty sure it's a (partly) physical problem of the connection, not (only) a software one. There is no point in doing Ctrl-Z. If you want to shoot - shoot, don't talk. Ctrl-C. 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 device they think is the right one and make /dev/pilot a link to it. It's very possible that they are wrong - as I said, it took me a lot of work to automatically make only the above 3 devices work, and the hotplug scripts intend to support theoretically all the devices. So, when you return to playing with this, do the following: connect the device/cable/hub etc. Press hotsync. Then try pilot-xfer or whatever with /dev/ttyUSB[0123] directly, not /dev/pilot. Each time try another one. I am pretty sure one (and probably only one) will work, and will work all the time. 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. 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. Good luck, -- Didi = 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]
Re: my new Palm Zire 72
On Friday 08 July 2005 13:00, Matan Ziv-Av wrote: > On Fri, 8 Jul 2005, Shlomo Solomon wrote: > > 3 - I did alot of experimenting (including connecting to different USB > > plug both with and without a hub). For some reason, out of abot 20 > > experiments I did in the past hour, most of the timed out on the Palm, > > but in 2 cases I got a dta error message from pilot-xfer. And more > > interesting - In 2 cases, pilot-xfer ACTUALLY WORKED. But I haven't been > > able to see any reason why on those 2 tries pilot-xfer DID talk to the > > Palm. > > In my experience - pilot-xfer rarely works, as you found out, but kpilot > works always (when /dev/pilot is created). > This is with kernel 2.6 (FC2,3,4). With kernel 2.4.23 which I used > before installing Fedora, the TE worked flawlessly. I saw this message after sending the results of my experiments and I must say that now I'm completely confused. Of course, I can't argue with your experience, but 1 - I've used pilot-xfer for over 4 years with no problems (on my Palm 3C). Of course that's a serial connection and not USB. Did you mean to say that the problem occurs with USB? 2 - Since I'm quite sure that Kpilot uses pilot-xfer services, why woul Kpilot work whaen pilot-xfer doesn't? 3 - I GOOGLED and found no significant amount of complaints about pilot-xfer with a USB ZIRE72. In fact, I found many claims that it works :-) 4 - I tried what you suggested (Kpilot) and it worked only once out of about 10 attempts. The autodetect wizard did not find the Palm and I had to manually configure for /dev/pilot. Without going into all the details, while trying Kpilot I kept a terminal window open to see what was running and I found that I'm back to the problem I had earlier with multiple ttyUSB* devices. Also, /dev/pilot wich should point to ttyUSB1 sometimes points at ttyUSB3. 5 - Even if Kpilot did work, it's not what I need. I don't want a GUI solution because I have severaal scripts I've written over the years to use pilot-xfer for various tasks - backup, program installation, etc. A GUI won't do what I need. Fir instance, I've set up rotating backups of my valuable data so that the backup script can save different versions on disc or CD and provide me with a log of which backups were done when, etc. -- 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]
Re: my new Palm Zire 72
On Friday 08 July 2005 10:05, Shlomo Solomon wrote: > I now intend to clean everything up and make a few more tries. I'll try to > keep acurate records of what I do and see if the log entries can be of any > help. OK - I did several experiments. Unfortunately, I was unable to reproduce the situation I mentioned befor when pilot-xfer worked 2 times in about 20 tries. But here are the results of my experiments. I tried 3 different USB sockets on my machine. Below I've written what I did each time and included syslog entries. The first few experiments use the USB plug in the back of the computer There are now no /dev/ttyUSB* or /dev/pilot devices Plug in USB cable - ttyUSB0 and 1 and /dev/pilot now exist try pilot-xfer -p /dev/pilot -l and push Palm hotsync button - no result Jul 8 12:15:18 shlomo1 kernel: usb 2-3: new full speed USB device using address 68 Jul 8 12:15:18 shlomo1 kernel: visor 2-3:1.0: Handspring Visor / Palm OS converter detected Jul 8 12:15:18 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 Jul 8 12:15:18 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 Jul 8 12:15:47 shlomo1 kernel: usb 2-3: USB disconnect, address 68 Jul 8 12:15:47 shlomo1 kernel: visor 2-3:1.0: device disconnected Jul 8 12:15:47 shlomo1 kernel: usb 2-3: new full speed USB device using address 69 Jul 8 12:15:47 shlomo1 kernel: visor 2-3:1.0: Handspring Visor / Palm OS converter detected Jul 8 12:15:47 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB2 Jul 8 12:15:47 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB3 Ctrl-Z + cancel Palm hotsync Palm timed out - /dev/pilot is gone but USB0 and 1 still exist Jul 8 12:17:58 shlomo1 kernel: usb 2-3: USB disconnect, address 69 Jul 8 12:17:58 shlomo1 kernel: visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2 Jul 8 12:17:58 shlomo1 kernel: visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3 Jul 8 12:17:58 shlomo1 kernel: visor 2-3:1.0: device disconnected kill pilot-xfer - now USB0 and 1 are gone too Turn on Palm + plug in USB + hotsync button - USB0 and 1 + /dev/pilot now exist pilot-xfer gave error message - "error accepting data on /dev/pilot" Jul 8 12:20:14 shlomo1 kernel: usb 2-3: new full speed USB device using address 70 Jul 8 12:20:14 shlomo1 kernel: visor 2-3:1.0: Handspring Visor / Palm OS converter detected Jul 8 12:20:14 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 Jul 8 12:20:14 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 Jul 8 12:20:43 shlomo1 kernel: usb 2-3: control timeout on ep0in Palm timed out - devices are gone Jul 8 12:22:25 shlomo1 kernel: usb 2-3: USB disconnect, address 70 Jul 8 12:22:25 shlomo1 kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0 Jul 8 12:22:25 shlomo1 kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1 Jul 8 12:22:25 shlomo1 kernel: visor 2-3:1.0: device disconnected Turn on Palm + plug in USB + hotsync button - USB0 and 1 + /dev/pilot now exist hotsync button + pilot-xfer gave error message - "error accepting data on /dev/pilot" the devices still exist but the the pilot-xfer process is gone Jul 8 12:25:11 shlomo1 kernel: usb 2-3: new full speed USB device using address 71 Jul 8 12:25:11 shlomo1 kernel: visor 2-3:1.0: Handspring Visor / Palm OS converter detected Jul 8 12:25:11 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 Jul 8 12:25:11 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 Jul 8 12:25:32 shlomo1 kernel: usb 2-3: USB disconnect, address 71 Jul 8 12:25:32 shlomo1 kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0 Jul 8 12:25:33 shlomo1 kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1 Jul 8 12:25:33 shlomo1 kernel: visor 2-3:1.0: device disconnected Jul 8 12:25:33 shlomo1 kernel: usb 2-3: new full speed USB device using address 72 Jul 8 12:25:33 shlomo1 kernel: visor 2-3:1.0: Handspring Visor / Palm OS converter detected Jul 8 12:25:33 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 Jul 8 12:25:33 shlomo1 kernel: usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 Jul 8 12:25:51 shlomo1 kernel: usb 2-3: control timeout on ep0in unplug cable - devices now disappear Jul 8 12:26:48 shlomo1 kernel: usb 2-3: USB disconnect, address 72 Jul 8 12:26:48 shlomo1 kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0 Jul 8 12:26:48 shlomo1 kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1 Jul
Re: my new Palm Zire 72
On Fri, 8 Jul 2005, Shlomo Solomon wrote: 3 - I did alot of experimenting (including connecting to different USB plug both with and without a hub). For some reason, out of abot 20 experiments I did in the past hour, most of the timed out on the Palm, but in 2 cases I got a dta error message from pilot-xfer. And more interesting - In 2 cases, pilot-xfer ACTUALLY WORKED. But I haven't been able to see any reason why on those 2 tries pilot-xfer DID talk to the Palm. In my experience - pilot-xfer rarely works, as you found out, but kpilot works always (when /dev/pilot is created). This is with kernel 2.6 (FC2,3,4). With kernel 2.4.23 which I used before installing Fedora, the TE worked flawlessly. -- Matan Ziv-Av. [EMAIL PROTECTED] = 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]
Re: my new Palm Zire 72
On Friday 08 July 2005 05:37, Shlomo Solomon wrote: > On Friday 08 July 2005 00:38, Yedidyah Bar-David wrote: > > Can you at least rmmod visor and usb_serial (and modprobe them if > > needed), then repeat the tests? I've made some progress, so I'm on the right track, but . 1 - I figured out why I was getting **seemingly** random device numbers and why some of them disappered and others didn't. When the Palm and pilot-xfer don't communicate, the Palm is usually the one to time-out and when that happens I stop pilot-xfer with Ctrl-Z. I discovered that in these cases, the pilot-xfer proccess is still running. Killing the proccess also kills the ttyUSB* devices that pilot-xfer seems to be holding on to. The cases when pilot-xfer timed out (or got a data error) didn't leave stray proccesses or devices. 2 - After discovering how to get rid of the extra processes and devices, rmmod worked and when I reconnected the USB cable, the modules and devices were correctly loaded. 3 - I did alot of experimenting (including connecting to different USB plug both with and without a hub). For some reason, out of abot 20 experiments I did in the past hour, most of the timed out on the Palm, but in 2 cases I got a dta error message from pilot-xfer. And more interesting - In 2 cases, pilot-xfer ACTUALLY WORKED. But I haven't been able to see any reason why on those 2 tries pilot-xfer DID talk to the Palm. I now intend to clean everything up and make a few more tries. I'll try to keep acurate records of what I do and see if the log entries can be of any help. -- 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]
Re: my new Palm Zire 72 - resend
On Friday 08 July 2005 00:38, Yedidyah Bar-David wrote: > Can you at least rmmod visor and usb_serial (and modprobe them if > needed), then repeat the tests? Sorry, I forgot to write that I tried that and was not able to remove the modules. I didn't try --force because the man page says this is dangerous. [EMAIL PROTECTED] solomon]$ su Password: [EMAIL PROTECTED] solomon]# rmmod visor ERROR: Module visor is in use [EMAIL PROTECTED] solomon]# rmmod usbserial ERROR: Module usbserial is in use by visor [EMAIL PROTECTED] solomon]# lsmod |grep visor visor 16144 4 usbserial 25384 10 visor usbcore 103172 10 usb-storage,visor,usbserial,quickcam,usbmouse,usbhid,usblp,ohci-hcd -- 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]
Re: my new Palm Zire 72 - resend
On Fri, Jul 08, 2005 at 12:02:12AM +0300, Shlomo Solomon wrote: > strange - I sent 2 messages to the list, but only the 2nd one got througt - > so > here's the 1st one again. > > > On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote: > > On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote: > > > OK. Let's start from the very beginning. > > > First, start from a clean known state. Either after a reboot, or try to > > > > For completely unrelated reasons, re-booting is not an option today. I hope > > I'll be able to do the tests you recommended in a day or two and I'll let > > you know what happens - thanks. > > > On thinking it over again, and after a few more of my own experiments, I > can't > see how my problem will be solved by re-booting. After all, that's not really > the LINUX way, is it :-) Can you at least rmmod visor and usb_serial (and modprobe them if needed), then repeat the tests? -- Didi = 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]
Re: my new Palm Zire 72
On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote: > On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote: > > OK. Let's start from the very beginning. > > First, start from a clean known state. Either after a reboot, or try to > > For completely unrelated reasons, re-booting is not an option today. I hope > I'll be able to do the tests you recommended in a day or two and I'll let > you know what happens - thanks. On thinking it over again, and after a few more of my own experiments, I can't see how my problem will be solved by re-booting. After all, that's not really the LINUX way, is it :-) I don't know what has changed, but with all the things I've tried, I'm now getting a /dev/pilot device when I plug in the Palm. But niether it or the /dev/ttyUSB* devices seem to be communicating with the Palm. Here's a bit of output. Notice that at first there's no /dev/pilot and I have USB 0, 1, 4 and 5. Don't ask where 2 and 3 disappered to - I have no answer. [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot ls: /dev/pilot: No such file or directory [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 Now I plug in the Palm and look what **magically** happens. I get the /dev/pilot and USB 2 and 3 devices. [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot lrwxrwxrwx 1 root root 12 Jul 7 23:06 /dev/pilot -> /dev/ttyUSB3 [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 2 Jul 7 23:06 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 7 23:06 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 But when I try pilot-xfer on the 2 new devices (/dev/pilot is really just a link to /dev/ttyUSB3), nothing happens until I do Ctrl-Z. BTW, it doesn't look like a permission problem because solomon is the owner and has read and write permission on the relevant devices. [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/pilot -l Listening to port: /dev/pilot Please press the HotSync button now... [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/ttyUSB4 -l Listening to port: /dev/ttyUSB4 Please press the HotSync button now... Then I look at the devices again: [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 2 Jul 7 23:09 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 7 23:09 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 And again after Hotsync times out - 2 and 3 are gone again. [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 Here's what syslog looks like (I've edited out irrelevant stuff - mostly TCP Rejects from the Firewall): Jul 7 23:08:51 shlomo1 kernel: usb 2-2: USB disconnect, address 31 Jul 7 23:08:51 shlomo1 kernel: visor ttyUSB6: Handspring Visor / Palm OS converter now disconnected from ttyUSB6 Jul 7 23:08:51 shlomo1 kernel: visor ttyUSB7: Handspring Visor / Palm OS converter now disconnected from ttyUSB7 Jul 7 23:08:51 shlomo1 kernel: visor 2-2:1.0: device disconnected Jul 7 23:09:06 shlomo1 kernel: usb 2-2: new full speed USB device using address 32 Jul 7 23:09:06 shlomo1 kernel: visor 2-2:1.0: Handspring Visor / Palm OS converter detected Jul 7 23:09:06 shlomo1 kernel: usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB2 Jul 7 23:09:06 shlomo1 kernel: usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB3 Jul 7 23:11:17 shlomo1 kernel: usb 2-2: USB disconnect, address 32 Jul 7 23:11:17 shlomo1 kernel: visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2 Jul 7 23:11:17 shlomo1 kernel: visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3 Jul 7 23:11:17 shlomo1 kernel: visor 2-2:1.0: device disconnected -- 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]
Re: my new Palm Zire 72 - resend
strange - I sent 2 messages to the list, but only the 2nd one got througt - so here's the 1st one again. On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote: > On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote: > > OK. Let's start from the very beginning. > > First, start from a clean known state. Either after a reboot, or try to > > For completely unrelated reasons, re-booting is not an option today. I hope > I'll be able to do the tests you recommended in a day or two and I'll let > you know what happens - thanks. On thinking it over again, and after a few more of my own experiments, I can't see how my problem will be solved by re-booting. After all, that's not really the LINUX way, is it :-) I don't know what has changed, but with all the things I've tried, I'm now getting a /dev/pilot device when I plug in the Palm. But niether it or the /dev/ttyUSB* devices seem to be communicating with the Palm. Here's a bit of output. Notice that at first there's no /dev/pilot and I have USB 0, 1, 4 and 5. Don't ask where 2 and 3 disappered to - I have no answer. [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot ls: /dev/pilot: No such file or directory [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 Now I plug in the Palm and look what **magically** happens. I get the /dev/pilot and USB 2 and 3 devices. [EMAIL PROTECTED] solomon]$ ls -la /dev/pilot lrwxrwxrwx 1 root root 12 Jul 7 23:06 /dev/pilot -> /dev/ttyUSB3 [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 2 Jul 7 23:06 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 7 23:06 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 But when I try pilot-xfer on the 2 new devices (/dev/pilot is really just a link to /dev/ttyUSB3), nothing happens until I do Ctrl-Z. BTW, it doesn't look like a permission problem because solomon is the owner and has read and write permission on the relevant devices. [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/pilot -l Listening to port: /dev/pilot Please press the HotSync button now... [EMAIL PROTECTED] solomon]$ pilot-xfer -p/dev/ttyUSB4 -l Listening to port: /dev/ttyUSB4 Please press the HotSync button now... Then I look at the devices again: [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 2 Jul 7 23:09 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 7 23:09 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 And again after Hotsync times out - 2 and 3 are gone again. [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyU* crw-rw 1 solomon uucp 188, 0 Jul 6 00:16 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 6 00:16 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 4 Jul 6 05:31 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 6 05:31 /dev/ttyUSB5 Here's what syslog looks like (I've edited out irrelevant stuff - mostly TCP Rejects from the Firewall): Jul 7 23:08:51 shlomo1 kernel: usb 2-2: USB disconnect, address 31 Jul 7 23:08:51 shlomo1 kernel: visor ttyUSB6: Handspring Visor / Palm OS converter now disconnected from ttyUSB6 Jul 7 23:08:51 shlomo1 kernel: visor ttyUSB7: Handspring Visor / Palm OS converter now disconnected from ttyUSB7 Jul 7 23:08:51 shlomo1 kernel: visor 2-2:1.0: device disconnected Jul 7 23:09:06 shlomo1 kernel: usb 2-2: new full speed USB device using address 32 Jul 7 23:09:06 shlomo1 kernel: visor 2-2:1.0: Handspring Visor / Palm OS converter detected Jul 7 23:09:06 shlomo1 kernel: usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB2 Jul 7 23:09:06 shlomo1 kernel: usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB3 Jul 7 23:11:17 shlomo1 kernel: usb 2-2: USB disconnect, address 32 Jul 7 23:11:17 shlomo1 kernel: visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2 Jul 7 23:11:17 shlomo1 kernel: visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3 Jul 7 23:11:17 shlomo1 kernel: visor 2-2:1.0: device disconnected -- 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]
Re: my new Palm Zire 72
I forgot to mention, in my previous message, that I did check the Palm on my kids' Win98 computer and was able to hotsync - so this is not a problem with the Palm. Also, since my LINUX box has no problem communicating with several other USB devices (scanner, printer, camera, mouse, disk-on-key), I don't see this as being a hardware problem. -- 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]
Re: my new Palm Zire 72
On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote: > OK. Let's start from the very beginning. > First, start from a clean known state. Either after a reboot, or try to For completely unrelated reasons, re-booting is not an option today. I hope I'll be able to do the tests you recommended in a day or two and I'll let you know what happens - thanks. -- 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]
Re: my new Palm Zire 72
On Tue, Jul 05, 2005 at 06:23:30PM +0300, Shlomo Solomon wrote: [snip] > I still think it's strange that plugging in the USB cable causes the Kpilot > icon to pop up, so something is, at least partly, set up properly. Not necessarily. Something is set up to respond to USB hotplug events. Maybe not properly. > OK - let me clarify somethig. USB4 and 5 was just an example. Each time I > try, > 2 new USB devices get created (and sometimes get deleted after a while). At > the moment, here's how my system looks (with 12 devices): [snip] OK. Let's start from the very beginning. First, start from a clean known state. Either after a reboot, or try to rmmod both visor and usb-serial. Make sure you have no /dev/ttyUSB*. Then do 'dmesg -c' to clean the kernel's buffer (maybe into some file if you want to keep it). Then do the following things. After each of them, do 'dmesg -c' into a new file. This will let us see what the kernel says at each point. 1. Plug in your cable. 2. Connect the palm to it. 3. Press the hotsync button. 4. Wait until the palm times out. 5. Disconnect the palm from the cable. 6. Unplug the cable. Now do again all of 1-6 (to see what happens on a second time). I hope that the first time will only show USB0 and USB1, as it does for me. Maybe something in kde or kpilot keeps the device(s) open, and that's why on subsequent tries you get new devices. To try that, do all of this without KDE or something smart like it (try e.g. fvwm, wmaker etc. or even a text console if you feel comfortable enough in it). Now, assuming it does start with USB0 and 1, start again from a clean state, then, after you press the hotsync button, try pilot-xfer. First on USB0, then 1. Tell us what happend. -- Didi = 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]
Re: my new Palm Zire 72
On Tuesday 05 July 2005 02:31, Yedidyah Bar-David wrote: > But, as I said, some are actually accessible from ttyUSB0 and some from > ttyUSB1. I wanted to find out automatically which one, which wasn't > easy (found no real info on google). So I simply tried, and at least for > the first 3, I use the following script: > #!/bin/sh > > MAX=30 > The script you included is way above my head - and in any case, you yourself said it probably doesn't apply to my case. I still think it's strange that plugging in the USB cable causes the Kpilot icon to pop up, so something is, at least partly, set up properly. > > I never saw one that used 4 and 5 like yours. A first guess would be OK - let me clarify somethig. USB4 and 5 was just an example. Each time I try, 2 new USB devices get created (and sometimes get deleted after a while). At the moment, here's how my system looks (with 12 devices): [EMAIL PROTECTED] solomon]# ls -la /dev/ttyUSB* crw-rw 1 solomon uucp 188, 0 Jul 4 22:33 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 4 22:33 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 10 Jul 5 17:59 /dev/ttyUSB10 crw-rw 1 solomon uucp 188, 11 Jul 5 17:59 /dev/ttyUSB11 crw-rw 1 solomon uucp 188, 2 Jul 5 00:54 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 5 00:54 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 5 01:09 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 5 01:09 /dev/ttyUSB5 crw-rw 1 solomon uucp 188, 6 Jul 5 17:51 /dev/ttyUSB6 crw-rw 1 solomon uucp 188, 7 Jul 5 17:51 /dev/ttyUSB7 crw-rw 1 solomon uucp 188, 8 Jul 5 17:51 /dev/ttyUSB8 crw-rw 1 solomon uucp 188, 9 Jul 5 17:51 /dev/ttyUSB9 > that you also have other usb-serial hardware connected, but you say that > before connecting there are no devices, which rules it out. I have several USB devices (camera, printer, scanner, USB Hub) but I guess none of them use usb-serial or need to define /dev/ttyUSB* since all my hardware works but as I said, none of the /dev/ttyUSB* existed before. > Did you try also 0-3 (Even though the kernel says 4 and 5)? yes > Doesn't google say anything useful about Zire72? I found lots of info, but none seems to be relevant to my problem. > Are you sure the hardware is ok? Does it work in Windows? You might > even be able to find out what device it uses in Windows (I have no > idea how). I don't have Windows on my box. I suppose I could try on my kids' machine, but I don't think that would prove anything since I guess the USB definitins on another machine would be different. > BTW, which kernel version? Did you try doing this as root (not needed 2.6.8.1-12mdk (Mandrake 10.1) I also tried as root > here, but lsusb -vv does need it on some combinations of > kernel/filesystem (there are both usbfs and the older usbdevfs)? lsusb -vv does need root, as you said. (It seems OK to me, but I don't really know): Bus 002 Device 068: ID 0830:0061 Palm, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x0830 Palm, Inc. idProduct 0x0061 bcdDevice1.00 iManufacturer 1 PalmOne, Inc. iProduct2 Palm Handheld iSerial 5 303056594131363535523158 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type none wMa
Re: my new Palm Zire 72
On Tuesday 05 July 2005 02:31, Yedidyah Bar-David wrote: > But, as I said, some are actually accessible from ttyUSB0 and some from > ttyUSB1. I wanted to find out automatically which one, which wasn't > easy (found no real info on google). So I simply tried, and at least for > the first 3, I use the following script: > #!/bin/sh > > MAX=30 > The script you included is way above my head - and in any case, you yourself said it probably doesn't apply to my case. I still think it's strange that plugging in the USB cable causes the Kpilot icon to pop up, so something is, at least partly, set up properly. > > I never saw one that used 4 and 5 like yours. A first guess would be OK - let me clarify somethig. USB4 and 5 was just an example. Each time I try, 2 new USB devices get created (and sometimes get deleted after a while). At the moment, here's how my system looks (with 12 devices): [EMAIL PROTECTED] solomon]# ls -la /dev/ttyUSB* crw-rw 1 solomon uucp 188, 0 Jul 4 22:33 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 4 22:33 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 10 Jul 5 17:59 /dev/ttyUSB10 crw-rw 1 solomon uucp 188, 11 Jul 5 17:59 /dev/ttyUSB11 crw-rw 1 solomon uucp 188, 2 Jul 5 00:54 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 5 00:54 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 5 01:09 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 5 01:09 /dev/ttyUSB5 crw-rw 1 solomon uucp 188, 6 Jul 5 17:51 /dev/ttyUSB6 crw-rw 1 solomon uucp 188, 7 Jul 5 17:51 /dev/ttyUSB7 crw-rw 1 solomon uucp 188, 8 Jul 5 17:51 /dev/ttyUSB8 crw-rw 1 solomon uucp 188, 9 Jul 5 17:51 /dev/ttyUSB9 > that you also have other usb-serial hardware connected, but you say that > before connecting there are no devices, which rules it out. I have several USB devices (camera, printer, scanner, USB Hub) but I guess none of them use usb-serial or need to define /dev/ttyUSB* since all my hardware works but as I said, none of the /dev/ttyUSB* existed before. > Did you try also 0-3 (Even though the kernel says 4 and 5)? yes > Doesn't google say anything useful about Zire72? I found lots of info, but none seems to be relevant to my problem. > Are you sure the hardware is ok? Does it work in Windows? You might > even be able to find out what device it uses in Windows (I have no > idea how). I don't have Windows on my box. I suppose I could try on my kids' machine, but I don't think that would prove anything since I guess the USB definitins on another machine would be different. > BTW, which kernel version? Did you try doing this as root (not needed 2.6.8.1-12mdk (Mandrake 10.1) I also tried as root > here, but lsusb -vv does need it on some combinations of > kernel/filesystem (there are both usbfs and the older usbdevfs)? lsusb -vv does need root, as you said. It seems OK to me, but I don't really know. Here's part of the output: Bus 002 Device 068: ID 0830:0061 Palm, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x0830 Palm, Inc. idProduct 0x0061 bcdDevice1.00 iManufacturer 1 PalmOne, Inc. iProduct2 Palm Handheld iSerial 5 303056594131363535523158 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type
Re: my new Palm Zire 72
On Tue, Jul 05, 2005 at 01:32:33AM +0300, Shlomo Solomon wrote:
> OK - I think I'm making "some" progress here. Each time I connect or
At last :-)
> disconnect the USB cable, there are changes in the /dev directory. Notice
> that there are several USB devices being created - always two at a time. I'm
> also including dmesg output below. But I've tried using each of the USB
> devices to sync and I get no response from the Palm.
>
> For example, the command pilot-xfer -p/dev/ttyUSB5 -l and running hotsync
> does
> nothing and eventually, the Palm hotsync application times out.
>
>
>
> [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyUSB*
> crw-rw 1 solomon uucp 188, 0 Jul 4 22:33 /dev/ttyUSB0
> crw-rw 1 solomon uucp 188, 1 Jul 4 22:33 /dev/ttyUSB1
> crw-rw 1 solomon uucp 188, 2 Jul 5 00:54 /dev/ttyUSB2
> crw-rw 1 solomon uucp 188, 3 Jul 5 00:54 /dev/ttyUSB3
> crw-rw 1 solomon uucp 188, 4 Jul 5 00:55 /dev/ttyUSB4
> crw-rw 1 solomon uucp 188, 5 Jul 5 00:55 /dev/ttyUSB5
[snip]
> -- from dmesg
>
> usb 2-2: new full speed USB device using address 54
> visor 2-2:1.0: Handspring Visor / Palm OS converter detected
> usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB4
> usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB5
[snip]
OK.
I have no idea about how to continue. I'll just summarize my experience.
I never used a Zire72.
I did use (i.e. connected to a linux machine) a VX (serial cradle), and
m130, Tungsten T, Tungsten T3, Zire31 (only a few times). All of them,
IIRC, and at least the Tungstens for sure, emit two connections in dmesg
- e.g.
Jul 3 08:01:59 maint kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached to ttyUSB0
Jul 3 08:01:59 maint kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached to ttyUSB1
Jul 3 08:02:03 maint kernel: visor ttyUSB0: Handspring Visor / Palm OS
converter now disconnected from ttyUSB0
Jul 3 08:02:03 maint kernel: visor ttyUSB1: Handspring Visor / Palm OS
converter now disconnected from ttyUSB1
But, as I said, some are actually accessible from ttyUSB0 and some from
ttyUSB1. I wanted to find out automatically which one, which wasn't
easy (found no real info on google). So I simply tried, and at least for
the first 3, I use the following script:
#!/bin/sh
MAX=30
# Fallback
dev=ttyUSB1
tmp1=`mktemp /tmp/get-palm-dev.XX`
n=0
while [ $n -lt $MAX ]; do
lsusb -v > $tmp1
if cat $tmp1 | awk '/Palm/ {palm=1; p=$0} palm && /bcdUSB/ {print p,
$0; exit}' | grep -q 'P
alm Tungsten T.*bcdUSB.*1\.00'; then
dev=ttyUSB1
break
elif cat $tmp1 | grep -q Palm; then
dev=ttyUSB0
break
fi
sleep 1
echo -n . 1>&2
n=`expr $n + 1`
done
rm $tmp1
echo $dev
That is, the only difference between the Tungstens is the bcdUSB, which
is IIRC 1.10 with the T3 and 1.00 with T (or vice-verse).
I do not think it will work for other palms without tweaking, so do not
use it as is.
I never saw one that used 4 and 5 like yours. A first guess would be
that you also have other usb-serial hardware connected, but you say that
before connecting there are no devices, which rules it out.
Did you try also 0-3 (Even though the kernel says 4 and 5)?
Doesn't google say anything useful about Zire72?
You might want to look at linux/Documentation/usb/usb-serial.txt.
Are you sure the hardware is ok? Does it work in Windows? You might
even be able to find out what device it uses in Windows (I have no
idea how).
BTW, which kernel version? Did you try doing this as root (not needed
here, but lsusb -vv does need it on some combinations of
kernel/filesystem (there are both usbfs and the older usbdevfs)?
--
Didi
=
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]
Re: my new Palm Zire 72
On Monday 04 July 2005 23:43, Yedidyah Bar-David wrote: >If not, maybe you need to manually load the module - I don't know if >hotplug does that automatically (and you did not say if you use hotplug >but I guess you do). ># modprobe visor not necessary - the module is loaded: [EMAIL PROTECTED] solomon]# lsmod | grep visor visor 16144 17 usbserial 25384 27 visor usbcore 103172 9 visor,usbserial,usbmouse,quickcam,usbhid,usblp,ohci-hcd [EMAIL PROTECTED] solomon]# > Ohhh, one more thing - maybe that's the problem: The device is connected > only when you do hotsync (with the cradle or the hotsync app). Try to > press it and then check stuff (if you have a device etc.). Otherwise it > does not appear to be connected (e.g. you won't see it in lsusb). On Tuesday 05 July 2005 00:15, Matan Ziv-Av wrote: > You should create this file. No matter the name (as long as it ends > with .rules), but the content should be the line I wrote. If you don't > have ttyUSB devices at all, that might indicate a problem. Please show > the relevant lines from dmesg. At least on the TE, the device is > recognized (and the device files created) only when I run hotsync on the > Palm. OK - I think I'm making "some" progress here. Each time I connect or disconnect the USB cable, there are changes in the /dev directory. Notice that there are several USB devices being created - always two at a time. I'm also including dmesg output below. But I've tried using each of the USB devices to sync and I get no response from the Palm. For example, the command pilot-xfer -p/dev/ttyUSB5 -l and running hotsync does nothing and eventually, the Palm hotsync application times out. [EMAIL PROTECTED] solomon]$ ls -la /dev/ttyUSB* crw-rw 1 solomon uucp 188, 0 Jul 4 22:33 /dev/ttyUSB0 crw-rw 1 solomon uucp 188, 1 Jul 4 22:33 /dev/ttyUSB1 crw-rw 1 solomon uucp 188, 2 Jul 5 00:54 /dev/ttyUSB2 crw-rw 1 solomon uucp 188, 3 Jul 5 00:54 /dev/ttyUSB3 crw-rw 1 solomon uucp 188, 4 Jul 5 00:55 /dev/ttyUSB4 crw-rw 1 solomon uucp 188, 5 Jul 5 00:55 /dev/ttyUSB5 [EMAIL PROTECTED] solomon]$ ls -la /dev/tts total 0 drwxr-xr-x 2 root root 320 Jul 5 00:55 ./ drwxr-xr-x 21 root root 4540 Jul 5 00:55 ../ lrwxrwxrwx 1 root root8 Jun 24 05:31 0 -> ../ttyS0 lrwxrwxrwx 1 root root8 Jun 24 05:31 1 -> ../ttyS1 lrwxrwxrwx 1 root root8 Jun 24 05:31 2 -> ../ttyS2 lrwxrwxrwx 1 root root8 Jun 24 05:31 3 -> ../ttyS3 lrwxrwxrwx 1 root root8 Jun 24 05:31 4 -> ../ttyS4 lrwxrwxrwx 1 root root8 Jun 24 05:31 5 -> ../ttyS5 lrwxrwxrwx 1 root root8 Jun 24 05:31 6 -> ../ttyS6 lrwxrwxrwx 1 root root8 Jun 24 05:31 7 -> ../ttyS7 lrwxrwxrwx 1 root root 10 Jul 4 22:33 USB0 -> ../ttyUSB0 lrwxrwxrwx 1 root root 10 Jul 4 22:33 USB1 -> ../ttyUSB1 lrwxrwxrwx 1 root root 10 Jul 5 00:54 USB2 -> ../ttyUSB2 lrwxrwxrwx 1 root root 10 Jul 5 00:54 USB3 -> ../ttyUSB3 lrwxrwxrwx 1 root root 10 Jul 5 00:55 USB4 -> ../ttyUSB4 lrwxrwxrwx 1 root root 10 Jul 5 00:55 USB5 -> ../ttyUSB5 [EMAIL PROTECTED] solomon]$ -- from dmesg usb 2-2: new full speed USB device using address 54 visor 2-2:1.0: Handspring Visor / Palm OS converter detected usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB4 usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB5 < snip > usb 2-2: USB disconnect, address 54 visor ttyUSB4: Handspring Visor / Palm OS converter now disconnected from ttyUSB4 visor ttyUSB5: Handspring Visor / Palm OS converter now disconnected from ttyUSB5 visor 2-2:1.0: device disconnected usb 2-2: new full speed USB device using address 55 visor 2-2:1.0: Handspring Visor / Palm OS converter detected usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB4 usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB5 usb 2-2: USB disconnect, address 55 visor ttyUSB4: Handspring Visor / Palm OS converter now disconnected from ttyUSB4 visor ttyUSB5: Handspring Visor / Palm OS converter now disconnected from ttyUSB5 visor 2-2:1.0: device disconnected usb 2-2: new full speed USB device using address 56 visor 2-2:1.0: Handspring Visor / Palm OS converter detected usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB4 usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB5 -- 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]
Re: my new Palm Zire 72
On Mon, 4 Jul 2005, Shlomo Solomon wrote:
On my Fedora system, this is the content of
/etc/udev/rules.d/10-visor.rules:
BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*",
SYMLINK="pilot"
If you are using another system based on udev, it might be similar. If
you don't use udev, just create this symbolic link (pilot->ttyUSB1).
Mandrake also uses udev, but I didn't find anything "interesting"
in /etc/udev/rules.d - again, maybe I'm looking in the wrong palce. I admit
to knowing very little about how udev works. Here's the content of that
directory.
[EMAIL PROTECTED] solomon]$ ls -la /etc/udev/rules.d
total 28
drwxr-xr-x 2 root root 272 Jan 4 15:55 ./
drwxr-xr-x 5 root root 160 Jan 4 15:55 ../
-rw-r--r-- 1 root root 2094 Dec 28 2004 00-lsb.rules
-rw-r--r-- 1 root root 4090 Dec 28 2004 01-devfs.rules
-rw-r--r-- 1 root root 64 Dec 28 2004 06-dvb.rules
-rw-r--r-- 1 root root 29 Dec 20 2004 dvd2.rules
-rw-r--r-- 1 root root 28 Dec 20 2004 dvd.rules
-rw-r--r-- 1 root root 37 Dec 20 2004 mouse.rules
-rw-r--r-- 1 root root 312 Dec 28 2004 provision.tbl
You should create this file. No matter the name (as long as it ends
with .rules), but the content should be the line I wrote. If you don't
have ttyUSB devices at all, that might indicate a problem. Please show
the relevant lines from dmesg. At least on the TE, the device is
recognized (and the device files created) only when I run hotsync on the
Palm.
--
Matan Ziv-Av. [EMAIL PROTECTED]
=
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]
Re: my new Palm Zire 72
On Mon, Jul 04, 2005 at 10:56:55PM +0300, Shlomo Solomon wrote: > On Monday 04 July 2005 21:46, Yedidyah Bar-David wrote: > > USB Palms use either /dev/ttyUSB0 or /dev/ttyUSB1, depending on model. > > Use e.g. something like 'dlpsh -p /dev/ttyUSB0' (from pilot-link) to > > find out which one, and make /dev/pilot a link to it. > I tried the dlpsh command (even though neither of these devices exist), but > as > I expected there was no result. OK. For a start, try to create it manually. # mknod /dev/ttyUSB0 c 188 0 # mknod /dev/ttyUSB1 c 188 1 If it works, you might try playing with udev etc. if you want. If not, maybe you need to manually load the module - I don't know if hotplug does that automatically (and you did not say if you use hotplug but I guess you do). # modprobe visor Ohhh, one more thing - maybe that's the problem: The device is connected only when you do hotsync (with the cradle or the hotsync app). Try to press it and then check stuff (if you have a device etc.). Otherwise it does not appear to be connected (e.g. you won't see it in lsusb). -- Didi = 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]
Re: my new Palm Zire 72
On Monday 04 July 2005 21:43, Lior Kaplan wrote:
> why not to link from /dev/pilot to /dev/usb ? (or whatever the device is
> called on your system).
as I wrote before, I didn't find any new device in /dev - maybe I'm not
looking in the right place.
On Monday 04 July 2005 21:46, Yedidyah Bar-David wrote:
> USB Palms use either /dev/ttyUSB0 or /dev/ttyUSB1, depending on model.
> Use e.g. something like 'dlpsh -p /dev/ttyUSB0' (from pilot-link) to
> find out which one, and make /dev/pilot a link to it.
I tried the dlpsh command (even though neither of these devices exist), but as
I expected there was no result.
On Monday 04 July 2005 22:26, Matan Ziv-Av wrote:
> On my Fedora system, this is the content of
> /etc/udev/rules.d/10-visor.rules:
>
> BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*",
> SYMLINK="pilot"
>
> If you are using another system based on udev, it might be similar. If
> you don't use udev, just create this symbolic link (pilot->ttyUSB1).
Mandrake also uses udev, but I didn't find anything "interesting"
in /etc/udev/rules.d - again, maybe I'm looking in the wrong palce. I admit
to knowing very little about how udev works. Here's the content of that
directory.
[EMAIL PROTECTED] solomon]$ ls -la /etc/udev/rules.d
total 28
drwxr-xr-x 2 root root 272 Jan 4 15:55 ./
drwxr-xr-x 5 root root 160 Jan 4 15:55 ../
-rw-r--r-- 1 root root 2094 Dec 28 2004 00-lsb.rules
-rw-r--r-- 1 root root 4090 Dec 28 2004 01-devfs.rules
-rw-r--r-- 1 root root 64 Dec 28 2004 06-dvb.rules
-rw-r--r-- 1 root root 29 Dec 20 2004 dvd2.rules
-rw-r--r-- 1 root root 28 Dec 20 2004 dvd.rules
-rw-r--r-- 1 root root 37 Dec 20 2004 mouse.rules
-rw-r--r-- 1 root root 312 Dec 28 2004 provision.tbl
I looked at all the files listed above, but none of them mention the Palm.
The strange thing is that, as I wrote earlier, a Kpilot icon pops up when I
plug in the USB cable, so obviously, something is at least partially
configured.
--
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]
Re: my new Palm Zire 72
On Mon, 4 Jul 2005, Shlomo Solomon wrote:
When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on
the KDE desktop so I thought - "wow, this is going to be easy". But, although
the icon popped up (and usbview also recognizes the Palm), it doesn't work. I
tried autodetection in the Kpilot configuration wizard, but it seems to be
looking for /dev/pilot which doesn't exist. I looked in the /dev directory
and didn't find anything.
If someone could "walk me through" the setup, it would be greatly appreciated.
On my Fedora system, this is the content of
/etc/udev/rules.d/10-visor.rules:
BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*", SYMLINK="pilot"
If you are using another system based on udev, it might be similar. If
you don't use udev, just create this symbolic link (pilot->ttyUSB1).
--
Matan Ziv-Av. [EMAIL PROTECTED]
=
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]
Re: my new Palm Zire 72
On Mon, Jul 04, 2005 at 09:07:02PM +0300, Shlomo Solomon wrote: > This should be easy, but for some reason, I can't seem to sync my new USB > Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked > fine. > > When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on > the KDE desktop so I thought - "wow, this is going to be easy". But, although > the icon popped up (and usbview also recognizes the Palm), it doesn't work. I > tried autodetection in the Kpilot configuration wizard, but it seems to be > looking for /dev/pilot which doesn't exist. I looked in the /dev directory > and didn't find anything. USB Palms use either /dev/ttyUSB0 or /dev/ttyUSB1, depending on model. Use e.g. something like 'dlpsh -p /dev/ttyUSB0' (from pilot-link) to find out which one, and make /dev/pilot a link to it. > > If someone could "walk me through" the setup, it would be greatly appreciated. Feel free to contact me if you need help. -- Didi = 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]
Re: my new Palm Zire 72
why not to link from /dev/pilot to /dev/usb ? (or whatever the device is called on your system). Shlomo Solomon wrote: > This should be easy, but for some reason, I can't seem to sync my new USB > Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked > fine. > > When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on > the KDE desktop so I thought - "wow, this is going to be easy". But, although > the icon popped up (and usbview also recognizes the Palm), it doesn't work. I > tried autodetection in the Kpilot configuration wizard, but it seems to be > looking for /dev/pilot which doesn't exist. I looked in the /dev directory > and didn't find anything. > > If someone could "walk me through" the setup, it would be greatly appreciated. > > TIA > -- Regards, Lior Kaplan [EMAIL PROTECTED] http://www.Guides.co.il Debian GNU/Linux unstable (SID) = 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]
my new Palm Zire 72
This should be easy, but for some reason, I can't seem to sync my new USB Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked fine. When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on the KDE desktop so I thought - "wow, this is going to be easy". But, although the icon popped up (and usbview also recognizes the Palm), it doesn't work. I tried autodetection in the Kpilot configuration wizard, but it seems to be looking for /dev/pilot which doesn't exist. I looked in the /dev directory and didn't find anything. If someone could "walk me through" the setup, it would be greatly appreciated. TIA -- 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]
