lanefu

@lanefu
Connection with Github works now - project has to be public and "Armbian" was changed to public @CSQ-Vero @qstaq (and read-only for anonymous), other Project remains private only.
https://armbian.atlassian.net
 

Components are set by admins, labels by any register/approved user. Component "kernel" is IMO enough.
 
 
Yes, something like that. Next we need perhaps to define sprint length?
 
Create 4, 6 or 12 sprints / year. Having an IRC meeting to discuss what was done, adjust upcoming time slot on the end of each? Is that realistic?

New thread here! 

I'll add more to original post as old information is found....  Can't think clearly right now.

I started contributing a few dollars per month to help defray server costs. I might like to increase this amount to help out in purchasing hardware, etc. As I stated before, I have almost no time for anything, but happy to contribute few dollars here and there as luckily I am in a position to do so.
 
I couldn't help but wonder however, how much the PayPal fees and exchange rate were eating into my little contribution each month? And if it's significant, maybe we can figure out a better way to transfer funds. I have a strong dislike for middle men taking a cut anyway. Parasites.

Didn't know where to put this. Perhaps here  

Now there are two merge requests. 2nd shell be merged to 1st, tested and then 1st (branch arm64) to master. When checked.
https://github.com/armbian/build/pull/1586
https://github.com/armbian/build/pull/1587
I leave this separate for better visibility.
 
Now we get additional branch "current" which has to be enabled elsewhere. 

After this gets tested & merged legacy cleaning party?

Well I've fixed my instability issue. The root cause was the same as https://forum.netgate.com/topic/144636/sg-1100-intermittent-reboots, and it was power related. The fix was to replace the 470uf/16V capacitor (component EC1 on the schematic) sat immediately behind the 12V DC jack which under testing leaked under certain temperature conditions (variations). As such the board is now stable and has been running OpenWRT 18.06.2 for 24 hours with memtester and stress running continuous during that entire time.
 
I'll leave it a few more days, after that I'm going to assume that its fixed and that is what NetGate were referring too when they mention 'a power related component'.
 
And GlobalScape will not tell you, they know of the problem, in a reply from Kevin Liu he says 'Yes, I do have knowledge regards the power related component issue.' when I asked which component it was so i could attempt to replace myself.

New version of SPIboot 20191003.
Added support for running official Armbian images (although more correctly, you need to change the logic of creating an image in official images).
Fixed a bug with the kernel and now there is a full image for the SD card to update SPIboot.

Another edge-router based on the Armada 3700 series...
 
Specs look decent - 1GB, 16MB SPI-NOR, 8GB eMMC - runs OpenWRT, but they promise ubuntu support - shipping mid-October 2019
 
https://www.gl-inet.com/products/gl-mv1000/
 

 
I've done work with other devices in their product lineup - and GL-Inet does a pretty good job on the HW side, and good SW support.
 
Nice that they have USB gadget support on the USB-C port (which is also power)
 
Initial vendor docs here -- https://docs.gl-inet.com/en/3/setup/brume/first-time_setup/
 
 
 
 

I've been looking at something relating to this, recompiling and modifying atf/A3700-marvell-utils to build a viable u-boot. From what I've figure out already, it seems the voltage (VDD) applied by marvell is too low by default.
 
