08-09-2024, 01:04 AM
Seems to pass all the suggested checks.
Oddly, /opt/RoonBridge and all its subdirectories and contents have ownership 1001:116 rather than the root:root (e.g., 0:0) I was expecting.
Just for grins I started from scratch with yet another fresh moOde 9.0.6 on the Pi Zero 2W.
This time the RoonBridge renderer started upon reboot and the RoonBridge section on the moOde Renderer Config panel is alive. Ownership of the relevant material is again 1001:116 and I left it that way.
No idea what went wrong the first time. Before giving up on it I did try changing ownership of the relevant material to root:root. After cold starting moOde, the RoonBridge Renderer started. I can't point to the step that "fixed" the original failure which is why I started over from scratch.
Regards,
Kent
Oddly, /opt/RoonBridge and all its subdirectories and contents have ownership 1001:116 rather than the root:root (e.g., 0:0) I was expecting.
Just for grins I started from scratch with yet another fresh moOde 9.0.6 on the Pi Zero 2W.
This time the RoonBridge renderer started upon reboot and the RoonBridge section on the moOde Renderer Config panel is alive. Ownership of the relevant material is again 1001:116 and I left it that way.
No idea what went wrong the first time. Before giving up on it I did try changing ownership of the relevant material to root:root. After cold starting moOde, the RoonBridge Renderer started. I can't point to the step that "fixed" the original failure which is why I started over from scratch.
Regards,
Kent
