Can anyone explain what files control the udev device mapping. I’m trying to get a fresh install of 11.3 to sync a palm pilot with jpilot.
I have created a "10-pilot.rules " file in /etc/udev/rules.d containing:
BUS==“usb”, SYSFS{product}==“Palm Handheld*”, KERNEL==“ttyUSB*”, NAME=“ttyUSB%n”, SYMLINK+=“pilot”, GROUP=“users” MODE=“0666”, OPTIONS+=“last_rule”
when I hit hot-sync I get:
crw-rw-r-- 1 root dialout 188, 0 Jul 18 22:13 /dev/ttyUSB0
crw-rw-r-- 1 root dialout 188, 1 Jul 18 22:13 /dev/ttyUSB1
If spent the last 6 hours googling around and yes I’m a member of “dialout”
What is controlling the attributes of these nodes?
Oh, and P.S. Why’d they put alpha video drivers into the kernel>:) another 3 hours wasted.
Thanks
Dave
If your rule is working, then ttyUSB* will be owned by users group. What does the following return?
ls -l /dev/ttyUSB*
What is controlling the attributes of these nodes?
IIRC, the uucp group is usually the default group for ttyUSB devices (by virtue of the ‘standard’ openSUSE udev rules).
see above, that is the result of “ls -l /dev/ttyUS*”
Well, I’ll change it to uucp an see what happens.
Sorry, I did a quick skim read on this one - forget the uucp group, it clearly is not involved with the creation of the ttyUSB device nodes here (otherwise your results would show that).
Does the symlink /dev/pilot get created? If not, then some how your rule is being skipped.
Here is the content of /var/log/messages, maybe it will be enlightning
Jul 19 00:25:57 linux-smp4 kernel: [32793.482052] usb 3-1: new full speed USB device using ohci_hcd and address 17
Jul 19 00:25:57 linux-smp4 kernel: [32793.677073] usb 3-1: New USB device found, idVendor=0830, idProduct=0001
Jul 19 00:25:57 linux-smp4 kernel: [32793.677085] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 19 00:25:57 linux-smp4 kernel: [32793.677092] usb 3-1: Product: Palm Handheld
Jul 19 00:25:57 linux-smp4 kernel: [32793.677097] usb 3-1: Manufacturer: Palm, Inc.
Jul 19 00:25:57 linux-smp4 kernel: [32793.677102] usb 3-1: SerialNumber: 00R035H260B8
Jul 19 00:25:57 linux-smp4 kernel: [32793.683079] visor 3-1:1.0: Handspring Visor / Palm OS converter detected
Jul 19 00:25:57 linux-smp4 kernel: [32793.683674] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
Jul 19 00:25:57 linux-smp4 kernel: [32793.683811] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1
Jul 19 00:27:09 linux-smp4 kernel: [32865.319092] usb 3-1: USB disconnect, address 17
Jul 19 00:27:09 linux-smp4 kernel: [32865.319864] visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
Jul 19 00:27:09 linux-smp4 kernel: [32865.319988] visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
Jul 19 00:27:09 linux-smp4 kernel: [32865.320021] visor 3-1:1.0: device disconnected
I’m not familiar with this hardware, but I wonder if there is a udev rule already implemented to handle these devices. It may be that the attibutes in your rule do not all match correctly. Try simplifying your rule slightly.
KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*", SYMLINK+="pilot", GROUP="uucp", MODE="0660"
Note: uucp is the usual group associated with usb devices.
I know that udevinfo can be used to list the attributes associated with your device. Something like ‘udevinfo -a -p /sys/class/tty/ttyUSB0’ may work here.
SOLVED: ( now how do I change the title?)
pilot-link 0.25 ( latest ) they changed the names of the tools and j-pilot doesn’t recognize them!
run
Harkness:/usr/bin # for file in pilot*; do file2=echo $file | sed s/pilot-//; ln -s $file $file2; done
pilot-file fails but that life
Thanks for all your help
Dave