Failed to load EDID with HDMI to USB capture device

[db39]

Description

After installing TinyPilot community, load-tc358743-edid.service runs and fails to load an EDID when using an HDMI to USB capture device.

When running with an HDMI to USB capture device, TinyPilot doesn't need to load an EDID, since TinyPilot only requires an EDID for TC358743 capture devices.

These errors can be confusing when troubleshooting display issues on a community install: Example 1, example 2

What's the behavior that you expect?

I would expect the load-tc358743-edid.service to be disabled with a standard install. It should only become enabled if the user runs additional configuration steps for a TC358743 HDMI to CSI capture chip.

What's happening instead?

The load-tc358743-edid.service starts and fails.

What are the steps to reproduce this behavior?

1. Install TinyPilot following the simple instructions in the README.
2. Run sudo service load-tc358743-edid status.
3. See the error.

● load-tc358743-edid.service - Load EDID for TC358743 HDMI capture chip.
     Loaded: loaded (/lib/systemd/system/load-tc358743-edid.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-01-24 12:16:30 GMT; 12min ago
    Process: 1161 ExecStart=v4l2-ctl --set-edid=file=/home/ustreamer/edids/tc358743-edid.hex --fix-edid-checksums (code=exited, status=1/FAILURE)
   Main PID: 1161 (code=exited, status=1/FAILURE)
        CPU: 16ms

Jan 24 12:16:30 raspberrypi systemd[1]: load-tc358743-edid.service: Scheduled restart job, restart counter is at 20.
Jan 24 12:16:30 raspberrypi systemd[1]: Stopped Load EDID for TC358743 HDMI capture chip..
Jan 24 12:16:30 raspberrypi systemd[1]: load-tc358743-edid.service: Start request repeated too quickly.
Jan 24 12:16:30 raspberrypi systemd[1]: load-tc358743-edid.service: Failed with result 'exit-code'.
Jan 24 12:16:30 raspberrypi systemd[1]: Failed to start Load EDID for TC358743 HDMI capture chip..