Updating to 2.6.2 Results in "NO SIGNAL"

Hi there!

I ordered one of the original TinyPilot Hobbyist kits back in 2021. Up until today, it had been working perfectly, however, today I upgraded to 2.6.2 and while it came back up, I have been unable to get video to work since it came up.

I found a similar issue where the solution was to change HDMI cables, but that didn't work for me.

Additionally, I have tried changing the video output resolution using a VNC application. I have tried multiple different resolutions, but none of them seemed to work for me. I eventually settled on 1280x720 at 60 Hz following the advice of the support article and the No Signal FAQ.

I have also tried changing from MJPEG to H.264 with various settings (including setting it to use a STUN server) to see if that would change anything, but that didn't make any changes either.

When I look at the logs I see:

Jan 09 20:00:21 tinypilot launch[3272]: -- INFO  [10035.123    stream] -- Device fd=11 opened
Jan 09 20:00:21 tinypilot launch[3272]: -- INFO  [10035.123    stream] -- Using input channel: 0
Jan 09 20:00:21 tinypilot launch[3272]: -- ERROR [10035.123    stream] -- Can't subscribe to DV-timings events: Invalid argument
Jan 09 20:00:21 tinypilot launch[3272]: -- INFO  [10035.123    stream] -- Device fd=11 closed
Jan 09 20:00:21 tinypilot launch[3272]: -- INFO  [10035.123    stream] -- Sleeping 1 seconds before new stream init ...

In playing around with it a little bit, I tried editing the /opt/ustreamer-launcher/configs.d/000-defaults.yml file and changing ustreamer_use_dv_timings: true to ustreamer_use_dv_timings: false, but that just changed the error above to the following error in the ustreamer logs:

Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.283    stream] -- Device fd=10 opened
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.283    stream] -- Using input channel: 0
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.284    stream] -- Using resolution: 1280x720
Jan 09 18:59:18 tinypilot launch[3070]: -- ERROR [6372.285    stream] -- Could not obtain the requested format=JPEG; driver gave us MJPEG
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.285    stream] -- Falling back to format=MJPEG
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.285    stream] -- Using format: MJPEG
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.286    stream] -- Using HW FPS: 15 -> 20 (coerced)
Jan 09 18:59:18 tinypilot launch[3070]: -- ERROR [6372.286    stream] -- Device doesn't support setting of HW encoding quality parameters
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.286    stream] -- Using IO method: MMAP
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.292    stream] -- Requested 5 device buffers, got 5
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.294    stream] -- Capturing started
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.294    stream] -- Switching to HW encoder: the input is (M)JPEG ...
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.294    stream] -- Using JPEG quality: encoder default
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.294    stream] -- Creating pool JPEG with 1 workers ...
Jan 09 18:59:18 tinypilot launch[3070]: -- INFO  [6372.295    stream] -- Capturing ...
Jan 09 18:59:19 tinypilot launch[3070]: -- INFO  [6372.698    stream] -- H264: Configuring encoder: DMA=0 ...

This cleared up the No Signal problem, but just left a blank black box in it's stead. After seeing this, I reverted my manual change of the file, and went back to the No Signal issue because I think it represents a better baseline to begin troubleshooting from.

Any help that you can give would be appreciated.

The HTTP portions of the log file seemed to include more information that I was comfortable with, so I have included an abbreviated log here: https://pastebin.com/1UTY99yL