-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
klipperscreen can't install #12
Comments
The error you're encountering indicates that there was an issue installing the build dependencies for the The error message suggests that CMake 3.15 or higher is required, but your current version is 3.13.4. To resolve this issue, you can try upgrading CMake to a newer version. Here's how you can do it:
Once the CMake upgrade is complete, you can try installing |
Thank you, I tried that but it didn't work for me. Now I have a different problem: -sh: 8: /home/print3D/printer_data/config/: not found No printer_data directory on my phone should I open a new issue for it? |
This path is automatically created when klipper is installed. If not, it means that klipper may not be installed properly. You can try to reinstall klipper, and pay attention to see if there are any errors during the installation process! Also, why are you using "oldstable"? |
hello, I also have problems with cmake that I can't solve, I tried this guide, https://linuxhint.com/install-cmake-on-debian/, but when you try to give the command "cd cmake-3.24.2" it doesn't enter the unzipped folder, and it doesn't give any error. as if the folder doesn't exist. please help me |
Which version of debian are you using? |
i fixed cmake with oldstable and busybox, stable and buster not work for me (same with/whitout busybox) (huawei mediapad t5) now i'm stuck on for now when I turn on the tablet, if connected with otg, klipperscreen starts automatically but does not connect to the printer, moonraker works correctly. I just can't understand where is the error because with the notebook it connects using mainsail. |
Try running: ls -al /dev/ |
|
|
The current information is not easy to judge. You unplug the printer control board from the phone and run the command again to see the difference in the output. |
this is whitout printer connected: |
Do you see a difference from the two files? I don't seem to notice any changes. If you don't see a difference, then reconnect your printer motherboard to the phone, then restart the phone, and try to execute the following command after entering debian: "dmesg". |
with the tablet I don't see the usb connection to the printer with dsmeg, now I'm using a galaxy A50, and on dsmeg I found my printer, this: instead using ls -al /dev/ they look the same both connected and disconnected, how can I translate these lines? |
full report [ 1871.866771] [0: kworker/0:1:11792] usb 1-1: new full-speed USB device number 4 using xhci-hcd |
Run the following command to see if there are new discoveries Send the output information again, and let's analyze it together. In addition, copy and paste all the output of the "dmesg" command into a text file and send it. I'll analyze it to see what's different from mine. grateful. |
$ dmesg | grep 1-1 full dmesg here (somefile) https://github.com/Dani7710/my-test I think the problem is the robin nano v3 motherboard, I also tried with a galaxy note 3 neo and the result is the same, it doesn't appear on dev, like in the huawei mediapad T5, like in the galaxy a50. I can also try with an old galaxy J3 2016, but I'm afraid it's the same. while as soon as I connect the printer, octoprint recognizes it, but I think it needs some tricks there too (whit old marlin no problem), on the octoprint screen it gives me: |
this is the printer.cfg of flsun original speederpad which is officially supported and for sale as klipper upgrade, finally sonicpad and speederpad are tablets... |
Take a look at the discussion at the link below to see if it helps you. Especially test this command: ls -l /sys/bus/usb-serial/devices/ |
Hello
Trying to install klipperscreen but there's an error
can someone please help
Creating virtual environment
Collecting jinja2==3.1.2 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 1))
Using cached Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting netifaces==0.11.0 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 2))
Using cached netifaces-0.11.0.tar.gz (30 kB)
Preparing metadata (setup.py) ... done
Collecting requests==2.31.0 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 3))
Using cached requests-2.31.0-py3-none-any.whl (62 kB)
Collecting websocket-client==1.5.3 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 4))
Using cached websocket_client-1.5.3-py3-none-any.whl (56 kB)
Collecting pycairo==1.23.0 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 5))
Using cached pycairo-1.23.0-cp37-cp37m-linux_armv7l.whl
Collecting PyGObject==3.44.1 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 6))
Using cached PyGObject-3.44.1.tar.gz (720 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting python-mpv==0.5.2 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 7))
Using cached python-mpv-0.5.2.tar.gz (25 kB)
Preparing metadata (setup.py) ... done
Collecting six==1.16.0 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 8))
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting dbus-python==1.3.2 (from -r /home/print3D/KlipperScreen/scripts/KlipperScreen-requirements.txt (line 9))
Using cached dbus-python-1.3.2.tar.gz (605 kB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [129 lines of output]
Collecting meson-python>=0.8.1
Using cached meson_python-0.13.1-py3-none-any.whl (79 kB)
Collecting meson>=0.60.0
Using cached meson-1.1.1-py3-none-any.whl (918 kB)
Collecting ninja
Using cached ninja-1.11.1.tar.gz (27 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting patchelf
Using cached patchelf-0.17.2.1-py2.py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl (381 kB)
Collecting setuptools
Using cached setuptools-67.8.0-py3-none-any.whl (1.1 MB)
Collecting wheel
Using cached wheel-0.40.0-py3-none-any.whl (64 kB)
Collecting pyproject-metadata>=0.7.1 (from meson-python>=0.8.1)
Using cached pyproject_metadata-0.7.1-py3-none-any.whl (7.4 kB)
Collecting tomli>=1.0.0 (from meson-python>=0.8.1)
Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting packaging>=19.0 (from pyproject-metadata>=0.7.1->meson-python>=0.8.1)
Using cached packaging-23.1-py3-none-any.whl (48 kB)
Building wheels for collected packages: ninja
Building wheel for ninja (pyproject.toml): started
Building wheel for ninja (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Error: pip install exited with status code 0
The text was updated successfully, but these errors were encountered: