latency-histogram -->> cannot gain I/O privileges - forgot 'sudo make setuid'

latency-histogram --nobase --sbinsize 1000 --show
cannot gain I/O privileges - forgot 'sudo make setuid' or using secure boot? -parallel port access is not allow
Note: Using POSIX realtime

I've noticed the above message of late..... anyone give any advice?

I don't seem to have anything wrong with the latency ~48uS & Std Dev 1.5uS
clean debian bullseye iso install (without su password entered)
git clone linuxcnc + local build of debs (master 2.9 today)
install of debs on build machine using
sudo dpkg -i <package>.deb

I've done a "bit" of a search and read of previous posts.... not seen a "fix" just suggestions that the user may not have sudo privilages....

cdimage.debian.org/cdimage/unofficial/no...onfree/amd64/iso-cd/

not the edu one but the other one.

installed the RT kernel (amd64) and then built the linuxcnc debs locally and installed the debs

Well, did you forget 'sudo make setuid' after the build?

I'm not sure how a local dpkg install works, but if you build linuxcnc manually and either run in place or install using 'make install' you do need to run 'sudo make setuid' after the build to give the executables the proper privileges.

That is the bit I am not sure about, as it is not a RIP, it is basically installing the deb files onto the machine.

Yes they are made locally, but it is exactly the same as downloading from the buildbot respository and installing the debs from their ..... I would have thought (yup that's the failing! thinking!) that the deb would setuid for RT process access.

There is nothing in the "building debs" section relating to setuid
linuxcnc.org/docs/devel/html/code/buildi...ding_debian_packages

buildbot.linuxcnc.org/dists/buster/maste...reempt/binary-amd64/

I can't see where to do a "sudo make setuid" when installing debs

sure know how and when to do it with a RIP

I guess the fix is to just set linuxcnc + latency-histogram files via chmod u+s

www.computerhope.com/jargon/s/setuid.htm...calated%20privileges.

(again thought that installing a deb should do this automatically, instead of having the trawl various folders to set chmod on various files?)

No, just standard sudo.

only 1 user set up on the machine (did not set up su / root, and just entered 1 user + password at time of install).

install was via
sudo dpkg -i <linuxcnc_deb_package>.deb

github.com/LinuxCNC/linuxcnc/issues/1272

github.com/LinuxCNC/linuxcnc/commit/37c107c47f588

The incorporated commit removed the error return code
(EPERM) so the message is just for information
regarding use of parallel port (with secure boot)