On Sun, 2020-03-01 at 16:37 +0100, Thorsten Glaser wrote: > retitle 929841 systemd-udevd: regulatory.0: Process '/sbin/crda' failed with > exit code 255. > thanks > > Could this have to do with /lib/udev/rules.d/85-regulatory.rules ? > > A quick search through the code shows it returns “-1” (i.e. 255) in > multiple places (the main function is written like kernel code, not > userspace…), and is called from two files in /lib/udev/rules.d/, one > indirectly via iw reg set (which we already established works for me) > and once directly via the aforementioned file. > > That file contains this comment… > > # For more information see: > # http://wireless.kernel.org/en/developers/Regulatory/CRDA > > … but that URL is dead, but the Internet Archive has it under: > http://web.archive.org/web/20190825055504/https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA > > Interestingly enough, the 85-regulatory.rules does not set $COUNTRY, > and calling crda without it set does result in exitting with -1.
The kernel sets COUNTRY in the uevent, which is copied into the device
properties. Then udev copies the device properties into the
environment when running an external program.
Ben.
> Unfortunately, none of the printfs found in crda make it into syslog.
>
> Retitling the bug so the actual issue, not a red herring, is used as title.
>
> bye,
> //mirabilos
--
Ben Hutchings
It is a miracle that curiosity survives formal education.
- Albert Einstein
signature.asc
Description: This is a digitally signed message part
