lanefu

I have drafted a procedure for tasks management. Please take a look and share your thoughts. Armbian Task Tracking Process @Igor and others If you want to move forward, we have the following action items to perform: * Create new Forum Topic "Armbian Tasks" * Create GitHub Milestone "claimed tasks" * Create GitHub Milestone "unclaimed tasks" * Migrating some threads to new topic, etc. * Break out tasks from this thread into new procedure.

Still grokking big picture -- interest piqued.

i had a bit of an epiphany after i posted this. ill get something drafted Sent from my SM-G920V using Tapatalk

i volunteered for a task to crearte a process. im still very short on delivery and i appologize. im over thinking the forum to github issue relationship. questions for all... for issues does it make sense to keep all dialog on the forum, but create a corresponding issue in github && just have it provide a hyper link to the forum? Sent from my SM-G920V using Tapatalk

that output is totally good enough! To me the value of PDF documentation is for treating it as e-reading for ones platform of choice (or wasting paper) look just fine on mobile. ... requirement met HTML docs value is for people in their standard project hacking scenarios where browser is king. Sent from my SM-G920V using Tapatalk

I'm a big fan of markdown-based solutions. I moved my team from a wiki to markdown + mkdocs and have great success. here's a few bullet points (i recognize some of these may be redundant to other posts in the forum) * typically content renders nicely out of the box with modern version control front ends such as github, bitbucket, gitlab * markdown's popularity lowers barrier to entry across masses * text file nature easy for *nix users and developers to quickly update docs while coding from their favorite editor or IDE * file ÷ git commit process makes writing the doc feel more deliberate / focused because process is the same as commiting code. ive experienced documentation quality go up because of it * output in multiple formats via post processing. as an example my doc repo has a git hook that executes mkdocs on post commit. my internal documentation is automatically updated with searchable documentation.

any error messages? have you tried attaching TTL serial console to look for messages?

I burned a weekend trying to outsmart privledged mode to get armbian builder working with docker.. Should be fine for building kernels, but if you're doing system images, the loopback devices needed for the disk image creation becomes a nightmare. You're better off having a ubuntu box as a jenkins slave ready to go

Okay since i'm pretty much doing the same thing with my team at work, I'll take on establishing clearer process / procedures for issue tracking. Since both the forum and github support a concept of tagging there's some opportunities there for integration. We want to make issue/task creation is easy, but deliberate enough that we don't end up with having to filter a bunch of noise.

Hey man I feel you.. Sometimes there's no glory in the easy way.

I don't know what your financial constraints are, but launching a Ubuntu 14.04 AWS EC2 instance and running armbian builder on it is cake....and fast.. AKA $1 of cloud computing will save you a lot of time and effort.

I'm totally interested in participating. Is the issues list on github the source of truth for open tasks or are there other places? PS it looks like the issues in github arent taking advantage of labels. probably worth while

sure ill take a look this evening. i was just using ttl serial.console last time. ill hook it up.to a monitor this time Sent from my SM-G920V using Tapatalk

Fired up and tested my Plus 2e I posted my DRAM test results. Hopefully my comment makes sense. Other stuff I built latest Armbian 5.12 jessie for OPi PC from repo and booted without issue Once I symlinked my fex to /boot/bin/orangepiplus2e.bin, I was able to see the onboard eMMC, and the onboard ethernet. Ethernet was able link at gigabit. I hit 700mbit on a quick iperf No luck with wifi with using already included modules no luck with wifi following instructions described in this thread http://forum.armbian.com/index.php/topic/942-rebuild-rtl8189es-from-git-for-opi/page-2?hl=8189ftv#entry9574 There's a garbage Fat32 Filesystem with android stuff on the onboard flash (let me know if anybody really interested) I found this while poking around on the onboard flash root@orangepipc:/mnt/tmp# cat misc/wifi/wifi_hardware_info realtek:rtl8189fs

my opi 2e arrived today. so i should * run and document dram test * see if the untested wifi driver works * make a dorky unboxing video ... anything else of value I can do in the name of armbian? Sent from my SM-G920V using Tapatalk

Leonardo, I'm excited to try your patch. Have you had an opportunity to submit a pull request to the armbian project? i saw a a gc2035 patch in the unresolved folder but it didnt look like your changes Sent from my SM-G920V using Tapatalk

I had to blacklist the standard realtek module in order to get things to behave with the patched one that comes with the distro lane@orangepione-2:~$ cat /etc/modprobe.d/wifi-blacklist.conf blacklist rtl8192cu Prior to blacklisting, it would just crash and reboot as soon as the wifi module loaded. This was using one of the little rt8192 dongles from adafruit running an armbian image I built from the repo yesterday.

