Werner

Check this out @NicoD @Werner, beautiful and it was usable for most of the time
 
cat /proc/swaps
Filename                                Type            Size    Used    Priority
/dev/zram0                              partition       329960  328920  5
/dev/zram1                              partition       329960  329020  5
/dev/zram2                              partition       329960  329076  5
/dev/zram3                              partition       329960  328840  5
/dev/zram4                              partition       329960  329008  5
/dev/zram5                              partition       329960  329000  5
/swapfile                               file            8388604 516160  -2
 
vmstat 5 100
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
14  1 2945416  82864   3580 281876   14   20    13     6   44   53  1  0 99  0  0
10  0 2965260  79092   2084 251232 43369 35211 34502 13287 10110 17175 58 34  6  2  0
 9  0 2999792  83996   4204 293888 32905 38888 31712 27475 9000 15632 61 34  4  1  0
 
I think most of my original problems were related to: Power, Memory, HEAT
1- at one time I made a mistake and was not using the factory power supply
2- the problem with zram and swapping that you fixed for me @NicoD
3- When I first installed it I had not installed fan management, this should come standard.
Thanks you, I'll cross post this to my other post
 

It's the spirit of TK and persistent testing and tuning that must live on.... any help in that front is great

If you have an NVMe installed anyways you should put the swap there since it is way faster than an eMMC.
Or investigate if there is a memory leak.

Hi @JrRockeTer 
Do :
sudo apt install zram-config and reboot. 
That will increase your zram from 1024MB to 2048MB. There's a fault in the armbian zram-config. For 4GB ram it should create 2GB zram. But it by default creates 1GB. 

If you run on an NVMe, then create a big swap file (don't forget sudo, or use "su" before applying the commands :
 
fallocate -l 8G /swapfile chmod 600 /swapfile mkswap /swapfile swapon /swapfile echo "/swapfile swap swap defaults 0 0" >> /etc/fstab
I'll check out Focal mainline now on the M4V2. Cheers.

If you have an NVMe installed anyways you should put the swap there since it is way faster than an eMMC.
Or investigate if there is a memory leak.

So.... ¯\_(ツ)_/¯

Hi wanted to say we had a really awesome swarm of hacking last weekend.
 
Also we got a bit distracted on cutting RC branch due to the infrastructure move.

This happens after upgrading armbian-firmware package and it is already fixed in master and will be part of v20.08 release.

right /usr/bin/qemu-arm-static /bin/bash -i requires the `binfmt_misc` kernel module... can you confirm your build vm has that module.

I literally replicated your issue by not having that module, and then switched to a kernel with that module, and built successful.  Please at least consider investigating the binfmt_misc module

As am I JR...
Armbian is such a huge project, with not many people working actively on it. So that's why these things happen. If it were Microsoft we should be p*ssed. But this is Armbian. Free software made for free.

As I said, for a reliable desktop with the M4V2, this is still the image to go for. https://dl.armbian.com/nanopim4v2/Bionic_legacy_desktop
There are many other issue's with Focal alone. Then using a mainline kernel with issue's. My bet is it will take about 6 months before that's fully functional. But as said before, I'm no dev. Just a dude trying things out
Good luck.
 

Interesting. This needs to be investigated.
 
 
https://armbian.atlassian.net/browse/AR-340

Interesting. This needs to be investigated.
 
 
https://armbian.atlassian.net/browse/AR-340

It's not your fault. It's a bug in the latest Focal release.
 
Yesterday I flashed the latest Focal release available on the website. Everything was working fine until I did a 'sudo apt-get update && sudu apt-get upgrade". After that the kernel updated and my wifi interface was gone.
 
Buster does not have this bug. So if you are going to reinstall, make sure to flash Buster. Otherwise every time you will run and 'upgrade'  it will destroy your wifi interface.
 
 

We have moved the forums to a new host with higher availability.  Caches may need to be cleared.  Hopefully performance will be better as well.   Please reply here to report any forum-related issues.

That could be an issue. This kind of upgrade is neither tested nor supported. If you have a chance try with a fresh image.
And always handy to have: armbianmonitor -u

Hi @NicoD  nice to see you and nice to watch the videos, there are 3 I have not seen yet ..
I don't know what caused the problems.. After talking to werner I recompiled the fancontrol C program and set it up as a service and I used the original power supply. The rebooting issue disappeared.
I think it is stable now but it gave me a lot of problems, I finally changed to SDDM instead of the default and changed to Ubuntu Mate..
Now it works just like I want it to BUT ; In the process I managed to lose my wlan0 device, which I posted about in another post.
Yesterday I donated some money to Armbian hoping to help on the support side.
 
And thanks to  @Werner who tried his best.
Have fun holidaying, I'm not venturing far this year!

Enjoy yourself

Hi guys! Fortunately I found a solution to the problem: Use a gigabit switch. 
 
Orange Pi 3 and Orange Pi 4 just work on switch with Gigabit technology fine and not with 10/100 interface. Orange Pi One works fine but as exposed in old topic it was fixed. I found after first update many scripts of NetworkManager modified, maybe there are flags and other scripts impacting on NetworkManager.

I fixed issue by adding "load_addr=0x45000000" to /boot/armbianEnv.txt

Yeah I know, saw the YT videos
 
Unfortunately there is not much documentation in that case. It is quite hard to keep track what are current issues, what has been solved, what is new and everything across literaly hundred boards...
Anyway what might be interesting for you is to check JIRA for open threads: https://armbian.atlassian.net/projects/AR/issues/
I could have mentioned that before.
 
Support terms are stated here:https://github.com/armbian/build#support
 
And no, I am no maintainer or developer. I am just a random guy that spends (sometimes too much) time in the forums and help others and collect information that might be useful for actual contributors.
The issue in general is that the team behind Armbian is way too small for the amount of work and can barely catch up with everything. This of course has some downsides and relying on the community to provide p2p support.

You're welcome!
Glad to hear you could make progess.
 
If you come across stuff that can be enhanced or patched and you would like to share with the community please do so. Armbian heavily relying on community contributions.

Thx for the PR.
 
You can also things like blacklisting the wifi module, using iwconfig wlan0 power off ...

Actually no, you do not have to. Though the performance seems slightly better with kernel >=5.6.x

Hi guys,
some months ago I implemented an Odroid C2 as readout controller for a scientific instrument.
Lot of people were kind and helped me with some problems with Armbian, especially eMMC and PWM.
 
Today, finally, we managed to have our instrument (two strings with several Odroid C2 and other stuff) deployed.
It is sitting now at 2628m depth in the Pacific Ocean, and will go operational the next days.
 
Here we are... I think I can announce the deepest Odroid so far (cry loud if I'm wrong :) )
In the picture you just can see the Titanium housing with two glass covers attached to the string.
 
Again, thanks for the fish :)
 
Michael

rien ne va plus. Code freeze day