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
Device disabled, device 'ws281x' signals error #1280
Comments
The error 'Failed to open. Error message: mmap() failed' means that Hyperion is missing the access rights to write to the ws281x. Only for this type of LED, you need to run under root. |
As I stated in my description, I tried what is required by reading forums. |
I think that the Alpha 9 release of Hyperbian was already setup to run as root. |
can you start hyperiond and show me the output from "top | grep hyperiond" |
|
|
You are right! But I don't remember having to do this on alpha 9 though. Thanks |
Sorry for a noob question. When you said that you fixed the issue by re-flashing the image, does it mean you re-flashed it with the same version of hyperbian from https://docs.hyperion-project.org/en/user/HyperBian.html 2.0.0-alpha.10? |
Yes that's what I did. |
Bug report
ws281x won't work on fresh install Hyperbian alpha 10. Was working fine on alpha 9.
Steps to reproduce
-Start a fresh image of Hyperbian.
-Choose ws281x
What is expected?
What is actually happening?
-LEDs won't turn on
[hyperiond LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed'
appears on the log.What I tried:
sudo systemctl disable --now hyperion@pi
without dsudo systemctl enable --now hyperion@root
without dafter doing these LEDs still won't work but also USB capture disappeared.
System
Hyperion Server:
Hyperion Server OS:
The text was updated successfully, but these errors were encountered: