syncing with Sony Clie - this is driving me insane.

mike2297 · n00b Joined: 22 Jan 2003 Posts: 46 Location: Maryland, USA

Somtimes I think linux seems more trouble than its worth.

Ok, so my Clie wont sync. Well, actually, it did sync twice with gpilot, and that was after i pushed cancel and restarted the hotsync process a few times.

I'm almost positive I have everything I need in the kernel, but just to show you, here's what lsmod shows:

mike2297 · n00b Joined: 22 Jan 2003 Posts: 46 Location: Maryland, USA

Went back to Mandrake, because it works perfectly there (even with their stock kernel). It must have been those errors in the log file, because I'm not getting them in Mandrake. This must be some sort of bug in Gentoo? I hope they fix it because I loved the portage system. Its just that getting my Clie to sync is rather important to me. Maybe I have some very weird problem nobody else is getting, judging from the number of responses I received from my first post. Goodby, Gentooites, I hope to see you again one day.

-Mike

mallchin · Posted: Wed Feb 05, 2003 12:29 am Post subject:

After a day fiddling I have a Clie using the visor module working under 2.4.20 and have successfully connected using used coldsync, jpilot and gnome-pilot.

There are several good clie how-to's and, apart from devfs not giving user permissions to tts/0, it worked like a charm.

_________________
6700 @ 2.66GHz, 4Gb RAM, 2 x 500Gb, 8800 GTX, PhysX, X-Fi, 24" Widescreen, Tux mascot

mike2297 · n00b Joined: 22 Jan 2003 Posts: 46 Location: Maryland, USA

Well I put mandrake on and my Clie would sync right with the default kernel. I then noticed that it had an older version of Evolution, so I decided to get the new one. So, I downloaded the Evolution sources and began to read how to compile them.

And now, I am back in Gentoo

I realized that emerge is a bit more important to me than my clie, heh.

The odd thing was, when I looked at lsmod under mandrake, there was absolutly no sign of visor or usbserial. I would doubt something like that would be compiled directly into their default kernel, especially since it pretty much came with every possible thing it could as a module, so I wonder what mandrake had that Gentoo didn't.

Anyways, I still can't get it syncing in Gentoo. I'm guessing that nobody has any idea what my problem is, because I have followed every single how-to i could find down to the very last line and nobody has responded to my post with any really good suggestions. Thanks for responding though, mallchin. What kind of Clie did you get to work, by the way?

-Mike

mallchin · Posted: Sun Feb 23, 2003 3:17 pm Post subject: Clie

Hi Mike, I have a Sony Clie T675.

I would have included the steps to get it going but I didn't note them down, just fiddled around installing some apps and added support into the kernel as modules. I got a very similar error regarding coldsync - it would echo a message to press the HotSync button (which I did) but nothing else. Once I had edited the permissions on tty/0 and tty/1 and altered my coldsync settings it all fell into place.

The is the config of my ~/.coldsyncrc:

modal · Apprentice Joined: 02 Oct 2002 Posts: 277

I am having so many troubles with my NX70v. I have seen a few forum threads that seem to give awesome info, but never help me get it right.
Where are these great guides, how-tos, etc for getting my palm working?
Some linkage would be great.
Thanks

mallchin · Posted: Tue Feb 25, 2003 12:48 pm Post subject:

mike2297 · n00b Joined: 22 Jan 2003 Posts: 46 Location: Maryland, USA

I just dont get it. All the proper modules are loaded. It never fails, I can only sync ONCE. The initial sync where it gets the ID from the palm, and then the next sync right after that are the only syncs that ever work. When I do a CTRL-ALT-F1 during those syncs, I see messages comming up about it listening to the /dev/pilot link. After that 2nd sync where it copies everything to evolution from the palm, I can never ever get another message to show up. It doesnt even try to listen to the port apparently. Im totally baffled.

-Mike

jkratz · n00b Joined: 15 Mar 2003 Posts: 28

The only way I was able to get my Clie (S-360) to sync up with KPilot and pilot-link was to chmod 777 /dev/usb/tts/1. The chmod had to be done while the Clie was trying to sync up (ie: that is the only time that the 1 entry shows up in /dev/usb/tts). Once I did that I had no problems. Have you done that on your setup? (I'm using the visor and usbserial stuff as modules in my kernel and have hotplug and pilot-link installed).

mike2297 · n00b Joined: 22 Jan 2003 Posts: 46 Location: Maryland, USA

yep. ive done that.. still completely random when it decides to actually connect

blamothe · Posted: Tue Apr 08, 2003 2:12 pm Post subject:

ok, i have a palm m125 that uses the m5** cradle, and i got it to sync flawlessly with jpilot. First, under USB support, depending on your hardware architecture, you either need to enable OHCI or UHCI, if you have an intel chipset, its UHCI. If you need UHCI, make sure you don't load the alternate/JE driver which is selected by default in Gentoo, unselect that and the other one will appear. After that, you should go to serial converter support and enable the visor driver. Then you should enable the primary USB device filesystem, and under general setup you should enable support for hot-pluggable devices. Then you need to go to filesystems and enable the /dev filesystem and automatically mount it at boot, and unselect the /dev/pts filesystem because you don't need that at all. then reboot and emerge jpilot (in my opinion, the best syncing software) this will automatically give you pilot-link. While jpilot is merging, make two symlinks and call them pilot and palm to the dev entry in your clie with, if you use devfs, which you should,

nealbirch · n00b Joined: 18 Jan 2003 Posts: 25

If you use devfs, you need to modify your /etc/devfsd.conf file so the permissions are setup automatically.

add something like this to the /etc/devfsd.conf:

# Manage Palm pilot stuff

LOOKUP ^pilot$ CFUNCTION GLOBAL mksymlink usb/tts/1 pilot
REGISTER ^usb/tts/1$ CFUNCTION GLOBAL mksymlink $devname pilot PERMISSIONS root.users
REGISTER ^usb/tts/1$ PERMISSIONS root.users 666
UNREGISTER ^usb/tts/1$ CFUNCTION GLOBAL unlink pilot
#

this lets members of the users group access /dev/usb/tts/1 though I suppose you could setup another group for palm access.

Not sure what you do for udev, but it's along the same lines.