Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
…Is is possible to install klipper on a non-systemd operating system, and is there a listing of browsers that run with Fluidd?
Thank you for the information: I was trying to install klipper on a 32 bit laptop using a non-systemd OS, and the kaiuh install failed due to the lack of systemd directories. If klipper doesn’t actually rely on systemd services, then by creating the missing directory, the install should be successful. I shall try that. Note that I do use a 2B Rpi as an alternative configuration, but all of the 32 bit light browsers I tried to use to link too Fluidd failed due to the lack of javascripting or produced only blank screens.
One further question: why the prohibition of doing the kaiuh install as a root user? I have used various 32 bit Puppy Linux versions, and have never found a successful means of using the non-root “Spot” user account to do so. I also found that unlike the common claim that klipper will run on essentially all Linux systems, I have encountered several that that is not the case.
Using klipper over the OEM Marlin firmware is suffieciently rewarding that I am willing to expend the effort to try to find a way to use it on some of my out-dated equipment that would fit the role if I can avoid the issues they create.
At a minimum, using kiauh, the klipper installation requires the presence of the “/etc/systemd/system” directory or it fails to complete the process on my non-systemd OS. This is made evident when you then try to install moonraker and it responds that klipper is not installed. Creating that directory allows klipper to be installed, and that allows moonraker and fluidd to complete the process, but so far, this system fails to connect to moonraker, for reasons I have not yet discovered. This occurred for me on a Debian based 32 bit OS without systemd capability (antiX 32 bit).
KIAUH is not needed; you can install all products manually and thus influence the process, e.g., by installing rc.d/init.d versions.
Running services under root permissions should be avoided at all costs due to significant security concerns. There is simply no need to do so, and allowing it would be unwise.
Running Fluidd or other web interfaces on the same machine as the Klipper host was never intended. These web interfaces are designed to offload the workload to the browser or client, relieving the server of these tasks.
After I created the missing systemd directory, the kiauh install appeared to work as the remaining packages also installed. However, I could not establish a moonraker link. Fluidd runs as a localhost entity, 127.0.0.1, in a browser, and has worked well in the past as a single PC controller. However, since that is not the intent of the klipper app, I an accept that and just use via the Pi 2B interface.
Unfortunately I have already abandoned that system, and with it the possible evidence of the moonraker.log. If this issue is of interest for you and worth reestablishing the capability of replicating the problems, I can reinstall the necessary software and provide the information you might use to solve it. Just let me know…