Disable the new GL driver on Pi 4, now see error on boot?

[dachshund-digital]

Disable the new GL driver on Pi 4, now see error on boot?

`# systemctl status gldriver-test
● gldriver-test.service - Check for v3d driver
Loaded: loaded (/lib/systemd/system/gldriver-test.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-05-25 00:33:41 UTC; 6min ago
Main PID: 416 (code=exited, status=1/FAILURE)

May 25 00:33:41 localhost systemd[1]: Starting Check for v3d driver...
May 25 00:33:41 localhost gldriver_test.sh[416]: /usr/lib/systemd/scripts/gldriver_test.sh: line 12: /usr/share/X11/xorg.conf.d/99-fbturbo.conf: No such file or directory
May 25 00:33:41 localhost systemd[1]: gldriver-test.service: Main process exited, code=exited, status=1/FAILURE
May 25 00:33:41 localhost systemd[1]: gldriver-test.service: Failed with result 'exit-code'.
May 25 00:33:41 localhost systemd[1]: Failed to start Check for v3d driver.
`

Raspberry Pi OS lite installed on Pi4. The GL driver is applicable only to X11 environment right? This error should not be occurring thus?

[XECDesign]

@spl237 The [Unit] section of gldriver-test's gldriver-test.service should probably have ConditionPathIsDirectory=/usr/share/X11/xorg.conf.d?

[dachshund-digital]

I will check,.. Nope, or I should say, yeah, maybe that is the fix, the unit file is pretty basic...

`[Unit]
Description=Check for v3d driver

[Service]
Type=oneshot
ExecStart=/usr/lib/systemd/scripts/gldriver_test.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
`

Since I am running lite, none of the is applicable per se. Seems lite something that was missed when the lite image was established. For now I disabled the service to avoid the error, which as far as I can see, just informational if you are not using the GL driver in the first place.

Unit script, executing it directly, it fails with...

'/usr/lib/systemd/scripts/gldriver_test.sh: line 12: /usr/share/X11/xorg.conf.d/99-fbturbo.conf: No such file or directory'

For Pi OS lite image.