Jeffrey L. Taylor wrote:

Quoting Jose Thadeu Cavalcante <thadeurj@terra.com.br>:

...

Hi,

I can not connect my Palm Tungsten E with SuSE 9.3, but I can do with SuSE 9.2. There are some special configuration now?

Thanks Thadeu

I can connect to my Handspring Visor. A couple of suggestions: make sure /dev/pilot points to /dev/ttyUSB1 for a USB cradle, press sync on the cradle first, wait until the messages in syslog stop, then click sync or backup in J-pilot. I found that too fast and the other way around didn't work. And you may need to invoke J-Pilot with:

LANG=C /usr/bin/jpilot

It doesn't like UTF-8.

Hm. Does anyone know if there are any differences between the KPilot install on SuSE and the one that comes with Knoppix 2.6? I ask, because I've had a similar problem. Running Knoppix on the same hardware, I could get KPilot to connect to my Sony Clie with no trouble (I didn't use /dev/pilot, I just adjusted KP to use /dev/ttyUSBx), but doing the exact same thing under SuSE 9.1Pro KP kept giving dieing on "could no open device" errors. This is one of those problems I haven't really done any serious work on yet, because I've got so many others with higher priority....

On Wednesday 01 June 2005 5:35 pm, Joe Morris (NTM) wrote:

David McMillan wrote:

...

Hm. Does anyone know if there are any differences between the KPilot install on SuSE and the one that comes with Knoppix 2.6? I ask, because I've had a similar problem. Running Knoppix on the same hardware, I could get KPilot to connect to my Sony Clie with no trouble (I didn't use /dev/pilot, I just adjusted KP to use /dev/ttyUSBx), but doing the exact same thing under SuSE 9.1Pro KP kept giving dieing on "could no open device" errors. This is one of those problems I haven't really done any serious work on yet, because I've got so many others with higher priority....

You might want to make sure that ttyUSBx is listed in /etc/resmgr.conf, as SuSE uses this (i.e. resource manager) to adjust permissions. I don't believe Knoppix uses it. I just upgraded my systems (home and work) to SuSE9.3. In the past, I had updated udev, but I specifically did not do that. One thing you need to do is to either place yourself into the uucp group or set the permissions to /dev/usb/ttyUSB1

I tried this at home last night after I completed the install. (I always do new installs to an empty partition so I can roll back). The first thing I did was dlpsh -p /dev/usb/ttyUSB1 Then I pressed the sync button, and the palm was detected successfully. I then synced up with my Treo650. Same here at work. Note that the Palm does not always come up as ttyUSB1 Also, the Treo used ttyUSB1 where some of the older palms use ttyUSB0. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

On Thu, 2005-06-02 at 10:14 -0300, Jose Thadeu Cavalcante wrote:

Finally I solved the problem by changing the permission on ttyUSBx devices. As root I do the commands chmod a+wr /dev/ttyUSB0 chmod a+wr /dev/ttyUSB1

The strange is that the commands above are recommended for serial connection (of course, changing USB to S in ttyUSBx). But now, the communication is working. After I do other testing to see backups and etc. Cheers Thadeu

The only problem with this is that the permissions will be reset when you reboot. Also add the permissions to /etc/permissions.local so they are also set at boot time. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge

Jerry Feldman wrote:

I just upgraded my systems (home and work) to SuSE9.3. In the past, I had updated udev, but I specifically did not do that. One thing you need to do is to either place yourself into the uucp group or set the permissions to /dev/usb/ttyUSB1

I tried this at home last night after I completed the install. (I always do new installs to an empty partition so I can roll back). The first thing I did was dlpsh -p /dev/usb/ttyUSB1 Then I pressed the sync button, and the palm was detected successfully. I then synced up with my Treo650.

I've never seen that command before, but I tried it just for the heck of it (as root, so I didn't bother with permissions). And darned if it didn't work! Another troubleshooting tool for the arsenal -- thank you very much.

Same here at work. Note that the Palm does not always come up as ttyUSB1 Also, the Treo used ttyUSB1 where some of the older palms use ttyUSB0.

Interesting. My Clie shows up as *both*. The relevant portion of dmesg: usb 1-1: new full speed USB device using address 2 usb 1-1: Product: Palm Handheld usb 1-1: Manufacturer: Palm, Inc. drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5 drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0 usb 1-1: palm_os_4_probe - error -32 getting connection info visor 1-1:1.0: Handspring Visor / Palm OS converter detected usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB0 (or usb/tts/0 for devfs) usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB1 (or usb/tts/1 for devfs) usbcore: registered new driver visor drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver v2.1 usb 1-1: USB disconnect, address 2 Using the dlpsh command with ttyUSB1 works, USB0 doesn't. Something to do with the two different versions of Clie shown above? But dmesg doesn't indicate which one associates to which USB port... <headscratch>

Joseph Loo wrote:

I have the same problem syncing with a plam pilot on RS232. port. The first quesion that needs to be asked is it the 64 bit or 32 bit version. I had used the 64 bit and there is a problem. It seems that the person who wrote jpilot has some 54 bit issues a couple months ago.

Mine is 32bit (9.1Pro), running on an Athlon XP-M 1600. Right now, I'm just trying to learn enough about 32bit SuSE to survive, before I try to tackle 64bit. :)