Werner

The questions which come up in the 'development' forum are anyway more like the average 'supportquestions' there's not much a difference... IMO development was never used the way it was supposed to be used..

could we 'switch' the behavior as well? E.g. default is mainline kernel and subforum is outdated 3.4 kernel which is only available for H3 anyway? Some kind force that people should move to mainline..

Forum enachements:
theme "armbian" updated with upstream version, manual fixes and adjustment with theme designer, fixed recycle bin, updated member map plugin added crowdfunding plugin (this will show supporters automagically) added "show new topic rules" plugin (currently enabled in recycle bin for test) added raffles and giveaway system (will be enabled for users when properly tested) Please report if you find any bugs in the forum theming

If one is running a DNS server for the LAN/WLAN - probably better to keep it on the wire

You can send a PR with your changes to the kernel config here: https://github.com/armbian/build

If you purchase one, they are so cheap, it will help a lot ...

All the information you can think of on an easy and simple webgui
https://github.com/netdata/netdata
 
Even has a really simple script to download all deps and compile the program for you
https://github.com/netdata/netdata#quick-start
 
Just thought you folks might be interested...if it's linux...this will work on it

Thanks. I saw the applied patches for testing.
I read your links and realized that it is customary to make changes in a separate branch and then pull request. 
Of course, first we need to discuss with the community the need to develop new functionality. I will do so in the future.
I'm currently laying out a number of patches that I think are the most important. Although it is not a tradition.
You can apply them on your own behalf, after testing, if you see them reasonable. I don't claim authorship.
Thank you for your understanding.

We, Armbian Devs, didn't found a way to fix that issue yet, so you will need another way to get ethernet, such as USB adaptor ...

Yes, I've just added NEXT to them : https://github.com/armbian/build/commit/c6e7f4fa4539d4aa1a9c9dc4b66a44a5619f4926
 

Share and we will take some  

I can share the fact that I've not resolved the H6 issue freezing at "starting kernel", I've even tried them with 5.0.0-rc1, still the same.
If someone can help narrow the issue, I will be glad ...

H6 can be created with NEXT now in as is state, but has to be enabled/added. If DEV is broken for some boards now ... that is not an issue.

after searching the internet we have to do it the blacklist way

for every module you doenst want to load create a file in /etc/modprobe.d with the name <modulname>.conf that will include the line
blacklist <modulname>
like that :
/etc/modprobe.d/xradio_wlan.conf : blacklist xradio_wlan  
If we do this for all 3 modules we get:
 
root@opi-zero(192.168.6.99):/etc/modprobe.d# cat xradio_wlan.conf mac80211.conf cfg80211.conf blacklist xradio_wlan blacklist mac80211 blacklist cfg80211 After a reboot the modules arent loaded anymore
root@opi-zero(192.168.6.99):~# lsmod Module Size Used by lz4hc 16384 4 lz4hc_compress 24576 1 lz4hc ftdi_sio 40960 0 sun8i_codec_analog 24576 1 sun4i_codec 32768 3 usbserial 24576 1 ftdi_sio snd_soc_core 118784 2 sun4i_codec,sun8i_codec_analog snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 69632 2 snd_pcm_dmaengine,snd_soc_core zram 24576 5 snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun4i_gpadc_iio 16384 0 uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1  
for reference:  KernelModuleBlacklisting
 
Howto: Create a file '/etc/modprobe.d/<modulename>.conf' containing 'blacklist <modulename>'. Run 'depmod -ae' as root Recreate your initrd with 'update-initramfs -u'  

Very good!! it is working for me as well
 

I've received my OrangePi-RK3399 recently ...
Just for trials, before doing any real development, I gave a try with a NanoPC-T4 4.19.y image compiled a month ago, and it worked "as is", even eMMC and WiFi is running fine.
That it is a good starting point !
 
Of course, to be able to boot from SDCard, we need to short the eMMC clock using the test point TP50265 :
 

