hmm, you may need to see what usb device files get created when you connect the pda, in the past the device file would not get created until one actually started a hotsync, of course since the hotsync requires knowledge of the device file the hotsysnc would fail! however, the line: > 22:17:01 Pilot device /dev/pilot doesn't exist. Assuming the device uses > DevFS. > 22:17:02 Trying to open device... > 22:17:02 Could not open device: /dev/pilot (will retry) > 22:17:08 Device link ready. > 22:17:08 Checking last PC.. makes me think that kpilot is a lot cleverer than that now, in fact the log states that: > 22:17:09 KPilot 4.3.10 (BRANCH) HotSync starting... > > 22:17:09 [Conduit abbrowser_conduit] > 22:17:09 Running with flags: > 22:17:10 No Files to install > 22:17:10 End of HotSync > > 22:17:10 HotSync Completed. so you did do a hotsync! if the results weren't what you expected then perhaps you need to check the settings for the abbrowser conduit (thats the one for syncing the pda addressbook with the kde one), it appears that no other conduits are configured since they aren't referenced in the log
as for why you get the error message after the hotsysnc: > 22:17:10 HotSync Completed. > 22:17:12 Pilot device /dev/pilot doesn't exist. Assuming the device uses > DevFS. > 22:17:13 Trying to open device... > 22:17:13 Could not open device: /dev/pilot (will retry) i'm not sure, that might not indicate an error, just the logic of the part of the sync daemon that keeps the connection open? i'm not sure that you do need to create a /dev/pilot link given what the log says, but if you wish to do so then i'd start a hotsync while seeing what files get created in /dev/usb, if you see a file called /dev/usb/tts/1 or /dev/usb/tts0 then try creating /dev/pilot as a link to one of those: ln -s /dev/usb/tts/1 /dev/pilot, or try linking to any other files that seem to be created when you press the hotsync button bascule On Wednesday 03 Mar 2004 3:24 am, g wrote: > Hi folks, > > I'm a newbie and admit that I have little idea what I am doing. > I am trying to get my Sony USB based palm pilot (model PEG-SJ22) to synch > with built in programs under mandrake 9.2 > I am currently using the Gnome desktop, and have tried synching with both > jpilot as well as kpilot. > > When I try to synch, this is what kpilot has to say about it: > > ================================== > > Version: KPilot 4.3.10 (BRANCH) > Version: pilot-link 0.11.8 > Version: KDE 3.1.3 > Version: Qt 3.1.2 > > HotSync Log > > 22:17:01 Pilot device /dev/pilot doesn't exist. Assuming the device uses > DevFS. > 22:17:02 Trying to open device... > 22:17:02 Could not open device: /dev/pilot (will retry) > 22:17:08 Device link ready. > 22:17:08 Checking last PC... > 22:17:09 KPilot 4.3.10 (BRANCH) HotSync starting... > > 22:17:09 [Conduit abbrowser_conduit] > 22:17:09 Running with flags: > 22:17:10 No Files to install > 22:17:10 End of HotSync > > 22:17:10 HotSync Completed. > 22:17:12 Pilot device /dev/pilot doesn't exist. Assuming the device uses > DevFS. > 22:17:13 Trying to open device... > 22:17:13 Could not open device: /dev/pilot (will retry) > ================================== > > There does seem to be some communication taking place between the computer > and PDA as the PDA hotsynch log registers: > "KPilot 4.3.10 (BRANCH) HotSynch" and shows the proper date and time that I > tried to initiate the synch. > > I have tried various settings both on the pilot as well as in kpilot. > What does "/dev/pilot" mean? I looked in the /dev directory and found no > entry for "pilot". Do I need to create this? If so how? > > Any help would be much appreciated ! > Thanks a bunch. > Gideon Turner -- "`The best way to get a drink out of a Vogon is to stick your finger down his throat...'" -- The Book, on one of the Vogon's social inadequacies.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
