Don't know anything about Debian -- The board works for fedora :-) I did find this with some "google foo" and looks like it might help? http://wiki.debian.org/udev which refers to this http://www.reactivated.net/writing_udev_rules.html#syntax
but if it works for root, it seems like a permissions issue... One bug report diagnostic on debian had this to work out what was happening with a printer/scanner issue..WITHOUT The rules... # lsusb Bus 007 Device 003: ID 03f0:1411 Hewlett-Packard PSC 750 # ls -l /dev/bus/usb/007/003 crw-rw-r-- 1 root lp 189, 770 Apr 7 18:49 /dev/bus/usb/007/003 # and the person wasn't a member of lp group to write. With and without the rules in place, do you have permission on the device? Worth a crack ?? :-) Pete On 12/09/11 13:21, [email protected] wrote: > Hi, > > I have a programmable board connected via USB that is only writeable by > root, so I have to run every make command as root, which is not good. > This is for a class, and the lecturer has given us some udev rules to > use, but they don't work on Debian stable. I new enough versions of the > development tools, so that's not the problem. > > Here are the instructions from the lecturer... > > > set up the USB permissions by creating a file called > /etc/udev/rules.d/52-bootloadDFU.rules containing: > > ATTR{idVendor}=="03eb", ATTR{idProduct}=="2fee", MODE="666" > ATTR{idVendor}=="03eb", ATTR{idProduct}=="2ff0", MODE="666" > > To activate this new rule, reboot or use > > sudo udevadm control --reload-rules > > Note, with older versions of udev (prior to Ubuntu 10.04 Lucid Lynx) you > need the following syntax: > > SYSFS{idVendor}=="03eb", SYSFS{idProduct}=="2fee", MODE="666" > SYSFS{idVendor}=="03eb", SYSFS{idProduct}=="2ff0", MODE="666" > > > I tried both syntaxes and even rebooted when neither worked after > running udevadm. > > I'm going crazy here. I can just run make commands as sudo, but that's > rather unsafe, especially when it comes to writing our own make files. > Anyone know what on Earth the problem could be? I've attached the (I > think) the relevant part of my syslog. It does not appear to even be > trying to load the new rule file. > > Ripping hair out, > Aidan > -- Peter Glassenbury Computer Science& Software Engineering [email protected] University of Canterbury +64 3 3667001 ext 7874 _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
