- @david
I decided to use the Raspberry Imager instead of the stock Tinypilot image on my Voyager2a… I have a few Pi’s in different places on a Cloudflared tunnel network, and I want them to be similar with VNC and cloudflared. I loaded Bullseye 32 bit and installed Tinypilot via GitHub. All works except I get No Signal for my Macmini target. Logs show “ Can't access device: No such file or directory.” I assume by not using a stock image the hdmi port is output only. Is this correct? If so is there a way for it to be input via configuration, and will that affect VNC?
David @david2024-10-07 11:40:29.188ZHi @vince, I'm sorry you're running into this "No Signal" issue.
Thanks for all those details! It sounds like you may need to run the additional configuration steps to allow your TinyPilot Voyager 2a to capture the video signal using its integrated HDMI capture chip. By default, the community version of TinyPilot assumes you're using a self-built device with an HDMI to USB capture device, so that could explain why you're now seeing the "No Signal" image.
I should note that TinyPilot community lacks a few of Pro's features (like Virtual Media and TLS), so you may want to use TinyPilot Pro instead - TinyPilot Pro uses the same Bullseye 32-Bit base operating system, so you can install and set up third-party software if you like (unless I'm missing some specific details for why you're using the default Pi image here).
I hope that helps! Please let me know if you have any questions.
Ok. I might just reload pro then… probably for the virtual media. My encryption is handled by the tunnel network so I’m not too worried about TLS. Thanks for the info!
David @david2024-10-08 11:02:53.688ZYou're welcome! Feel free to reach out again if you have any questions.
- Progresswith handling this problem