Man in a van wrote:
> Well,
>
> I have tried another install and SSH'd into the cubietruck, but then
> realised I did not knowthe command line instruction to see what was
> happening.:mad:
>
> I have attached a copy of the text displayed during the install (must be
> similar, I would think) and the "_*-failure-*_" word can be seen towards
> the end.
>
> atb
>
> Ronnie
Ronnie,
Don't know if you are prepared to try this again. Once connected via
SSH, and before you "Accept installer disclaimer" that shows on the
initial Web installer, this command should show what's happening:
Code:
--------------------
journalctl -f
--------------------
I had another look at Triode's cubietruck installer image and what ever
else might be going wrong, there's certainly one obvious error now. The
installer images runs a script which includes setting some initial
values:
Code:
--------------------
#!/bin/bash
CARD=$1
HOSTNAME="soa-cubietruck"
FS_TAR=ArchLinuxARM-sun7i-latest.tar.gz
UBOOT_TAR=*uboot-cubietruck-2014.04-10-armv7h.pkg.tar.xz*
FIRMWARE=ap6210.zip
FIRMWARE_URL="http://dl.cubieforums.com/patwood/$FIRMWARE";
IMAGE="soa-image-cubietruck"
IMAGE_URL="https://github.com/SqueezeOnArch/soa-installers/raw/master/$IMAGE.img.zip";
--------------------
Later in the script The UBOOT file is downloaded and written to the SD
card:
Code:
--------------------
echo "Fetching uboot"
wget "http://mirror.archlinuxarm.org/armv7h/alarm/$UBOOT_TAR";
echo "Writing uboot"
tar -xf $UBOOT_TAR -C mnt --exclude='.PKGINFO' --exclude='.MTREE'
--exclude='.INSTALL'
sync
dd if=mnt/boot/u-boot-sunxi-with-spl.bin of=$CARD bs=1024 seek=8
sync
--------------------
No doubt Triode had good reason to hard code this file name, but it's
changed and no longer exists at
http://mirror.archlinuxarm.org/armv7h/alarm/
The latest version is uboot-cubietruck-2015.01-5-armv7h.pkg.tar.xz
The second snippet of code above does not include any test to see if the
UBOOT download failed or not, so the script just proceeds regardless.
If it failed the install should abort with a message. Triode could
easily sort this out. In the meantime, the UBOOT file name can be fixed
manually by editing this script, It's easy to do in Linux as root:
1. Mount installer img as a loop device, eg:
Code:
--------------------
mount -o loop,offset=$((2048*512)) soa-image-cubietruck.img /mnt
--------------------
2. Navigate to install scripts directory:
Code:
--------------------
cd /mnt/scripts
--------------------
3. Use your preferred editor to change the UBOOT file name in
create-sdcard-soa-cubietruck.sh e.g:
Code:
--------------------
nano create-sdcard-soa-cubietruck.sh
--------------------
At line 5, change
"UBOOT_TAR=uboot-cubietruck-2014.04-10-armv7h.pkg.tar.xz" to
"UBOOT_TAR=uboot-cubietruck-2015.01-5-armv7h.pkg.tar.xz" , and save the
change.
(This is correct at time of writing, it may change at any time, so check
for current name here: http://mirror.archlinuxarm.org/armv7h/alarm/ )
4. Umount img, e.g :
Code:
--------------------
cd /
umount /mnt
--------------------
5. Write modified installer img to SD card as normal.
Hopefully, you or someone else can make this change and re-test the
installer and see if the failure was due to this simple 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
