On 09/10/2015 09:25 AM, Mandar Joshi wrote:
I do not know how to build an image that works via the RBF.
In your case, since you have both Cubietruck and Cubieboard2, you should generate a generic image i.e. a QEMU image and then write it to your microSD card using rbfinstaller.py. Choose Cubietruck/Cubieboard2 depending on the which microSD card you are writing to.
In short, on your current CentOS Cubietruck # git clone https://github.com/mndar/rbf.git # cd rbf # ./rbf.py build templates/qemu.xml # ./rbfinstaller.py centos.img /dev/sdb
The README has more details.
Where is the readme? I am gathering, that ON the Cubietruck, I can build the generic image. I trust that this readme has good instructions for how to do that...
You can look in the section, "Usage of rbf.py". If you want to use QEMU, this doc will be useful https://github.com/mndar/rbf/blob/master/doc/QEMU_README.md
I am looking at:
https://github.com/mndar/rbf/blob/master/doc/
ANd see a number of readmes, and trying to figure out the flow. Will the scripts work on the CT without a GUI?
I do not know if enough has been compiled to work with the lastest builds I want to be testing out the image build process as well as the rest. Please let me know where we stand and how to build images.
I built a new CentOS image my Cubietruck last week. With the latest kernel in the repo, I am having trouble with the mmc_block driver in QEMU not detecting the disk and with the ethernet driver on my Cubietruck. I generated the image and then copied over the old kernel to the new image to make everything functional in both cases. I have yet to look into these two issues in more detail.
Regards Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev