In a previous post I described my experience with getting the Treo 650 talking to SuSE 10.0 OSS. Now that I’ve switched to Kubuntu I need to mention a few things.
This Ubuntu page was a major help for me. Starting with the config from my SuSE install, the first thing I had to do was:
LOAD THE visor MODULE
You aren’t going to get very far without this. You can load it manually with:
sudo modprobe visor
Adding visor to /etc/modules should cause the module to automatically load next time you boot.
CREATE A udev RULE
I finally dove into udev for the first time and found it to be pretty straightforward. I created a file /etc/udev/rules.d/50-treo650.rules with the following line:
BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB*", SYMLINK+="treo650", MODE="666"
This will create /dev/treo650 as a symlink that points to whichever /dev/ttyUSB device that the kernel assigns the Treo. Note that the 666 MODE is very permissive, allowing any user on your system to access the Treo.
FIRE UP KPilot
The only setting I had to change from before was to set the device to /dev/treo650.
DEBUGGING
Open up a shell and run: sudo tail -f /var/log/messages
After you hit the hotsync button, run lsusb -v in a different shell. Scroll through the output and you should be able to find the Treo in there – just look for the word “Palm”.
These tools should provide you with plenty of information to figure out what’s going on.
YES, LINUX IS READY FOR THE DESKTOP
Every grandmother knows how to spoil their grandchildren, how to bake an apple pie, how to load a kernel module, and how to create a udev rule.