UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Cura Linux Slicing crashes: How to choose GPU or use only CPU?
Posted
· Cura Linux Slicing crashes: How to choose GPU or use only CPU?
Ah... damned... it's one of these cases when posting about the issue forces us to look deeper into it and solves the issue.
===== SOLVED =====
The "127.0.0.1" in the logs of 5.1.0 (above) alerted me on something... My "lo" interface was down and there was no route for it (due to some custom VPN scripts I made that apparently turned it down inadvertently).
So the solution was simply:
ifconfig lo up
ip route add 127.0.0.0/8 dev lo
(both as root of course)
That doesn't solve it for 5.6.0 which seems to be another issue, but that version 5.6.0 never worked for me anyway if I remember correctly.
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Recommended Posts
FlorianBad 0
Ah... damned... it's one of these cases when posting about the issue forces us to look deeper into it and solves the issue.
===== SOLVED =====
The "127.0.0.1" in the logs of 5.1.0 (above) alerted me on something... My "lo" interface was down and there was no route for it (due to some custom VPN scripts I made that apparently turned it down inadvertently).
So the solution was simply:
That doesn't solve it for 5.6.0 which seems to be another issue, but that version 5.6.0 never worked for me anyway if I remember correctly.
Link to post
Share on other sites