Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privilege problem of device files on de10-nano board #184

Closed
2 tasks done
marktwtn opened this issue Aug 27, 2019 · 2 comments
Closed
2 tasks done

Privilege problem of device files on de10-nano board #184

marktwtn opened this issue Aug 27, 2019 · 2 comments
Assignees

Comments

@marktwtn
Copy link
Collaborator

marktwtn commented Aug 27, 2019

Executing the PoW on de10-nano board needs to open or do the operation to the following device files

  • /dev/cpow-ctrl
  • /dev/cpow-idata
  • /dev/cpow-odata
  • /dev/mem

The first three device files appears after installing the specific kernel module.
The last device file is physical memory.

Since the previous arm image from LampaLab uses root as logging account, everything went well.
However, when it comes to the new armhf image, the image uses normal user logging account.
Hence it has some problems since the operation to /dev/mem is only allowed when using root account or using sudo command.
Even if I changed the file privilege, it did not help.

Goal:

  • buildkite CI can build dcurl and execute PoW with FPGA
  • Ansible Playbook can activate the remote worker of multiple de10-nano boards easily
@marktwtn marktwtn self-assigned this Aug 27, 2019
@marktwtn
Copy link
Collaborator Author

marktwtn commented Aug 29, 2019

We can set the user account of the buildkite agent as root.
Since the buildkite agent is managed with systemd, the user account can be changed by modifying the service user configuration /lib/systemd/system/buildkite-agent.service.

@marktwtn
Copy link
Collaborator Author

marktwtn commented Sep 9, 2019

Since Ansible Playbook also uses systemd to manage the remote worker, it would not be a problem to set it as root account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant