| Autore |
 Discussione  |
|
|
galexonline
Amministratore
Regione: Lazio
Prov.: Viterbo
Città: Civita Castellana
122 Messaggi |
 Inserito il - 10/08/2005 : 15:16:49
|
Faccio eco ad un post utilissimo che ho trovato su http://forum.phpsoft.it/index.php?showtopic=709
ne riporto anche il contenuto :
ATTENZIONE: Il seguente articolo è semplicemente una traduzione di un howto presente su Ubunto Forum, scritto da tUrtleAE86.
Il sottoscritto non si prende alcun merito in merito a cio che segue.
Sincronizzare un Pocket PC con Evolution
Il vostro PDA piace a Linux ?
Connettete il vostro PDA al computer, aprite la shell e digitate "dmesg" per verificare se il modulo iPAQ è caricato nel kernel. L'output dovrebbe essere simile al seguente:
QUOTE
sirdaid@sirdaid:~$ dmesg
.....
usb 4-2: new full speed USB device using uhci_hcd and address 3
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
ip_tables: © 2000-2002 Netfilter core team
PPP BSD Compression module registered
PPP Deflate Compression module registered
usb 4-2: USB disconnect, address 3
ipaq 4-2:1.0: device disconnected
PocketPC PDA ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
usb 4-2: new full speed USB device using uhci_hcd and address 4
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
usb 4-2: USB disconnect, address 4
PocketPC PDA ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
ipaq 4-2:1.0: device disconnected
usb 4-2: new full speed USB device using uhci_hcd and address 5
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
usb 4-2: USB disconnect, address 5
PocketPC PDA ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
ipaq 4-2:1.0: device disconnected
usb 4-2: new full speed USB device using uhci_hcd and address 6
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
usb 4-2: USB disconnect, address 6
ipaq 4-2:1.0: device disconnected
PocketPC PDA ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
usb 4-2: new full speed USB device using uhci_hcd and address 7
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
usb 4-2: USB disconnect, address 7
PocketPC PDA ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
ipaq 4-2:1.0: device disconnected
usb 4-2: new full speed USB device using uhci_hcd and address 8
ipaq 4-2:1.0: PocketPC PDA converter detected
usb 4-2: PocketPC PDA converter now attached to ttyUSB0
In questa miriade d' informazioni, prendete in considerazione solo le ultime tre righe (evidenziate in gassetto) ed in partcolare prendendete nota di quale tty viene utlizzato (nel mio caso ttyUSB0)
Installazione e configurezione di SynCE
*Note: nei seguenti esempi troverete il comando "sudo", considerato che su alcune distribuzioni non è installato di default potrebbe essere necessario utilizzare precedentemente il comando "su" per entrare in modalità amministratore ("sudo" infatti esegue un comando come amministratore)
1) SynCE richiede i seguenti pacchetti :
librra0 librra0-tools librapi2-tools libsynce0 synce-dccm synce-multisync-plugin synce-serial
se possedete una distribuzione Debian dovre decommentare i repository universe nel soureces.list
e poi
CODE
sudo apt-get install librra0 librra0-tools librapi2-tools libsynce0 synce-dccm synce-multisync-plugin synce-serial
Se invecie possedete un distribuzione redheat based (Fedora, Suse, Mandrivia, .....) è necessario scricare synce dal sito ufficiale http://http://sourceforge.net/project/showfiles.php?group_id=30550&package_id=22569&release_id=310079
Assicuratevi di loggare come root e poi installate :
* synce-X.X-X.i386.rpm (Note: questo pacchetto include i moduli libsynce, librapi2, dccm, serial e rra.)
* synce-multisync_plugin-X.X-X.i386.rpm (per la sincronizzazione dell'acenda)
* synce-trayicon-X.X-X.i386.rpm (consigliato agli utenti GNOME 2.x)
* synce-gnomevfs-X.X-X.i386.rpm (consigliato agli utenti GNOME 2.x)
Attraverso il comando :
QUOTE
rpm -Uvh synce*.rpm
Durante l'installazione del pacchetto "synce-serial " vi apprariranno delle schermate che vi chiederanno 1) La porta tty da utilizzare 2) l'indirizzo locale 3) L'indirizzo remoto 4)L'indirizzo del server DNS.
Solitamente le opzioni de default vanno bene, ovvero :
QUOTE
/dev/ttyUSB0
local address: 192.168.131.102
remote address: 192.168.131.201
no dns entry needed
Questo è sopratutto vero per gli utenti Debian. Controllate perciò che le ultime tre opzioni vengano settate come sopra detto, per quanto riguarda la prima opzione è necessario verificare se la porta tty corrispoende a quella che ci era stata riportata da "dmesg".
3) Eseguire il seguente comando per dire a SynCE su che porta guardare. (Potrebbe sembrare rindondante ma non lo è)
CODE
sudo synce-serial-config ttyUSB0
Ricordatevi che è neccessario mettere la vostra porta tty e non quella dell'esempio se le due non corrispondono !
4) Avviare il demon SynCE attraverso il comando shell "dccm". Nel caso il vostro Pocket PC richiedesse una password per la connessione potete usare il seguente comando:
CODE
dccm -p password
dove apssword è la costra pasword.
5) Iniziare una connessione seriale digitando
CODE
sudo synce-serial-start
.
Se tutto va come dovrebbe andare, allora comparira un messagio che recita
QUOTE
synce-serial-start is now waiting for your device to connect
(ovvero, synce-serial-start è in attesa che la tua periferica sia connessa).
6) Digitando
CODE
synce-pstatus
, potrete visualizzare una quantità notevole di informazioni sul vostro PDA .
7) E' ora necessario che stabiliate una partnership tra il vostro Pocket PC e il vostro PC, per questo usere il seguente comando :
CODE
synce-matchmaker create INDEX
INDEX puo assumere due valori 1 o 2, sta a voi inserire uno dei due valori nel comando sovrastante.
Successivamente verrete accolti dal seguente messaggio:
QUOTE
Partnership creation succeeded. Using partnership index INDEX.
(ovvero, partnership creata correttamente. Usando l'inidice di partenership INDEX)
Installare e configurare Multisync
1)Se possedete una distribuzione debina base potrete lanciare il seguente comando
CODE
sudo apt-get install libmultisync-plugin-all multisync
Oppure
QUOTE
sudo apt-get install libmultisync-plugin-evolution libmultisync-plugin-backup multisync
Se invecie possedete una readhead based, troverete i file da scricare qui.
2) Avviate MultiSync digitando "multisync" da linea di comando. Oppure per i possessori di Debian potranno gia trovare un'icona del programma nel menu Applicazioni -> Accessori -> MultiSync.
3) Create una nuova sincronizzazione ed assegnate come plugin (l'ordine non è importante) "SynCE Plugin" e "Ximian Evolution 2". Avrete, inoltre, la necessità di creare dei nuovi contatti, dei nuovi appuntamenti, ....
4) Premete il pottone Sync
Disconnettere il PDA
1) Chiudete MultiSync
2) Digitare "killall -HUP dccm", per terminare la connessione seriale
3) COME ULTIMA RISORSA, digitate "synce-serial-abort" se il comando sopra riportato non dovesse funzionare.
Nel caso ci dovessero essere imprecisioni o malfunzionamenti siete pregati di farmelo sapere (visto che ho medde delle piccole agguinte che non posso controllare di persona) 175.gif
|
|
|
galexonline
Amministratore
Regione: Lazio
Prov.: Viterbo
Città: Civita Castellana
122 Messaggi |
Inserito il - 19/08/2005 : 15:47:26
|
Ho trovato il seguente Howto di SynbCE ufficiale
vi consiglio di leggerlo direttamente dal sito
http://synce.sourceforge.net/synce/howto.php
se la pagina non fosse disponibile leggete questo post :
SynCE - Linux USB HOWTO
Please note that this HOWTO is not yet finished!
The purpose of this HOWTO is to connect a single Windows CE device with USB support to a PC running a Linux distribution with a 2.6.x kernel, as this is assumed to be the most common setup for SynCE users.
If this does not apply to your system, go to the No HOWTO page.
In case you are not on a 32-bit x86 system but for example using a 64-bit system (such as AMD64) or a big-endian system (such as PowerPC), there might be some additional quirks. You are very welcome to write to the synce-users@lists.sourceforge.net list about your experiences with SynCE on such systems!
You must also be running a Linux kernel build that supports loadable modules. (If you don't know what this means, you probably don't have to worry about this!)
1. Special note for owners of Microsoft Smartphone devices
These devices are not guaranteed to work with any released Linux kernel! Read on for the solution!
This note is known or probable to apply to the following devices, but may also apply to others:
* HTC Canary/Tanager (also known as i-Mate Smartphone, Orange SPV/SPV e100, Qtek 7070)
* HTC Voyager (also known as i-Mate Smartphone 2, Orange SPV e200, Qtek 8080)
* HTC Typhoon (also known as Orange c500, Qtek 8010) -- Dave Jenkins reports that it works with an unpatched 2.6.11-1.1369_FC4 kernel.
* Motorola MPx200
If you follow the USB debug instructions for any of the device you will see something very similar to this in the debug log, here with the most important line marked with red color:
pppd[1061]: pppd 2.4.2 started by root, uid 0
kernel: usbserial.c: serial_open
kernel: ipaq.c: ipaq_open - port 0
kernel: host/usb-uhci.c: interrupt, status 3, frame# 1541
kernel: ipaq.c: ipaq_read_bulk_callback - port 0
kernel: ipaq.c: ipaq_read_bulk_callback - nonzero read bulk status received: -84
kernel: usbserial.c: serial_ioctl - port 0, cmd 0x5416
kernel: usbserial.c: serial_ioctl - port 0, cmd 0x5401
kernel: usbserial.c: serial_ioctl - port 0, cmd 0x5401
kernel: usbserial.c: serial_ioctl - port 0, cmd 0x5404
kernel: usbserial.c: serial_chars_in_buffer = port 0
kernel: ipaq.c: ipaq_chars_in_buffer - queuelen 0
kernel: usbserial.c: serial_set_termios - port 0
kernel: usbserial.c: serial_ioctl - port 0, cmd 0x5401
kernel: usbserial.c: serial_open
kernel: usbserial.c: serial_close - port 0
If you have a device with the error above, you need a workaround in order for your device to work with SynCE!
Note: The support for Microsoft Smartphone will be simplied in the future!
2. Installation of the SynCE software
Please note that this HOWTO is not yet finished!
For the time being, this part is very brief!
If you are running an RPM-based Linux distributions such as the ones in this list, install the latest RPM version of SynCE:
* Fedora
* RedHat
* Suse
* Mandrake
If you are running Debian Testing or Unstable, the latest version of SynCE should be available in your repository.
If you are running Gentoo, there is an ebuild for SynCE, but make sure it uses the latest SynCE version!
If any of the above does not apply to you for some reason, you can compile SynCE yourself.
3. Configuration of the kernel driver
Please note that this HOWTO is not yet finished!
These actions described in this section have to be performed every time you upgrade your Linux kernel!
SynCE uses a Linux kernel driver called ipaq in order to handle the USB connection. You may need to patch this driver before you can make a successful USB connection.
Everything in this section should be performed as the root user.
If you compile the kernel yourself...
Pre-compiled Linux kernels usually includes the ipaq Linux kernel driver that is required to use SynCE with USB.
If you compile the Linux kernel yourself, make sure that this driver is included in your kernel configuration:
USB Support ->
USB Serial Converter support ->
USB PocketPC PDA Driver
Kernel version
Note: The recommended Linux kernel version for SynCE is 2.6.10 or later!
Run this command to find out your kernel version:
uname -r
Read more in the apropriate section below:
2.4.x Your kernel is not supported by this HOWTO, sorry. Use the No HOWTO page.
2.5.x kernel Your kernel is not supported at all by SynCE. We suggest that you upgrade to a 2.6.x kernel!
2.6.x kernel Keep going!
Linux distribution
If your Linux distribution is one of these and you have a kernel version prior to 2.6.9 you need to patch your Linux kernel:
* Suse 9.1
* Gentoo
* Debian Unstable
If this applies to you, download kernel-2.6-driver.tar.gz, extract and follow the instructions in the README file.
Find out USB information about your device
In order to find out if your Linux kernel is ready for your Windows CE device you shall connect the Windows CE device to the PC with the USB cable, but first you should save a list of the current USB devices, to make it easy to find the new device. Run this command:
cat /proc/bus/usb/devices > /tmp/before
Now connect your Windows CE device and make sure it is turned on. Wait a few seconds and run a similar command to get the list of USB devices including the Windows CE device:
cat /proc/bus/usb/devices > /tmp/after
After running the command above you should disconnect your Windows CE device.
Now you shall compare the two files to find out the USB information about your device:
diff /tmp/before /tmp/after
The output from the above command will look something like this:
23a24,31
> T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=049f ProdID=0003 Rev= 0.00
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ipaq
> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms
>
Important parts of the output have been marked with red color, and may be referenced in the instructions below.
The number of USB configurations
First look at the value of #Cfgs=. If it's 1, skip to The Driver entry below! If it's 2 or more, please send a mail to synce-devel@lists.sourceforge.net and tell us:
1. brand and model of your device
2. the output from diff /tmp/before /tmp/after
3. if it worked properly with this HOWTO
The Driver entry
Second you look at the Driver entry. Read more in the apropriate section below.
Driver=ipaq or Driver=usbserial Your kernel driver recognized your device, good!
Driver=(none) Your kernel driver did not recognize your device. You need to perform some special configuration:
1.
Only if your Linux kernel is 2.6.10 or later: please send a mail to synce-devel@lists.sourceforge.net and tell us...
1. your kernel version
2. brand and model of your device
3. vendor/product USB IDs for your device (see Vendor= and ProdID=)
2.
Follow the instructions in Appendix A to add options like this, but replace the red digits with the corresponding ones from the output from the command you ran earlier:
vendor=0x049f product=0x0003
3.
If you have the file /etc/rc.local, open it with a text editor and add this line in order to have things working directly next time you restart your computer:
/sbin/modprobe ipaq
4.
Now run these commands to reload the ipaq module:
rmmod ipaq
modprobe ipaq
If you get the message ERROR: Module ipaq does not exist in /proc/modules when running the rmmod command, just ignore it.
5.
If you got no output from the modprobe command (meaning it succeeded), restart this HOWTO from the Find out USB information about your device section.
6.
If you get the message FATAL: Module ipaq not found, download kernel-2.6-driver.tar.gz, extract and follow the instructions in the README file.
7.
If you got another error message, ask for help!
Another Driver entry Ask for help!
The number of USB endpoints
Next you look at the #EPs= entry or count the number of lines beginning with E:, meaning the number of USB endpoints:
Two or three USB endpoints Nothing to do here, good!
Four USB endpoints You need some special action here. Either follow Stefan Langeland's instructions or these:
First, even if you already did this in the Linux distribution section, download kernel-2.6-driver.tar.gz, extract, replace the file free_len_zero.patch with mitac_mio168.patch, and follow the instructions in the README file.
Second, follow the instructions in Appendix A to add the following option to the kernel module:
ttyUSB=1
Now unload the kernel module and load it again:
rmmod ipaq
modprobe ipaq
No output from the above commands means success.
Note: The support for devices with four USB enpoints will be simplied in the future!
Another number of endpoints Ask for help!
4. Configuration of the connection
Please note that this HOWTO is not yet finished!
Everything in this section should be performed as the root user.
1. Connect your Windows CE device
2.
Try the following synce-serial-config commands until one of them succeed:
* synce-serial-config ttyUSB0
* synce-serial-config tts/USB0
* synce-serial-config usb/tts/0
* synce-serial-config usb/ttyUSB0
Important! If you had four USB endpoints in the USB information for your device instead of the usual two, you should use 1 instead of 0 in the command above!
If you get the error message synce-serial-config was unable to find a character device named..., ask for help!
This does not have to be done again on your system unless your device appears on a different tty for some reason.
5. Starting the connection
For the time being, this part is very brief!
1.
As your own user (not root), start dccm:
dccm (if your device is not password-protected)
dccm -p password (if your device is password-protected)
This must be done after each time you have rebooted your computer.
2. Connect your Windows CE device
3.
As root, run this command:
synce-serial-start
6. Testing the connection
Applications and tools (except for synce-serial-*) that use SynCE must be executed by the same user as is running dccm (not root).
As your own user (not root), try this command:
pstatus (not on Debian)
synce-pstatus (on Debian)
If you successfully got information about your device, congratulations for enduring all the quirks involved in setting up SynCE! :-)
Now is a good time to play with the other command line tools included with SynCE. However, don't forget steps 7 and 8 below!
If you get the message below, the connection failed, and you should make sure that you followed all the steps in this HOWTO properly.
pstatus: Unable to initialize RAPI: An unspecified failure has occurred
If you truly did follow the HOWTO, you may want to get help.
7. Disconnection
In order to properly disconnect your device, you should first close the network connection between Windows CE and SynCE. There are a couple of ways to do this.
Just unplugging the USB cable is not proper disconnection when using SynCE. (This will hopefully be fixed in the kernel driver some day.)
Before you unplug the cable you should do one of these actions, in order of preference:
1. Disconnect with the GNOME Tray Icon or with SynCE-KDE
2. Disconnect with the appropriate action on your PDA
3. Run killall -HUP dccm from the command line
4. Run synce-serial-abort. Please note that this command is only to be used when everything else fails. It also seems like it only works for USB connections while the USB cable is connected.
8. Donation
To show how grateful you are for SynCE, you can donate!
Appendix A. Adding kernel module options
This is a special appendix because the actions here varies between distros.
First select the first alternative to exist on your Linux distribution:
1. The directory /etc/modprobe.d
2. The directory /etc/modutils
3. The file /etc/modprobe.conf.local
4. The file /etc/modprobe.conf
5. The file /etc/modules.conf
If one of the directories exists on your Linux distribution, use a text editor to create the file synce in that directory. If you didn't have any of the directories, open the file you have with a text editor.
Add a line like this, but replace options with the actual options you need to add to the kernel module:
options ipaq options
If you created or edited the /etc/modutils/synce file, run the update-modules command.
Examples
If you have a device with vendor ID 0x1114 and product id 0x0006 that is not recognized by the kernel driver:
options ipaq vendor=0x1114 product=0x0006
If you have a device with four USB endpoints:
options ipaq ttyUSB=1
|
 |
