unable to locate most like means your nameserver isnt workling properly in chroot
You probably need to:
echo "nameserver 127.0.1.1" > /etc/resolv.conf
echo "nameserver 184.108.40.206" >> /etc/resolv.conf
That should fix it.
On another note, I dont think I will continue..
It is very disappointing to see a product like this with a total lack of support and process..
Khadas team - You need to supply a step-by-step for ANY build that is fully functional. I honestly dont believe you can work like this efficiently.
You have half baked scripts that create a linux with NO drivers.
You have half baked scripts that COPY drivers (so useless to even attempt to generate a newer version since depmod will fail).
You have not created a 'proper' GUI version.
Eveything that has been posted to build a system -forgets something- and then when that is fixed - forgets something else-
At some point you built a Ubuntu with a kernel 4.9 (if I remember correctly) in both server and in GUI. So how come someone on your team can not post an absolutely definitive step-to-step to recreate that process?
This needs to include all the little quirk modifications (like tweaking DTS files). everything.
This needs to be from scratch - no downloading core ingredients from your github. DRIVERS/Linux Core/Kernel/ U-Boot/ etc must all come from the lowest common possible denominator. Mali might be the only exception, but it should still be buildable for any kernel version etc..
And completion to a eMMC image - (or TF card, but either way) - complete steps for both, because there are some differences...
If you had this - people would be able to logically change one step at a time and test everything properly starting from a base process.
Also your forums would not be taken up with so much of the simpler support..
You would be helping yourselves out here.
I might also post this separately so its not lost.