I fought the good fight over the weekend trying to get Armbian builder to build full images while running in a docker container. I've had some success, and managed to build a armban 5.11 image for my Orange Pi One.. I'm running on it with wifi etc. I'm using a CentOS7 Docker 1.9.1 host and using Ubuntu 14.04 Trusty Docker Container for the Armbian builder container. (I just used the Dockerfile from the armbian git repo) Bottom line loopback management inside containers is a bad time.. especially when losetup implementations vary between host and container. The partprobe step in the container doesn't seem to trigger appropriate feedback to udev to create partitiion devices on the /dev loop back devices. I got around it by creating them ahead of time. Here's a few tricks to limp through. I'll try to add more clarity later. 1. Don't. just go build a ubuntu 14.04 VM or use a turn key one on amazon and get your life back. From Docker Host #you need modules modprobe binfmt_misc modprobe loop #scrub loopbacks for good luck rm -rf /dev/loop[0-9]* Launch armbian builder container with --privileged=true #sudo docker run --privileged=true --name=armbian -it armbianbuilder #or if you're re-using container #sudo docker start -i armbian From container #start apt-cacher-ng service apt-cacher-ng start ​ #scrub loopbacks again in container for good luck rm -rf /dev/loop[0-9]* #create all your loop back devices mknod /dev/loop0 b 7 0 mknod /dev/loop0p1 b 259 0 mknod /dev/loop0p2 b 259 1 mknod /dev/loop0p3 b 259 2 mknod /dev/loop0p4 b 259 3 mknod /dev/loop1 b 7 1 mknod /dev/loop1p1 b 259 0 mknod /dev/loop1p2 b 259 1 mknod /dev/loop1p3 b 259 2 mknod /dev/loop1p4 b 259 3 mknod /dev/loop2 b 7 2 mknod /dev/loop2p1 b 259 0 mknod /dev/loop2p2 b 259 1 mknod /dev/loop2p3 b 259 2 mknod /dev/loop2p4 b 259 3 #build your dreams cd ~ ./compile.sh Every time you build an image you should destroy the loopbacks and recreate. It's your best chances of getting the partitions in the loopback image to behave for mounting.

where you able to find something that worked for you? Sent from my SM-G920V using Tapatalk

I have 2 Opi Ones if additional testing is needed. one with heatsink one without. i have a 2e coming also Sent from my SM-G920V using Tapatalk

I'm running an Orange Pi One -- no heat sink, open sitting on my desk. I built latest legacy armbian kernel via armbian build process. Folllowed instructions for fex settings, etc. I've been running cpuburn for over an hour, and here's the bottom of my log.. I'll run overnight and post on a gist or something It's been holding steady with these numbers for at least 30 minutes 23:43:33: 912MHz 4.01 100% 0% 99% 0% 0% 0% 78°C 23:43:38: 912MHz 4.01 100% 0% 99% 0% 0% 0% 78°C 23:43:43: 912MHz 4.01 100% 0% 99% 0% 0% 0% 78°C 23:43:48: 912MHz 4.01 100% 0% 99% 0% 0% 0% 77°C 23:43:53: 912MHz 4.01 100% 0% 99% 0% 0% 0% 77°C 23:43:59: 912MHz 4.01 99% 1% 98% 0% 0% 0% 78°C 23:44:04: 912MHz 4.01 99% 0% 99% 0% 0% 0% 78°C 23:44:09: 912MHz 4.01 99% 0% 99% 0% 0% 0% 77°C 23:44:14: 912MHz 4.01 99% 0% 99% 0% 0% 0% 77°C 23:44:19: 912MHz 4.00 99% 0% 99% 0% 0% 0% 78°C 23:44:24: 912MHz 4.00 100% 0% 99% 0% 0% 0% 78°C 23:44:29: 912MHz 4.00 100% 0% 99% 0% 0% 0% 78°C 23:44:34: 912MHz 4.00 99% 0% 99% 0% 0% 0% 78°C 23:44:40: 912MHz 4.00 99% 0% 99% 0% 0% 0% 78°C 23:44:45: 912MHz 4.00 99% 0% 99% 0% 0% 0% 78°C 23:44:50: 912MHz 4.08 99% 0% 99% 0% 0% 0% 78°C 23:44:55: 912MHz 4.07 100% 0% 99% 0% 0% 0% 78°C 23:45:00: 912MHz 4.06 100% 0% 99% 0% 0% 0% 77°C 23:45:05: 912MHz 4.06 99% 0% 98% 0% 0% 0% 78°C 23:45:10: 912MHz 4.05 99% 0% 98% 0% 0% 0% 78°C 23:45:15: 912MHz 4.05 99% 0% 98% 0% 0% 0% 78°C 23:45:21: 912MHz 4.05 100% 0% 99% 0% 0% 0% 78°C And Since I had already let it run overnight.. here's a graph of it holding steady just because

The WiringPi libraries for c and python work well. see my post on the "free" forum section on how to build the Python libraries Sent from my SM-G920V using Tapatalk

I removed source "fs/fs_compat.kconfig" from /usr/src/linux-headers-3.4.112-sun8i/fs/Kconfig and then I was able to run make scripts on Armbian 5.10 aka sed -i '287d;' /usr/src/linux-headers-3.4.112-sun8i/fs/Kconfig make scripts i was able to get the module built afterwards.. whether or not i get it to work with my wifi adapter is another story update: wifi seems to be alive now... i went back to /usr/src and did sudo cp ./rtl8192cu-fixes/blacklist-native-rtl8192.conf /etc/modprobe.d/ sudo cp ./rtl8192cu-fixes/8192cu-disable-power-management.conf /etc/modprobe.d/ rebooted then re-inserted the wifi

That's pretty frustrating. Complex git requests get picky over HTTP especially with pushes. You may have better luck setting up a github account and adding your public SSH key (if you haven't already) and switch your clone method to SSH-based prior to copying the clone URL to your clipboard. SSH is much more resilient, and you'll have additional tuning options available to you

Hey I managed to get the WiringOP libraries to build with the Python WiringPi libraries on my OPI One. I wrote up a quick gist and made a dinky fork to save some people some time: Orange PI WiringPi-Python Gist PS: Igor, TKaiser, and other contributors. Armbian is a really great distro. I'm very grateful for all your hard work.