01-10-2021 10:47 AM
I have used petalinux on virtual machines many times. Now I observed on a fresh install of Vitis + petalinux 2020.2 on Ubuntu 18.04.4 that petalinux fails to build:
The reason is it cannot fetch sources with git. I cannot do it myself on the terminal:
joan@joan:~$ git clone git://github.com/Xilinx/embeddedsw.git rubbish Cloning into 'rubbish'... remote: Enumerating objects: 27, done. remote: Counting objects: 100% (27/27), done. remote: Compressing objects: 100% (23/23), done. error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
Looking for that error there is a variety of recipes to fix that. Apparently some work for some people. I just tried some 20 of them in series and it must be my unlucky day as no one worked for me.
what puzzles me is that with some installs (VM, OS, packages, Xilinx sw) there is no problem and with others is that hell.
I think it's an issue that deserves an AR as there could be a number of users wasting their time with that.
01-10-2021 01:23 PM
@watari There are 200 GB, with just Vitis + Vivado + HLS + petalinux installed, so not even 50% used. Network driver on host? Not sure, I haven't changed anything related to network o the host machine and for the VM it is using what it came with VirtualBox 6.1. And inside of it all that comes with Ubuntu 18.04.4
01-11-2021 12:25 AM - edited 01-11-2021 12:49 AM
You are better to debug git
Alternatively, to avoid fetching from remote git repository, do setting download mirror
01-11-2021 01:22 AM
Is petalinux what uses git and does it the way it is, so workarounds, mirrors, etc. don't apply.
I tried a number of the recipes in that post and in similar ones.
Interestingly, for the same error, there are a variety of 'solutions', and none works.
01-11-2021 02:40 AM - edited 01-11-2021 02:43 AM
Most people couldn't reproduce your problem.
I think your problem comes from something wrong in your system.
I have an experience I suffered from other git problem while using petalinux and I eventually fixed it by modifying git configuration in ~/.gitconfig
01-11-2021 02:51 AM
One of the last things I noticed yesterday before wiping the VM and starting again with all the install is that Ubuntu upgraded itself to 18.04.5 which is apparently not supported.
If that is the reason or not I don´t know.
I normally disable updates and upgrades for the principle of having a known reproducible system to work on. I'll be more careful with that this time and will let you know.
01-11-2021 05:20 AM
I can confirm that a fresh install of Ubuntu 18.04.4 on a VirtualBox 6.1 and installing petalinux 2020.2 following the procedure in the user guide and installing the necessary packages without error, produces again the above error.
"something wrong in your system" does not seem to apply to a fresh install, sorry.
"Most people couldn't reproduce your problem" I bet I did what anyone would do: set up a VM, install things.
As I have been working without problems in an 18.04 release, I guess the problem is in the .4 update.
01-12-2021 01:26 PM
As you know, since petalinux (yocto) is resource-hungry, ex. cpu, network, storage, for parallel compile, it tends to take place.
Also, as you know, behavior of network on Ubuntu 18.04, especially DNS setting (systemd set dns as localhost. and it easily occurs.) is a little different before.
So, as I mentioned before, I told my suggestion to you.
> As I have been working without problems in an 18.04 release, I guess the problem is in the .4 update.
Would you reduce resource setting, ex. parallel cpu setting for build on petalinux, if you didn't have enough time to investigate the route cause ?
Perhaps, you might have to change environment from VM to native machine...
I hope this helps.
01-13-2021 12:56 AM
@watari I was about giving up with all 18.04 and install a 16.04. I'm surprised that I tried a number of times, all plain 18.04 to 18,04,5 with the same result: git doesn't work what makes petalinux-build fail. Even without installing any xilinx tool, git fails. I can't believe this is general as in that case many people would suffer that and it would be fixed, so it makes sense there is something in the VM configuration. I don't know how virtual hw can affect how git works. I will decide to either spend more precious time or just go for 16.04. At the end of the day, the OS is just the carpet on the floor, is not making anything.
01-13-2021 12:01 PM - edited 01-24-2021 04:30 AM
Incredible. I have been installing and wiping all 18 releases and updates, tweaking the virtual machine settings, looking for that error on the internet to only find a range of diverse "solutions" that, apparently, some work for some (?) but no one works for me.
So, my conclusion after half a week of dispair: petalinux 2020.2 doesn't work on Ubuntu 18 on, at least, a VirtualBox VM.
Actually, I would say any petalinux, because the problem is git doesn't work and it doesn't because of some problem with GnuTLS.
How do I dare to generalize from my personal case? Because I'm taking a fresh install, no updates, and doing just the minimum setup in the petalinux install guide.
Surprised that this isn't a general problem affecting many people. Anyways, I will stick to 16.04 and here is my experience.
If anyone comes with detailed, precise instructions on how to set up Ubuntu 18 and have petalinux working, happy to hear.
01-24-2021 04:30 AM - edited 01-24-2021 04:33 AM
Update: I've been researching a bit more and the same (or similar) error happens on a VMWare virtual machine. I have been playing with different VM network settings to no avail. Nevertheless, the work laptop has a VirtualBox VM with Ubuntu 16.04 (with the default network settings) and there is no problem there, even with VPN and non-admin access, so the updated conclusion is something is screwed in this 10 -yo desktop that otherwise has no problem.