Does anyone have any visibility on where the modification to ddr4-*cs-/*g.txt from http://wiki.espressobin.net/tiki-download_file.php?fileId=216 came from? namely the following line:
+;Step9: DDRPHY Driver/Receiver & DQS internal Pullup/Pulldown settings
+;WRITE: 0xC0001004 0xD0133449
+WRITE: 0xC0001004 0xD0677449
 
That is the only difference between the Espressobin provided ddr init and the mainline Marvell A3700 ddr init code.
At the moment I'm running an Espressobin v7 1000/800 using WTMI-devel-18.12.1-e6bb176 / 2018.03-devel-18.12.3-gc9aa92ce70 with a modification to bump the AVS voltage from 1.032V to 1.155V by default. This is looking to be more stable currently..
 
If anyone wants the resulting builds let me know. I cannot use the latest https://dl.armbian.com/espressobin/u-boot/ provided versions of WTMI-devel-18.12.1-e6bb176 since it randomly fails to boot. I rebuilt and enabled debugging and so far no stalls.
 

@lanefu Ok please send me a PM to arrange replacement of PSU.

What about proceeding from vendor named kernels toward generic arm64 / armhf ? I think we should start doing this with 5.3.y ... sunxi64+meson64+rockchip64 -> "armbian64" This is something we have to start doing at some point and can be a first step toward this goal.

It's been a while since I read this topic .... For reference u-boot-2019 and kernel 5.x have been working at N2 with Armbian (Including sound.).

Maybe someone here knows the 8-Bit Guy and the project of his Dream-Computer - the Commander X16
 
You could see the actual state of the real hardware at YT-Video from the 8-Bit Guy:
(Building my Dream Computer - Part 2)
https://www.youtube.com/watch?v=sg-6Cjzzg8s
 
Since the hardware isnt ready/completed yet there is a Emulator which uses SDL2 and can be compiled now (since r30)
also on Linux ARM
 
Github-page of the emulator: https://github.com/commanderx16/x16-emulator https://github.com/commanderx16/x16-emulator/releases Source: https://github.com/commanderx16/x16-emulator/archive/r30.zip or https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz Linux-Binary for PC including the 2 ROMs: https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip libsdl2-dev hasnt to be compiled from source for armbian, because we have already a installable package
and the runtime libsdl2-2.0-0 is already installed in the desktop image.
 
For compiling the Emulator I used on my NanoPi K1 Plus a fresh compiled (with armbian-build-system) dev-image:
Armbian_5.97_Nanopik1plus_Debian_buster_dev_5.3.0-rc8_desktop
 
For to have all programs for compiling the application I did use 
sudo apt install gcc git make libsdl2-dev zip unzip -y
 
Then we do create a directory and download the source and extract it:
mkdir x16
cd x16
wget https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz
tar -xvf r30.tar.gz
 
Now we change in the newly created directory and do compile with make:
cd x16-emulator-r30/
make
 
For running the emulator we do need the 2 ROMs chargen.bin and rom.bin out of the archive
https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip
in the same directory as the compile x16emu binary.
 
Now we can run the emulator (here with german keymap):
./x16emu -keymap de
 
Unfortunately the emulator doesnt run very fast, do use only one CPU-core and hasnt idle-support - so the CPU will get really fast very hot (70 Degree).
 
A AMD Phenom II X4 with 4x3GHz max. is about 2 times more faster (100%+200%=300%) than the X16 on the NanoPi K1 Plus
 
 
 


X16_r30_ROMs.zip

Small progress update -
 fresh photo.
 
 

@SweetKick Regarding the issue of WoL not being enable at each startup, there is effectively a timing issue that seems to be new... the eth0 interface is not yet ready when helios4-wol.service is triggered. I'm going to look at this and see how to fix that.
 
Regarding the other issue where your system reboot 1-2 minute after the system has been put in suspend mode, my guess is because you have installed OpenMediaVault. OMV install watchdog service by default. When the system is put in standby / suspend mode the watchdog is not stopped, therefore since nothing will be kicking the watchdog in that state, the watchdog will reset the system after 60sec.

The workaround for now is to disable watchdog service.
 
sudo systemctl disable watchdog  
Note: you will need to reboot after you disable the watchdog in order to ensure the watchdog is stopped.
 
This also something I was supposed to investigate, in order to see how to make systemcl disable / enable watchdog before / after going to suspend mode.
 
Edit:
Actually I forgot but I did work with OMV guys to fix the watchdog / suspend issue here : https://github.com/openmediavault/openmediavault/issues/343 But the fix only made to it OMV5.
You can add manually the tweak for OMV4,  by creating files /lib/systemd/system-sleep/openmediavault and /usr/lib/pm-utils/sleep.d/openmediavault with the code you find in this commit : https://github.com/openmediavault/openmediavault/pull/345/commits/1c162cf69ed00beccdfe65501cb93f6fb1158df0
 
Edit 2:
I fixed the issue related to WoL not being enable at startup. The issue was now that we rely completely on NetworkManager to configure the network interface, the unit file that enabled WoL on eth0 didn't use anymore the right target dependency and was called too early. Just edit /lib/systemd/system/helios4-wol.service,
 
Replace :
Requires=network.target
After=network.target
 
by :
After=network-online.target
Wants=network-online.target
 
then do sudo systemctl daemon-reload and reboot the system
 

I'm not a fan of the rasperry pi and the fundation behind it for reasons I don't want to go into here and would rather not support them with money. Honestly, hearing that the N2 will have no trouble with fbdev/turbo in 1280x1024 was pretty much all I wanted to hear. I could probably use kodi for multimedia, that'd leave checking out how well libsdl/sdl2 is supported with mali and framebuffer. Many thanks!

I'm running an Odroid N2 as a desktop at 2460x1440@60hz  typically with 3 terminals, and chromium with hangouts, homeassistant, plex, slack, and armbian forums always pinned.   

i'd tried ARM desktop in the past with my le potato and tritium h5... wasn't quite there...... I used an Atomic Pi and it was sufficient--but ultimately 2 gigs of ram wasn't enough even with zram compression.   Finally I tried the N2, and I think it's there.. even with bruteforce fbturbo doing the video..    I'm running Armbian bionic, with vendor kernel and Mate Desktop... pretty happy with it.

Its (always) a compromise 
 
The primary reason for this upgrade is to have a better working solution for easy experimenting with things as such: https://forum.armbian.com/topic/11424-playing-with-limamesa-mali-drivers/ 
 
Initial upload repository size will be addressed (recreating/truncating), while for upload limit, there is nothing I can do. On the other hand Github has advantages, like existing user management ... for one user this is not a problem.
 
The bulk of the job surrounding this change is elsewhere - package management RFC - rebuild is done much faster/in parallel, cleaning is more efficient ... 

Hi, 
 
I have encountered this issue for many times on OrangePi PC,  this issue happened by using following version 
Armbian version: 5.41, Kernel version: 4.14.32 Armbian version: 5.77,  Kernel version: 4.19.25 Armbian version: 5.90,  Kernel version: 4.19.57 I have more than 10 Orangepi PC running busy tasks at the same time, and this issue happened more than 15 times in the past year, still have no idea how to deal with this,  it is still able to send data to my server somehow, which means that the internet connection is available, but i'm not able to ssh.
 
I have tried the following methods:
Wrote a udev file to copy all system log when usb pendrive is detected,  this works fine when device runs normally, but not working when encounter this issue. Using watchdog, works fine if using fork bomb to test, but not able to recover from this issue Tried connect to a keyboard and hdmi monitor,  this works fine when device runs normally, but not working when encounter this issue. Using TTL serial to usb adapter,  I'm able to control device when it runs normally, but not working when encounter this issue.   
I found that dmesg record some error message as below when I encountered this again yesterday
 
Currently, I might try to continuously detect whether this error message occurred in dmesg, if yes, I will try using this command "sudo systemctl --force --force reboot"(it seems that /sbin/reboot does not work at the moment)
 

There are graphical backgrounds?
 
This is my favorite, and the only one I ever saw, prior to opening this thread:
____ _ _ _ _ / ___| _| |__ (_) ___| |_ _ __ _ _ ___| | __ | | | | | | '_ \| |/ _ \ __| '__| | | |/ __| |/ / | |__| |_| | |_) | | __/ |_| | | |_| | (__| < \____\__,_|_.__/|_|\___|\__|_| \__,_|\___|_|\_\ Welcome to Debian Jessie with Armbian Linux 4.19.62-sunxi System load: 1.06 0.64 0.58 Up time: 19:01 hours Memory usage: 28 % of 2010MB IP: 192.168.1.5 10.0.1.5 CPU temp: 35°C Usage of /: 6% of 59G storage/: 9% of 3.6T Last login: Fri Aug 23 01:51:43 2019 from 10.0.1.12  
All jokes aside, I probably like the last one (rounded with plain grey background), and also the terra cotta army one mane me smile.

Thanks for the input, but proprietary software is a non-starter for me. So much so in fact, that I purchase hardware nowadays based on how free/open the driver support (and company/community around it in general) are. In fact, I never even considered purchasing any IP cameras until I came across those ones with the Dafang hacks.
 
I did hear the Zoneminder guy on some Linux podcast a few months back, and it sounded like some more development has been going on of late. Well, I certainly hope, anyway. I have yet to touch it, but I will be knee deep in it here soon enough! :D
 
So, I've got (2x) the fixed (Xiaofang) ones and (1x) PTZ (Dafang) on the way from AliExpress as we speak. The former were only lke $20 something each, and the latter ~$30(!). I can remember what seems like only a few short years ago PTZ cameras being like $500!
 
Anyway, back to topic, I came across this post which nicely summarizes sort of where we are today with regard to SBCs and particularly how open they are which leads directly to how well they are supported by community / Linux which means a good, long term, and stable experience for end users.
 
For now I am going to pull trigger on (1-2) ODROID-XU4, one for dedicated ZoneMinder instance, and the other one for a spare / development / testing platform. I've also ordered a 16 port (8 PoE) gigabit switch, 1000' box of Cat5e (only $38 shipped on eBay, surprisingly!) and some ends, crimping tool, etc... so yeah we will see how it goes!

panfrost driver is far away from daily use, still under heave develop..
 
if you have mali450/400 device, lima driver is near.

I try not to aim at the total noobs with my videos. I expect people who watch my videos to know what an SBC is, and how to write an image to an SD-card.
I think ETA-Prime is better for you. He's a noob explaining to other noobs Try to learn from him Then later on maybe again watch one of my videos again
No hard feelings, just messing a bit.

Panfrost instructions Armbian
 
!!!! I made a script that does all this, check a few posts later for the script !!!!!  
This tutorial explains how to build an Armbian image with panfrost. And what else you need to make it work.
These are early drivers. Many things don't work yet. Only OpenGL 2.1 works now.
 
You need to build an image with kernel 5.2 or later.
For this you need an x86 pc with Ubuntu 18.04 or a virtual Ubuntu 18.04 x86 image.

First install git, then clone the build folder from Armbian, and enter the build directory.
 
apt-get -y -qq install git git clone --depth 1 https://github.com/armbian/build cd build Now run the script with EXPERT=yes so you can choose to build a dev image.
sudo ./compile EXPERT=yes Choose "Full OS image for flashing" Then "Show a kernel configuration menu before compilation" Choose your board. If it's not in the regular list, look in "Show SCS/WIP/EOS/TVB". Choose Development version kernel configuration -> device drivers -> graphic drivers -> panfrost  
Let it run until it's finished. The image will be in the /build/output/images
Burn it to an SD-card/eMMC/...
 
Now we need to install all the needed software
sudo apt install flex bison python3-mako libwayland-egl-backend-dev libxcb-dri3-dev libxcb-dri2-0-dev libxcb-glx0-dev libx11-xcb-dev libxcb-present-dev libxcb-sync-dev libxxf86vm-dev libxshmfence-dev libxrandr-dev libwayland-dev libxdamage-dev libxext-dev libxfixes-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-present-dev x11proto-gl-dev x11proto-xf86vidmode-dev libexpat1-dev libudev-dev gettext glmark2 glmark2-es2 mesa-utils xutils-dev libpthread-stubs0-dev ninja-build bc python-pip flex bison cmake git valgrind llvm llvm-8-dev python3-pip pkg-config zlib1g-dev wayland-protocols Download and install meson
wget http://ftp.de.debian.org/debian/pool/main/m/meson/meson_0.55.3-1_all.deb sudo dpkg -i meson_0.55.3-1_all.deb Download and install mesa DRM
git clone git://anongit.freedesktop.org/mesa/drm cd drm meson build --prefix=/usr ninja -C build sudo -E ninja -C build install cd .. Download and install mesa graphics
git clone git://anongit.freedesktop.org/mesa/mesa cd mesa meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dprefix=/usr build/ ninja -C build/ sudo ninja -C build/ install REBOOT
 
Optionally, update sdl (recommended)
git clone https://github.com/SDL-mirror/SDL.git cd SDL mkdir build cd build cmake ../ make -j6 sudo make install REBOOT
 
Only thing that works ok with it is supertuxkart, to install it.
sudo apt install supertuxkart
 
Panfrost - Linux games working from repo
SuperTuxKart - Works well
ExtremeTuxRacer - lots of glitches
AssaultCube - lots of glitches
 
Instructions by Salvador Liébana & NicoD

Looks great@igor!