I can't say for sure that you have the same problem as I had, but it sounds like it.
I am running Debian testing with procbususb mounted. To find out if you have procbususb mounted type: mount | grep proc If it is (ie you see procbususb listed), you need the line listed for "Dapper" If you don't you will need the other line for "Gusty/Hardy". I don't see any harm in using both lines (it will match one of them that way) in the android rules file. The root access problem will come from the udev rule not matching, so the device ownership is not adjusted. As a side note, I know that older versions of udev (particularly Red hat Enterprise Linux 4) do not have the same udev support. I think if you copy both lines from the help page into the udev/rules.d/50-android file it should work. If it does not, you may have an older version which uses a separate permissions file. The important things for diagnosing the problem would be the following: distribution (Debian/Ubuntu/Red Hat Enterprise Linux/Fedora/Suse/Gentoo....etc) udevd --version (udev it the dynamic device node creation system, the rules help setup device access) uname -r (kernel version) mount | grep procbus (using usb_device instead of usb for udev match) Another check is to see if /sys/class/usb_device/ exists. Make sure you reload udev after modifying rules (either sudo /etc/init.d/udev reload or restart) Isn't that the exact same set of instructions I'm saying don't work? > I've done all that. There is still a permissions problem unless I run > the adb server as root. > --~--~---------~--~----~------------~-------~--~----~ > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
