On Mon, Sep 15, 2008 at 01:06, Gordon Farquharson <[EMAIL PROTECTED]> wrote:
> Therefore, the udev rules should therefore illuminate the Disk 1 LED > if a device is attached to either port 0 of bus 1 or port 0 of bus 2. > The Disk 2 LED should be illuminated if a device is attached to port 1 > of bus 0 or port 0 of bus 3. It seems that in /sys/bus/usb/devices, > the port numbers actually start at 1 and not 0 (I think) [2]. > > I think that by default, nslu2-utils only needs to support a standard > NSLU2 configuration. NSLU2s that have been hacked to obtain access to > additional USB ports or use one of the other ports to replace a broken > port are non standard, and in either of these cases, the user will > need to decide which LED to manipulate. With this stipulation, the > following udev patch to the udev rules should work. Here is some additional information on this bug from Michael Glockenstein. This email was originally posted to debian-arm [1]. --- Hello Gordon, that's what in my devices directory: # ls /sys/bus/usb/devices 1-0:1.0 1-1 1-1:1.0 1-2 1-2:1.0 1-2.4 1-2.4:1.0 2-0:1.0 3-0:1.0 I don't know what are the right names to use now, are you really sure regarding the names in your patch, I don't see a 2-1 or 3-1 device here. But with the following #ls /sys/class/usb_device usbdev1.1 usbdev1.2 usbdev1.23 usbdev1.24 usbdev2.1 usbdev3.1 I can see them. So what is the right directory for udev, and why it is not noted exactly in the rules and a wildcard is used? And today the lights are off, because yesterday they were at 3-1/3-2 (so at least I remember) and today again 1-1/1-2. So I think it is a bus numbering problem and changed my rules to SUBSYSTEM=="usb", DEVPATH=="*/[13]-[12]", ACTION=="add", PROGRAM="/usr/bin/leds disk-%n on" SUBSYSTEM=="usb", DEVPATH=="*/[13]-[12]", ACTION=="remove", PROGRAM="/usr/bin/leds disk-%n off" I will further investigate. Regards Michael --- [1] http://lists.debian.org/debian-arm/2008/09/msg00083.html -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
