Ok, let's see if I can remember how I got my Palm working .... ;-)

UDEV: /etc/udev/rules.d/10-udev.rules
BUS="usb", SYSFS{serial}="PalmSN12345678", NAME="pilot", MODE="0666"

The MODE paramter is VERY important! There had been some changes in this
area recently.

And just to be sure add a permission
here: /etc/udev/permissions.d/10-udev.permissions
# Palm Tungsten E
# pilot*:root:usb:0666
BUS="usb", SYSFS{serial}="PalmSN12345678", NAME="pilot", MODE="0666"

My Tungsten E doesn't have a craddle but can be directly connected with
an USB cable. I had to enable USB Serial Converter support in my kernel
(CONFIG_USB_SERIAL_VISOR) for that to work.

I believe that's pretty much it.

Regards

spox

Am Freitag, den 12.08.2005, 20:09 +0200 schrieb Stefan Onken:
> Am Freitag, 12. August 2005 04:58 schrieb Nick Rout:
> 
> > http://www.reactivated.net/writing_udev_rules.html
> ]...]
> 
> > 1. unlike many usb devices plugging a palm device in is
> > insufficient to get the kernel and udev and hotlpug to do
> > anything. you need to push the hotsync button.
> >
> > 2. you then get two devices (well on the treo anyway) - something
> > like ttyUSB0 and ttyUSB1 - only one of them is any good, the odd
> > one. They may not be in the top level of /dev, but in some
> > subdirectory.  find and the kernel logs are your friends.
> 
> well, I am using:
> 
> BUS="usb", SYSFS{serial}="504E35424D42583456354E35", 
> KERNEL="ttyUSB[1357]",  SYMLINK="pilot"
> 
> 
> some seconds after I am connecting the Palm (without pressing any 
> hotsync button !!! ) I am getting:
> 
> p7010 ~ # ls  -als /dev/tts/USB*
> 0 crw-rw-rw-  1 root tty 188, 0 Aug 12 20:01 /dev/tts/USB0
> 0 crw-rw-rw-  1 root tty 188, 1 Aug 12 20:01 /dev/tts/USB1
> 
> p7010 ~ # ls -als /dev/pilot
> 0 lrwxrwxrwx  1 root root 8 Aug 12 20:01 /dev/pilot -> tts/USB1
> 
> 
> but even now a test with the palm program stops here:
> 
> 
> p7010 ~ # pilot-xfer --port /dev/pilot -L
>    Listening to port: /dev/pilot
>    Please press the HotSync button now...
>                                             
> the moment I am pressing the hotsync button, the device (/dev/pilot) 
> is disappearing for a second and will be created insteadly again:
> 
> resulting:  Error read system info on /dev/pilot
> 
> 
> kpilot is not able to connect at all :(
> 
> -- 
> www.stonki.de:    the more I see, the more I know.......
> www.proftpd.de:   Deutsche ProFTPD Dokumentation
> www.krename.net:  Der Batch Renamer für KDE
> www.kbarcode.net: Die Barcode Solution für KDE
> 
-- 
Mit freundlichen Grüßen

Heinz Sporn

SPORN it-freelancing

Mobile: ++43 (0)699 / 127 827 07
Email:  [EMAIL PROTECTED]
        [EMAIL PROTECTED]
Snail:  Steyrer Str. 20
        A-4540 Bad Hall
        Austria / Europe

-- 
gentoo-user@gentoo.org mailing list

Reply via email to