The reason for this seems to be a regression or a missing commit from @Icenowy sources (https://github.com/Icenowy/linux/commits/h6-integrate-2-ugly) which has not made the jump into mainline (yet).
Therefore you either have to use the 4.18.0-rc7 kernel image (which I run two OPi 1+ perfectly fine on right now) or temporarily disable dwmac like @martinayotte did as workaround to successfully boot up the board with a kernel built from newer sources (and use a USB-Ethernet adapter).
For confirmation you can utilize a UART serial adapter to check the kernel boot for errors like "sun8i_dwmac_probe+0x164/0x518".
 
As stated mainline support has still a long way to go to better support the H6 SoC. Do not just discard the board. Just put it on the shelf and it may run fine in a couple of month.

On my side, I kept my previous OPiOne+ build done with h6-integrate-2-ugly branch.
I didn't investigate further about Mainline 4.18.10 since Icenowy suggested to check with 4.19.y, but I didn't take the time to check ...
 

I've just started new build with 4.18.12, and when finished, I will disable the dwmac and check if it boot properly, I think it will.
This would mean that patches for dwmac added in 4.19.y would need to be backported, or we wait for 4.19, which can still take awhile ...

Armbian is mostly ahead of the upstream kernel releases in board specific functions. Up to about one year. Regarding the biggest group (Allwinner), the only change will be that we will remove a few patches  and when 4.19.y is sorted out it will become our NEXT for A10/A20/H3/H5/H6/A64 and Armada 3700, Rockchip, Meson, ... almost all supported board as a first or second kernel.
 

Thanks. It turned out two topics on one big question:
How to do better?
I will prepare an explanatory note and patch, or as you said:
I think then the two topics can be combined.

Do it as you think it's best and if it turns out that it isn't perfect, the PR can still be edited before it gets merged. I would link to those two threads when sending the PR, so that a reviewer know where it comes from.  

There are still (many)some (short and) long-term questions which are scattered on the forum and in our heads which we would need to discuss.
 
- release naming, 2018.10 or 18.04 + some RFC as shown on the pic,
- collecting wishes on a special web page or forum topic. When someone approaches with "I want to help" that it is appointed to 1. Check issues on GH, 2. Fixing sound ... 3. Creating this ...
- improving testing protocols, automating what is possible. I'm low on ideas what more is possible to do.
- what to add to »end of support«?
- secure project longterm survival, leverage maintenance costs to users or drastically limit down free support,
- enforce browser of choice for desktop images, Firefox and/or some lighter alternatives?
- fix Bluetooth on all Broadcom AP62xx devices. Its the same on most boards, but we have it working only on a Cubietruck IIRC
- sum most frequent problems under »The Ten Commandments« / FAQ and promote it as much as possible
 
- does forum need structure update?
- add/remove moderators? Disable rights if not moderating content in past 6months?
- enforce forum rules? Some very simple ones.
- users are still seeking for help without providing logs. What to do about?

Download UX:
- make a bigger diff between nightly and stable, desktop and CLI (Gorazd)
- add a warning when nightly is downloaded, (Gorazd)
- tested devices lead to their test page where exists instead of Amazon affiliate, (Gorazd)
- tested hardware have information to which kernel is attached to but not displayed, (Gorazd)
- check other download option still no visible enough, (Gorazd)
- add a support box with 1. Check common issues 2. Search for solution 3. Ask (with a link to the correct forum) (Gorazd)
- add a button »alternative builds« with a link to dl.armbian.com/DEVICE (Gorazd)
 
To keep things in place, I would like to ask @Tido and @chwe  to help keep this 2do list up2date according to with our decisions.

@martinayotte
 
Ok, new image is up and running:
 
AP6255 Wifi works, however somewhat flaky. Ping times are normal for Wifi, but when I type it takes some time to show the characters.
 
USB3 Ethernet is not being recognized in dmesg nor does it show up in lsusb
 
USB Wifi can scan, however it does not let me connect, complaining about a wrong WPA2 Password.
 
 
update:
just switched to the nightly built via armbian-config. Update to 4.18.11 went successful
USB Wifi works now, USB3 Ethernet still not recognized

Yes, that is planned, but we still have weeks - we also don't need to jump on v4.19.0 ... It's DEV kernel and the idea is that DEV becomes NEXT when the time is right. Which is even more distant. Since 4.19.y is the next LTS it will be worth to prepare it and port support from more recent versions. 4.19.y is for 2019