Re: I can't sync my TE2

[Qball Cow <qball qballcow nl>]

It seems to be a known dapper problem. On the forum more people complain
about it. (I have the same problem).
The palm will sync fine with jpilot, and also do some kind of sync with
multisync. Yet gpilot is completely unresponsive.
The dmesg out put is correct (compared to working systems), so are the
entries in /proc/bus/usb/devices. I've also check permissions and udev
rules.

I'll will see if I can make a custom build of gpilot and try it with
that..

Syncless,

Qball

On Sun, 2006-03-05 at 13:32 +0000, Matt Davey wrote:
> > Could you help me ?
> > My tungsten worked fine with ubuntu breezy, and now, I use Dapper Drake
> > 
> > 
> > I use :
> > - evolution 2.5.92
> > - gnome-pilot 2.0.13
> > - pilot-link version 0.11.8
> > - ubuntu dapper drake
> > 
> > note that my Tungsten E2 sync well under ubuntu breezy
> 
> This is all a bit odd.  Very little seems to have changed between
> breezy and dapper.  The versions of pilot-link and gnome-pilot are
> essentially the same, as far as I can see.
> 
> My feeling is that your problem might well lie at the kernel layer.
> Is it possible for you to boot with the breezy kernel?
> 
> What messages do you see in dmesg?  You said:
> 
> > On the dmesg, I've this :
> > [4306068.179000] visor ttyUSB0: Handspring Visor / Palm OS converter now
> > disconnected from ttyUSB0
> > [4306068.179000] visor ttyUSB1: Handspring Visor / Palm OS converter now
> > disconnected from ttyUSB1
> 
> Where are the 'connected' messages?  Do these 'disconnected' messages
> appear immediately after the connected ones?  Do you get an entry
> for the palm in /proc/bus/usb/devices (while a sync is being attempted) ?
> 
> Matt
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list