|
Dimensione: 15227
Commento:
|
Dimensione: 9304
Commento:
|
| Le cancellazioni sono segnalate in questo modo. | Le aggiunte sono segnalate in questo modo. |
| Linea 76: | Linea 76: |
| == Notes from other users == * Note: "jpilot" works self-contained and matches fields on your device. "kpliot" syncs with Kubuntu/KDE's Kontact and maps fields, as best it can. * All Palm handhelds create 2 connections when the HotSync button is pushed. In most cases these are /dev/ttyUSB0 and /dev/ttyUSB1. Your connections may vary, depending on what other USB devices you have connected. * For most Palm devices, the data communication takes place on the second connection created (i.e. /dev/ttyUSB1). There are a handful of Palm devices which use the first connection to do data communication. You may have to try both to discover which is appropriate for your particular device. I once found a list specifying which devices went which way; alas I have lost it. * I used these directions and they worked great. but after upgrading to gusty I had problems again. I seems that in gusty there is a udev rule already set up for palm devices that conflicted with this rule above. in the file "60-symlinks.rules" I commented out the rule that was for palm devices and my treo 650 syncs again like before. With the 2 rules together I was getting /dev/pilot becoming symlink to IT'S SELF. if you see some thing like this: ls -l /dev/pilot lrwxrwxrwx 1 root root 5 2008-01-21 00:10 /dev/pilot -> pilot you might have a similar problem. * If you experience unreliable syncing, consider hardware problems. Try another USB connection. If you are using a USB hub, eliminate it or try another. Don't be afraid to swap the USB cable either. These are easy things to try, and I have had syncing problems due to both a hub and a cable. * I could not use the "ttyUSB*" kernel option, as udev kept creating the /dev/pilot symlink pointing to /dev/ttyUSB0. I had to specify "ttyUSB[13579]". * Before creating too quickly a rule if your sync doesn't work, check if you don't already have a similar rule or line related to a Palm device. It was the case for me in Ubuntu 5.10. I had 2 custom rules (created before, in previous attempts) plus a basic one in the udev.rules file. To make it work, I had to delete all rules or lines related to Palm in my udev tree. Then create a brand new one as explained. Then test the results in pressing the Hotsync button and doing a ls -l /dev/ttyUSB* or ls -l /dev/pilo*. Something must show up if the rule is working. Once you're done go ahead for jpilot/gnomepilot/kpilot or wathever. * To get my Palm T5 to sync I added line (BUS="usb", SYSFS{product}="palmOne Handheld*", KERNEL="ttyUSB[13579]", SYMLINK="pilot), without (), to above described created file (gksudo gedit /etc/udev/rules.d/010-custom.rules). This was done with information found on link (http://andyspace.me.uk/node/250). *Using the information from the link provided above I was able to setup my Treo650 to work on Ubuntu 5.10 (Breezy Badger). I ammended the line in the "010-custom.rules" file to the following: BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[13579]*", SYMLINK=="treo". Then run the PalmDevices setup. *I'm using Breeze Badger and I was having trouble syncing with all the information provided on this link. It would sync once and then not again, or maybe it was random but it didn't sync every time I tried. I switched to jpilot and changed the "010-custom.rules" file to: BUS=="usb", SYSFS{product}=="PalmOne Handheld*", KERNEL=="ttyUSB*", NAME{ignore_remove}=="treo", MODE=="666". That worked like a charm for the Treo 650. Now it syncs every time. *I'm using Edgy with Treo 650. I created a file named "/etc/udev/rules.d/010-custom.rules" containing 'BUS=="usb", SYSFS{product}=="*[vVisor]*", KERNEL=="ttyUSB[13579]", SYMLINK+="pilot", GROUP="dialout", MODE="0660"'. I'm not sure if it's necessary, but I then did "/etc/init.d/udev restart". Even though it makes no sense, synchronization wasn't possible until I upped the speed in JPilot to 57600. Yeah, I know--it shouldn't matter--but it does. Now it syncs every time. If you're fighting with this, make sure you "sudo tail -f /var/log/messages" and keep an eye on "ls -l /dev/pilot". Also, make sure you're user has dialout permissions. *Just a note on the difference between "==" and "=" in the above. The former is used for equality comparisons (as in BUS, SYSFS, & KERNEL), whereas the latter is for assignments (as in NAME & MODE). This is a very important distinction which if ignored will yield a rather elaborate udev no-op line in your rules file! * Important for all '''Treo 650 users trying to sync with Evolution''': before doing anything, you should make sure that you add the lines <!-- Treo 650 --> and <device vendor_id="0830" product_id="0061" /> to your /usr/share/gnome-pilot/devices.xml file. Without this line, your Treo will behave erratically when syncing and may crash Gnome Pilot (especially if you are trying to sync tasks). == Handspring Visor Prism(a colori) su Jaunty == Funzioona correttamente e richiede il modulo Visor (vedi punto 5 del paragrafo precedente) caricato all'avvio. == Treo 680 su Feisty == I found that Feisty comes with all the right settings; notably no changes are needed to the rules files. However, the rules are set up such that the link /dev/pilot is created dynamically when the OS recognizes the palm device, at the time the hotsync button is pressed. This has complications for the sync software such as kpilot. The sync software (notably the daemon that's opening the device node) must be started _after_ the hotsync button is pressed. Otherwise the OS might reassign the device node and the daemon will be looking at a stale device node. This can be avoided by having the sync software talk to /dev/ttyUSB0 directly, rather than via the /dev/pilot, but if you use multiple serial devices, then they might confuse each other, as the OS will pick the next free device node, e.g. ttyUSB1, ... |
|
| Linea 133: | Linea 100: |
| == Palm T5 on Ubuntu 9.10 - Karmic Koala == | == Palm T5 e Ubuntu 9.10 - Karmic Koala == |
BR Indice(depth=2 align=right)
Palm OS
Questa pagina spiegherà come sincronizzare computer palmari Palm OS con Ubuntu.
Introduzione
Ci sono molti programmi che consentono la connessione di un dispositivo palmare con Linux. Questa guida coprirà i più diffusi programmi e metodi di connessione.
Programmi
gpilotd BR jpilotBR kpilotBR pilot-linkBR
Configurazione di un dispositivo Palm
Istruzioni
1. Eseguire in un Terminale, facendo clic su Applicazioni -> Accessori -> Terminale, il seguente comando:
gksudo gedit /etc/udev/rules.d/10-custom.rules
oppure per Kubuntu:
sudo kate /etc/udev/rules.d/10-custom.rules
}}]
3. Inserire la seguente linea nel file vuoto:
{{{
BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*", NAME{ignore_remove}="pilot", MODE="666"4. Salvare il file, chiudere Gedit o Kate e chiudere il Terminale.
5. Per le versioni Ubuntu 7.04 (Feisty Fawn), 7.10 (Gutsy Gibbon), 8.04 (Hardy Heron) and 9.04 (Jaunty Jackalope) se il precedente sistema non funziona, aggiungere il modulo visor in etc/modules:
gksudo gedit /etc/modules
oppure
sudo kate /etc/modules
aggiungere alla fine
visor
e salvare il file. Riavviare il computer. È possibile anche caricare il modulo immediatamente, senza riavviare il computer:
sudo modprobe visor
Importante: prima avviare la sincronizzazione di Palm dopodiche jpilot.
Conclusioni
Qualsiasi applicazione per la sincronizzazione di dispositivi Palm cerca il file /dev/pilot, quindi questa semplice soluzione consentirà al dispositivo palm di essere plug-and-play.
Extra Information
Information for this article comes from http://www.reactivated.net/writing_udev_rules.html#example-pilot Writing UDEV Rules
Treo 755p su Hardy
Treo non viene riconosciuto automaticamente al collegamento del cavo USB, quindi è necessario eseguire da terminale:
lsusb
e quindi sarà possibile la sincronizzazione tramite gnome-pilot. È richiesto il caricamento del modulo visor all'avvio, ma non è necessaria alcuna modifica ai file di configurazione di Udev.
Palm Centro
Ubuntu 8.10 - Hardy Heron (amd64)
La sincronizzazione di Evolution con Palm Centro non presenta problemi seguendo i passi soprariportati.
Ubuntu 9.04 - Jaunty Jackalope (amd64)
Usare usb: (libusb) al posto di /dev/pilot (modulo visor) per la sincronizzazione via USB.
Palm TX e Ubuntu 9.04 - Jaunty Jackalope
Nel file /etc/udev/rules.d/10-custom.rules, aggiungere la seguente linea:
BUS="usb", SYSFS{product}="Handspring Visor*", KERNEL="ttyUSB*", NAME{ignore_remove}="pilot", MODE="666"Palm TX identifica se stesso come "Handspring Visor", non con una stringa che inizia con "Palm"
Palm T5 e Ubuntu 9.10 - Karmic Koala
- Ubuntu: 2.6.31-20-generic (Feb 8 09:05:19 UTC 2010)
- Palm OS: Garnet v.5.4.8
- J-pilot: 1.6.2.4
Purtroppo con questa combinazione, qualsiasi tentativo di syncronizzazione causerà problemi con il Palm.
Per aggirare il problema fare clic su File|Preferenze|Conduits disabilitare tutti conduits tranne memo. Ciò permetterà la sincronizzazione. Quindi abilitare uno o più conduits alla volta per trovare quello colpevole, oppure sino a che abbiate quelli necessari funzionanti.
Gnome-pilot
Gnome-pilot is the default Palm synchronization software of Gnome. It can be installed from the repositories, look for gnome-pilot and gnome-pilot-conduits.
Three programs (commands) are part of this:
- gpilotd: do the synchronization. BR - gpilot-applet: applet for the Gnome panel. Allow synchronizing from the Palm's hot sync button. BR - gpilotd-control-applet: GUI for setup the options. BR
The first step is to add the applet to the Gnome panel. To do this right click somewhere on a free space in the panel and choose Add to Panel, then under the Utilities category choose Pilot Applet. After installation the applet a new icon appear in the panel. This icon allow automatic synchronizing the Palm just by pressing the hotsync button in the Palm. And by doing a this icon the program Pilot Settings pop up. This applet is the equivalent to the Hotsync icon in Windows.
The second step is to configure the synchronization options. Open this by doing a click on the applet or by selecting System -> Preferences -> PalmOS Devices in the Ubuntu menu. A message appears “You seem to be running Gnome-Pilot for the first time ... “, press «Forward» and then choose your options.
The connection should work fine. If not try this: BR 1) Verify that the cable are well plugged, or the infrared is working in both devices. By the end of 2006 Bluetooth isn't supported yet as gnome-pilot does not include it. BR 2) Try each speed of connection. Adjust the value in both Ubuntu and the Palm. BR
Answer if the device was previously synchronized or not, then forward. Once identified the user press «forward». Fill in the boxes for the pilot name and local base dir. Pilot name is just a name for identify a device among others.
Final step is configure the conduits. Conduits are the instructions to synchronize an application in Gnome with an application in the Palm. Unfortunately, there is only a couple of conduits for Gnome-pilot. There are conduits for synchronize contacts, calendars, memos, and tasks between Evolution and the corresponding Palm applications (See further for details).
There is a useful conduit for backup your Palm programs and database. There is a bug in this conduit for Ubuntu versions prior to 7.04 (Feisty Fawn) that resets the Palm; to solve it:
sudo edit ~/.gnome2/gnome-pilot.d/backup-conduit
then add WiFiCoreLib to exclude_files as follows:
exclude_files=WiFiCoreLib
Other conduits are available but are not mention here.
Evolution and Gnome-pilot
Here is an explanation of what modules work with Evolution and Gnome-pilot. Every module can by configured to import, export, o synchronize. Use System -> Preferences -> PalmOS Devices or click on the Gnome-pilot applet (See Gnome-pilot instructions).
- Mail: not available yet (January 2007). A workaround could be synchronize Evolution with your mail account in Ubuntu and synchronize the mail client of the palm in Windows. Another solution may be use a Yahoo! mail account in Ubuntu and synchronize the palm and Yahoo using Yahoo's Intellisync in Windows.
- Contacts: Works well, but be aware that some fields are not received by the Palm. For a clean synchronization delete AddressDB and ContactsDB-PAdd in your Palm (just in case do a previous backup), you can use [http://www.nosleep.net/|FileZ] for free to do this.
- Calendar: Works well.
- Memos: Works well.
- Tasks: Works well.
More help can be found at Evolution User guide in Evolution (Menu Help -> Contents or by pressing F1 in the keyboard). Go to Synchronizing Your Handheld Device. Skip Enabling Synchronization because this part was explained here with more detail (Gnome-pilot), and jump to Selecting Conduits.
If your device fails to sync with an error message relating to the 'visor' module, probably TREO models. At a command prompt, type "sudo modprobe visor", press «ENTER» and try again. If this works, you can permanently load the visor module at every startup by adding the line 'visor' at the end of the /etc/modules file. You could use "gksudo nautilus" from a command prompt to do this, then browse to the file in /etc/.
VMWare Workstation and Windows XP
You can run the Palm Desktop software under VMWare and use the Palm HotSync Manager. USB syncing can be elusive to get working. Under VMWare Workstation 5.5.4 you may have to add
usb.generic.skipSetConfig = "TRUE"
to your .vmx file. You may have to unload the visor kernal module prior to starting your vitual machine using, for example,
sudo modprobe -r visor
Under Ubuntu 7.04 (Fiesty Fawn), you may have to mount usbfs using, for example,
mount -t usbfs usbfs /proc/bus/usb
or by adding the line
/proc/bus/usb /proc/bus/usb/ usbfs none 0 0
to your /etc/fstab file.
Troubleshooting
To verify that the palm has been detected after plugged and turned on type in a terminal:
gedit /var/log/messages
and check the last lines.
To take a look of the running processes type:
ps -A
To kill a process type:
kill ###
where ### is the number of the process.
An alternative way to move/copy files into the Palm is to move/copy the files to a memory card (SD, MS, ...) first using a card reader and Nautilus, then insert the card in the palm's slot and transfer it using a program like Filez FileZ.
