I didn’t realize this had been released. Note that I haven’t tested that but let us know the results.
My Pi3b setup is so slow that it’s not a pleasant place to live. I had not planned to spend much time there when I thought that the most of the basics were working. However, the issue with Fill mode now has me bothered although I suspect it won’t be easy to track down.
First of all, THANKS! for the information. I was not able to get it working on a Pi5, but have it on a Pi4 with absolutely no issue. No issue except for 1. It seems that each time I run the “launch.sh” it must create a new instance because it does not remember my license. I did not see that problem mentioned. What have y’all done to solve the license issue?
Glad this is working for you. it’s unclear to me how many people are actually using this.
It launches LightBurn as it would normally be launched. If you have a running instance from another shell, it will create another instance. But there’s nothing unusual in this.
As for the license, you get this every time you launch? In my limited testing I would need to occasionally re-enter the key if I had not used it in a while. But not at every launch of the app. I had assumed it was due to a change in environment or because of updates but perhaps there’s something else going on.
Note that I did find one other potential issue with using Fill operations. LightBurn seems to generate artifacts not in the original design. It will be apparent in the Preview. Can you give it a shot and see if you get the same results. I did not have a Pi4 or Pi5 to test this on.
By the way, what issue did you have running this on Pi5?
Not every time. I had to go into my license manager and delete one of my pi instances.
On the Pi5, there was a hash mismatch. I forget which one, but one of the ones posted in #32 above.
At some point if I ever get a Pi5 I’ll look at updating against latest builds of PiOS, LightBurn, and donor distro.
If you could confirm on the Fill operation I’d appreciate it. That one bothers me.
I never could get the camera to work so that’s a major hole. I’m happy for someone to help solve that.
Note that a recent Pi OS update seems to have resolved this issue.
How’s the performance?
Once up and running the performance is surprisingly good. Activities that would be slow on a normal computer are exaggeratedly slow on the Pi but otherwise perfectly usable. I see no reason this couldn’t be used as a job computer other than the lack of camera support.
I recently got a Pi 4 with 1GB of RAM. Definitely a bit faster than the 3B+ I was originally using but I suspect memory is the real bottleneck in terms of performance. It crashed when trying to use Chromium and LightBurn at the same time.
Hi @berainlb , ive tried your way to install lightburn at my PI 5. Ive followed all steps but i couldnt run it. Im using the current PI-OS version. If you can help me that would be soooo kind. Im really at the end with my solutions…
As far as I’m aware this has never been run successfully on a Pi5. I don’t have one and one other user reported that it did not work for him on Pi5 while it did on Pi4.
I suspect it could be made to work but would require some specific library changes. Do you have a Pi3 or Pi4 that could be used instead?
Hello berainlb,
Unfortunately I don’t have a Pi4 or 3. I would have to get it first (my thought was Pi5 more power = better but as I unfortunately discovered, the Pi5 is completely different and still too new so that it doesn’t have the same options as the pi4)
If you give me the recommendation that I should get a pi4 and it works well, I will do that (easiest way:))
Unfortunately, I’m not very familiar with Linux systems. Is there a solution in the near future? for the Pi5? or another way to get LB to run on a Pi 5? (honest windwos I’ve already done that 
and LB works there too but windos gets more and more problems over time)
Thank you for existing and sharing your knowledge with everyone
I can say at least that Pi4 should work and is likely the easiest path forward, at least for now.
This likely would require going through the same type of exercise that I did initially to get this working. I don’t think there’s anything fundamentally different about the Pi5 that would prevent this from working. It would just require some tedious testing and tracking down of packages.
If I ever get a Pi5 I’ll likely review and revise the packages/steps necessary for this to work but I have no plans currently to get one. Perhaps someone else who does have a Pi5 can piggyback on this work to do the same.
You could try the legacy 64-bit version…
Note that Legacy is not listed as being compatible with Pi5.
Having said that, this could very well be a Bullseye vs Bookworm issue and not a Pi4 vs Pi5 thing.
At some point, I may try to update the process and libraries for Bookworm which may solve the Pi5 issue but that’s purely speculation.
It works on my Pi3b+! I had some issues at first. Finally I started with a clean install of RPi OS (Bullseye). Once I got that squared away, and once I found the correct verrsion, Box64 was a simple install, as was Lightburn 1.4.xx. Although the latter it took two tries. LB 1.5 kept tossing an error related to not finding a QT platform plugin. I mucked around troubleshooting, saw that the plugin was actually there, and decided to use 1.4.xx, re-extracted all of the files into the LightBurn directory and it started right up. I activated the demo, did the upgrade and am now running 1.5.06. It’s a bit slow but works so far.
Note: BOX 64 install (after setting up Ryan Fortner’s repository)
sudo apt update && sudo apt install box64-rpi3arm64 -y
Best,
Jerry
That’s fantastic. Just to get some more data points, how much RAM does your Pi have?
I followed a guide and installed Buster (32 bit) on PI5, maybe tomorrow I will try to install Bullseye on PI5 with the same method. This topic is only for 64bit, will it also work with 32bit?
On the first boot it crashed and restarted, then auto-updated and ran for a few hours with open box CPU:34-39º 3-32% Memory: 29%.
There is no 32-bit build of LightBurn for Linux that I’m aware of. Running 64-bit apps on a 32-bit OS would be impractically difficult.
You could potentially try running the 32-bit Windows version of LightBurn via Wine using Box86.
I think all of the 3B+ models have 1GB on them.
One thing that I did run into was the issue with losing the USB port that my engraver is plugged into. It came back but I’m not sure what I did. As I recall there’s a Linux comment that resets and rescans the USB bus but I haven’t had a moment to dig it out. I ran another job on the thing yesterday (once it found the engraver again) and it worked. I’m going to try something more photo-realistic tomorrow, I think, and will report more when it’s done.
PI5 with Bullseye it`s a no go. Boot with kernel errors and no menus. However command line works.
