You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GPIO permission errors after upgrade to 3.18.x (Raspbian) #791
When the latest package raspberrypi-bootloader:armhf 1.20150130-1 was installed, the gpio symbolic links in /sys/class/gpio/ moved from /sys/devices/virtual/ to /sys/devices/soc/20200000.gpio.
The permissions in /sys/devices/soc/20200000.gpio do not include the "x" bit, as as such nobody but root can use the gpio.
This has changed since the latest bootloader, and the only way I can fix this is on boot, as root, run
chmod -R +x /sys/devices/soc/20200000.gpio
Is there a better way to allow a non-root user to access the GPIO?
I think this is happening because /lib/udev/rules.d/60-python-pifacecommon.rules and /lib/udev/rules.d/60-python3-pifacecommon.rules no longer function as expected.
For example, here's /lib/udev/rules.d/60-python3-pifacecommon.rules:
I came round this issue when testing my PiFace Digital, where pifacecommon/interrupts.py threw an exception of not finding /sys/devices/virtual/gpio.
Setting device_tree=off in config.txt makes /sys/devices/virtual/gpio reappear.
After that, PiFace Digital works as expected again.
Can somebody explain how PiFace (my phone really wanted to write "pigface" there) uses these file nodes, and why it doesn't/can't use the nodes under /sys/class/gpio/ instead?
In order for user pi to be able to access gpios without root permissions on a michine with the device tree disabled, udev rules are needed for both /sys/class/gpio and /sys/devices/virtual/gpio. They are needed for /sys/devices/virtual/gpio because the gpioN directories in /sys/class/gpio are links to the gpioN directories in /sys/devices/virtual/gpio. For example, see directory gpio4 here:
pi@raspberrypi /sys/class/gpio $ echo 4 > export
pi@raspberrypi /sys/class/gpio $ ls -la
total 0
drwxrwx--- 2 root gpio 0 Feb 7 20:11 .
drwxr-xr-x 38 root root 0 Feb 7 19:28 ..
-rwxrwx--- 1 root gpio 4096 Feb 7 20:11 export
lrwxrwxrwx 1 root gpio 0 Feb 7 20:11 gpio4 -> ../../devices/virtual/gpio/gpio4
lrwxrwxrwx 1 root gpio 0 Jan 1 1970 gpiochip0 -> ../../devices/virtual/gpio/gpiochip0
-rwxrwx--- 1 root gpio 4096 Feb 7 19:40 unexport
pi@raspberrypi /sys/class/gpio $
I can't think of a sane reason to use /sys/devices/virtual/gpio in source code as /sys/class/gpio can always be used instead, if I'm not mistaken.
Note that this only functions when the device tree is disabled. When the device tree is enabled, /sys/devices/virtual/gpio disappears.
If the device tree is enabled, the udev rules on the Pi 2 need to use /sys/devices/soc/3f200000.gpio/gpio/ instead. The address 3f200000 may be different on the Pi 1, I'm not sure.
Note that /sys/devices/virtual/gpio is used in both /lib/udev/rules.d/60-python3-pifacecommon.rules and /lib/udev/rules.d/60-python-pifacecommon.rules in Raspbian. I've no idea how many users rely on this now.
@pelwell The new rule works when the interrupt module in pifacecommon points to /sys/class/gpio instead of /sys/devices/virtual/gpio. I'm going to patch this in and the updated package should go live asap.
@pelwell The new rule you provided above also works for me. I'm not using PiFace, but rely on the rule to enable user pi on Raspbian to use gpio without root privileges. Thanks :)
The udev rules modify the permissions asynchronously and your code runs at the same time, so your code may end up trying to access the files before the permissions are changed.
If that is the case, then how long should one wait after exporting before using the pin?
There isn't really a good answer to this question as it will be highly dependent on the current system load.
In onoff it's done like this. The code keeps attempting to set the direction of the GPIO until it succeeds. In theory it tries up to 10000 times. In practice it only has to try once or twice when the system load is "normal". After the direction has been set, onoff doesn't have any further special code for dealing with the issue.
Had the same issues. raspberrypi-sys-mods was not installed. Installing it, and confirming to overwrite /etc/udev/rules.d/99-com.rules if prompted, resolved the issue for me. Be sure to remove any existing GPIO exports, or simply reboot - or existing exports will still have the broken permissions.
In regards to @XECDesign's above question, this is what I had before (non-working):
This issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested.
Activity
fivdi commentedon Feb 7, 2015
I think this is happening because
/lib/udev/rules.d/60-python-pifacecommon.rulesand/lib/udev/rules.d/60-python3-pifacecommon.rulesno longer function as expected.For example, here's
/lib/udev/rules.d/60-python3-pifacecommon.rules:The directory
/sys/devices/virtual/gpiono longer exists, so the rule doesn't work.popcornmix commentedon Feb 7, 2015
Does disabling device-tree (add "device_tree=" to config.txt) work around the issue?
Ping @pelwell @asb
OliverHoermann commentedon Feb 7, 2015
I came round this issue when testing my PiFace Digital, where pifacecommon/interrupts.py threw an exception of not finding /sys/devices/virtual/gpio.
Setting device_tree=off in config.txt makes /sys/devices/virtual/gpio reappear.
After that, PiFace Digital works as expected again.
BR
Oliver
pelwell commentedon Feb 7, 2015
Can somebody explain how PiFace (my phone really wanted to write "pigface" there) uses these file nodes, and why it doesn't/can't use the nodes under /sys/class/gpio/ instead?
popcornmix commentedon Feb 7, 2015
I believe it's just used in /lib/udev/rules.d/60-python3-pifacecommon.rules (which we include in raspbian image)
pelwell commentedon Feb 7, 2015
I don't buy that. Why bother changing permissions on files or directories that you aren't otherwise going to use?
OliverHoermann commentedon Feb 7, 2015
Phil,
the /sys/..../gpio is used in pifacecommons/interrupts.py.
I tried changing above file. Pifacedigital-emulator started up afterwards,
but didn't read the input lines then. Only output settings worked.
Hope that helped,
Oliver
Am 07.02.2015 um 20:10 schrieb Phil Elwell notifications@github.com:
I don't buy that. Why bother changing permissions on files or directories
that you aren't otherwise going to use?
—
Reply to this email directly or view it on GitHub
#791 (comment).
fivdi commentedon Feb 7, 2015
In order for user pi to be able to access gpios without root permissions on a michine with the device tree disabled, udev rules are needed for both
/sys/class/gpioand/sys/devices/virtual/gpio. They are needed for/sys/devices/virtual/gpiobecause thegpioNdirectories in/sys/class/gpioare links to thegpioNdirectories in/sys/devices/virtual/gpio. For example, see directorygpio4here:I can't think of a sane reason to use
/sys/devices/virtual/gpioin source code as/sys/class/gpiocan always be used instead, if I'm not mistaken.Note that this only functions when the device tree is disabled. When the device tree is enabled,
/sys/devices/virtual/gpiodisappears.If the device tree is enabled, the udev rules on the Pi 2 need to use
/sys/devices/soc/3f200000.gpio/gpio/instead. The address3f200000may be different on the Pi 1, I'm not sure.Note that
/sys/devices/virtual/gpiois used in both/lib/udev/rules.d/60-python3-pifacecommon.rulesand/lib/udev/rules.d/60-python-pifacecommon.rulesin Raspbian. I've no idea how many users rely on this now.pelwell commentedon Feb 9, 2015
Can somebody try this modified version of
/lib/udev/rules.d/60-python-pifacecommon.rules(change either or both versions)?:It should work with and without DT, on Pi1 and Pi2.
tompreston commentedon Feb 9, 2015
Hi, I'm one of the Tom's at PiFace -- we're looking into this right now. :)
tompreston commentedon Feb 9, 2015
@pelwell The new rule works when the interrupt module in pifacecommon points to
/sys/class/gpioinstead of/sys/devices/virtual/gpio. I'm going to patch this in and the updated package should go live asap.pelwell commentedon Feb 9, 2015
That sounds like the right change - you can think of /sys/class/gpio as the generic interface, and /sys/devices/*/gpio as the specific implementation.
firmware: Move to 3.18 kernel with device tree enabled
fivdi commentedon Feb 14, 2015
@pelwell The new rule you provided above also works for me. I'm not using PiFace, but rely on the rule to enable user pi on Raspbian to use gpio without root privileges. Thanks :)
alexanderhaensch commentedon Feb 15, 2015
in /boot/config.txt
device_tree=
is the only solution for me. i am using lric_rpi and some gpios. even lirc_rpi dt_overlay is not working correctly... :(
16 remaining items
fivdi commentedon Apr 1, 2017
The udev rules modify the permissions asynchronously and your code runs at the same time, so your code may end up trying to access the files before the permissions are changed.
There isn't really a good answer to this question as it will be highly dependent on the current system load.
In onoff it's done like this. The code keeps attempting to set the direction of the GPIO until it succeeds. In theory it tries up to 10000 times. In practice it only has to try once or twice when the system load is "normal". After the direction has been set, onoff doesn't have any further special code for dealing with the issue.
deadprogram commentedon Apr 1, 2017
Thank you for the tip @fivdi and the link.
I've implemented that solution now, and works great.
trgtylcnky commentedon Apr 3, 2017
Sorry for late reply. I was away from my pi.
pelwell commentedon Apr 3, 2017
The udev rule uses $devpath to locate the device nodes, and it is looking like that mechanism isn't working in your case. Can you try these tests?:
trgtylcnky commentedon Apr 4, 2017
pelwell commentedon Apr 5, 2017
That all looks OK. What do you have in /etc/udev/rules.d/99-com.rules? You can omit the spi/i2c/tty rules.
trgtylcnky commentedon Apr 10, 2017
pelwell commentedon Apr 10, 2017
That rule for "gpio*" doesn't match the current Raspbian version - try using this instead (replacing
/devices/platform/soc/*.gpio/gpiowith$devpath):@XECDesign - @trgtylcnky says he is running OctoPi Raspbian. Does this look like an old Raspbian rules file, or is it some other concoction?
XECDesign commentedon Apr 10, 2017
It looks like it's an older version of the file:
https://github.com/RPi-Distro/raspberrypi-sys-mods/blob/c2f4795c7214a2c87589391acbae73d31e8099a3/etc/udev/rules.d/99-com.rules
What is the md5sum of the file? Is raspberrypi-sys-mods installed? If so, what version?
ziesemer commentedon May 12, 2017
See also: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=183481
Had the same issues.
raspberrypi-sys-modswas not installed. Installing it, and confirming to overwrite/etc/udev/rules.d/99-com.rulesif prompted, resolved the issue for me. Be sure to remove any existing GPIO exports, or simply reboot - or existing exports will still have the broken permissions.In regards to @XECDesign's above question, this is what I had before (non-working):
... and after (working):
Regarding OctoPi: I am not using OctoPi, but vitormhenrique/OctoPrint-Enclosure#16 also looks to be the same.
JamesH65 commentedon Jun 27, 2018
This issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested.
JamesH65 commentedon Aug 31, 2018
Closing due to lack of activity. Please request to be reopened if you feel this issue is still relevant.
Merge pull request raspberrypi#791 from wedsonaf/async-revocable