You are not logged in.
Hi there,
I use a Sony Clié as my palm. It worked with no hitches, up to now--since the last greater update (udev and kernel26), it can't connect using either jpilot or the gnome-pilot-applet/evolution. In the gpilotd-control-applet, the cradle device is set to /dev/tts/USB1. Now, if I hit the hotsync button and do a ls -l /dev/tts, no USB1 appears.
/var/log/kernel says:
Jul 17 21:12:08 karoshi kernel: usb 2-1: new full speed USB device using uhci_hcd and address 5
Jul 17 21:12:08 karoshi kernel: usb 2-1: configuration #1 chosen from 1 choice
Jul 17 21:12:14 karoshi kernel: usb 2-1: USB disconnect, address 5
Now, how do I find out where in /dev my palm is when connecting it to the PC? Any ideas?
Any feedback is much welcome.
/edit: this probably better fits with the "kernel" subforum. If a mod could move this thread, it would be much appreciated, too. Sorry for the hassle.
Offline
Okay, found the error: Apparently, the latest udev doesn't autoload the "visor" kernel module. I had to add it by hand to rc.conf, now it works again.
Sorry for the bother.
Offline
Okay, found the error: Apparently, the latest udev doesn't autoload the "visor" kernel module. I had to add it by hand to rc.conf, now it works again.
Sorry for the bother.
Not a bother, had the same problem and now I have the solution thanks. Just for that, I'll move your thread! :-)
Dusty
Offline
Are you (or is anyone) having problems with this again? I'm finding /dev/tts/USB1 is not being created when I plug the palm in, but now visor is indeed loaded. Further, the kernel isn't even trying to recognize it, nothing about it in dmesg or /var/log/messages and lsusb isn't showing it. I'm trying to determine if this is a general problem for people since the last kernel release, or if I'm having troubles with my USB controller again, its been sketchy... Maybe I need a new cable.
Dusty
Offline
I know from a friend (also running arch), that his palm have exactly the same problem. The kernel doesn't recognize that a palm is plugged. No messages in dmesg.
But he is on holiday for 10 days...After his return he can post more informations about his problem...
Daniel
Offline
For me, I think it may be a cable problem, it suddenly started working and then stopped. managed to sync it though. We'll see what your friend has to say.
Dusty
Offline
It still worked on the week-end, and I'm pretty sure I didn't update the kernel since then. But I'll check tonight.
Offline
Okay, still works.
kernel26 2.6.17.6-1
udev 096-1
-Sascha.rb
Offline
I ordered a cradle... will see how that works...
Dusty
Offline
I'm using a cradle, I can only suggest everybody does. Far less hassle.
Offline