<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I am starting on a fresh install of the 1611 Cubietruck image. This
time I am running on a Cubietruck, not a Cubieboard2.<br>
<br>
I have the cubietruck uboot on a mSD card and the image installed on
a Kingston 240Gb SSD drive.<br>
<br>
I boot up, log in with root with the default password. All I do is
change /boot/extlinux/extlinux.conf with:<br>
<br>
sed -i -e "s/enforcing=0/enforcing=1/w /dev/stdout"
/boot/extlinux/extlinux.conf<br>
<br>
Note that <a class="moz-txt-link-freetext" href="https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32">https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32</a>
is wrong saying:<br>
<br>
If you want to switch to enforcing mode, you'll have so to first
modify the following files <span class="anchor" id="line-131"></span>/etc/sysconfig/selinux
: change from "permissive" to "enforcing" <span class="anchor"
id="line-132"></span>
<ul>
<li>rpi2/rpi3 : /boot/cmdline.txt: change "enforce=0" to
"enforcing=1" <span class="anchor" id="line-133"></span></li>
<li>other image/board[s]: /boot/extlinux/extlinux.conf : change
the "enforce=0" to "enforce=1" </li>
</ul>
<br>
It is enforcing=0 on the Cubietruck image. Then:<br>
<br>
touch /.autorelabel<br>
<br>
and<br>
<br>
reboot<br>
<br>
I get the log message:<br>
<br>
[ 18.453896] brcmfmac: brcmf_sdio_htclk: HT Avail timeout
(1000000): clkctl 0x50<br>
<br>
*** Warning -- SELinux targeted policy relabel is required.<br>
*** Relabeling could take a very long time, depending on file<br>
*** system size and speed of hard drives.<br>
[ 54.365478] random: nonblocking pool is initialized<br>
Warning: Skipping the following R/O filesystems:<br>
/sys/fs/cgroup<br>
<br>
<br>
Then after some time, it goes through a shutdown, reboots and comes
back to this state. Then reboots again. I have tried this twice.<br>
<br>
Next I will try on my Cubieboard2, that I will have to take down
from its testing position for this test. If it still fails, I will
try a HD. These commands have worked for my on the C2 with a HD and
a mSD card. I don't recall if I have tried them on a CT.<br>
<br>
But any thoughts are appreciated!<br>
<br>
thanks<br>
<br>
</body>
</html>