lanefu

I did it.. thank you!

Yes. We definitely need to figure out when to cut a release, when to increment, what a RC version number means, etc. -rc1 was really a rolling release branch this time. AR-176 I really see that as 2 parts. * Make building alternate armbian build branches easier. * Make upstream dependencies consistent. Both are important, I think the first is a higher priority. AR-176 I partially agree with this. All features in an RC should exist in master--first. Bug fixes no. If a bug fix obviously will improve master, then yes it can be cherry-picked, But the primary purpose of bugfix is to assure the stability of the release. Simple Example.. we add a patch to a release on 5.4 kernel... master has moves to 5.5... may not make sense. In practice---during this release we ended up cherry-picking most fixes from master and into the RC branch.

Hey thanks for the positive feedback! It's super helpful to know what went well too. I'm really glad you were able to see so many improvements.

Hey Sorry. @TonyMac32 and I came across this issue the other day.. There's a second step needed.... create a file in your build filed called .ignore_changes I've updated the FORCE_CHECKOUT section of the documentation touch .ignore_changes

I'd like a fixed with font inside the spoiler. Ugly inside spoiler Pretty fixed width font in code block

Would be nice to tweak the forum theme so that spoilers used code-friendly formatting

We just pushed a few updates. you may want to download the latest lepotato image we posted today.

FYI I am working to document things that went wrong / improvement areas... so please share those thoughts on this thread.

This is to discuss and prioritize enhancements and bugfixes we want to target for v20.05 (Kagu). We will lock this thread 2020-03-15 to manage scope creep. Many items are currently in Jira here https://armbian.atlassian.net/projects/AR/issues/?filter=allopenissues If you're a frequent contributor and would like to join our Jira, please PM me. It's not mandatory, but it would make things easier. To track. Remember the Armbian Mission Statement: Armbian is a base operating system platform for single board computers that other projects can trust to build upon. Let's try to prioritize things that help us deliver on that mission

not sure how you'd manage the .debs for it.. but as u-boot... its just pointing to a symlinks to the different active versions.. so you can just modify symlinks lane@cranbone:/boot$ ls -l total 37442 -rw-r--r-- 1 root root 166 Feb 19 14:13 armbianEnv.txt -rw-r--r-- 1 root bin 0 Nov 20 2018 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 Nov 18 2018 armbian_first_run.txt.template -rw-r--r-- 1 root root 230454 Nov 18 2018 boot.bmp -rw-r--r-- 1 root root 2970 Nov 18 2018 boot.cmd -rw-r--r-- 1 root root 4882 Nov 18 2018 boot-desktop.png -rw-rw-r-- 1 root root 3042 Nov 18 2018 boot.scr -rw-r--r-- 1 root root 168792 Dec 22 09:31 config-5.4.6-sunxi64 lrwxrwxrwx 1 root root 17 Dec 28 17:27 dtb -> dtb-5.4.6-sunxi64 drwxr-xr-x 2 root root 1024 Dec 28 17:06 dtb-5.3.9-sunxi64 drwxr-xr-x 3 root root 1024 Dec 28 17:06 dtb-5.4.6-sunxi64 lrwxrwxrwx 1 root root 17 Nov 23 19:03 dtb.old -> dtb-5.3.9-sunxi64 lrwxrwxrwx 1 root root 21 Dec 28 17:27 Image -> vmlinuz-5.4.6-sunxi64 -rw-r--r-- 1 root root 9418877 Feb 19 14:00 initrd.img-5.4.6-sunxi64 drwx------ 2 root root 12288 Nov 18 2018 lost+found -rw-r--r-- 1 root root 3381515 Dec 22 09:31 System.map-5.4.6-sunxi64 lrwxrwxrwx 1 root root 21 Feb 19 14:01 uInitrd -> uInitrd-5.4.6-sunxi64 -rw-r--r-- 1 root root 9418941 Feb 19 14:01 uInitrd-5.4.6-sunxi64 -rwxr-xr-x 1 root root 15685640 Dec 22 09:31 vmlinuz-5.4.6-sunxi64

Allwinner use's megous's repo . https://github.com/armbian/build/blob/master/config/sources/families/include/sunxi_common.inc#L12 you could look at see what he's using also you could add to lib.conf KERNELSOURCE='git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git'

Whats your favorite little heat sink for the Allwinner SoCs... LibreComputer's doesn't count.

Testing, documenting, spell checking, helping others and just reading issues on github are all great ways to start

Here's lepotato holding together and using lots of ram. with 2 instances of armbianmonitor -z running

Okay i've got patched 5.4..... sound works.... was able to use more than a gig of ram when i ran armbianmonitor -z and watched htop from the desktop https://github.com/armbian/build/pull/1805

best thing you can do is probably roll back sudo apt install linux-image-current-meson64=19.11.3

I heard about this today. https://github.com/teejee2008/timeshift sounds pretty neat..

apt install docker.io then read some of the documentation here https://docs.linuxserver.io/general/containers-101

the OS mongo packages are usually super outdated, not surprised they don't work. Consider this container. the linuxserver.io project builds multiarch containers for arm32, arm64, and x86. https://hub.docker.com/r/linuxserver/unifi-controller

yeah that's super interesting.. according to your armbianmonitor -u the OS definitely sees 2 gig. What happens if your turn swap off total used free shared buff/cache available Mem: 1,9Gi 755Mi 953Mi 23Mi 254Mi 1,1Gi Swap: 981Mi 452Mi 528Mi

Okay were providing our own updated stable build with armbian. If you're using the standard debian one. It's probably an issue with the upstream wireless driver

Use dnsmasq. No more non-armbian questions please. This isn't a generic linux support forum.

Sorry you're having trouble. we switched from a special kernel branch to mainline... Honestly you'll probably want to roll back to the older kernel for all the DRM stuff at this point. Try this image and see if its any better.. The audio has hte same issue on this image tho. https://armbian.lane-fu.com/Armbian_20.02.0_Lepotato_buster_current_5.4.20_desktop.img

@FantasyCookie17 You may want to try the distro-provided hostapd rather than the armbian one.. it lacks some features, but maybe it'll work out for you.

sorry thats all the help I can give on this issue... you'll figure it out.