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>