Le 20/09/2018 à 13:02, Pablo Sebastián Greco a écrit : > > Stephan, sorry for the delay > No problemo. Clearly, it's not an emergency. Thx for your reply. > El 10/9/18 a las 12:28, Stephan Guilloux escribió: >> Hello, >> >> Small issues, today, with dtoverlay gpio-shutdown/poweroff >> >> [root at mypi ~]# dtoverlay gpio-shutdown >> su: user pi does not exist >> * Failed to apply overlay '1_gpio-shutdown' (kernel) >> su: user pi does not exist >> [root at mypi ~]# dtoverlay gpio-poweroff >> su: user pi does not exist >> su: user pi does not exist >> [root at mypi ~]# > That seems to come from here > (https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/dtoverlay/dtoverlay-pre). > If you run as root, it tries to run as the user "pi", as a normal > user(any), you shouldn't have that problem well ... not so sure :-) [stephan at myrpi ~]$ dtoverlay gpio-poweroff * Must be run as root - try 'sudo dtoverlay ...' [stephan at myrpi ~]$ sudo dtoverlay gpio-poweroff [sudo] password for stephan: su: user pi does not exist su: user pi does not exist [stephan at myrpi ~]$ dtoverlay -l Overlays (in load order): 0: gpio-poweroff [stephan at myrpi ~]$ Then, I don't understand why it needs to be run with SUDO from any user to gain ROOT access ? [root at myrpi ~]# dtoverlay gpio-shutdown su: user pi does not exist su: user pi does not exist [root at CrisalidBox-C9A58C ~]# dtoverlay -l Overlays (in load order): 0: gpio-poweroff 1: gpio-shutdown [root at myrpi ~]# Just funny :-) >> >> Even if I add a fake user "PI", this does not work better. >> >> [root at mypi ~]# useradd -r pi -p pi >> [root at mypi ~]# >> [root at mypi ~]# >> [root at mypi ~]# dtoverlay gpio-poweroff >> * Failed to apply overlay '2_gpio-poweroff' (kernel) >> [root at mypi ~]# dtoverlay gpio-shutdown >> * Failed to apply overlay '2_gpio-shutdown' (kernel) >> [root at mypi ~]# > That bit seems to come from here > (https://github.com/raspberrypi/userland/blob/2448644657e5fbfd82299416d218396ee1115ece/host_applications/linux/apps/dtoverlay/dtoverlay_main.c#L982), > it fails to check if the overlay was actually applied >> >> But when I check the overlay list, I get: >> >> [root at mypi ~]# dtoverlay -l >> Overlays (in load order): >> 0: gpio-shutdown >> 1: gpio-poweroff >> [root at mypi ~]# >> >> At least, something is done :-) >> > That is a little stranger, why does it say it did something when the > command before said it failed??? >> Last problems: >> [root at mypi ~]# dtoverlay -h gpio-shutdown >> * Help file not found >> [root at mypi ~]# dtoverlay -h gpio-poweroff >> * Help file not found >> [root at mypi ~]# dtoverlay -h rpi-rtc >> * Help file not found >> [root at mypi ~]# dtoverlay -h rpi-display >> * Help file not found >> [root at mypi ~]# >> >> >> > I guess I'll have to add some debugging info and check in my rpi (as > time permits) >> In case ... >> [root at mypi ~]# cat /proc/version >> Linux version 4.14.65-v7.1.el7 >> (mockbuild at armhfp-03.bsys.centos.org) (gcc version 4.8.5 20150623 >> (Red Hat 4.8.5-28) (GCC)) #1 SMP Mon Aug 20 19:04:20 UTC 2018 >> [root at mypi ~]# >> >> [root at mypi ~]# rpm -qa 'raspberrypi-vc*' >> raspberrypi-vc-demo-source-20170705-502.gitaa39775.el7.noarch >> raspberrypi-vc-libs-20170705-502.gitaa39775.el7.armv7hl >> raspberrypi-vc-utils-20170705-502.gitaa39775.el7.armv7hl >> [root at mypi ~]# >> > 2 questions > 1) has it ever worked before? Well... never tried before. I was just comparing the result between CentOS and R at spbi@n... > 2) which rpi exactly are you using? (don't know if it is really relevant). Standard RPI 3b. > > Thanks. > Pablo. >> >> Stephan. >> > P.S.: Today we built 4.14.71 and will be released as soon as it passes > the tests. Great ! What's new for RPI, I mean compared to 68, 69 and 70 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20180920/b4768e97/attachment-0006.html>