Jump to content
Ultimaker Community of 3D Printing Experts

Experimental Cura build for Raspberry Pi 4 now available


Recommended Posts

Posted · Experimental Cura build for Raspberry Pi 4 now available

Today's build (20200602) with the mesa-2.1 graphics files installed now supports the orientate selected face downwards feature (looks like poor benchy hit an iceberg)...

 

Screenshot_2020-06-02_11-40-22.thumb.png.a139579d7a0e6678b6966ca514f05564.png

 

 

  • Link to post
    Share on other sites
    • 3 weeks later...
    • Replies 130
    • Created
    • Last Reply

    Top Posters In This Topic

    Top Posters In This Topic

    Popular Posts

    Now available is a Linux AppImage that runs on an armhf system (e.g. a Pi 4). It has received minimal testing but it does appear to work (I sliced a benchy OK!).   Obviously, even the amazin

    I have managed to workaround the various limitations and bugs in the graphic library and now have quite a nice display. It still has some compromises compared to the other builds (Linux/Mac/Windows) a

    Here's the system it was built on. Very nice case from thingiverse sliced without top/bottom skins, just gyroid infill. The SSD wasn't actually used during the build as all files were on the SD card.

    Posted Images

    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi Burt - would  you  consider compiling one for the new 64bit Beta RaspberryPi OS?  https://www.raspberrypi.org/forums/viewtopic.php?t=275370  I tried running the latest version (installed the mesa tarball and libgles-dev) however it balks and barks about libz.so - which is on my system - however when I put it in my LD_LIBRARY_PATH it says: 

     

    <code>

     

    ./Cura-mb-master-armhf-20200610.AppImage 

     

    ./Cura-mb-master-armhf-20200610.AppImage: error while loading shared libraries: libz.so: wrong ELF class: ELFCLASS64

     

    </code>

  • Link to post
    Share on other sites
    Posted (edited) · Experimental Cura build for Raspberry Pi 4 now available

    Hi @kentisevil, I may make a 64 bit release in the future but right now I don't have a 64 bit OS installed and I think I will wait a little for it to mature before I try.

     

    Is it worth copying all the files in the /usr/lib/arm-linux-gnueabihf directory on a 32 bit installation to the 64 bit machine and adding that to the LD_LIBRARY_PATH? Maybe also need some from /lib/arm-linux-gnueabihf as well?

    Edited by burtoogle
  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Just for my own education what do you mean by "Installing" the mesa tarball?

     

    I am somewhat a newbie but, does that mean to copy the files into the appropriate directory or is there something else that needs to be done?

     

    I am running the new 64-bit raspberry pi os and having the same issues as others.  

     

    I am running FreeCad and it would be great to have a slicer and CAD program on the same machine.

     

    Thanks

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hello @saxonpaul92, what I mean is that tar file should be unpacked with a command like "sudo tar xf mesa-20.1-date.tar.gz".

     

    As mentioned above, there's a problem with running that 32 bit AppImage because it requires some 32 bit system libraries to be present. It's probably possible to gather all the required libraries from a 32 bit Pi but that is an experiment that I am not going to do (yet) because I don't have any Pi 4's running the 64 bit OS and I won't be bothering until it becomes more mature. At the very least it has to support VNC server which I don't believe it does yet.

     

    I expect that I will do a 64 bit release for the Pi 4 but it won't be for a while.

     

    Finally, as all the source code that my releases are built from is freely available (of course), it doesn't stop anyone else from building a 64 bit release using that code.

     

    • Thanks 1
    Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    thank you off google! I think you are completely correct for waiting - it wouldn't make sense to do this for a 'beta' anyway - plus with Vulcan in the works we should see what that will bring - that may change everything....

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    @burtoogle

     

    I got tightvnc to work on the 64-bit Raspberry Pi OS.  

     

    Your right the VNC in the release does not work.

     

    Thanks for the info

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    I need the VNC server because none of my Pi's have screens attached, I access them using VNC.

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi,

     

    Am trying out the Cura appimage (20200714) on RPI4 8Gb with Raspian OS (32-bit) build 4.19. For me it works fine w/o /opt/mesa-20.1 (20200709) but with mesa am getting the openGL error shown in attached image. Reproduced the error on another RPI4 4Gb with fresh 4.19 OS image. Any ideas what is causing this?

     

    Thanks

    2020-07-15-115524_1920x1080_scrot.png

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi, Sorry, orrection to previous post. This attached image shows the error.

     

    Thanks

     

    2020-07-15-125404_1920x1080_scrot.thumb.png.53567c76f7d3732aecea9e03b6c10e61.png

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi. Looks perhaps like a permissions problem. The files under /opt/mesa-20.1 should be readable and executable by everyone.

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi burtoogle,

     

    Checked permissions and all was 755. Tried 777 on the Dirs and chown -R pi:pi /opt/mesa-20.1, and ran appimage as root. Alas, still got same error with each of these changes.

     

    thanks

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Maybe it's a group permissions thing, this is what I have for me...

    uid=1001(markb) gid=1001(markb) groups=1001(markb),4(adm),27(sudo),44(video),107(render),109(netdev)

    Are you a member of the render group?

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Hi,

     

    yes pi is in render (107) group.

     

    thanks

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    I still don't know why it is failing for you. You could possibly get more information by setting the LIBGL_DEBUG environment variable (set to "verbose" to get maximum info).

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Was this version built on 32 or 64-bit Raspberry Pi OS?

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    32 bit.

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    couldn't find a way of passing env vars into the appimage. maybe its designed that way.

     

    dropping this now as i can live w/o the extra functionallity, but may try again in future, cheers. 

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    You can simply prefix the command line like this...

     

    LIBGL_DEBUG=verbose Cura-mb-master-armhf-20200721.AppImage

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    I just did that and this is what I got when it started up normally...

     

    libGL: Can't open configuration file /opt/mesa-20.1/etc/drirc: No such file or directory.
    libGL: Can't open configuration file /home/markb/.drirc: No such file or directory.
    libGL: Can't open configuration file /opt/mesa-20.1/etc/drirc: No such file or directory.
    libGL: Can't open configuration file /home/markb/.drirc: No such file or directory.
    libGL: Can't open configuration file /opt/mesa-20.1/etc/drirc: No such file or directory.
    libGL: Can't open configuration file /home/markb/.drirc: No such file or directory.
    libGL: Can't open configuration file /opt/mesa-20.1/etc/drirc: No such file or directory.
    libGL: Can't open configuration file /home/markb/.drirc: No such file or directory.
    libGL: Can't open configuration file /opt/mesa-20.1/etc/drirc: No such file or directory.
    libGL: Can't open configuration file /home/markb/.drirc: No such file or directory.
    drmOpenDevice: node name is /dev/dri/renderD128
    drmOpenDevice: open result is 15, (OK)
    drmOpenDevice: node name is /dev/dri/renderD129
    drmOpenDevice: node name is /dev/dri/renderD130
    drmOpenDevice: node name is /dev/dri/renderD131
    drmOpenDevice: node name is /dev/dri/renderD132
    drmOpenDevice: node name is /dev/dri/renderD133
    drmOpenDevice: node name is /dev/dri/renderD134
    drmOpenDevice: node name is /dev/dri/renderD135
    drmOpenDevice: node name is /dev/dri/renderD136
    drmOpenDevice: node name is /dev/dri/renderD137
    drmOpenDevice: node name is /dev/dri/renderD138
    drmOpenDevice: node name is /dev/dri/renderD139
    drmOpenDevice: node name is /dev/dri/renderD140
    drmOpenDevice: node name is /dev/dri/renderD141
    drmOpenDevice: node name is /dev/dri/renderD142
    drmOpenDevice: node name is /dev/dri/renderD143
    drmOpenDevice: node name is /dev/dri/renderD128
    drmOpenDevice: open result is 15, (OK)

     

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    thanks, that helped, could be shared library version mismatch?:

     

    libGL: MESA-LOADER: failed to open /opt/mesa-20.1/lib/arm-linux-gnueabihf/dri/vc4_dri.so: libLLVM-7.so.1: cannot open shared object file: No such file or directory
     

    sudo find / -name 'libLLVM*' -print
    /usr/lib/arm-linux-gnueabihf/libLLVM-9.so
    /usr/lib/arm-linux-gnueabihf/libLLVM-9.so.1
     

     

     

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    That's interesting, I have both -7 and -9 LLVM libraries.

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    installing llvm-7-dev should be sufficient to give you the missing library

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Thanks burtoogle, adding that package has resolved the problem, Cura starts with MESA enabled and I can now see the additional functionallity.

     

    Great, many thanks for your help.

  • Link to post
    Share on other sites
    Posted · Experimental Cura build for Raspberry Pi 4 now available

    Sorry for the hassle, perhaps I should build Mesa against llvm-9 if that is what people have. I'll see what buster defaults to.

    • Like 1
    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!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    • 22 Visiting our virtual showroom

      1. 1. Have you visited our virtual showroom before?


        • Yes
        • No
      2. 2. If yes - what content did you find most interesting?


        • Information about Ultimaker ecosystem
        • Applications & application stories
        • Customer success stories
        • Webinar sessions
        • Material wall & ecosystem partners
        • New product introduction; software subscription plans
      3. 3. What of the below would make you consider visiting (again)?


        • New Live Ultimaker Webinar streams
        • ‘Ask Me Anything’ with industry experts or Ultimaker staff via main stage and public chat
        • New customer success stories
        • New applications
        • Presentations/news from ecosystem partners
        • Opportunity to meet representatives for an interactive tour
        • Helpful videos like Software tutorials
        • Other; leave input in a comment below!

    • Our picks

      • Ultimaker turns 10: A look back
        Ultimaker is turning 10 years old and that means it is story telling time! We'll explore 2010-2014, traveling through the evolution of the business from the Protobox and Ultimaker Original, to the major leaps forward with the Ultimaker 2 and Ultimaker 3.
          • Like
        • 0 replies
      • Ultimaker Transformation Summit
        Visit our virtual showroom and learn more about the Ultimaker ecosystem!
        • 14 replies
      • New here? Register your Ultimaker for free 3D printer onboarding course
        Hi,
         
        Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
        Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.   
        They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access. 
        Ready? Register your product here in just 60 seconds.
          • Like
        • 0 replies
    ×
    ×
    • Create New...