| 1 |
On 8/18/06, Willie Wong <wwong@×××××××××.edu> wrote: |
| 2 |
> So I am not quite sure whether it is a rules problem or a problem on |
| 3 |
> how udev handles the events. Is there a way to check that? |
| 4 |
|
| 5 |
Well you can start with "udevcontrol log_priority=debug". That should |
| 6 |
cause udev to output debug information to /var/log/messages. What you |
| 7 |
are looking for is a sequence of messages in the form of: |
| 8 |
|
| 9 |
udev_done: seq 3110, pid [8009] exit with 1, 0 seconds old |
| 10 |
udev_event_run: seq 3111 forked, pid [8024], 'add' 'scsi_disk', 0 seconds old |
| 11 |
udev_event_run: seq 3112 forked, pid [8025], 'add' 'block', 0 seconds old |
| 12 |
udev_event_run: seq 3115 forked, pid [8026], 'add' 'scsi_device', 0 seconds old |
| 13 |
udev_event_run: seq 3116 forked, pid [8027], 'add' 'scsi_generic', 0 seconds old |
| 14 |
run_program: '/sbin/modprobe ' |
| 15 |
udev_rules_get_name: reset symlink list |
| 16 |
udev_rules_get_name: add symlink 'sdb' |
| 17 |
udev_rules_get_name: rule applied, 'sdb' becomes 'usbkey' |
| 18 |
... |
| 19 |
|
| 20 |
The "udev_rules_get_name" parts would be the most interesting. |
| 21 |
|
| 22 |
Other than that, the only other thing I might suggest is try a newer |
| 23 |
kernel version. |
| 24 |
|
| 25 |
-Richard |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives