Closed svenrademakers closed 3 months ago
@dgdonovan Thanks for testing! could you elaborate what "aborting" problems you see?
i agree there are still a lot of loose ends in the UI. Would be really nice to get them out of the way at some point
I'll get the precise output from bmcd. It was complaining about not being able to find a file. I was about to start looking at doing a standalone bmcd build with debug to isolate the issue.
@dgdonovan, just so you are aware, I fixed an issue recently that affected the bmcd.bin being cleared. see: #191
Yes. I saw that commit and can confirm the issue was fixed by it. I don't believe that bug was the cause of bmcd failing to start. The three errors emitted there mentioned gpiod, pin controller and file not found.
The precise error sequence was:
# /etc/init.d/S94bmcd start Starting bmcd... # 2024-03-23T03:04:32.224Z INFO [bmcd] Turing Pi 2 BMC Daemon v2.0.5 Error: pin_controller
Caused by: 0: gpiod chip1 1: No such file or directory (os error 2)
There has been a lot of commit churn. At this point I'm not certain I can find the precise commit hash, but the current builds seem to be working so maybe not worth the time and effort. I'd rather spend time deciphering the UI code.
Looks good so far. With this commit (and the previous v2.0.5-35-related commits), I am able to apply my minor customizations and build the firmware without the issue of bmcd aborting on startup (pin controller). I have a few nits with the web UI, but those can wait a bit.