Hello,
We are finding that the x735 software discussion page on the geekworm wiki is presenting an inappropriate approach to handling powering on the fan in an imbedded system type of application.
There is commentary in the thread for the post which indicates an approach that is more reasonable using a systemd unit file, but the example given can result in the console being completely disabled for the raspberry pi once implemented, requiring booting from an alternative sd card or drive to recover from.
The wiki seems to no longer allow for commenting, which is unfortunate. We would like to submit improved instruction to remove/not use the Conflicts=getty@tty1.service in the unit file.
Adding this to the unit file means the console will be disabled as the service is enabled. This means the system will have no console enabled anymore. To recover, you might need to boot into rescue or recovery/emergency mode and re-enable the console.
The approach we are testing with is to completely disable the .bashrc approach (as no one is logging into an embedded system pi) to allow the fan to start up properly on power on/boot. We are disassembling the setup script and re-writing to be properly configured for headless systems, and ran into this problem with the systemd unit file proposed in the discussion present in the wiki.
Also, it would probably be a good idea to point the wiki pages to this forum for discussions in general.
