[opensuse-factory] Palm Pilot device
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it. Has anyone on the list got a similar one to work? -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Jan 22, 2011 at 12:19:03AM -0600, Donn Washburn wrote:
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it.
Has anyone on the list got a similar one to work?
Use the pilot-link packages to talk to the device, it should be able to find it just fine. If you have problems, ask on the pilot-link lists, they can hep out out. Hope this helps, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/21/2011 11:35 PM, Greg KH wrote:
On Sat, Jan 22, 2011 at 12:19:03AM -0600, Donn Washburn wrote:
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it.
Has anyone on the list got a similar one to work? Use the pilot-link packages to talk to the device, it should be able to find it just fine.
If you have problems, ask on the pilot-link lists, they can hep out out.
Hope this helps,
greg k-h
Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 22 Jan 2011 06:27:28 -0600 Donn Washburn <n5xwb@comcast.net> wrote:
Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem
pilot-link is a program IIUC, not a driver. Start it. Search the device with it. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/22/2011 12:00 PM, Stefan Seyfried wrote:
On Sat, 22 Jan 2011 06:27:28 -0600 Donn Washburn<n5xwb@comcast.net> wrote:
Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem pilot-link is a program IIUC, not a driver.
Start it. Search the device with it. Well if lsusb doesn't see the device then it is a kernel problem with visor or it is a udev rule problem. pilot-link works with jpilot but has nothing to with the lsb system. I say it is a udev problem.
-- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 22 Jan 2011 14:27:25 -0600 Donn Washburn <n5xwb@comcast.net> wrote:
Well if lsusb doesn't see the device then it is a kernel problem with visor or it is a udev rule problem. pilot-link works with jpilot but has nothing to with the lsb system. I say it is a udev problem.
Did you try it? If greg k-h tells you to try pilot-link, that's the most expert advice you can probably get. If you choose to ignore it, well, good luck ;) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/23/2011 10:44 AM, Stefan Seyfried wrote:
On Sat, 22 Jan 2011 14:27:25 -0600 Donn Washburn<n5xwb@comcast.net> wrote:
Well if lsusb doesn't see the device then it is a kernel problem with visor or it is a udev rule problem. pilot-link works with jpilot but has nothing to with the lsb system. I say it is a udev problem. Did you try it? If greg k-h tells you to try pilot-link, that's the most expert advice you can probably get. If you choose to ignore it, well, good luck ;) openSuSE 11.4 M5 from the NET
Well to be honest! I blew it today and had to reload due to a typo on this machine. 4 hrs. of reloading from the NET and all of the "not found" on the sites the NET offered. Like "libkdecards4" which is required by many games. Then once back up many thing still fail like the gpm mouse and and X refused to come up as a user but worked in root. Both fixed! Therefore, I have not had time to look into much today. Blender is working! -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/23/2011 10:44 AM, Stefan Seyfried wrote:
On Sat, 22 Jan 2011 14:27:25 -0600 Donn Washburn<n5xwb@comcast.net> wrote:
Well if lsusb doesn't see the device then it is a kernel problem with visor or it is a udev rule problem. pilot-link works with jpilot but has nothing to with the lsb system. I say it is a udev problem. Did you try it? If greg k-h tells you to try pilot-link, that's the most expert advice you can probably get. If you choose to ignore it, well, good luck ;)
Well it must have been a connection problem on the palm device and its craddle. I wiggled it around and mounted the visor module. Hit the button and it worked. It must be a poor connection on the craddle or device pins I checked /dev and there were ttyUSB0 and ttyUSB0 when it worked. Thanks for the assistance. Sorry for the trouble. Unfortunately, many new devices have no diagnostic tools to help track down problems -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Jan 24, 2011 at 03:40:32PM -0600, Donn Washburn wrote:
Thanks for the assistance. Sorry for the trouble. Unfortunately, many new devices have no diagnostic tools to help track down problems
"new"? Heh, that's a very old device, sorry, running on a bastardisized serial protocol created add-hoc in the mid 1990's, tunnelled over USB and slightly changed every other device just because the firmware developers at Palm had no idea what their predecessor had done. It's amazing the thing works at all, especially given that Palm has been actively hostile to Linux over the years when all of this host-side code was written. good luck, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 2011-01-22 at 06:27 -0600, Donn Washburn wrote:
On 01/21/2011 11:35 PM, Greg KH wrote:
On Sat, Jan 22, 2011 at 12:19:03AM -0600, Donn Washburn wrote:
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it. Has anyone on the list got a similar one to work? Use the pilot-link packages to talk to the device, it should be able to find it just fine. If you have problems, ask on the pilot-link lists, they can hep out out. Hope this helps, Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem
The Palm Pilot / pilot-link support is very buggy and version specific (version of the Palm device an Palm OS). If you simply want to export data [and not repeatedly sync] it is easier to use one of the USB volume managers or on-device file managers to export the DBA files and extract the data off the device in delimited text or vCard files. I don't know how helpful the pilot-link list will be; I was there for a long time and when I left it was essentially moribund. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/22/2011 01:49 PM, Adam Tauno Williams wrote:
On 01/21/2011 11:35 PM, Greg KH wrote:
On Sat, Jan 22, 2011 at 12:19:03AM -0600, Donn Washburn wrote:
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it. Has anyone on the list got a similar one to work? Use the pilot-link packages to talk to the device, it should be able to find it just fine. If you have problems, ask on the pilot-link lists, they can hep out out. Hope this helps, Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem The Palm Pilot / pilot-link support is very buggy and version specific (version of the Palm device an Palm OS). If you simply want to export data [and not repeatedly sync] it is easier to use one of the USB volume managers or on-device file managers to export the DBA files and extract
On Sat, 2011-01-22 at 06:27 -0600, Donn Washburn wrote: the data off the device in delimited text or vCard files.
I don't know how helpful the pilot-link list will be; I was there for a long time and when I left it was essentially moribund.
Every thing used to work 10.# back. I lost my home made udev rules file. Also pilot-link (as long as usb was specified) it always worked and jpilot was a bit tricky spotting the devices but it did work. I started on that back when it was download only and USB was still /dev/ttyUSB#. All of the headaches started about the time udev/rules started. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 2011-01-22 at 14:47 -0600, Donn Washburn wrote:
On 01/22/2011 01:49 PM, Adam Tauno Williams wrote:
On 01/21/2011 11:35 PM, Greg KH wrote:
On Sat, Jan 22, 2011 at 12:19:03AM -0600, Donn Washburn wrote:
I have a Palm Pilot Tungsten C which is a USB device. I have "visor" according to "lsmod". I have looed at lsusb and it is not seen. I suspect a /dev naming problem. I have written a /etc/udev/rules.d file and plugged it in. Problem is lsub and hwinfo --usb do not see it. Has anyone on the list got a similar one to work? Use the pilot-link packages to talk to the device, it should be able to find it just fine. If you have problems, ask on the pilot-link lists, they can hep out out. Hope this helps, Pilot-link is already installed according to "zypper in pilot-link". And visor is up but the device is still not found. I even tried a different kernel to check if visor was a problem The Palm Pilot / pilot-link support is very buggy and version specific (version of the Palm device an Palm OS). If you simply want to export data [and not repeatedly sync] it is easier to use one of the USB volume managers or on-device file managers to export the DBA files and extract
On Sat, 2011-01-22 at 06:27 -0600, Donn Washburn wrote: the data off the device in delimited text or vCard files.
I don't know how helpful the pilot-link list will be; I was there for a long time and when I left it was essentially moribund.
Every thing used to work 10.# back. I lost my home made udev rules file. Also pilot-link (as long as usb was specified) it always worked and jpilot was a bit tricky spotting the devices but it did work.
I started on that back when it was download only and USB was still /dev/ttyUSB#. All of the headaches started about the time udev/rules started.
Kernel device like ttyUSB# names never changed with udev. They always have been defined, and still are defined by the kernel. Udev only created symlinks for pilot devices in the past, but that approach did not work in too many cases, so we dropped it, and let a program find out which port to use, instead of a expecting a fixed name in /dev. Kay -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Adam Tauno Williams
-
Donn Washburn
-
Greg KH
-
Kay Sievers
-
Stefan Seyfried