Igor

That's not possible unless you manually installed NEXT (4.11.x) packages. default can only upgrade to next default kernel, which is still 3.4.113, last Armbian build is 5.30

I guess you are not using latest system? Can't find such option in our script: https://github.com/armbian/build/blob/master/scripts/nand-sata-install/usr/lib/nand-sata-install/nand-sata-install.sh

I changed a part of structure which looks more or less clear, but let's do some double checking before we move everything here and there - tutorials which are currently everywhere, mostly under Technical support. There could be also "Tutorials" pinned topics with pinned tutorials, like Tony suggested. - each subforum in here should have "Readme first - FAQ" tagged with "IMPORTANT" with most common questions -> link to answered topics as Thomas proposed. I added hidden post into Allwinner A20 section as example - unhide when done. You should have the power to do so. It is also possible to make use of "Forum rules". Currently this is the text: Use search before starting new topic - add questions to existing topics - support on private messaging is ignored - humans are not error free, be polite. - what to do with "Preview of this and that" board from Free? I would suggest moving SD card performance, storage benchmark and similar at least to "Technical support / common" section? - current "Project and services" should be split into other forums and section removed? - we have "Allwinner A64/H5", but we don't support. Should remain simply under Development? - Build tasks? Merge / remove? - community projects: 3rd party, deprecated and exotics boards, ... this part is still a bit confusing to me.

Armbian is community driven open source project. To keep it relevant and up to date it needs maintenance round the clock. This work is done by a small amateur contributor force which was under-powered since early days and it still is. For most basic tasks! Any help is more then welcome. https://forum.armbian.com/staffapplications/ (what do we need) https://docs.armbian.com/Quick_facts/ (overview) https://www.armbian.com/get-involved/ (how-to contribute) https://github.com/armbian (sources for build engine, documentation, scripts) <---- <---- <---- Also refactoring, better wording, code cleanup. General tips: plan to do things you understand. expect little to no guidance. focus on common needs and forget what is important only to you. start small. If you still don't know how to start, attach your questions below in the topic.

Any objections for rebuild and update?

It works for me to, cubox-next, ath10 and brcmfmac. @tonymac32 Reboot reboots. http://sprunge.us/CaOj U-boot on eMMC: U-Boot SPL 2017.05-rc3-armbian (May 04 2017 - 15:10:29) Returning to boot ROM... U-Boot 2017.05-rc3-armbian (May 04 2017 - 15:10:29 +0200)

I revert cubox and clearfog, for sunxi I am bit confused what to remove and what to leave due to overlay support ... and Tinkerboard / MiQi @TonyMac32, shall we go back to 4.9 with NEXT too?

We have idea, but lack of time, to provide IOT / slim version, which means rework (put under switch) those sections + conduct few tests ... https://github.com/armbian/build/blob/master/configuration.sh#L103-L139 https://github.com/armbian/build/blob/master/distributions.sh#L105-L106 Other option is do uninstall certain - non relevant to your case - packages.

Client, ath10, crashed also on Clearfog with 4.11. Will do more test and provide logs ... currently out of office.

Well, also I could reproduce on Hummingboard when trying to connect wireless - it instantly crashed on 4.11.5 while working fine on 4.9.33 ... Of course there is risk when upgrading, especially u-boot, because worse case boot breaks ... but kernel upgrades are more flexible since it "only" breaks some part of functionality at worse. Like in this example. Perhaps this upgrade procedure should be divided and provide more selective relevant upgrades. That should limit down problems. Also possible to apply it to images by default and we gain stability - user must act to get latest updates. Like on deprecated boards.

Another small example: https://forum.armbian.com/index.php?/topic/4557-blank-password/#comment-34201 This question was posted to Allwinner H3 section but it's unrelated to hardware - it's very general question - better to be moved one level up, to general section.

