Re: [opensuse-factory] Palm Pilot module
Greg KH wrote:
On Thu, Jul 30, 2009 at 11:29:11AM -0400, Fred A. Miller wrote:
Greg KH wrote:
On Thu, Jul 30, 2009 at 01:06:53AM -0400, Fred A. Miller wrote:
On 07/29/2009 08:30 PM, Donn Washburn wrote:
Hey group;
In the past my Palm device was spotted right off by SuSE after installing a custom /etc/udev/rules.d file. Now it is not even spotted by hwinfo --usb. This brings me to my question. (Senior Moment) - What was the kernel module need to have this device seen? Something like "joliet".
Got it - visor and usbserial
It is amassing how quickly a old brain comes around Sometimes. Where do I find "visor" and "usbserial" as Yast doesn't find
Donn Washburn wrote: them for 11.1? They are kernel modules, not separate packages.
I get the error(s):
01:04:20 Starting the KPilot daemon ... 01:04:20 Daemon started. 01:04:20 Daemon status is `.kde.kpilot.daemon was not provided by any .service files' 01:04:22 Trying to open device /dev/pilot... 01:04:22 Cannot open Pilot port: [/dev/sr0].
Do you or anyone else know how to fix this? press sync on your device first. Tried that and still get:
HotSync Log
11:25:55 Starting the KPilot daemon ... 11:25:55 Daemon started. 11:25:55 Daemon status is `.kde.kpilot.daemon was not provided by any .service files' 11:25:55 Trying to open device /dev/pilot... 11:25:55 Cannot open Pilot port: [/dev/sr0]. 11:25:59 Trying to open device /dev/pilot... 11:25:59 Cannot open Pilot port: [/dev/sr0]. 11:26:04 Trying to open device /dev/pilot... 11:26:04 Cannot open Pilot port: [/dev/sr0].
Looks like kpilot needs to be configured to use the proper device node (usually /dev/ttyUSB1 or so.) But note, it's usually better to just use the libusb version of the pilot-link tools these days, no need to touch the kernel drivers at all. That works much better, as the visor kernel driver is pretty much unmaintained due to a lack of hardware (yes, it's my code, but without hardware, I can't test it anymore...)
Try asking on a kpilot mailing list,
good luck,
Thanks.....I'm going to need it! ;) You are correct...the system does see it, and as /dev/ttyUSB1, which of course is in /dev, bu then, neither is pilot. :( Even though the system does see it, NO software will. Thanks for trying, Fred -- Liberals ALWAYS, ALWAYS consider socialist dogma more important than telling the truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Fred A. Miller - 16:19 30.07.09 wrote:
Greg KH wrote:
On Thu, Jul 30, 2009 at 11:29:11AM -0400, Fred A. Miller wrote:
Greg KH wrote:
On Thu, Jul 30, 2009 at 01:06:53AM -0400, Fred A. Miller wrote:
On 07/29/2009 08:30 PM, Donn Washburn wrote: > Hey group; > > In the past my Palm device was spotted right off by SuSE after > installing a custom /etc/udev/rules.d file. > Now it is not even spotted by hwinfo --usb. This brings me to my > question. (Senior Moment) - What was the kernel module need to have > this device seen? Something like "joliet". > Got it - visor and usbserial
It is amassing how quickly a old brain comes around Sometimes. Where do I find "visor" and "usbserial" as Yast doesn't find
Donn Washburn wrote: them for 11.1? They are kernel modules, not separate packages.
I get the error(s):
01:04:20 Starting the KPilot daemon ... 01:04:20 Daemon started. 01:04:20 Daemon status is `.kde.kpilot.daemon was not provided by any .service files' 01:04:22 Trying to open device /dev/pilot... 01:04:22 Cannot open Pilot port: [/dev/sr0].
Do you or anyone else know how to fix this? press sync on your device first. Tried that and still get:
HotSync Log
11:25:55 Starting the KPilot daemon ... 11:25:55 Daemon started. 11:25:55 Daemon status is `.kde.kpilot.daemon was not provided by any .service files' 11:25:55 Trying to open device /dev/pilot... 11:25:55 Cannot open Pilot port: [/dev/sr0]. 11:25:59 Trying to open device /dev/pilot... 11:25:59 Cannot open Pilot port: [/dev/sr0]. 11:26:04 Trying to open device /dev/pilot... 11:26:04 Cannot open Pilot port: [/dev/sr0].
Looks like kpilot needs to be configured to use the proper device node (usually /dev/ttyUSB1 or so.) But note, it's usually better to just use the libusb version of the pilot-link tools these days, no need to touch the kernel drivers at all. That works much better, as the visor kernel driver is pretty much unmaintained due to a lack of hardware (yes, it's my code, but without hardware, I can't test it anymore...)
Try asking on a kpilot mailing list,
good luck,
Thanks.....I'm going to need it! ;) You are correct...the system does see it, and as /dev/ttyUSB1, which of course is in /dev, bu then, neither is pilot. :( Even though the system does see it, NO software will.
Thanks for trying,
Fred
In most software you can specify the port used: for example with pilot-link it's -p option. Then you can use either -p /dev/ttyUSB1 or -p usb: I'll take a look why /dev/pilot is pointing to the wrong location... -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
participants (2)
-
Fred A. Miller -
Michal Hrusecky