RPI4 Support #104213
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#104213
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I have tried several ways to run flamenco on my RPI, using box64 to emulate the made build and also baking the build from the RPI4 (I can't install correctly GO on RPI) and neither of the 2 works.
Hi @PGSCOM - this to me falls into a wider question for flamenco dev team on what is the plan to support ARM targets in general, like Mac M1, RaspberryPi 32 & 64bit etc. Depending on your development experience level, I can help you generate arm64 flamenco-manager executable from flamenco working-copy that is based on a flamenco release but there is a problem in v3.2 that fails to compile on arm64. This was fixed in the main branch and will be included in v3.3.
Does 'baking the build from RPI4" mean you tried to build Flamenco-Manager on RaspberryPi host?
Yes @michael-2, I tried to build Flamenco-Manager and Flamenco-Worker in Raspbian installing all the dependencies with the tutorial.
What was the outcome/failure? I have not tried a native build on RaspPi host.
With the last commit (
0a2d7d3361
)The minimum version requirements for Flamenco must be met and I can see from your logs, you are using earlier version of golang 1.15 and minimum is 1.20. Usually, RaspPi/Debian/Ubuntu distros have fairly old golang, nodejs and npm releases.
I dont have a RaspPi 4. I have a Rasp3 with 1GB RAM and while trying to create an example for you, it jams up trying to install go packages during
make with-deps
at the end... but RaspPi runs out of memory.You could try this script...
Let me know if this succeeds on a RaspPi4. ;o)
I have created a flamenco-manager arm64 using Docker if you're interested in a more involved build process, not using the RaspPi host, but using Docker buildx using a similar script to that shown above on an amd64 workstation.
There's probably that error because I've done tests before, I'd better do a new installation of raspbian and try it again.
The script says it can't find go, so probably the symlink in the script is broken.
The symlink in the script is set by...
Check that the script unpacked go to /usr/local/go/ and what the symlink is pointing to by trying these commands on the RaspPi...
I don't know why Go didn't install correctly. I install it line by line and now works
And it finaly works!!! Thanks @michael-2
Now I have a problem, I can't enter a Windows path (Because the workers will be Windows), so, the RPI4 will do as NAS and also for Manager server. But I cant put it because the path didn't exsist in Linux.
And when I edit the .yml file manualy to Z:\ the path in the plugin is /home/pablo/Z:\ and not Z:\
There is any config that can decide what path is used in each platform?
@PGSCOM - yes, there is documentation on how to configure shared-storage paths between platform types. RaspPi will be a 'linux' platform type. Flamenco will translate between them. See documentation on flamenco website using shared-storage two-way variables.
If you need functional setup help, I recommend using the blender chat instead of raising git issues. I would keep this specific Issue about creating a RaspPi ARM build.