Palm tungsten c usb sync problem - [SOLVED]

muphicks · n00b Joined: 22 Nov 2003 Posts: 48

Hi,

I'm trying to get my palm tungsten c to sync and having a few problems doing it. So far I've compiled module support for usbserial and visor. I've also installed hotplug (and enabled the option in the kernel).

When I plugin my palm usb cradle and press the hotsync button I get the following message in my logs (and the visor/usbserial modules load in)

simon_irl · Guru Joined: 07 Oct 2004 Posts: 403 Location: New Zealand

if you want reassurance that your system recognises a tungsten, maybe try (as root): lsusb

on my system, dmesg gives the same output you're getting (when i press hotsync, it mentions a visor/palmos device but isn't specific about the device...however, when i try lsusb, it does list the device model (in my case, a Palm m515).

glancing at the usb/serial devices in the kernel configuration menu, it does look like the visor module is all there is...i'm running 2.6.9-gentoo-r9, so if there's a new tungsten-specific module, it's something you'll have to find elsewhere. i suggest googling for evidence that people have used the visor module successfully with tungstens.

simon_irl · Guru Joined: 07 Oct 2004 Posts: 403 Location: New Zealand

doh...just realised that lsusb probably isn't any kind of reassurance at all...just because the usb subsystem recognises the device, doesn't mean there's any kind of kernel support.

sorry...maybe i'll leave this one for someone who knows what they're talking about!

GenKreton · Posted: Fri Dec 17, 2004 5:23 am Post subject:

I use usbserial and visor modules for my T|C and jpilot as a frontend.

Under udev I need to set it to use /dev/tts/USB1 and all works as advertised. I don't even concern myself with the order, palm or software, as they fixed that.

simon_irl · Guru Joined: 07 Oct 2004 Posts: 403 Location: New Zealand

there ya go! mine also is at /dev/tts/USB1 (only exists during hotsync).

muphicks · n00b Joined: 22 Nov 2003 Posts: 48

I don't get a tts/USB1 device, I get tts/1 or tts/0. Is this because I'm using devfs and not the newer usb dev system I've read about?

GenKreton · Posted: Fri Dec 17, 2004 5:57 pm Post subject:

I have no experience under devfs with it, your best bet is to ask google probably.

Udev is a maintained version of devfs in userspace. Worth looking at since Devfs has unfixed problems that will forever remain unfixed since the developer disappeared I guess.

muphicks · n00b Joined: 22 Nov 2003 Posts: 48

I've emerged udev and followed a few of the guides/post on these forums, but still get the same problem. The device detects as /dev/tts/USB0 and /dev/tts/USB1 (and is assigned correct permissions for root/usb group) after pressing the hotsync button. However if I try to then do pilot-xfer -p /dev/tts/USB1 -l (or 0) I get a segmentation fault.

If I press hotsync and do nothing, the palm eventually timesout saying it cannot sync. The log files show the connection and later disconnection of the palm as well as creating the devices, so I'm assuming that its talking correctly. However, I'm still not sure what might be causing the seg fault when I try to do anything that uses the device with pilot-xfer

As before, I get the following error in my logs after the seg fault is reported: