List Info

Thread: Tungsten-E problems with gnome-pilot on Fedora 7




Tungsten-E problems with gnome-pilot on Fedora 7
country flaguser name
United States
2007-08-06 09:23:43
I have a Tungsten E (Te) running PalmOS that I would like to
sync with
Evolution using the gnome-pilot-2.0.15-5.fc7 package on a
Fedora 7
system; however, I'm having difficulties.  First, I had to
create
an /etc/udev/rules.d/10-palm.rules file with the following
content:

BUS=="usb", SYSFS=="Palm
Handheld", KERNEL=="usbdev?.*",
SYMLINK+="pilot",  MODE="0666"

See the following udev bug for more details.

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=25
0948

When I attach the Te and press the hotsync button, then the
/dev/pilot
device is created which is linked to:

0 crw------- 1 gk4 root 189, 129 2007-08-05 19:46
/dev/bus/usb/002/002

The command "/sbin/lsusb" returns:

Bus 002 Device 002: ID 0830:0060 Palm, Inc. Palm Tungsten T
/ Zire 71

The file /proc/bus/usb/devices contains:

T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12 
MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=
 1
P:  Vendor=0830 ProdID=0060 Rev= 1.00
S:  Manufacturer=Palm, Inc.
S:  Product=Palm Handheld
S:  SerialNumber=PalmSN12345678
C #Ifs=
1 Cfg#= 1 Atr=c0 MxPwr=  2mA
I If#=
0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=visor
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

The command "/sbin/lsmod | grep usbserial"
returns:

usbserial  35753  1 visor

When using gnome-pilot settings for the first time, then I
set:

name: cradle
type: usb
timeout: 2
device: /dev/pilot
speed: 57600
owner: gk4
pda id: 500

However, the initial sync never returns and I must cancel
the setup.

The command "/usr/bin/pilot-debugsh /dev/pilot"
returns:

Unable to connect

The jpilot.i386 0:0.99.9-3.fc7 returns:

pi_bind error: /dev/pilot Invalid argument
Check your serial port and settings
Exiting with status SYNC_ERROR_BIND
Finished

Reference info:

http://www.faqs.org/docs/Linux-HOWTO/PalmOS-HOWTO.html


Any suggestions?

Thanks,

George (gk4)


_______________________________________________
gnome-pilot-list mailing list
gnome-pilot-listgnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list

Re: Tungsten-E problems with gnome-pilot on Fedora 7
user name
2007-09-08 15:07:39
Looks familiar.  I too have a Te and have been using jpilot
with
libusb (preferences set to "usb:" rather than
"/dev/pilot")
rather than the ttyUSB stuff.  I sometimes use a USB to
serial
converter (e.g., with a GPS), so the Palm can use ttyUSB0+1
or
ttyUSB1+2, so the ttyUSB mechanisms have never been
reliable.
RH were slow to provide a version with libusb enabled, so I
compiled
it myself, but I think this has now been done via an
update.

Syncing  wothusb: was problematic at first but has been
getting better
with new  udev and kernel versions.   Debian has had similar
issues
with 2.6.22 kernels.

On 8/6/07, George Kraft <gkraftgnome.org> wrote:
> I have a Tungsten E (Te) running PalmOS that I would
like to sync with
> Evolution using the gnome-pilot-2.0.15-5.fc7 package on
a Fedora 7
> system; however, I'm having difficulties.  First, I had
to create
> an /etc/udev/rules.d/10-palm.rules file with the
following content:
>
> BUS=="usb", SYSFS=="Palm
Handheld", KERNEL=="usbdev?.*",
SYMLINK+="pilot",  MODE="0666"
>
> See the following udev bug for more details.
>
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=25
0948
>
> When I attach the Te and press the hotsync button, then
the /dev/pilot
> device is created which is linked to:
>
> 0 crw------- 1 gk4 root 189, 129 2007-08-05 19:46
/dev/bus/usb/002/002
>
> The command "/sbin/lsusb" returns:
>
> Bus 002 Device 002: ID 0830:0060 Palm, Inc. Palm
Tungsten T / Zire 71
>
> The file /proc/bus/usb/devices contains:
>
> T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2
Spd=12  MxCh= 0
> D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64
#Cfgs=  1
> P:  Vendor=0830 ProdID=0060 Rev= 1.00
> S:  Manufacturer=Palm, Inc.
> S:  Product=Palm Handheld
> S:  SerialNumber=PalmSN12345678
> C
#Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  2mA
> I
If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00
Driver=visor
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>
> The command "/sbin/lsmod | grep usbserial"
returns:
>
> usbserial  35753  1 visor
>
> When using gnome-pilot settings for the first time,
then I set:
>
> name: cradle
> type: usb
> timeout: 2
> device: /dev/pilot
> speed: 57600
> owner: gk4
> pda id: 500
>
> However, the initial sync never returns and I must
cancel the setup.
>
> The command "/usr/bin/pilot-debugsh
/dev/pilot" returns:
>
> Unable to connect
>
> The jpilot.i386 0:0.99.9-3.fc7 returns:
>
> pi_bind error: /dev/pilot Invalid argument
> Check your serial port and settings
> Exiting with status SYNC_ERROR_BIND
> Finished
>
> Reference info:
>
> http://www.faqs.org/docs/Linux-HOWTO/PalmOS-HOWTO.html

>
> Any suggestions?
>
> Thanks,
>
> George (gk4)
>
>
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-listgnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>


-- 
George N. White III <aa056chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
_______________________________________________
gnome-pilot-list mailing list
gnome-pilot-listgnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list

Re: Tungsten-E problems with gnome-pilot on Fedora 7
country flaguser name
United States
2007-09-08 15:24:34
On Sat, 2007-09-08 at 17:07 -0300, George N. White III
wrote:
> RH were slow to provide a version with libusb enabled,
so I compiled
> it myself, but I think this has now been done via an
update.

No distro should be shipping with Palm libusb enabled by
default. 

They're more than welcome to build their
pilot-link/libpisock packages
with libusb support, but enabling that iterface by default
(i.e.
disabling visor in the process), is definitely not something
they should
be doing. 

libusb, while it works reliably for some, still isn't fully
debugged to
be "production-ready" for all devices. 


-- 
David A. Desrosiers
desrodgnu-designs.com
setuidgmail.com
http://projects.plkr.org/
Skype...: 860-967-3820

_______________________________________________
gnome-pilot-list mailing list
gnome-pilot-listgnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )