Problem with root and problem with the grabber

[LeSenegal]

Hello,
I had hyperhdr installed in version 20.0.0.0, but I changed my internet box, so I reinstalled it, but this time I can't get it to work. I tested pi os in 32 bits, 64 bits, reinstalling hyperhdr several times. I've also tried using the hyperhdr image, but it doesn't work. I can access to the dashboard but led didn't work.
In the log that's said :
[LEDDEVICE0_WS281X] Device 'ws281x' is disabled due to an error: 'Failed to open. Error message: mmap() failed. YOUR NEED TO RUN HYPERHDR AS A ROOT USER FOR MMAP TO WORK. SUCH CONFIGURATION IS NOT OFFICIALLY SUPPORTED.'

I already tested with :
sudo systemctl stop [email protected]
sudo systemctl disable hyperhdr@pi
sudo systemctl enable hyperhdr@root

And I now have a problem with my grabber that inverse the colors I think :
Image captured by the grabber :

Real image :

My configuration actually :

• Raspberry Pi 3 Model B Plus Rev 1.3
• led WS2812B
• Navy U3 grabber
• HyperHDR 20.0.0.0
• And the OS :
  

Thank you for your help

[awawa-dev]

Hi
You may be using a different user than pi, which only exists in our images, because the official flasher and images have removed it and you can use a non-standard username (then you need to adapt the command for systemctl, you need to stop the service for the user it is currently installed and running on ). BTW sudo systemctl enable hyperhdr@root doesnt start the service and the restart is required. As for inverted colors it's a kernel bug: #797

[LeSenegal]

Thank you I try for the led problem, that works fine, and for the grabber problem where can I find an older image of RaspiOS ?
Or should I get the Raspberry Pi OS version Legacy ?

[awawa-dev]

I think HyperHDR OS images have an older kernel version because they are based on Debian Bullseye and not the latest Bookworm. Or you can also manually downgrade the Bookworm kernel using the standard Debian procedure.

[LeSenegal]

Effectively, the HyperHDR OS image is on kernel 6.1.21, all works, thanks for your time. Love your work

[awawa-dev]

You did not read or understand the instructions provided or the related discussion on the picamera2 forum that explained what this command does: provide a pre-production beta kernel that is not available anywhere else. May contain other bugs, but the released "stable" kernel also contains a critical colors-affecting bug. And according to picamera2 this beta kernel solved a similar problem.

Since this is a kernel bug and not a problem of our application, I think we have covered the topic with available solutions, the rest is up to the user to share his experience and provide feedback to others. Or if you want the simplest solution, you should probably wait a while for the Raspberry Pi kernel channel until the kernel release, which is currently in beta testing.

[drharis]

Hi,
You are right, I did not understand exactly the instruction on that webpage. Thanks for clarifying. Now, I that I have some more time to play around with it, I can say that it is working fine now. I tried the sudo update command and the kernel did get updated but the problem persisted. So, I removed the card and re-flashed with legacy Bullseye version on pi OS and reinstalled HyperHDR. It all worked fine! Thanks for your help. If it was not for that I would have been spending many more hours and pulling whatever hair left in my head! Thanks again

[awawa-dev]

It's great that you managed to solve the problem. I just have a question because I want to make sure which command you used before and which one didn't help, because it will also be information for others.
sudo update (there is no such command I think) or sudo apt update or sudo apt upgrade or sudo rpi-update
Did you restart Rpi after that?

[drharis]

I tried sudo rpi-update as per the pi camera website link you provided

[awawa-dev]

Ok, thanks. So the source of the RPi kernel/firmware problem is still unknown and unfortunately we don't know if someone is working on it or is aware of it. I guess it's limited to RPi only, we havent received similar reports from x86_x64 systems yet.