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

More
26 May 2022 12:29 - 26 May 2022 12:30 #243889 by robertspark
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....

chips@LinuxCNC:~$ groups
chips cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner
chips@LinuxCNC:~$


open to suggestions, thanks as always to anyone for pointers / suggestions
Last edit: 26 May 2022 12:30 by robertspark.

Please Log in or Create an account to join the conversation.

More
30 May 2022 00:32 #244165 by andypugh
Where did you get a Bullseye ISO from?

Please Log in or Create an account to join the conversation.

More
30 May 2022 06:00 #244184 by robertspark
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

Please Log in or Create an account to join the conversation.

More
30 May 2022 10:31 #244195 by arvidb
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.

Please Log in or Create an account to join the conversation.

More
30 May 2022 13:34 #244209 by robertspark
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

Please Log in or Create an account to join the conversation.

More
30 May 2022 13:39 #244210 by robertspark
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?)

Please Log in or Create an account to join the conversation.

More
30 May 2022 14:26 #244216 by tommylight
Did you use ROOT at any point in the process?
Or sudo su?
Or sudo -i?
Although the last one should be OK.

Please Log in or Create an account to join the conversation.

More
30 May 2022 14:45 #244220 by robertspark
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

Please Log in or Create an account to join the conversation.

More
30 May 2022 15:35 #244223 by dgarrett
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)

Please Log in or Create an account to join the conversation.

More
30 May 2022 17:13 #244229 by tommylight
sudo apt install gdebi
then you can click on any .deb package from the file manager and it will install.
Avoid using dpkg as it can break things.

Please Log in or Create an account to join the conversation.

Time to create page: 0.079 seconds
Powered by Kunena Forum