On Wednesday 13 April 2005 14:26, Bjarne Wichmann Petersen wrote:
> Just got myself a Palm Zire and I'm trying to get it to connect with
> kpilot, but i'm not having any success. And I'm a bit at a loss as what I'm
> supposed to setup before running kpilot.
Figure it out with pilot-xfer first. That's command-line and _far_ easier to
tweak, since it's not reading config files scattered across the system, nor
suffering from a split between daemons and UIs and whatnot.
> 1) I'm running 5.3-STABLE and KDE 3.3.2
> 2) The Zire connects to /dev/ugen0 when I activates the HotSync on the
> Zire.
Sounds reasonable. Um, no. Not at all. kldload uvisor, so that it actually
gets /dev/ucom0. Note that GENERIC ships with every weird-ass USB driver
enabled including the Rio 500 specific USB module, but _not_ the Palm uvisor
driver.
> 3) I've only readpermissons to /dev/ugen0, even though I've put "perm
> 666 ugen0" into /etc/devfs.conf
Getting devfs to work is a size large pain in the ass. I seem to have lost my
devfs setup now -- I used to have a script that I would run as root after
boot to actually set up the devfs rules properly. It did this:
devfs ruleset 10
devfs rule delset
devfs rule add path ucom* mode 666 group console
devfs rule add path acd* mode 666 group console
devfs rule applyset
> 4) Kpilot (usign the wizard) can't connect to the Zire.
I wouldn't swear that the wizard works at all. But it might. Most important is
that you load the visor driver first.
--
As of September 1st, 2004, the University of Nijmegen will _still_ be the
University of Nijmegen, but with a different nonsensical adjective in front.
Reach me at [EMAIL PROTECTED] instead. GPG FEA2 A3FE
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
