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

energenie-controller can't access GPIO since upgrading to bookworm #479

Closed
TWilkin opened this issue Feb 6, 2024 · 0 comments · Fixed by #482
Closed

energenie-controller can't access GPIO since upgrading to bookworm #479

TWilkin opened this issue Feb 6, 2024 · 0 comments · Fixed by #482
Assignees
Labels
bug Something isn't working energenie-controller Relating to the energenie controller service kubernetes Relating to the Kubernetes deployment

Comments

@TWilkin
Copy link
Owner

TWilkin commented Feb 6, 2024

When starting the energenie-controller reports that is isn't running on a Pi, which is usually caused by it not being able to access /dev/gpiomem. The device manager seems to be working as the device is mounted.

The following has changed since it was working:

  • Upgraded the nodes in my cluster to the latest Raspbian image based on bookworm.
  • Rebuilt the cluster from scratch.
@TWilkin TWilkin added bug Something isn't working energenie-controller Relating to the energenie controller service labels Feb 6, 2024
@TWilkin TWilkin self-assigned this Feb 6, 2024
@TWilkin TWilkin added the kubernetes Relating to the Kubernetes deployment label Feb 6, 2024
TWilkin added a commit that referenced this issue Feb 11, 2024
#479 fix: energenie-controller GPIO in Bookworm hosts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working energenie-controller Relating to the energenie controller service kubernetes Relating to the Kubernetes deployment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant