-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Permission denied: '/tmp/printer'' #3432
Comments
The log indicates that it's not seeing your MCU.
What is the output of |
The output of ls /dev/serial/by-id/* /dev/serial/by-id/usb-Klipper_lpc1768_1CB0FF14089DC5AEB375C656C62000F5-if00 |
Anyone? |
I do not know DietPi, so just a wild stab:
|
The output of ls -al /dev/serial/by-id/* is: I have no idea what that means :( |
Please post the entire output. Should look like
Under which user do you run klipper? If you do not know, then start klipper and issue the command
The line When you have the user issue the command
If you do not see Finally log off the shell, log back in and restart klipper. |
This week I installed Octopi from scratch and ran a
I can only connect to |
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
Posted a solution in #1902 for changing octoprint.service |
klippy.log
I read one or two posts on this issue and one of them did not list the serial correctly (which I did)- #1296
The second one was too technical for me to understand- #1902
UPDATE: I found a 3rd post, don't know if it is related but sounds similar to the second post (above). Again, too technical for me to understand :(
My issue resembles more with the first one. I should mention that I have been using a Rock64 with DietPi->Octoprint instead of a RPi. It worked perfectly well last year, haven't used the printer since March and I think some kind of update might have broken it but I might be wrong. I would really appreciate some feedback. Thanks!
The text was updated successfully, but these errors were encountered: