| View previous topic :: View next topic |
| Author |
Message |
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
 Posted: Fri Jun 01, 2007 2:40 am Post subject: pilot will not sync[SOLVED] |
 |
|
I don't know what changed, but I've recently tried to sync my
visor with kpilot. The sync operation timed out. Looking at the
dev file "/dev/tts/USB{0,1}" I found them being owned by root.
So, ownership seems to be my problem.
I thought the files where owned by some group called pilot,
and I thought I was part of that group.
In any case, I thought I would write this for anyone that
becomes frustrated with an unattained sync.
Last edited by Horatio on Sun Jun 03, 2007 8:18 pm; edited 2 times in total |
|
| Back to top |
|
 |
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Fri Jun 01, 2007 6:05 am Post subject: |
|
|
| See my udev rules for a Palm device. |
|
| Back to top |
|
|
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
| Posted: Fri Jun 01, 2007 2:51 pm Post subject: |
|
|
PaulBredbury, thank you for all the helpful information in the linked post.
I tried putting the lines
| Code: |
# Visor Neo
BUS=="usb",SYSFS{manufacturer}=="Handspring Inc",NAME="pilot"
# This works for one user's Handspring Visor. Put the desired user in the "usb
" group.
KERNEL=="ttyUSB[01]*", NAME="tts/USB%n", GROUP="usb", MODE="0660"
|
in my /etc/udev/rules.d/10-udev.rules file, and the files /dev/tts/USB{0,1}
did not appear after pressing the sync button on my visor.
PaulBredbury, I know you suggested anyone, with pragmatic intrest here,
edit the /etc/udev/rules.d/91-local.rules file, but I had not read your post.
PaulBredbury, I shall use some of your advice in lieu of the udev rule
run+="..." commands
Last edited by Horatio on Sat Jun 02, 2007 1:40 pm; edited 1 time in total |
|
| Back to top |
|
|
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Fri Jun 01, 2007 3:03 pm Post subject: |
|
|
Do not set the NAME. Set the SYMLINK.
And use the KERNEL entry I specified. There is no point in potentially confusing zero and one. |
|
| Back to top |
|
|
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
| Posted: Sat Jun 02, 2007 3:03 pm Post subject: |
|
|
I put
| Code: |
# Visor Neo
BUS=="usb", SYSFS(manufacturer=="Handspring Inc", KERNEL=="ttyUSB[1, 3, 5, 7, 9
]", Action=="add", SYSLINK+="pilot", GROUP=="usb", MODE=="0660"
|
in /etc/udev/rules.d/91-local.rules and removed the other lines from /etc/udev/rules.d/10-udev.rules. Although, the file /dev/tts/{0,1} appear, but /dev/pilot does not. Also, the owner and group of the files /dev/tts/{0,1} are root.
Sorry, but I am confused. Is there something interfering, or did I not configure the udev usb to serial correctly. |
|
| Back to top |
|
|
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Sat Jun 02, 2007 6:04 pm Post subject: |
|
|
You're adding spaces, failing to close brackets, using the wrong kind of brackets. What a comedy of errors  |
|
| Back to top |
|
|
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
| Posted: Sun Jun 03, 2007 8:17 pm Post subject: |
|
|
I was wondering what packages all the rule files
belonged to and found
| Code: |
10-udev.rules
70-persistent-cd.rules
70-persistent-net.rules
|
did not belong to any package. So I moved them
and rebooted, and now kpilot sync workes.
Now the files /dev/tts/USB{0,1} are symbolic links
and they, repectively as the numbers
correspond, point to ../ttyUSB{0,1}.
Also the former two files are owned by root.root
and the latter two are owned by root.uucp.
My guess is that there was a conflict with old
configuration files.
p.s. PaulBredbury, I just may need my eyes examined.
Last edited by Horatio on Mon Jun 04, 2007 11:57 am; edited 1 time in total |
|
| Back to top |
|
|
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Sun Jun 03, 2007 8:29 pm Post subject: |
|
|
Symbolic links don't have permissions.
It's /dev/tts, not /etc/.
My rule is in /etc/udev/rules.d/91-local.rules so that it will overrule what the group was previously set to in the earlier udev rule files. "91" is named "91" deliberately.
| Code: | | GROUP="usb", MODE="0660" |
|
|
| Back to top |
|
|
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
| Posted: Tue Jun 05, 2007 11:28 am Post subject: |
|
|
| Quote: |
It is important that your own rules get processed before the udev defaults, otherwise your own naming schemes will not take effect! I suggest that you keep your own rules in a file at /etc/udev/rules.d/10-local.rules (this doesn't exist by default - create it). As 10 comes before 50, you know that your rules will be looked at first.
|
from
http://gentoo-wiki.com/HOWTO_Customizing_UDEV |
|
| Back to top |
|
|
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Tue Jun 05, 2007 12:09 pm Post subject: |
|
|
The key word there is naming. From man udev:
| Code: | NAME
The name of the node to be created, or the name the network
interface should be renamed to. Only one rule can set the node
name, all later rules with a NAME key will be ignored.
OWNER, GROUP, MODE
The permissions for the device node. Every specified value
overwrites the compiled-in default value. |
Udev was obviously written with the purpose of confusing people  |
|
| Back to top |
|
|
Horatio
Apprentice
Joined: 25 Feb 2004
Posts: 246
Location: Houston, TX
|
| Posted: Wed Jun 06, 2007 11:05 am Post subject: |
|
|
Interesting. I still have many more sources of documentation to read to start to understand udev.
Well, PaulBredbury, Thank you for all the help. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
