On 8/18/06, Willie Wong <[EMAIL PROTECTED]> wrote:
So I am not quite sure whether it is a rules problem or a problem on how udev handles the events. Is there a way to check that?
Well you can start with "udevcontrol log_priority=debug". That should cause udev to output debug information to /var/log/messages. What you are looking for is a sequence of messages in the form of: udev_done: seq 3110, pid [8009] exit with 1, 0 seconds old udev_event_run: seq 3111 forked, pid [8024], 'add' 'scsi_disk', 0 seconds old udev_event_run: seq 3112 forked, pid [8025], 'add' 'block', 0 seconds old udev_event_run: seq 3115 forked, pid [8026], 'add' 'scsi_device', 0 seconds old udev_event_run: seq 3116 forked, pid [8027], 'add' 'scsi_generic', 0 seconds old run_program: '/sbin/modprobe ' udev_rules_get_name: reset symlink list udev_rules_get_name: add symlink 'sdb' udev_rules_get_name: rule applied, 'sdb' becomes 'usbkey' ... The "udev_rules_get_name" parts would be the most interesting. Other than that, the only other thing I might suggest is try a newer kernel version. -Richard -- gentoo-user@gentoo.org mailing list
