Originally Posted by AapoRantalainen

[On-Topic]
This script is amazing!

Originally Posted by AapoRantalainen

Couple of remarks, for motivating others.

1) Works with Ubuntu-14.10
Needed tools:

Code:

#For compiling kernel
sudo apt-get install qemu-user-static gcc-arm-none-eabi
#For preparing card
sudo apt-get install debootstrap

Gcc in Ubuntu fails with same error than Debian. Downgrade e.g. http://se.archive.ubuntu.com/ubuntu/...arm-none-eabi/ (reported: https://bugs.launchpad.net/ubuntu/+s...i/+bug/1390912)

Originally Posted by AapoRantalainen

I'm first testing

Code:

debian.conf
-ARCH=armhf
+ARCH=armel

2) During debootstap it asks what locales to generate. And timezone. Could these be in config file? (-> Even more batch run)

Originally Posted by AapoRantalainen

3) My Fremantle could not read EXT4, so step "run configure_u-boot.sh" must be skipped and do manually uboot.item.

Originally Posted by AapoRantalainen

4) My first build was unusable, because even it associated with wireless access point, it never asked IP. So I made another build with added package isc-dhcp-client for dhclient. (Is this essential package or what is correct solution?)

Originally Posted by AapoRantalainen

Also

Code:

-EDITOR=vim
+EDITOR=nano

would be easier (no editor-war =) )

Originally Posted by AapoRantalainen

5) issue: shutting down jessie (init 0 or shutdown -hP now) will not shut device down. I don't know what state it is but it can't be started with power button. Battery must be taken off.

Originally Posted by AapoRantalainen

6) issue: File system gets corrupted often when doing apt-get update or install.
Command stops at

Code:

Error writing to output file - write (30: Read-only file system)

And dmesg shows:

Code:

[  560.576171] EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:4887: Out of memory
[  560.597259] Aborting journal on device mmcblk0p1-8.
[  560.607391] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
[  560.613403] EXT4-fs error (device mmcblk0p1) in ext4_dirty_inode:5006: IO failure
[  560.619506] EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:56: Detected aborted journal

I'm currently working with one SD-card and one N900-device, and I don't know if they are fault.

Originally Posted by AapoRantalainen

6b) Can't trigger fsck with

Code:

shutdown -rF 0

or

Code:

touch /forcefsck

I must remove card for fixing filesystem. And because device is not shutting down it needs also battery removal every time.