lanefu

So i just checked out the ideas of role needs on the contributions thread. @tkaiser what's the biggest pain point that makes it indicative of "pet project" characteristics? [mention=1]igor[/mention] what's the most important part of the armbian project to you? Sent from my SM-G950U using Tapatalk

Ohh. And there was the time i drove from Raleigh to Richmond like this Sent from my SM-G950U using Tapatalk

My 4x4 v8 truck doesnt have giant tires.....but oem is pretty big so... true statement 'Merica. Sent from my SM-G950U using Tapatalk

Okay... I did fresh kernel build.. and tried to be a little more thorough with killing services..... and i ran a bigass fan over my whole arm cluster http://ix.io/1nJl my quick list of services I shutdown.. (many wont be relevant) services="docker nomad consul rpcbind rpcbind.socket NetworkManager cron dbus.service haveged.service networkd-dispatcher.service ntp.service rsyslog.service snmpd.service systemd-resolved.service syslog.socket dbus.socket wpa_supplicant.service serial-getty@ttyS0.service" systemctl stop $services Re Crashing: Doubt it was running full load.... I use it as my main linux jump host... so mostly screen and ssh, vim, ansible, occasional docker image build and a few agents. (I'm amazed how much mileage i get with 1 gig ram!) I had been using a Opi PC2 to do the same stuff, but migrated to the OnePlus for excitement.

I bet unattended-upgrades was running in the background (you could check /var/log/dpkg.log) Ha man i tried so hard to stop any service i could find or think of, but unintended-upgrades was definitely missed. Sadly that board has been falling offline since running with the 1.8ghz patch. I'll take another pass Sent from my SM-G950U using Tapatalk

Just built debs and upgraded my kernel.. seems to work SBC bench http://ix.io/1nje w/ cheap ceramic heatsink (and a little bit of forced ambiant air) ########################################################################## 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: 1791 1792 1789 1792 1791 1791 1790 1791 1792 RAM size: 994 MB, # CPU hardware threads: 4 RAM usage: 882 MB, # Benchmark threads: 4 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2710 340 776 2637 | 76925 398 1648 6563 23: 2665 349 779 2716 | 75245 398 1634 6511 24: 2623 360 784 2821 | 73176 398 1615 6424 25: 1276 197 741 1457 | 69984 398 1567 6228 ---------------------------------- | ------------------------------ Avr: 311 770 2408 | 398 1616 6431 Tot: 355 1193 4420

Can you switch to newer kernel via armbian-config.. Switch kernel type from "default" to next/mainline. Then switch to nightly if needed. root@espressobin:~# uname -a Linux espressobin 4.18.6-mvebu64 #3 SMP PREEMPT Sat Sep 8 15:04:30 EDT 2018 aarch64 GNU/Linux root@espressobin:~# ls -l /dev/mapper total 0 crw------- 1 root root 10, 236 Sep 8 20:12 control

Current proposal? the FAT32 config partition is at the end of the disk image firstrun applies configuration changes config file is scrubbed via shred for security purposes fat32 part is destroyed rootfs expansion step proceeds as normal

Ohhh! You want to edit image such as the official ones. I get it. No depencies on build. Pretty sweet actually Sent from my SM-G950U using Tapatalk

Do you all envision this as a bolt-on that just kind of runs last after image build around the user-patches phase, or more tightly integrated into the build process? At a glance it seems more like a potential extension of armbian-config that could also be executed at anytime if needed a well.

This is really just a bash-centic question, but I'm baffled an tired of googling. Why does passing KEY=VALUE args to compile.sh work? I don't see bash flags, arg parsing or anything. I'm trying to do something similar in another script I'm just baffled. ex: sudo ./compile.sh EXPERT=yes EXTERNAL_NEW="compile" BOARD=orangepi-r1 BRANCH=next RELEASE="jessie" DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=no CLEAN_LEVEL=""

Okay couldn't resist sharing my insanity. My goto build server is my frankendell, which was pretty much motivated for building armbian stuff. A while back I noticed that dell enterprise desktop motherboards on ebay were really cheap. That inspired me to google to see what older optiplex models had i7s. So I started cobblin together a stupid server made from a dell desktop motherboard, an i7-2600, some fancy gamer ram from a co-worker, a 1U server case, a dual port nic, and an nvidia quadro card. Then I cut the case down to size with an angle grinder, put it on a comm shelf that conveniently screwed into some 1x4's i hung from my rafters. For extra credit, the bios is set to always power-on, and I spliced a Sonoff Basic into a powercord so that I can control from HomeAssistant. My build VM is actually running on NFS storage over 2x1GB LACP. IO's been good enough to keep me happy. I ended up buying real dell fans and a the front panel nonsense because it so hard to make the bios not freak out. Generally I advise just getting a whole optiplex 790/990 from ebay and spare yourself the excitement.

I sometimes use the cloud for building armbian. To make it a little easier I have an ansible role that sets up my build environment. keys, git repos, vim tweaks, and an rsync endpoint to easily pull images home. You definitely wouldn't want to leave it up 24/7, but its great to spin up for a weekend of intense hacking. The first run is the slowest just because all the tool chains have to download. Filling you Apt cache is less important in the cloud because the mirrors are so fast. The free instances wont cut it, and you definitely need additional space. Its usually easiest to just put your GIT checkout and build environment on a dedicated volume. At a minimum your build/cache directory needs a lot of disk. That's where toolchains, source, root filesystem images go. A few other thoughts: Use at least a quad core VM core count is typically more impactful than clockspeed, with the execption of the qemu-arm sessions where emulation is happening You don't need much RAM. 2-4 Gigs i sufficient even on 8 cores Use the market priced instances rather than standard on-demand In AWS -- Spot instances In GCE -- Preemptible instances These have become my favorite because of predictable pricing. Plug https://cloud.google.com/preemptible-vms/ Run armbian builder from a fork an save your work. You could randomly lose your node due to the ephemeral nature of above.

yep just docker. Try building your container from the `arm32v7/ubuntu` image. and just a pro tip, this command will clean up all your old docker messes `docker system prune -a`

That is true, but you still need the 32bit libraries for all the supporting dependencies or run a statically linked binary. I usually just run all my 32bit stuff in containers of 32bit flavors of whatever distro on my 64bit arm boards. If that's an option for you, its usually pretty streamlined. Ends up being pretty convenient as I have mixture of boards and it makes it easy to move workloads around.