Hello, I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing. Do I need an existing arm binary system? Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image? The end goal is to have a centos system with Selinux enabled.
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
RIght now we do not have a general image with all the uboots on it. But do not fear, we will get you going...
You will dd the Cubietruck image onto a mSD card. From:
http://mirror.centos.org/altarch/7/isos/armhfp/
I will get the Beaglebone black uboot, put it up on my server, and tell you how to dd that uboot onto the mSD card and then you should be good to boot...
On 12/28/2015 08:34 PM, Robert Moskowitz wrote:
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
RIght now we do not have a general image with all the uboots on it. But do not fear, we will get you going...
You will dd the Cubietruck image onto a mSD card. From:
http://mirror.centos.org/altarch/7/isos/armhfp/
I will get the Beaglebone black uboot, put it up on my server, and tell you how to dd that uboot onto the mSD card and then you should be good to boot...
OK. Look over at:
http://medon.htt-consult.com/~rgm/beaglebone/
To put these on your mSD card you would do:
sudo dd if=MLO of=$MEDIA count=1 seek=1 conv=notrunc bs=128k; sync sudo dd if=u-boot.img of=$MEDIA count=2 seek=1 conv=notrunc bs=384k; sync
where $MEDIA is /dev/<where your card is>
I THINK this will work. There was quite a thread on the BBB on the Fedora-arm list back in the summer...
Last point on this.
I was told by one of the Fedora people that the problems with the BBB are video. That a minimal image (like the current Centos) work fine.
On 12/28/2015 09:29 PM, Robert Moskowitz wrote:
On 12/28/2015 08:34 PM, Robert Moskowitz wrote:
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
RIght now we do not have a general image with all the uboots on it. But do not fear, we will get you going...
You will dd the Cubietruck image onto a mSD card. From:
http://mirror.centos.org/altarch/7/isos/armhfp/
I will get the Beaglebone black uboot, put it up on my server, and tell you how to dd that uboot onto the mSD card and then you should be good to boot...
OK. Look over at:
http://medon.htt-consult.com/~rgm/beaglebone/
To put these on your mSD card you would do:
sudo dd if=MLO of=$MEDIA count=1 seek=1 conv=notrunc bs=128k; sync sudo dd if=u-boot.img of=$MEDIA count=2 seek=1 conv=notrunc bs=384k; sync
where $MEDIA is /dev/<where your card is>
I THINK this will work. There was quite a thread on the BBB on the Fedora-arm list back in the summer...
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On Mon, Dec 28, 2015 at 11:58 PM, Robert Moskowitz rgm@htt-consult.com wrote:
Last point on this.
I was told by one of the Fedora people that the problems with the BBB are video. That a minimal image (like the current Centos) work fine.
Another data point, if interested... I use a BBB with the Debian 8.2 flasher snapshot image from 2015-12-27 (http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Sn..., SHA-256 f06a6a4f50).
Ive never had a problem, but I do everything over SSH.
Jeff
A BeagleboneBlack user. Awesome! If Robert's method works for you, you won't have to follow the rest of this email. If it modifies the entire bootloader area, it will work and you wont have to generate an image yourself. The current available image for CentOS is for the Cubietruck and Raspberry Pi 2.
If you have to or want to generate an image yourself, you can use RootFS Build Factory.
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
About RootFS Build Factory: It is a set of tools and scripts to generate rootfs images for 32-bit ARM Boards. It uses XML templates to get information about boards and Python & Shell Scripts to build and write image images to cards.
Do I need an existing arm binary system?
Yes to generate RootFS images, you do. Or you could do so in Qemu.
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
git clone https://github.com/mndar/rbf.git You will need Python2. (if it's not already there). There are two approaches you could take 1. Generate and image just for your board. Presently this uses bootloader NOT built on the CentOS servers. ./rbf.py build templates/beaglebone_centos_71511.xml
2. Generate a generic image first, then write it using rbfinstaller.py to your card. ./rbf.py build templates/qemu_centos_71511.xml (this will generate an image without a bootloader) ./rbfinstaller.py beaglebone-image.img /dev/sdb (change /dev/sdb according to your card writer) (Again, this second step uses the bootloader from the github repo and is not the one built on the CentOS servers)
The end goal is to have a centos system with Selinux enabled.
I personally haven't tested SELinux that much. But there is an option to set its mode while generating the image.
Regards Mandar Joshi
PS: These changes have to be made yet. https://lists.centos.org/pipermail/arm-dev/2015-December/001352.html Fabain, let me know when you'll have time to discuss.
You will need Python2. (if it's not already there). There are two approaches you could take 1. Generate and image just for your board. Presently this uses bootloader NOT built on the CentOS servers. ./rbf.py build templates/beaglebone_centos_71511.xml
Only the cubietruck_centos_71511.xml template uses the bootloader built on the CentOS servers.
On 12/29/2015 12:37 AM, Mandar Joshi wrote:
I personally haven't tested SELinux that much. But there is an option to set its mode while generating the image.
And thus I hope that soon a general image that includes the uboot-images-armv7 rpm is included with selinux enabled.
It is cheaper for all of us to turn off selinux than for each of us, who want it, to turn it on. :)
On 12/29/2015 12:37 AM, Mandar Joshi wrote:
A BeagleboneBlack user. Awesome! If Robert's method works for you, you won't have to follow the rest of this email. If it modifies the entire bootloader area, it will work and you wont have to generate an image yourself.
It is important we get this validation of the generic board approach taken by fedora-arm and that it works with our images.
It is the more practical way forward to get a solid uptake here.
It is important we get this validation of the generic board approach taken by fedora-arm and that it works with our images.
It is the more practical way forward to get a solid uptake here.
The approach Fedora takes, the one you suggested for BBB and the one I am suggesting are all the same in effect. The only difference is that RootFS Build Factory uses u-boot from the my github repo rather than taking it from the the uboot-images-armv7 package in the new centos rootfs. This has been changed in the new cubietruck templates.
On 12/30/2015 06:12 AM, Mandar Joshi wrote:
It is important we get this validation of the generic board approach taken by fedora-arm and that it works with our images.
It is the more practical way forward to get a solid uptake here.
The approach Fedora takes, the one you suggested for BBB and the one I am suggesting are all the same in effect. The only difference is that RootFS Build Factory uses u-boot from the my github repo rather than taking it from the the uboot-images-armv7 package in the new centos rootfs. This has been changed in the new cubietruck templates.
I understand that. But the Fedora approach results in one build of the image and everyone downloads that and customizes it for their board. Less resources on everyone's part. It will e more attractive to newcomers when the steps are:
download the image run the install script to a mSD card install mSD card on arm board boot
Thank you for all you have done for this project.
download the image run the install script to a mSD card install mSD card on arm board boot
This approach is already possible with RootFS Build Factory! 1. Generate an Image for Qemu using rbf.py. This just an image without any bootloader. Release this image. 2. Download this image. Install it to your card with rbfinstaller.py. It gives you an option to choose from list of possible boards (Right now, it uses uboot from the github repo)
Regards Mandar Joshi
Some things to note,
This thing works on debian, but you need to change /usr/bin/bash to /bin/bash.
You need to take out the check for read in the python script, as that is built into debian.
I ran into some problems with yum though:
Resolving Dependencies --> Running transaction check ---> Package aic94xx-firmware.noarch 0:30-6.el7 will be installed --> Processing Dependency: udev for package: aic94xx-firmware-30-6.el7.noarch ---> Package alsa-firmware.noarch 0:1.0.28-2.el7 will be installed --> Processing Dependency: alsa-tools-firmware >= 1.0.27 for package: alsa-firmware-1.0.28-2.el7.noarch --> Processing Dependency: udev for package: alsa-firmware-1.0.28-2.el7.noarch ---> Package basesystem.noarch 0:10.0-7.el7.centos will be installed --> Processing Dependency: filesystem for package: basesystem-10.0-7.el7.centos.noarch ---> Package firewalld.noarch 0:0.3.9-11.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: python-slip-dbus for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: python-decorator for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: pygobject3-base for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: iptables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: ebtables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: dbus-python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /usr/bin/python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch ---> Package iwl100-firmware.noarch 0:39.31.5.1-36.el7 will be installed ---> Package iwl1000-firmware.noarch 1:39.31.5.1-36.el7 will be installed ---> Package iwl105-firmware.noarch 0:18.168.6.1-36.el7 will be installed ---> Package iwl135-firmware.noarch 0:18.168.6.1-36.el7 will be installed ---> Package iwl2000-firmware.noarch 0:18.168.6.1-36.el7 will be installed ---> Package iwl2030-firmware.noarch 0:18.168.6.1-36.el7 will be installed ---> Package iwl3160-firmware.noarch 0:22.0.7.0-36.el7 will be installed ---> Package iwl3945-firmware.noarch 0:15.32.2.9-36.el7 will be installed ---> Package iwl4965-firmware.noarch 0:228.61.2.24-36.el7 will be installed ---> Package iwl5000-firmware.noarch 0:8.83.5.1_1-36.el7 will be installed ---> Package iwl5150-firmware.noarch 0:8.24.2.2-36.el7 will be installed ---> Package iwl6000-firmware.noarch 0:9.221.4.1-36.el7 will be installed ---> Package iwl6000g2a-firmware.noarch 0:17.168.5.3-36.el7 will be installed ---> Package iwl6000g2b-firmware.noarch 0:17.168.5.2-36.el7 will be installed ---> Package iwl6050-firmware.noarch 0:41.28.5.1-36.el7 will be installed ---> Package iwl7260-firmware.noarch 0:22.0.7.0-36.el7 will be installed ---> Package linux-firmware.noarch 0:20140911-0.1.git365e80c.el7 will be installed ---> Package rdma.noarch 0:7.1_3.17-5.el7 will be installed --> Processing Dependency: udev >= 095 for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: dracut for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/bash for package: rdma-7.1_3.17-5.el7.noarch ---> Package rootfiles.noarch 0:8.1-11.el7 will be installed ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: selinux-policy = 3.13.1-23.el7 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: selinux-policy = 3.13.1-23.el7 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: coreutils for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch ---> Package setup.noarch 0:2.8.71-5.el7 will be installed --> Processing Dependency: system-release for package: setup-2.8.71-5.el7.noarch ---> Package tuned.noarch 0:2.4.1-1.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: util-linux for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: python-pyudev for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: python-configobj for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: pygobject3-base for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: gawk for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: ethtool for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: dbus-python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /usr/bin/python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch ---> Package yum.noarch 0:3.4.3-125.el7.centos will be installed --> Processing Dependency: python(abi) = 2.7 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm >= 4.4.2 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-urlgrabber >= 3.9.0-8 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python >= 2.4 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: yum-plugin-fastestmirror for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm-python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyxattr for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-sqlite for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-iniparse for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyliblzma for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pygpgme for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: diffutils for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: cpio for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /usr/bin/python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/bash for package: yum-3.4.3-125.el7.centos.noarch --> Running transaction check ---> Package aic94xx-firmware.noarch 0:30-6.el7 will be installed --> Processing Dependency: udev for package: aic94xx-firmware-30-6.el7.noarch ---> Package alsa-firmware.noarch 0:1.0.28-2.el7 will be installed --> Processing Dependency: alsa-tools-firmware >= 1.0.27 for package: alsa-firmware-1.0.28-2.el7.noarch --> Processing Dependency: udev for package: alsa-firmware-1.0.28-2.el7.noarch ---> Package basesystem.noarch 0:10.0-7.el7.centos will be installed --> Processing Dependency: filesystem for package: basesystem-10.0-7.el7.centos.noarch ---> Package firewalld.noarch 0:0.3.9-11.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: pygobject3-base for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: iptables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: ebtables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: dbus-python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /usr/bin/python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch ---> Package python-configobj.noarch 0:4.7.2-7.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-configobj-4.7.2-7.el7.noarch ---> Package python-decorator.noarch 0:3.4.0-3.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-decorator-3.4.0-3.el7.noarch ---> Package python-iniparse.noarch 0:0.4-9.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-iniparse-0.4-9.el7.noarch ---> Package python-pyudev.noarch 0:0.15-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-pyudev-0.15-6.el7.noarch --> Processing Dependency: python-setuptools for package: python-pyudev-0.15-6.el7.noarch --> Processing Dependency: python for package: python-pyudev-0.15-6.el7.noarch ---> Package python-slip-dbus.noarch 0:0.4.0-2.el7 will be installed --> Processing Dependency: python-slip = 0.4.0-2.el7 for package: python-slip-dbus-0.4.0-2.el7.noarch --> Processing Dependency: python(abi) = 2.7 for package: python-slip-dbus-0.4.0-2.el7.noarch --> Processing Dependency: dbus-python >= 0.80 for package: python-slip-dbus-0.4.0-2.el7.noarch ---> Package python-urlgrabber.noarch 0:3.10-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: python-pycurl for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-urlgrabber-3.10-6.el7.noarch ---> Package rdma.noarch 0:7.1_3.17-5.el7 will be installed --> Processing Dependency: udev >= 095 for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: dracut for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/bash for package: rdma-7.1_3.17-5.el7.noarch ---> Package selinux-policy.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /usr/bin/sha512sum for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/awk for package: selinux-policy-3.13.1-23.el7.noarch ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: coreutils for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch ---> Package setup.noarch 0:2.8.71-5.el7 will be installed --> Processing Dependency: system-release for package: setup-2.8.71-5.el7.noarch ---> Package tuned.noarch 0:2.4.1-1.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: util-linux for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: pygobject3-base for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: gawk for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: ethtool for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: dbus-python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /usr/bin/python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch ---> Package yum.noarch 0:3.4.3-125.el7.centos will be installed --> Processing Dependency: python(abi) = 2.7 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm >= 4.4.2 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python >= 2.4 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm-python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyxattr for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-sqlite for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyliblzma for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pygpgme for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: diffutils for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: cpio for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /usr/bin/python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/bash for package: yum-3.4.3-125.el7.centos.noarch ---> Package yum-plugin-fastestmirror.noarch 0:1.1.31-29.el7 will be installed --> Running transaction check ---> Package aic94xx-firmware.noarch 0:30-6.el7 will be installed --> Processing Dependency: udev for package: aic94xx-firmware-30-6.el7.noarch ---> Package alsa-firmware.noarch 0:1.0.28-2.el7 will be installed --> Processing Dependency: alsa-tools-firmware >= 1.0.27 for package: alsa-firmware-1.0.28-2.el7.noarch --> Processing Dependency: udev for package: alsa-firmware-1.0.28-2.el7.noarch ---> Package basesystem.noarch 0:10.0-7.el7.centos will be installed --> Processing Dependency: filesystem for package: basesystem-10.0-7.el7.centos.noarch ---> Package firewalld.noarch 0:0.3.9-11.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: pygobject3-base for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: iptables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: ebtables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: dbus-python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /usr/bin/python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch ---> Package python-configobj.noarch 0:4.7.2-7.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-configobj-4.7.2-7.el7.noarch ---> Package python-decorator.noarch 0:3.4.0-3.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-decorator-3.4.0-3.el7.noarch ---> Package python-iniparse.noarch 0:0.4-9.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-iniparse-0.4-9.el7.noarch ---> Package python-pyudev.noarch 0:0.15-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-pyudev-0.15-6.el7.noarch --> Processing Dependency: python for package: python-pyudev-0.15-6.el7.noarch ---> Package python-setuptools.noarch 0:0.9.8-3.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-setuptools-0.9.8-3.el7.noarch --> Processing Dependency: python-backports-ssl_match_hostname for package: python-setuptools-0.9.8-3.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-setuptools-0.9.8-3.el7.noarch ---> Package python-slip.noarch 0:0.4.0-2.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-slip-0.4.0-2.el7.noarch --> Processing Dependency: libselinux-python for package: python-slip-0.4.0-2.el7.noarch ---> Package python-slip-dbus.noarch 0:0.4.0-2.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-slip-dbus-0.4.0-2.el7.noarch --> Processing Dependency: dbus-python >= 0.80 for package: python-slip-dbus-0.4.0-2.el7.noarch ---> Package python-urlgrabber.noarch 0:3.10-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: python-pycurl for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-urlgrabber-3.10-6.el7.noarch ---> Package rdma.noarch 0:7.1_3.17-5.el7 will be installed --> Processing Dependency: udev >= 095 for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: dracut for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/bash for package: rdma-7.1_3.17-5.el7.noarch ---> Package selinux-policy.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /usr/bin/sha512sum for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/awk for package: selinux-policy-3.13.1-23.el7.noarch ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: coreutils for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch ---> Package setup.noarch 0:2.8.71-5.el7 will be installed --> Processing Dependency: system-release for package: setup-2.8.71-5.el7.noarch ---> Package tuned.noarch 0:2.4.1-1.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: util-linux for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: pygobject3-base for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: gawk for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: ethtool for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: dbus-python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /usr/bin/python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch ---> Package yum.noarch 0:3.4.3-125.el7.centos will be installed --> Processing Dependency: python(abi) = 2.7 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm >= 4.4.2 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python >= 2.4 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm-python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyxattr for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-sqlite for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyliblzma for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pygpgme for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: diffutils for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: cpio for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /usr/bin/python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/bash for package: yum-3.4.3-125.el7.centos.noarch --> Running transaction check ---> Package aic94xx-firmware.noarch 0:30-6.el7 will be installed --> Processing Dependency: udev for package: aic94xx-firmware-30-6.el7.noarch ---> Package alsa-firmware.noarch 0:1.0.28-2.el7 will be installed --> Processing Dependency: alsa-tools-firmware >= 1.0.27 for package: alsa-firmware-1.0.28-2.el7.noarch --> Processing Dependency: udev for package: alsa-firmware-1.0.28-2.el7.noarch ---> Package basesystem.noarch 0:10.0-7.el7.centos will be installed --> Processing Dependency: filesystem for package: basesystem-10.0-7.el7.centos.noarch ---> Package firewalld.noarch 0:0.3.9-11.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: systemd for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: pygobject3-base for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: iptables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: ebtables for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: dbus-python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /usr/bin/python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch ---> Package python-backports-ssl_match_hostname.noarch 0:3.4.0.2-4.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-backports-ssl_match_hostname-3.4.0.2-4.el7.noarch --> Processing Dependency: python-backports for package: python-backports-ssl_match_hostname-3.4.0.2-4.el7.noarch ---> Package python-configobj.noarch 0:4.7.2-7.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-configobj-4.7.2-7.el7.noarch ---> Package python-decorator.noarch 0:3.4.0-3.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-decorator-3.4.0-3.el7.noarch ---> Package python-iniparse.noarch 0:0.4-9.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-iniparse-0.4-9.el7.noarch ---> Package python-pyudev.noarch 0:0.15-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-pyudev-0.15-6.el7.noarch --> Processing Dependency: python for package: python-pyudev-0.15-6.el7.noarch ---> Package python-setuptools.noarch 0:0.9.8-3.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-setuptools-0.9.8-3.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-setuptools-0.9.8-3.el7.noarch ---> Package python-slip.noarch 0:0.4.0-2.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-slip-0.4.0-2.el7.noarch --> Processing Dependency: libselinux-python for package: python-slip-0.4.0-2.el7.noarch ---> Package python-slip-dbus.noarch 0:0.4.0-2.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-slip-dbus-0.4.0-2.el7.noarch --> Processing Dependency: dbus-python >= 0.80 for package: python-slip-dbus-0.4.0-2.el7.noarch ---> Package python-urlgrabber.noarch 0:3.10-6.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: python-pycurl for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-urlgrabber-3.10-6.el7.noarch ---> Package rdma.noarch 0:7.1_3.17-5.el7 will be installed --> Processing Dependency: udev >= 095 for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: systemd-units for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: dracut for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/bash for package: rdma-7.1_3.17-5.el7.noarch ---> Package selinux-policy.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /usr/bin/sha512sum for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/awk for package: selinux-policy-3.13.1-23.el7.noarch ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7 will be installed --> Processing Dependency: policycoreutils >= 2.1.14-74 for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: coreutils for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch ---> Package setup.noarch 0:2.8.71-5.el7 will be installed --> Processing Dependency: system-release for package: setup-2.8.71-5.el7.noarch ---> Package tuned.noarch 0:2.4.1-1.el7 will be installed --> Processing Dependency: python(abi) = 2.7 for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: virt-what for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: util-linux for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: systemd for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: pygobject3-base for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: gawk for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: ethtool for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: dbus-python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /usr/bin/python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch ---> Package yum.noarch 0:3.4.3-125.el7.centos will be installed --> Processing Dependency: python(abi) = 2.7 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm >= 4.4.2 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python >= 2.4 for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: rpm-python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyxattr for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: python-sqlite for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pyliblzma for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: pygpgme for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: diffutils for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: cpio for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /usr/bin/python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/bash for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/awk for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /usr/bin/python for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-urlgrabber-3.10-6.el7.noarch --> Processing Dependency: /usr/bin/python for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /usr/bin/python for package: python-setuptools-0.9.8-3.el7.noarch --> Processing Dependency: /usr/bin/python for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /usr/bin/sha512sum for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/bash for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/bash for package: yum-3.4.3-125.el7.centos.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-targeted-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: rdma-7.1_3.17-5.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: firewalld-0.3.9-11.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: tuned-2.4.1-1.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Processing Dependency: /bin/sh for package: selinux-policy-3.13.1-23.el7.noarch --> Finished Dependency Resolution You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [INFO ] GROUP_INSTALL_ERROR: Error Installing Some Package Groups Retry (y/n)?
INFO ] KERNEL_PACKAGE_INSTALL_ERROR: Error installing Kernel Packages Retry (y/n)? Setting up Install Process No package kernel available. No package dracut-config-generic available. [INFO ] KERNEL_PACKAGE_INSTALL_ERROR: Error installing Kernel Packages
It also leaves the linux in a state where I have to undo things manually like umount devices, and delete temp folders.
From: emailmandar@gmail.com Date: Wed, 30 Dec 2015 17:01:09 +0530 To: arm-dev@centos.org Subject: Re: [Arm-dev] Implementing on beaglebone black.
download the image run the install script to a mSD card install mSD card on arm board boot
This approach is already possible with RootFS Build Factory!
- Generate an Image for Qemu using rbf.py. This just an image without
any bootloader. Release this image. 2. Download this image. Install it to your card with rbfinstaller.py. It gives you an option to choose from list of possible boards (Right now, it uses uboot from the github repo)
Regards Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
This thing works on debian, but you need to change /usr/bin/bash to /bin/bash.
I'll change this to just bash.
You need to take out the check for read in the python script, as that is built into debian.
Which read?
I ran into some problems with yum though:
Which xml template are you using? Which version of yum do you have? Which Debian version are you using?
[INFO ] GROUP_INSTALL_ERROR: Error Installing Some Package Groups Retry (y/n)?
What happens if you answer no here?
I'll generate an image right now for beaglebone and test if it builds correctly.
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
The Fedora23 installation instructions have been updated now at:
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Be...
Use that as guidance with the files I provided and let us know if you have C7 on your BBB.
The more we can cut-n-paste from Fedora, the less stumbling around we will do here. (IMNSHO)
Hi Robert,
Using that method, it got hung on the loading kernel:
-Boot 2015.10 (Nov 26 2015 - 14:45:29 -0500)
Watchdog enabled I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - bad CRC, using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 333 bytes read in 35 ms (8.8 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring unknown command: totaltimeout centos Options 1: centos Enter choice: 1 1: centos Retrieving file: /initramfs-4.2.3-200.el7.armv7hl.img 34976246 bytes read in 2043 ms (16.3 MiB/s) Retrieving file: /vmlinuz-4.2.3-200.el7.armv7hl 5866104 bytes read in 375 ms (14.9 MiB/s) append: enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 Retrieving file: /dtb-4.2.3-200.el7.armv7hl/am335x-boneblack.dtb 31457 bytes read in 245 ms (125 KiB/s) Kernel image @ 0x82000000 [ 0x000000 - 0x598278 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8dea4000, end 8ffff1f6 ... OK Loading Device Tree to 8de99000, end 8dea3ae0 ... OK
Starting kernel ...
Steps took:
Flashed Cubie Image Flushed MLO Flashed Uboot (with dd) To: arm-dev@centos.org From: rgm@htt-consult.com Date: Mon, 4 Jan 2016 10:22:42 -0500 Subject: Re: [Arm-dev] Implementing on beaglebone black.
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
The Fedora23 installation instructions have been updated now at:
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Be...
Use that as guidance with the files I provided and let us know if you have C7 on your BBB.
The more we can cut-n-paste from Fedora, the less stumbling around we will do here. (IMNSHO)
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Additionally if i recompile the kernel using Robert C Nelson's scripts, it still does the same thing. It hangs on loading the kernel From: davegermiquet@bell.net To: arm-dev@centos.org Date: Sat, 9 Jan 2016 02:38:18 +0000 Subject: Re: [Arm-dev] Implementing on beaglebone black.
Hi Robert,
Using that method, it got hung on the loading kernel:
-Boot 2015.10 (Nov 26 2015 - 14:45:29 -0500)
Watchdog enabled I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - bad CRC, using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 333 bytes read in 35 ms (8.8 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring unknown command: totaltimeout centos Options 1: centos Enter choice: 1 1: centos Retrieving file: /initramfs-4.2.3-200.el7.armv7hl.img 34976246 bytes read in 2043 ms (16.3 MiB/s) Retrieving file: /vmlinuz-4.2.3-200.el7.armv7hl 5866104 bytes read in 375 ms (14.9 MiB/s) append: enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 Retrieving file: /dtb-4.2.3-200.el7.armv7hl/am335x-boneblack.dtb 31457 bytes read in 245 ms (125 KiB/s) Kernel image @ 0x82000000 [ 0x000000 - 0x598278 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8dea4000, end 8ffff1f6 ... OK Loading Device Tree to 8de99000, end 8dea3ae0 ... OK
Starting kernel ...
Steps took:
Flashed Cubie Image Flushed MLO Flashed Uboot (with dd) To: arm-dev@centos.org From: rgm@htt-consult.com Date: Mon, 4 Jan 2016 10:22:42 -0500 Subject: Re: [Arm-dev] Implementing on beaglebone black.
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello,
I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing.
Do I need an existing arm binary system?
Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image?
The end goal is to have a centos system with Selinux enabled.
The Fedora23 installation instructions have been updated now at:
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Be...
Use that as guidance with the files I provided and let us know if you have C7 on your BBB.
The more we can cut-n-paste from Fedora, the less stumbling around we will do here. (IMNSHO)
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
I might suggest first getting Fedora23 minimal running on your BBB. Make sure what is know to work is working for you.
Go to:
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation
For instructions.
From there we may be able to figure out what is mismatched here with C7-arm and BBB.
On 01/08/2016 09:38 PM, Dave Germiquet wrote:
Hi Robert,
Using that method, it got hung on the loading kernel:
-Boot 2015.10 (Nov 26 2015 - 14:45:29 -0500)
Watchdog enabledI2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - bad CRC, using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 333 bytes read in 35 ms (8.8 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring unknown command: totaltimeout centos Options 1: centos Enter choice: 1 1: centos Retrieving file: /initramfs-4.2.3-200.el7.armv7hl.img 34976246 bytes read in 2043 ms (16.3 MiB/s) Retrieving file: /vmlinuz-4.2.3-200.el7.armv7hl 5866104 bytes read in 375 ms (14.9 MiB/s) append: enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 Retrieving file: /dtb-4.2.3-200.el7.armv7hl/am335x-boneblack.dtb 31457 bytes read in 245 ms (125 KiB/s) Kernel image @ 0x82000000 [ 0x000000 - 0x598278 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8dea4000, end 8ffff1f6 ... OK Loading Device Tree to 8de99000, end 8dea3ae0 ... OK
Starting kernel ...
Steps took:
Flashed Cubie Image Flushed MLO Flashed Uboot (with dd)
To: arm-dev@centos.org From: rgm@htt-consult.com Date: Mon, 4 Jan 2016 10:22:42 -0500 Subject: Re: [Arm-dev] Implementing on beaglebone black.
On 12/28/2015 08:28 PM, Dave Germiquet wrote:
Hello, I am looking into putting Centos on my Beaglebone Black, and I came across your rootfs factory. I'm wondering how it works and what is the high->low level of implementing. Do I need an existing arm binary system? Currently Beaglebone black comes with debian, and my desktop is debian, how would I use your scripts, to make the initial image? The end goal is to have a centos system with Selinux enabled.The Fedora23 installation instructions have been updated now at:
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Be...
Use that as guidance with the files I provided and let us know if you have C7 on your BBB.
The more we can cut-n-paste from Fedora, the less stumbling around we will do here. (IMNSHO)
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Dave Germiquet -
Jeffrey Walton -
Mandar Joshi -
Robert Moskowitz