|
|
galexonline
Amministratore
Regione: Lazio
Prov.: Viterbo
Città: Civita Castellana
122 Messaggi |
Inserito il - 19/08/2005 : 15:51:42
|
adesso l'help per il collegamento tra multisync e Synce
al solito leggetelo direttamente dal sito ufficiale
http://synce.sourceforge.net/synce/multisync_guide.php
ma per ogni evenienza, nel caso la pagina non fosse raggiungibile, lo riporto qui sotto
SynCE - Using the SynCE plugin for MultiSync
Warning! This is experimental software. Anything can happen. Use it at your own risk.
Follow these instructions to use the SynCE plugin for MultiSync
1. Get the latest 0.8x version of MultiSync up and running. Verify that MultiSync works with your version of Evolution by creating and testing a synchronization pair with the Evolution and Backup plugins.
2.
Use the synce-matchmaker tool to create a partnership between SynCE and your Windows CE device. If you don't have this tool you must install the synce-rra module. Download.
3.
Install the SynCE plugin for MultiSync. Download.
4.
Make sure that you have a working connection to your PDA, for example by running the pstatus tool.
5.
Create a new synchronization pair in MultiSync, where SynCE is one of the plugins.
6.
The first time you synchronize, the SynCE plugin for MultiSync will attach to the current partnership and subsequently only synchronize with a device that has this partnership.
Only have the SynCE plugin for MultiSync in one synchronization pair for each of your Windows CE devices. If you want to synchronize a Windows CE device with more than one other plugin, setup your synchronization pairs something like this:
SynCE - Evolution
Evolution - IrMC |
|
|
| |
Discussione |
|
|
|
Sincronizzare Pocket PC con Evolution su Linux