This job is for anyone with minimal inside knowledge. Related or unrelated to Armbian. Again - "no support" means we will not provide any information regarding state and problems of moving experimental things. It's expensive and provide negative results. Double negative from our perspective. When things are good enough for bare server usage, similar kind of report is found at download page - this and that is not working, ... Currently there are too much problems and no one out of five active developers would like to have yet another burden. We don't want that experimental images are used by end users in first place. Some even use those unfinished work in production and are saying that we are losers and idiots, because upgrade break their wonderfully working system. Yes it happens. It happens way to often and there is no compensation. They don't support as in any way but expect full support from us. We came to conclusion that we will not share any information (for end users) regarding WIP work. Developers can find and acquire information from Github commits, from ours an upstream. Everything relevant is written there, but to write a summary ... anyone can.

Shall we go back with sunxi and cubox NEXT to 4.9.x and push update out since: https://forum.armbian.com/index.php?/topic/4254-cryptdisks-fail-with-new-kernel-41012/#comment-31614 https://forum.armbian.com/index.php?/topic/4498-no-network-after-upgrade-to-530/&page=4#comment-33710 Any other critical thing?

Recent hot debates sparked many ideas, but no need to rush. Rome was not built in a day Rearrangement outdated forum structure should also improve the situation - at least we have to get the best out of forum, even it has limitations, which were exposed and I am aware of it. Few concrete ideas for reshaping the structure - what if we clearly divide support forum into stand alone section - we isolate section "Technical support" only for: "Allwinner A10/A20 Allwinner H2/H3 Allwinner A64/H5 Amlogic Freescale i.MX6x Other boards" Than we have section, which does not live very much and should also be redesigned: Projects and services Reviews Support of deprecated boards / old board support 3rd party armbian builds, etc. Development I propose to merge / remove Armbian build framework and Armbian Tasks into Development. Free / rearrange Move everything up to corresponding forums, what can be moved. This part was never meant for technical stuff but more for casual stuff like: "I have a new cat - what do you think?" stuff

It looks like a network-manager issue. I could reproduce ... but it only failing when trying to connect from windows machine while working fine when connecting from Linux.

username: root password: 1234 repeat the password: 1234 new password: xxxxxxxxxxxxxx repeat new password: xxxxxxxxxxxxxx

Yes, let's move all out and enable upon developers requests?

Compilation usually hangs / takes hours if SD media is from other century (extremely poor 4k performances). This one looks o.k. which probably means this: https://forum.armbian.com/index.php?/topic/3915-upgrade-time-cross-compile-kernel-on-another-machine/&do=findComment&comment=28620

I guess roll back to previous version (4.9.7) should do the job. apt install linux-image-next-sunxi=5.25 linux-dtb-next-sunxi=5.25 Than go to armbian-config and freeze kernel upgrades until this is not solved ...

If your power supply is below 1.5A / low quality, than strange random problems might happen in such configuration: board + mouse + keyboard + HDMI screen + wireless ... and we are back to basic hardware problems written in https://docs.armbian.com/User-Guide_Getting-Started/ Even you have a good one, just make sure to test with different one and remove all from USB ... Is this the case?

Default / standard open-ssh server which works perfectly well for millions of people. Problems are not on this level ... Dietpi is illusion of choice, copy of Armbian, it uses our kernel, builds system, everything what is relevant and it should behave the exact same way. Bugs present in Armbian (if this is a bug at all?) will be present there as well. I hope you don't use experimental images? They are not ready for usage.

Can you provide results of this test: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Take those as reference. PS. It's safe to kill the compiling headers process.

I put torrent server on Lime 2 and some stress testing scripts on Cubietruck with 4.11.5-sunxi ... I want to see then crash ... only one day up time, so hard to make any conclusions yet.

You mean that you will start directly in desktop? You need to login once to create a username, than desktop goes on and next time you will be running desktop ... if you downloaded desktop image in first place, otherwise you need to repeat the job. Check docs.armbian.com for basics.

I am almost 100% that it won't work - there are zero relevant changes to sources between 5.30 and today. Still wanna try? Those are development boards and if something is not working perfectly fine, nobody cares since most such things are fixed with software ... We have one (few?) known case(s) and there are 10.000+ happy Orange pi Zero users. Nobody will believe ... even I was initially very sceptical. It also could be some hardware damage, which can happen.