On Sat, Dec 26, 2009 at 11:22:18AM -0700, Nathanael Noblet wrote: > To clarify. > > on F12, the stock rpm has *no* udev rules file. When I take the udev rules > from your sources, and place them in the rules.d folder, subsequent > insertion of the blackberry no longer shows up in lsusb as a normal user or > btool -l. Prior to having the rules in place, it would show up, but btool -l > would get a perm denied when trying to do anything, same with bidentify and > all those other syncing tools. > > Also, it seems that once I put those udev rules in place, the device started > getting assigned the plugdev group, whereas without the udev rules, it was > always root:root...
Thanks for the clarification. There are two udev files that I include. One is for running bcharge automatically when you plug the device in, and the other is for setting the permissins and the group. Try this: remove the one with bcharge in it, and leave the 99-blackberry.perm.rules. Then plugin your device, wait a while, run bcharge manually as root, wait a while, and then see if the device shows up in 'lsusb' and whether btool can see it. I'm not pleased that udev rules can now affect what 'lsusb' even sees. Seems like somebody is breaking fundamental parts of Linux. :-( > So based on your two replies, I'm thinking that putting the udev rules there > has now made it change the group ownership, however I need to check the ACLs > ... > > [g...@iridium ~]$ getfacl /dev/bus/usb/001/003 > > getfacl: Removing leading '/' from absolute path names > # file: dev/bus/usb/001/003 > # owner: root > # group: plugdev > user::rw- > group::rw- > other::--- > > Which doesn't give me much info past what I can already see with a ls -l on > the directory... I'm wondering about how to debug the HAL fdi files in F12 > vs those in F11. The usb device nodes in F11 didn't change ownership or > anything, but I haven't had a chance to look at what they did with respect > to the ACL stuff... I should probably be filling some of this on the fedora > bugzilla I guess, but I figured you'd probably know what is going on. Any > other ideas? We need to fix the 'lsusb' issue first. The above getfacl output is consistent with udev-only operation. If the device showed up in 'lsusb', you'd be fine using the plugdev group. - Chris ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
