[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Tungsten T usb devfs
From:       Bleck <bleck () laposte ! net>
Date:       2003-11-27 18:20:04
[Download RAW message or body]

> Is kpilot (or the kpilot daemon) bneing created by the USB-hotplug daemon?

No, the kpilotDaemon is created by kpilot. The icon on the desktop, as well as 
the /dev/pilot entry are created by some other scripts, in  /etc/dynamic. 

> You should start KPilot, and 
> then hit the hotsync button yourself.

On my system, it makes no difference.
If I hit the button first, then the kpilot shortcut appears on desktop. I just 
click on it, then it runs the daemon which immediately finds the device.
If I lanch kpilot first, then it launches the daemon which waits for the 
device. When I hit the button, the device is created and found by the daemon.

Both methods are equaly [un]efficient.

> > It seems that /dev/ttyUSB0 is the only device that works with this Palm,
> > in
>
> That's odd, since traditionally the pilot devices have created a device 0
> for general use and a device 1 for hotsync use.

I know. That's why I wasted so much time until I succeeded in performing my 
first sync. It should be perfectly clear that on *this* system, with a usb 
Palm TT, /dev/ttyUSB0 is the *only* device that works.

> You could configure your USB demon
> to ln -s /dev/whatever /dev/pilot so that KPilot, which sits there trying
> to open /dev/pilot, latches on to the right device. One additional prolem
> might be that KPilot tries every second, and some pilots / OSses are
> snippy about timing.

On Linux MdK 9.2, the script which creates /dev/pilot is 
/etc/dynamic/scripts/visor.script. It took me some time to find it, since it 
does not seem to be the usual way and place (/etc/hotplug/usb/) to do it 
[ref. http://linux-hotplug.sourceforge.net]. I patched the script and 
reverted to kpilot orginal setting (/dev/pilot). It "works" (see below).

> > Journal de HotSync
>
> Comment? C'est la seule texte qui est traduite?

Oui...

Remaining problems
===============

I still have a hudge reliability problem. As I said in my previous mail, the 
only hotsync that always succeeds is the first sync after a linux reboot. But 
what happens after the Palm hangs off ? 

The following log reflects the problem :


13:10:11  Device link ready.
13:10:11  Checking last PC...
13:10:11  KPilot 4.3.10 (BRANCH) HotSync starting...

13:10:11  [Conduit vcal-conduit]
13:10:11  Running with flags:
13:10:12  Syncing with file 
"/home/asdrad/.kde/share/apps/korganizer/Agenda.ics"
13:10:12  No Files to install
13:10:12  End of HotSync

13:10:12  HotSync Completed.
13:10:14  Pilot device /dev/ttyUSB0 doesn't exist. Assuming the device uses 
DevFS.
13:10:15  Trying to open device...
13:10:15  Could not open device: /dev/ttyUSB0 (will retry)
     *** here, nothing happens until I hit the hotSync button (expected)  ***
13:10:18  Device link ready.
13:10:19  Checking last PC...
13:10:19  KPilot 4.3.10 (BRANCH) HotSync starting...

13:10:19  [Conduit vcal-conduit]
13:10:19  Running with flags:
13:10:19  Syncing with file 
"/home/asdrad/.kde/share/apps/korganizer/Agenda.ics"
13:10:20  No Files to install
13:10:20  End of HotSync
    *** this really is the last line ***

Here, the Palm has hanged off, but not the daemon. The daemon should complain, 
because the device does not exist anymore. It doesn't. If I hit the hotsink 
button, the daemon will not detect it. The daemon seems to be "lost".

At this stage, I could not stop the daemon process. Even root can not kill it 
(kill -9). Now, I understand why I needed to reboot before being able to sync 
again. But even rebooting is not always enough. If the KDE session manager is 
set to restore my previous session, then it will re-launch a kpilotDaemon, 
according to previous session's context. Then, if kpilot is run, it will 
launch another kpilotDaemon... In this case (two daemons), no sync will 
succeed.

Any idea ?

-- 
Bleck

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]