USB pilot-link under Fedora Core 3: /dev/ttyUSBx there but not there
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USB pilot-link under Fedora Core 3: /dev/ttyUSBx there but not there
I have pilot-link 0.11.8-8 and several of the higher-level utilities installed on an HP Visualize (similar to a Kayak) running Fedora Core 3 (kernel 2.6.12-1.1372_FC3 #1). Serial port syncing works fine for my Palm IIIe and Kyocera 7135, but I can't get USB syncing to work for either the Kyocera 7135 or my Visor Prism.
udev is installed, so the devices must be dynamically created. I created a file in /etc/udev/rules.d called pilot.rules, containing
lsmod shows the following:
Module Size Used by
ohci_hcd 26081 0
visor 20301 0
usbserial 28841 1 visor
.
.
.
So it appears all the necessary modules are loaded.
When I press the hotsync on the Visor cradle, the following messages are logged:
Oct 11 12:41:41 tala kernel: usb 1-1: new full speed USB device using uhci_hcd and address 15
Oct 11 12:41:41 tala kernel: usb 1-1: Handspring Visor / Palm OS: port 1, is for Generic use
Oct 11 12:41:41 tala kernel: usb 1-1: Handspring Visor / Palm OS: port 2, is for HotSync use
Oct 11 12:41:41 tala kernel: usb 1-1: Handspring Visor / Palm OS: Number of ports: 2
Oct 11 12:41:41 tala kernel: visor 1-1:1.0: Handspring Visor / Palm OS converter detected
Oct 11 12:41:41 tala kernel: usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
Oct 11 12:41:41 tala kernel: usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB1
Oct 11 12:41:46 tala udev[10333]: removing device node '/dev/ttyUSB1'
Oct 11 12:41:46 tala kernel: usb 1-1: USB disconnect, address 15
Oct 11 12:41:46 tala kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
Oct 11 12:41:46 tala kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
Oct 11 12:41:46 tala kernel: visor 1-1:1.0: device disconnected
Oct 11 12:41:46 tala udev[10330]: removing device node '/dev/ttyUSB0'
... however, the device files /dev/ttyUSB0 and /dev/ttyUSB1 are never actually created, so far as I can tell. Ls says no such files exist, though I'm checking in the interval between when the log says they are created (12:41:41 in the above example) and when they are removed (12:41:46 in the above example). The higher-level Palm tools give similar results.
I have a new treo 650, and set up evolution, gnome-pilot, pilot-link etc. yesterday. Evolution did not work, but the treo connected once (I had to push the sync button before I started pilot-xfer). Today, I upgraded evolution (with yum), and at least it starts up (with a lot of errors), but the sync does not work anymore (no ttyUSB*, though /var/log/messages shows that they are created and that the treo connects).
By the way: I could not login today, after installing all gnome-related rpms to get evolution and gnome-pilot to install. Umcommenting aline in /etc/pam.d/login helped:
# session required pam_loginuid.so
Anyone knows how to handle this? Thanks in advance.
I found out what my problem was. I had my machine configured so that udev was started at boot up. This was obviously changed when I installed some apps to be able to sync my treo.
"/sbin/udevstart" solved the problem, ttyUSB0 & 1 are created in /dev.
Nevertheless, I still cant sync my treo. gpilotd crashes, pilot-xfer gets errors etc ... but connecting works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.