wildcat_paris Posted January 2, 2016 Posted January 2, 2016 (edited) @Igor Thanks for b53... I nearly achieved the quick fix last night... my mistake: b53 needs to be included in the kernel, not as a module EDIT: Also, as you have added the patch in "lib" & I didn't remove the same patch from "userpatches", the patch was not applied twice (same file name), cool @zador : "Zador j'adore" (like Dior perfume commercial) I like Zador Edited January 2, 2016 by wildcat_paris silly joke 1
wildcat_paris Posted January 2, 2016 Posted January 2, 2016 for some days already, on sunxi-dev, after [ o.k. ] Extracting trusty from cache [ 7 days old ] in the "Force package update ..." box I get plenty of W: Failed to fetch http://ports.ubuntu.com/dists/trusty-security/Release.gpg Could not resolve 'ports.ubuntu.com' W: Failed to fetch http://apt.armbian.com/dists/trusty/Release.gpg Could not resolve 'apt.armbian.com' The image build does not failed but I haven't tested the image, only the debs. NOTE: not related to local DNS because I can ping both machines
zador.blood.stained Posted January 2, 2016 Author Posted January 2, 2016 7 days old cache? Maybe something's up with /etc/resolv.conf (or /etc/nsswitch.conf) inside cached rootfs? Try building without rootfs cache. Edit: /etc/resolv.conf is created or changed in install_kernel, so if for some reason it is not present in cached rootfs, DNS resolving in chroot won't work. 1
Igor Posted January 2, 2016 Posted January 2, 2016 I also encounter this problem today. Trusty only. I think i add a hack to fix this once ... creating resolv.conf with 8.8.8.8 Edit: https://github.com/igorpecovnik/lib/blob/master/boards.sh#L161-L163 Putting this to both debootstraps should solve the issue. Fixed: https://github.com/igorpecovnik/lib/commit/fae68084c0269a5739af0480695c2fdeb28e297d
zador.blood.stained Posted January 2, 2016 Author Posted January 2, 2016 Putting this to both debootstraps should solve the issue. Second debootstrap doesn't update file lists after extracting cached rootfs (for now at least). And now since installation of all distribution-specific and desktop-specific packages was moved into main debootstrap function, updating packages lists may not be needed at all. Anyway I'll check later if this hack is needed only for trusty or other distribution may be affected and I'll update my debootstrap code too.
wildcat_paris Posted January 3, 2016 Posted January 3, 2016 @Zador I've removed trusty.tgz (which then adds 110 minutes @home to the Armbian image making process) and *no* error messages @Igor @Zador I have my first fully running Armbian dev "4.81" (ok "next" is version "5.00"!) with kernel 4.4.0-rc6 and surprise, the patches from Corentin LABBE for AXP are working *now* http://sunxi.montjoie.ovh/patchs_current/ $ sensors axp209-isa-0000 Adapter: ISA adapter ACIN: +5.05 V VBUS: +0.00 V BATT: +1.52 V APS: +4.91 V CHIP: +50.4°C BATT: 0.00 W ACIN: +0.81 A VBUS: +0.00 A BATT_CHRG: +0.00 A BATT_DISCHRG: +0.01 A sun4i_ts-isa-0000 Adapter: ISA adapter SoC temperature: +39.1°C 1
zador.blood.stained Posted January 3, 2016 Author Posted January 3, 2016 (which then adds 110 minutes @home to the Armbian image making process) For me without rootfs cache this (old debootstrap) [ o.k. ] Create and sign [ Armbian_4.81_Cubietruck_Debian_wheezy_3.4.110.zip ] [ o.k. ] Runtime [ 73 min ] turns into this (new debootstrap, again, no rootfs cache) [ o.k. ] Signing and compressing [ Armbian_4.81_Cubietruck_Debian_wheezy_3.4.110.zip ] [ o.k. ] Done building [ /home/zador/armbian/output/images/Armbian_4.81_Cubietruck_Debian_wheezy_3.4.110.zip ] [ o.k. ] Runtime [ 16 min ] so there may be some small improvements, depending on storage type (SSD or mechanical HDD), available RAM and internel connection speed. *no* error messages Yes, resolv.conf was symlinked to /run/resolvconf/... and this dir is excluded in rootfs cache. Anyway, fixed by Igor now. 1
wildcat_paris Posted January 3, 2016 Posted January 3, 2016 so there may be some small improvements, depending on storage type (SSD or mechanical HDD), available RAM and internel connection speed. Yes, resolv.conf was symlinked to /run/resolvconf/... and this dir is excluded in rootfs cache. Anyway, fixed by Igor now. yes I am using a dedicated HDD (for the Armbian tool VM) with Virtualbox on top of Trusty/amd64, the Virtualbox VM crashes from time to time (compared to Virtualbox on Win7_64 which is quite stable)... ok I have a couple of free for use SSD @hands but rootfs cache is good enough!
zador.blood.stained Posted January 3, 2016 Author Posted January 3, 2016 ok I have a couple of free for use SSD @hands but rootfs cache is good enough! tmpfs is faster in any case But for me at this point lack of CPU power is the only thing that still makes using cached rootfs faster than making it from scratch 1
wildcat_paris Posted January 5, 2016 Posted January 5, 2016 guys, is it intended (bold), please ? or KERNEL_DEV ? # Kernel KERNEL_DEFAULT='https://github.com/linux-sunxi/linux-sunxi' KERNEL_DEFAULT_BRANCH="sunxi-3.4" KERNEL_DEFAULT_SOURCE="linux-sunxi" KERNEL_NEXT='git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git' [ "$USE_MAINLINE_GOOGLE_MIRROR" = "yes" ] && KERNEL_NEXT='https://kernel.googlesource.com/pub/scm/linux/kernel/git/ KERNEL_NEXT_BRANCH="v"`wget -qO- https://www.kernel.org/finger_banner| grep "The latest st" | awk '{print $NF}' | KERNEL_NEXT_SOURCE="linux-vanilla" KERNEL_DEV='git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git' [ "$USE_MAINLINE_GOOGLE_MIRROR" = "yes" ] && KERNEL_NEXT='https://kernel.googlesource.com/pub/scm/linux/kernel/git/ KERNEL_DEV_BRANCH="" KERNEL_DEV_SOURCE="linux-vanilla" btw, stable seems stalled @v4.4-rc6 I move to http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/refs/tags/
zador.blood.stained Posted January 5, 2016 Author Posted January 5, 2016 @wildcat_paris Bug, already fixed, but didn't push changes to github, partly because it actually doesn't break anything. 1
zador.blood.stained Posted January 8, 2016 Author Posted January 8, 2016 @Igor, what do you think about moving MAINTAINER, MAINTAINERMAIL, GPG_PASS and maybe ROOTPWD to configuration.sh or to main.sh - to keep compile.sh small and simple, I don't think these options are useful to people who just want to compile new kernel. 1
wildcat_paris Posted January 9, 2016 Posted January 9, 2016 (edited) (moved from another thread about LUKS dmcrypt) @Igor I enabled a bunch of missing crypto features for sunxi-dev branch, please enable those options on other branches. As with my test on lamobo-r1, you can enable NEON and anything for Cortex A7 crypto # At least one emulation must be selected # CONFIG_VFP=y CONFIG_VFPv3=y CONFIG_NEON=y CONFIG_KERNEL_MODE_NEON=y as well as the crypto # Security options # CONFIG_KEYS=y # CONFIG_PERSISTENT_KEYRINGS is not set # CONFIG_BIG_KEYS is not set CONFIG_ENCRYPTED_KEYS=y # CONFIG_SECURITY_DMESG_RESTRICT is not set # CONFIG_SECURITY is not set # CONFIG_SECURITYFS is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_XOR_BLOCKS=y CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_ASYNC_PQ=m CONFIG_ASYNC_RAID6_RECOV=m CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_RNG_DEFAULT=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_AKCIPHER2=y CONFIG_CRYPTO_AKCIPHER=y CONFIG_CRYPTO_RSA=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y CONFIG_CRYPTO_GF128MUL=y CONFIG_CRYPTO_NULL=y CONFIG_CRYPTO_NULL2=y CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=y CONFIG_CRYPTO_MCRYPTD=m CONFIG_CRYPTO_AUTHENC=y CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=y # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_CHACHA20POLY1305=y CONFIG_CRYPTO_SEQIV=y CONFIG_CRYPTO_ECHAINIV=m # # Block modes # CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=y CONFIG_CRYPTO_CTS=y CONFIG_CRYPTO_ECB=y # CONFIG_CRYPTO_LRW is not set CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=y CONFIG_CRYPTO_KEYWRAP=m # # Hash modes # CONFIG_CRYPTO_CMAC=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m # # Digest # CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRCT10DIF=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_POLY1305=y CONFIG_CRYPTO_MD4=y CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=y CONFIG_CRYPTO_RMD160=y CONFIG_CRYPTO_RMD256=y CONFIG_CRYPTO_RMD320=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_SHA512=y CONFIG_CRYPTO_TGR192=y CONFIG_CRYPTO_WP512=y # # Ciphers # CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_ANUBIS=y CONFIG_CRYPTO_ARC4=y CONFIG_CRYPTO_BLOWFISH=y CONFIG_CRYPTO_BLOWFISH_COMMON=y CONFIG_CRYPTO_CAMELLIA=y CONFIG_CRYPTO_CAST_COMMON=y CONFIG_CRYPTO_CAST5=y CONFIG_CRYPTO_CAST6=y CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_FCRYPT=y CONFIG_CRYPTO_KHAZAD=y CONFIG_CRYPTO_SALSA20=y CONFIG_CRYPTO_CHACHA20=y CONFIG_CRYPTO_SEED=y CONFIG_CRYPTO_SERPENT=y CONFIG_CRYPTO_TEA=y CONFIG_CRYPTO_TWOFISH=y CONFIG_CRYPTO_TWOFISH_COMMON=y # # Compression # CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_ZLIB=y CONFIG_CRYPTO_LZO=y CONFIG_CRYPTO_842=y CONFIG_CRYPTO_LZ4=y CONFIG_CRYPTO_LZ4HC=y # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=y CONFIG_CRYPTO_DRBG_MENU=y CONFIG_CRYPTO_DRBG_HMAC=y CONFIG_CRYPTO_DRBG_HASH=y CONFIG_CRYPTO_DRBG_CTR=y CONFIG_CRYPTO_DRBG=y CONFIG_CRYPTO_JITTERENTROPY=y CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_USER_API_RNG=m CONFIG_CRYPTO_USER_API_AEAD=m CONFIG_CRYPTO_HASH_INFO=y CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_SUN4I_SS=y CONFIG_CRYPTO_DEV_SUN4I_SS_PRNG=y CONFIG_ASYMMETRIC_KEY_TYPE=m CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=m CONFIG_PUBLIC_KEY_ALGO_RSA=m CONFIG_X509_CERTIFICATE_PARSER=m # CONFIG_PKCS7_MESSAGE_PARSER is not set # # Certificates for signature checking # CONFIG_SYSTEM_TRUSTED_KEYRING=y CONFIG_SYSTEM_TRUSTED_KEYS="" CONFIG_ARM_CRYPTO=y CONFIG_CRYPTO_SHA1_ARM=y CONFIG_CRYPTO_SHA1_ARM_NEON=y CONFIG_CRYPTO_SHA1_ARM_CE=m CONFIG_CRYPTO_SHA2_ARM_CE=m CONFIG_CRYPTO_SHA256_ARM=y CONFIG_CRYPTO_SHA512_ARM=y CONFIG_CRYPTO_AES_ARM=y CONFIG_CRYPTO_AES_ARM_BS=y CONFIG_CRYPTO_AES_ARM_CE=m CONFIG_CRYPTO_GHASH_ARM_CE=m # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_RAID6_PQ=y CONFIG_BITREVERSE=y CONFIG_HAVE_ARCH_BITREVERSE=y CONFIG_RATIONAL=y CONFIG_GENERIC_STRNCPY_FROM_USER=y CONFIG_GENERIC_STRNLEN_USER=y CONFIG_GENERIC_NET_UTILS=y CONFIG_GENERIC_PCI_IOMAP=y CONFIG_GENERIC_IO=y CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y CONFIG_CRC_CCITT=y CONFIG_CRC16=y CONFIG_CRC_T10DIF=m CONFIG_CRC_ITU_T=y CONFIG_CRC32=y CONFIG_CRC32_SELFTEST=y CONFIG_CRC32_SLICEBY8=y # CONFIG_CRC32_SLICEBY4 is not set # CONFIG_CRC32_SARWATE is not set # CONFIG_CRC32_BIT is not set CONFIG_CRC7=m CONFIG_LIBCRC32C=y CONFIG_CRC8=m # CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set CONFIG_RANDOM32_SELFTEST=y CONFIG_842_COMPRESS=y CONFIG_842_DECOMPRESS=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_LZ4_COMPRESS=y CONFIG_LZ4HC_COMPRESS=y CONFIG_LZ4_DECOMPRESS=y CONFIG_XZ_DEC=y CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y CONFIG_XZ_DEC_TEST=m CONFIG_DECOMPRESS_GZIP=y CONFIG_DECOMPRESS_BZIP2=y CONFIG_DECOMPRESS_LZMA=y CONFIG_DECOMPRESS_XZ=y CONFIG_DECOMPRESS_LZO=y CONFIG_DECOMPRESS_LZ4=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_ASSOCIATIVE_ARRAY=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT_MAP=y CONFIG_HAS_DMA=y CONFIG_CPUMASK_OFFSTACK=y CONFIG_CPU_RMAP=y CONFIG_DQL=y CONFIG_GLOB=y # CONFIG_GLOB_SELFTEST is not set just in case my whole config for 4.4-rc8 (needs the PRNG patch for A20) EDIT: NEON related [ 0.013562] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 4 [ 0.014834] xor: measuring software checksum speed [ 0.110001] arm4regs : 1243.600 MB/sec [ 0.210054] 8regs : 772.000 MB/sec [ 0.310110] 32regs : 792.400 MB/sec [ 0.410166] neon : 1162.400 MB/sec [ 0.410175] xor: using function: arm4regs (1243.600 MB/sec) [ 0.650868] raid6: int32x1 gen() 138 MB/s [ 0.820707] raid6: int32x1 xor() 111 MB/s [ 0.990812] raid6: int32x2 gen() 185 MB/s [ 1.160982] raid6: int32x2 xor() 120 MB/s [ 1.331052] raid6: int32x4 gen() 197 MB/s [ 1.501242] raid6: int32x4 xor() 122 MB/s [ 1.671257] raid6: int32x8 gen() 179 MB/s [ 1.841357] raid6: int32x8 xor() 116 MB/s [ 2.011385] raid6: neonx1 gen() 436 MB/s [ 2.181466] raid6: neonx1 xor() 324 MB/s [ 2.351636] raid6: neonx2 gen() 577 MB/s [ 2.521708] raid6: neonx2 xor() 423 MB/s [ 2.691842] raid6: neonx4 gen() 707 MB/s [ 2.861897] raid6: neonx4 xor() 480 MB/s [ 3.032095] raid6: neonx8 gen() 640 MB/s [ 3.202164] raid6: neonx8 xor() 451 MB/s [ 3.202172] raid6: using algorithm neonx4 gen() 707 MB/s [ 3.202179] raid6: .... xor() 480 MB/s, rmw enabled [ 3.202185] raid6: using intx1 recovery algorithm Edited January 9, 2016 by wildcat_paris neon stuff added
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 @Igor @Zador Igor : I decided to drop idea to put an AC card into the board since it's simply too problematic and expensive (66USD). This card doesn't have support in legacy kernel, in 4.4 have no idea if everything else already works + I have only one AC device in the lab. todo? it would not cost much to activate the kernel next/dev the "Minstrel 802.11ac support" (I tested it once with my dummy Alfa "AC")
Igor Posted January 10, 2016 Posted January 10, 2016 (edited) todo? it would not cost much to activate the kernel next/dev the "Minstrel 802.11ac support" (I tested it once with my dummy Alfa "AC") Kernel 4.x for ClearFog is not quite ready yet. I built 4.3.3 yesterday and yes PCI is working but haven't saw Ethernet phy which is somehow essential for a router board 60 euros for this AC card is also too much in beer fresh expensive Zadorland bottled sparkling water, otherwise named "free-alcohol beer" or Perrier. Edit: This AC card, even I would get it working in Linux, is a dead meat for me since my other wireless equipment is basic. Edited January 10, 2016 by wildcat_paris Armbian is alcohol free by design, btw it doesn't reply my "Minstrel 802.11ac support" remark... Igor has his new baby board -- signed: zealous moderator
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 @AnyFox is debootstrap-ng ready for 2 partitions yet? several tests, removed all the files dpkg-deb: building package `linux-firmware-image-odroidxu4' in `../linux-firmware-image-odroidxu4_4.83_armhf.deb'. dpkg-deb: building package `linux-dtb-odroidxu4' in `../linux-dtb-odroidxu4_4.83_armhf.deb'. dpkg-deb: building package `linux-headers-odroidxu4' in `../linux-headers-odroidxu4_4.83_armhf.deb'. dpkg-deb: building package `linux-image-odroidxu4' in `../linux-image-odroidxu4_4.83_armhf.deb'. [ o.k. ] Creating board support package. [ odroidxu4 ] [ o.k. ] Fingerprinting. [ Armbian 4.83 Odroidxu4 Ubuntu trusty default Linux 3.10.94 ] [ o.k. ] Building deb package. [ linux-trusty-root-odroidxu4_4.83_armhf.deb ] [ o.k. ] Starting build process for [ odroidxu4 trusty ] [ o.k. ] Extracting trusty-ng.tgz [ 0 days old ] trusty-ng.tgz: 176MB [51.2MB/s] [===================================================================================================>] 100% [ o.k. ] Fixing release custom applications. [ trusty ] [ o.k. ] Installing kernel, u-boot and board specific [ trusty odroidxu4 ] [ o.k. ] Install kernel [ linux-image-odroidxu4_4.83_armhf.deb ] [ o.k. ] Install u-boot [ linux-u-boot-odroidxu4_4.83_armhf.deb ] [ o.k. ] Install headers [ linux-headers-odroidxu4_4.83_armhf.deb ] [ o.k. ] Install firmware [ linux-firmware-image-odroidxu4_4.83_armhf.deb ] [ o.k. ] Install DTB [ linux-dtb-odroidxu4_4.83_armhf.deb ] (Reading database ... 39326 files and directories currently installed.) Removing lirc (0.9.0-0ubuntu5) ... runlevel:/var/run/utmp: No such file or directory invoke-rc.d: policy-rc.d denied execution of stop. [ o.k. ] Creating boot scripts [ odroidxu4 ] [ o.k. ] Adjusting boot scripts [ odroidxu4 ] [ o.k. ] Installing external applications [ USB redirector ] [ o.k. ] Installing external applications [ RT8192 driver ] [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] Preparing image file for rootfs [ odroidxu4 trusty ] [ o.k. ] Current rootfs size [ 673 MiB ] [ o.k. ] Creating blank image for rootfs [ 1025 MiB ] 1GB [93.7MB/s] [==================================================================================================================>] 100% [ o.k. ] Creating partitions [ /boot: fat root: ext4 ] losetup: invalid option -- 'P' Usage: losetup loop_device give info losetup -a | --all list all used losetup -d | --detach <loopdev> [<loopdev> ...] delete losetup -f | --find find unused losetup -c | --set-capacity <loopdev> resize losetup -j | --associated <file> [-o <num>] list all associated with <file> losetup [options] {-f|--find|loopdev} <file> setup Options: -e, --encryption <type> enable data encryption with specified <name/num> -h, --help this help -o, --offset <num> start at offset <num> into file --sizelimit <num> loop limited to only <num> bytes of the file -p, --pass-fd <num> read passphrase from file descriptor <num> -r, --read-only setup read-only loop device --show print device name (with -f <file>) -N | --nohashpass Do not hash the given password (Debian hashes) -k | --keybits <num> specify number of bits in the hashed key given to the cipher. Some ciphers support several key sizes and might be more efficient with a smaller key size. Key sizes < 128 are generally not recommended -v, --verbose verbose mode mkfs.fat 3.0.26 (2014-03-07) mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows /dev/loop0p1: No such file or directory Could not stat /dev/loop0p2 --- No such file or directory The device apparently does not exist; did you specify it correctly? mount: special device /dev/loop0p2 does not exist mount: special device /dev/loop0p1 does not exist [ o.k. ] Copying files to image [ tmprootfs.raw ] 620.37M 99% 72.26MB/s 0:00:08 (xfr#34740, to-chk=0/43498) sent 622.99M bytes received 698.87K bytes 73.38M bytes/sec total size is 623.97M speedup is 1.00 sed: can't read /home/gr/armbian/output/cache/mount/boot/boot.cmd: No such file or directory mkimage: Can't stat /home/gr/armbian/output/cache/mount/boot/boot.cmd: No such file or directory tmpfs 1.2G 673M 528M 57% /home/gr/armbian/output/cache/sdcard [ o.k. ] Writing bootloader [ /dev/loop0 ] [ error ] U-boot failed to install [ @host ]
zador.blood.stained Posted January 10, 2016 Author Posted January 10, 2016 I see... losetup -P option must be missing in Trusty Will fix in a moment Edit: Fixed Edit 2: Tested. Should work if boot partition size is increased to 32M to have enough space for 2 copies of zImage (I mean for all devices that have FAT /boot partition). @wildcat_paris Armbian is alcohol free sudo apt-get install wine not exactly, since you can add some wine to it 1
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 @AnyFox I guess you already know about uboot 16.01-rc4 and lamobo-r1 https://github.com/db260179/openwrt-bpi-r1/releases/tag/v1.1-stable-bpi-r1-openwrt @Zador already too much wine for Armbian I wanted to test but I am stuck @ [ o.k. ] ... updating [ linux-vanilla ] remote: Counting objects: 4421354, done. remote: Compressing objects: 100% (733075/733075), done. Receiving objects: 3% (154000/4421354), 65.41 MiB | 10.00 KiB/s
zador.blood.stained Posted January 10, 2016 Author Posted January 10, 2016 @wildcat_paris try USE_MAINLINE_GOOGLE_MIRROR=yes for me git.kernel.org is painfully slow (with any protocol) comparing to github or googlesource.com Edit: Probably you'll have to delete partially downloaded mainline kernel sources
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 (edited) @Zador sure! you are right. but I forgot to config my favorite git in configuration.sh #KERNEL_DEV='git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git' KERNEL_DEV='git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git' it is slow but limited to the latest tags for DEV Edited January 10, 2016 by wildcat_paris too slow... thanks Zador KERNEL_DEV='https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux'
zador.blood.stained Posted January 10, 2016 Author Posted January 10, 2016 Then it may be KERNEL_DEV='https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux' or KERNEL_DEV='https://github.com/torvalds/linux.git' 1
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 (edited) @Zador googlesource/torvard works like a charm (RX=5MB/s). thanks! I have applied your configuration-ng patch, some polish needed for trusty??? ("losetup: invalid option -- 'P'"???) dpkg-deb: building package `linux-firmware-image-dev-sunxi' in `../linux-firmware-image-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-dtb-dev-sunxi' in `../linux-dtb-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-headers-dev-sunxi' in `../linux-headers-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-image-dev-sunxi' in `../linux-image-dev-sunxi_4.83_armhf.deb'. dpkg-genchanges: warning: package linux-libc-dev-dev-sunxi in control file but not in files list dpkg-genchanges: binary-only upload - not including any source code [ o.k. ] Creating board support package. [ lamobo-r1 ] [ o.k. ] Fingerprinting. [ Armbian 4.83 Lamobo-r1 Ubuntu trusty dev Linux 4.4.0-rc8 ] [ o.k. ] Building deb package. [ linux-trusty-root-lamobo-r1_4.83_armhf.deb ] [ o.k. ] Starting build process for [ lamobo-r1 trusty ] [ o.k. ] Extracting trusty-ng.tgz [ 0 days old ] trusty-ng.tgz: 176MB [45.3MB/s] [===================================================================================================>] 100% [ o.k. ] Fixing release custom applications. [ trusty ] [ o.k. ] Installing kernel, u-boot and board specific [ trusty lamobo-r1 ] [ o.k. ] Install kernel [ linux-image-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install u-boot [ linux-u-boot-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install headers [ linux-headers-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install firmware [ linux-firmware-image-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install DTB [ linux-dtb-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Creating boot scripts [ lamobo-r1 ] [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] Preparing image file for rootfs [ lamobo-r1 trusty ] [ o.k. ] Current rootfs size [ 673 MiB ] [ o.k. ] Creating blank image for rootfs [ 1004 MiB ] 1e+03MB [ 102MB/s] [=================================================================================================================>] 100% [ o.k. ] Creating partitions [ root: ext4 ] losetup: invalid option -- 'P' Usage: losetup loop_device give info losetup -a | --all list all used losetup -d | --detach <loopdev> [<loopdev> ...] delete losetup -f | --find find unused losetup -c | --set-capacity <loopdev> resize losetup -j | --associated <file> [-o <num>] list all associated with <file> losetup [options] {-f|--find|loopdev} <file> setup Options: -e, --encryption <type> enable data encryption with specified <name/num> -h, --help this help -o, --offset <num> start at offset <num> into file --sizelimit <num> loop limited to only <num> bytes of the file -p, --pass-fd <num> read passphrase from file descriptor <num> -r, --read-only setup read-only loop device --show print device name (with -f <file>) -N | --nohashpass Do not hash the given password (Debian hashes) -k | --keybits <num> specify number of bits in the hashed key given to the cipher. Some ciphers support several key sizes and might be more efficient with a smaller key size. Key sizes < 128 are generally not recommended -v, --verbose verbose mode [ o.k. ] Copying files to image [ tmprootfs.raw ] 617.72M 99% 60.90MB/s 0:00:09 (xfr#35708, to-chk=0/44798) sent 620.41M bytes received 718.69K bytes 59.16M bytes/sec total size is 621.32M speedup is 1.00 tmpfs 1.2G 673M 528M 57% /home/gr/armbian/output/cache/sdcard /dev/loop0p1 972M 699M 208M 78% /home/gr/armbian/output/cache/mount [ o.k. ] Writing bootloader [ /dev/loop0 ] [ o.k. ] Signing and compressing [ Armbian_4.83_Lamobo-r1_Ubuntu_trusty_4.4.0-rc8.zip ] [ o.k. ] Done building [ /home/gr/armbian/output/images/Armbian_4.83_Lamobo-r1_Ubuntu_trusty_4.4.0-rc8.zip ] [ o.k. ] Runtime [ 6 min ] Edited January 10, 2016 by wildcat_paris Zador : patch badly applied
zador.blood.stained Posted January 10, 2016 Author Posted January 10, 2016 It didn't apply or it was force overwritten, There shouldn't be -P option now. 1
wildcat_paris Posted January 10, 2016 Posted January 10, 2016 (edited) @Zador I just forgot to remove/comment the line with "losetup -P" otherwise the process is fine -- my BAD dpkg-deb: building package `linux-firmware-image-dev-sunxi' in `../linux-firmware-image-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-dtb-dev-sunxi' in `../linux-dtb-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-headers-dev-sunxi' in `../linux-headers-dev-sunxi_4.83_armhf.deb'. dpkg-deb: building package `linux-image-dev-sunxi' in `../linux-image-dev-sunxi_4.83_armhf.deb'. dpkg-genchanges: warning: package linux-libc-dev-dev-sunxi in control file but not in files list dpkg-genchanges: binary-only upload - not including any source code [ o.k. ] Creating board support package. [ lamobo-r1 ] [ o.k. ] Fingerprinting. [ Armbian 4.83 Lamobo-r1 Ubuntu trusty dev Linux 4.4.0-rc8 ] [ o.k. ] Building deb package. [ linux-trusty-root-lamobo-r1_4.83_armhf.deb ] [ o.k. ] Starting build process for [ lamobo-r1 trusty ] [ o.k. ] Extracting trusty-ng.tgz [ 0 days old ] trusty-ng.tgz: 176MB [ 52MB/s] [===================================================================================================>] 100% [ o.k. ] Fixing release custom applications. [ trusty ] [ o.k. ] Installing kernel, u-boot and board specific [ trusty lamobo-r1 ] [ o.k. ] Install kernel [ linux-image-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install u-boot [ linux-u-boot-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install headers [ linux-headers-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install firmware [ linux-firmware-image-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Install DTB [ linux-dtb-dev-sunxi_4.83_armhf.deb ] [ o.k. ] Creating boot scripts [ lamobo-r1 ] [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] Preparing image file for rootfs [ lamobo-r1 trusty ] [ o.k. ] Current rootfs size [ 673 MiB ] [ o.k. ] Creating blank image for rootfs [ 1004 MiB ] 1e+03MB [79.2MB/s] [=================================================================================================================>] 100% [ o.k. ] Creating partitions [ root: ext4 ] [ o.k. ] Copying files to image [ tmprootfs.raw ] 617.72M 99% 62.20MB/s 0:00:09 (xfr#35708, to-chk=0/44798) sent 620.41M bytes received 718.65K bytes 65.38M bytes/sec total size is 621.32M speedup is 1.00 tmpfs 1.2G 673M 528M 57% /home/gr/armbian/output/cache/sdcard /dev/loop0p1 972M 699M 208M 78% /home/gr/armbian/output/cache/mount [ o.k. ] Writing bootloader [ /dev/loop0 ] [ o.k. ] Signing and compressing [ Armbian_4.83_Lamobo-r1_Ubuntu_trusty_4.4.0-rc8.zip ] [ o.k. ] Done building [ /home/gr/armbian/output/images/Armbian_4.83_Lamobo-r1_Ubuntu_trusty_4.4.0-rc8.zip ] [ o.k. ] Runtime [ 6 min ] Edited January 10, 2016 by wildcat_paris edit : like a charm => spoiler 1
zador.blood.stained Posted January 11, 2016 Author Posted January 11, 2016 @all FYI, kernel 4.4.0 is out Tested USB OTG on cubietruck; OTG autodetect and vbus (automatically enabling power on OTG port when OTG cable is plugged in) works with some extra kernel modules, will upload my kernel config later. As a side-effect, I can use onboard miniUSB port as a serial console (only after systemd starts necessary getty service, of course). Onboard audio works if DMA driver is loaded via /etc/modules or if it's compiled as built-in. Edit: extras for /etc/modules: # sunxi musb OTG sunxi # serial gadget (old) driver - required g_serial # ACM - for serial port emulation usb_f_acm Edit 2: For Debian Jessie (or stretch) gadget serial device name is /dev/ttyGS0, so command to enable it would be sudo systemctl enable getty@ttyGS0.service 3
Igor Posted January 13, 2016 Posted January 13, 2016 @zador https://github.com/igorpecovnik/lib/commit/7c1f7c548007d3238a6111f35750b795b4d94c38 boot-next.cmd fell out by mistake? I recreate it in next commit ...
zador.blood.stained Posted January 13, 2016 Author Posted January 13, 2016 @Igor I switched to using (and editing if needed) "standart" boot.cmd, since using "next" would break images for all boards that don't use mainline u-boot or use extra kernel parameters, even if no change to boot script is needed in the first place.
zador.blood.stained Posted January 13, 2016 Author Posted January 13, 2016 Looks like u-boot 2016.01 was released, will check changelog later. Edit: Nothing interesting apart from Lamobo-R1 support, so it's minus one u-boot patch. 1
wildcat_paris Posted January 17, 2016 Posted January 17, 2016 https://github.com/hardkernel/linux/tree/odroidxu-3.4.y/tools/hardkernel/u-boot-pre-built is it the blobs needed to boot the kernel? explaining why 4.2 4.4 kernel don't work as the blobs are not present in /boot please?
Igor Posted January 17, 2016 Posted January 17, 2016 Those are needed to boot u-boot and they are *must be* present in u-boot package.
Recommended Posts