Re: Cubietruck SOA install failure.
If you use Triode's Cubietruck install image
https://github.com/SqueezeOnArch/soa-installers/raw/master/soa-image-cubietruck.img.zip,
then a script runs called "create-sdcard-soa-cubietruck.sh", part of
which is to build a first boot script and systemd service -
"soa-firstboot.sh" & "soa-firstboot.service". The output of the failed
Cubietruck install shows a point has been reached near the end of the
first boot script around this code:
Code:
--------------------
systemctl enable avahi-daemon
pushd /boot
cp script.bin script.bin.orig
bin2fex script.bin > script.fex
sed -i -e "/screen0_output_type/c screen0_output_type = 3" script.fex
sed -i -e "/screen0_output_mode/c screen0_output_mode = 10" script.fex
sed -i -e "/fb0_width/c fb0_width = 1920" script.fex
sed -i -e "/fb0_height/c fb0_height = 1080" script.fex
fex2bin script.fex > script.bin
popd
if (pacman -Qq soa-web); then
systemctl disable soa-firstboot.service
echo SOA Install Complete
fi
sync
sleep 2
reboot
--------------------
Whether the soa-web service fails or not, the test "pacman -Qq soa-web"
is true so the line "echo SOA Install Complete" is reached and that
message appears in the output you've both posted. The previous section
re: script.bin is is generating errors for some reason. For the
Cubietruck to successfully boot, it needs a functioning script.bin on
its boot partition, this doesn't look as if it's being created
correctly. I think this is the problem.
------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
