Sony Clie TJ-37 Under FC3 almost working but not quite
Aaron O'Hara
ajeo at hungryforlife.org
Mon Feb 21 08:24:46 UTC 2005
Ok...I fixed one problem, but I have another.
As it turns out, I was able to get the sync to work only after doing
chmod 777 on ttyUSB0.
ttyUSB0 is created dynamically when I hit the hotsync button, so I can't
just set those permissions and have them stick. As this is a personal
system, I don't care about other users being able to access ttyUSB0, so
if there was a way to have the system automatically do a 'chmod 777' (or
equivalent) when the device was created, that would be really cool.
How should I go about doing this?
-- Aaron
On Sun, 2005-20-02 at 23:47 -0800, Aaron O'Hara wrote:
> All,
>
> I have a Sonly Clie TJ-37 and I'm having problems getting it to
> communicate with Gnome Pilot. I have created a sym link
> between /dev/pilot/ and /dev/ttyUSB0. When I follow the wizard and
> click the HotSync on the Clie, I get the following in /var/log/messages:
>
> Feb 20 23:41:21 sumas kernel: usb 2-1: new full speed USB device using
> uhci_hcd and address 12
> Feb 20 23:41:21 sumas kernel: visor 2-1:1.0: Handspring Visor / Palm OS
> converter detected
> Feb 20 23:41:21 sumas kernel: usb 2-1: Handspring Visor / Palm OS
> converter now attached to ttyUSB0
> Feb 20 23:41:21 sumas kernel: usb 2-1: Handspring Visor / Palm OS
> converter now attached to ttyUSB1
>
> Despite this apparent connectivity, The "Initial Sync" of Gnome Pilot
> hangs and the Clie eventually times out saying that a connection could
> not be established.
>
> Every time I do a hotsync, I notice that the one line
> in /var/log/messages increments:
>
> Feb 20 23:41:21 sumas kernel: usb 2-1: new full speed USB device using
> uhci_hcd and address 12
>
> I don't know if the 'address 12' is important enough that I need to tell
> Gnome Pilot.
>
> /var/log/messages also reports the device as "Handspring Visor", not
> Sony Clie, but I don't know if that's important either.
>
> Based on /var/log/messages, it seems as though the USB link is working,
> but it's just getting Gnome Pilot to work that's the issue.
>
> Any help would be greatly appreciated!
>
> --Aaron
>
>
>
More information about the fedora-list
mailing list