Arch Linux User Repository

@peterpan4 Thanks for the hint, but I think it is preferable to let users enable the network socket explicitly if they need it.

@SpotlightKid

Many might prefer the -l option so as to disable remote access and only allow local access to the socket.

[Service]
ExecStart=/usr/bin/pigpiod -l

@crodjer: thanks for the headsup! Upstream changed the service type from "simple" to "forking", which made this change necessary.

Attention: pigpiod is now also run with the -k (disable socket interface) by default for security reasons. To enable it, run systemctl edit pigpiod and put the following in /etc/systemd/system/pigpiod.service.d/override.conf (your default editor will automatically open this file for editing):

[Service]
ExecStart=/usr/bin/pigpiod

This overrides the command to start pigpiod and removes the -k option.

Please remove the line:

 sed -e 's|/usr/bin/pigpiod|/usr/bin/pigpiod -g|' -i util/pigpiod.service

This is causing the service to be stuck. pigpiod loads as a daemon by default. Adding -g foregrounds it.

@Vlou: Please report this upstream: https://github.com/joan2937/pigpio/issues

I just installed this package on my Raspberry Pi 3B+ running the AArch64 kernel, and the pigpiod daemon won't launch (segmentation fault) :

Aug 10 17:41:31 rpi1 systemd[1]: Started Process Core Dump (PID 1118/UID 0). Aug 10 17:41:31 rpi1 systemd-coredump[1119]: [LNK] Process 1117 (pigpiod) of user 1001 dumped core.

                                         Stack trace of thread 1117:
                                         #0  0x0000ffff93a3b338 _IO_fclose@@GLIBC_2.17 (libc.so.6 + 0x65338)
                                         #1  0x0000ffff93b94700 n/a (libpigpio.so.1 + 0x9700)
                                         #2  0x0000ffff93bbfd7c gpioHardwareRevision (libpigpio.so.1 + 0x34d7c)
                                         #3  0x0000ffff93bc05ac initInitialise (libpigpio.so.1 + 0x355ac)
                                         #4  0x0000ffff93bc3560 gpioInitialise (libpigpio.so.1 + 0x38560)
                                         #5  0x0000aaaada2c4574 n/a (pigpiod + 0x1574)
                                         #6  0x0000ffff939f9d90 __libc_start_main (libc.so.6 + 0x23d90)
                                         #7  0x0000aaaada2c48a8 n/a (pigpiod + 0x18a8)
                                         #8  0x0000aaaada2c48a8 n/a (pigpiod + 0x18a8)

Details about my installation of archlinux arm : Linux rpi1 5.8.0-1-ARCH #1 SMP Sun Aug 9 00:03:44 UTC 2020 aarch64 GNU/Linux

Did anyone face this issue ?

EDIT : By compiling with the aarch64user branch, this problem is gone. But there is another, which is described here : https://github.com/joan2937/pigpio/issues/259 But the kernel parameters don't fix the issue for me...

EDIT 2 : Using the raspberry kernel instead of the mainline one ( https://aur.archlinux.org/packages/linux-aarch64-raspberrypi-bin/ ),pigpiod works without problems with this package !

Could you please add 'armv7h' to the architecture?

@codeworkx: Done.

Please add 'aarch64' architecture for Raspberry Pi 3+ running with AArch64 kernel.

@haphi: Fixed. Can you report this upstream? https://github.com/joan2937/pigpio/issues