Werner

I have a dedicated KVM image, as I don't want to introduce changes from the distribution that might impact the build process - it's an old habit of mine.
 
Anyways - root is a major deity on a *nix system, and an errant script could do a fair amount of damage - it doesn't have to be a "bad actor" but even a typo...
 
Started looking at fakeroot as an option, as this does provide the opportunity to do file manipulation as needed to build an image.
 

By default yes, but it is possible to tune-up (at least KVM) to run almost at the same speed.

Changes were applied also to the stable repository. No need to switch anywhere. I guess all mirrors have also been updated by now.

Agreed.
 
I think the logs are a good call,  if we have SoC sub forums in "community forums" we can allow more or less anything appropriate.

If it helps anyone,  I've been running succesfully with gigabit ethernet on eth0 using the dts and h6 dtsi from Icenowy's
 aosc-sunxi64-4.19-malimidgard-hack-2
 
branch and the armbian dev kernel .    I force a stable mac_address by adding  
allow-hotplug  eth0 
iface eth0 inet dhcp
    hwaddress ether xx:xx:xx:xx:xx:xx  (replace the xx's of course with a good address)
 
in the /etc/network/interfaces  file.  
 
I haven't yet been able to get spi-jedec-nor  flashed to enable sdi boot,  I get an error indicating that there is a mismatch between what is specified in the DTS vs the overlay, but I am booting off of an sd card with the file system on a usb connected ssd.
I'm going to try to build with the mainline 5 kernel soon,  to see If I can pick up the new graphics drivers...
 
I believe version B of the device is supposed to be out soon...

Thankyou so much for all your comments and help. I honestly did do my reading, but not what has been pointed out. So I stuffed up. 
 
I rebuilt using bionic before reading the last of those comments, but its up and running so Ill see how it goes.
 
The first thing I notice is the CPU is running at 47c instead of 57-60.c I also changed IP address and it instantly changed it without reboot. Two big differences already.
 
In trawling the logs I did notice some DNS messages. Now they make sense. So it looks like pihole was having problems with Jessie as well, just like you point out. 
 
So all up, although its only been running for an hour or so its already looking better.
 
Thankyou very much for the help. And hopefully I wont be back on this thread !!

https://github.com/armbian/documentation/commit/9d43fb8b2baf45258b5ef84dafc31585889cfc70

In case you want to squeeze in something. DUE: Sunday.

Yes. Or Debian with the same kernel. Depends on your taste  
As for myself I prefer Debian as the directly by Debian maintained packages count is way higher than by Ubuntu.
Lots of packages on Ubuntu are Universe or Multiverse which means there is no guarantee for support or (even critical) fixes.

Since the last year (and around v3.3 of pihole) it isnt recommend to use pihole with debian jessie anymore:
https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/

So pihole will run much smoother with debian strech (or Ubuntu bionic).

That is a lot of traffic but you don't have to host the downloads, that's why I said necessarily. You can use sourceforge to host all the files, and you currently use torrents which is smart.
 
Thank you for sharing the information, it is interesting to see.
 

 
I didn't realize there was so much traffic but file hosting can be had for free being Armbian is open source. I was strictly speaking of the website when I said 100/month.
 
I think hosting fees is very relevant since that money can be used elsewhere, especially since it seems like it must be expensive currently.
 

I think that was never the intention that 'armbian people' only answer to questions.. fist cause there are for sure other smart(er) people here and their contributions are highly appreciated.
Personally I wouldn't participate in such an sub-forum. But I don't spend as much time in armbian when my 'dayjob' doesn't allow it. By paying for support people expect solutions, solutions aren't that easy. If *random hardware feature* doesn't work the pressure should be on the boardvendors side to fix it not on ours. For maintainers spending much more time to keep the project running (e.g. Igor) some sort of a salary might be mandatory and ways to make this possible isn't as easy but I don't think that such a payed supportforum is the way to go.
how about a less radical approach. Just ignore topics which don't provide the needed information? Those really interested in getting their issue heard/solved may get it that there's information missing.
 
challenge accepted. (we shouldn't lose our sense of humor even if it's a dark one )
 
Besides that, I'm fine with stupid questions. Even in the field I'm good in (chemistry) I sometimes have stupid questions.. Happens.. but the way you react when you realize that you asked a stupid question makes the difference.. If you start to complain about support and and come up with "but the users are most important" I'll answer you with a polite form of "Go fu... *have sex with yourself*"... If you look at a forum from an SBC armbian doesn't support you'll see that moderators there have some sort of a scheme for questions they don't want to answer - always ends with: believe us we sold 20 millions boards we know what we're doing..
We've to accept that there are people on forums which don't spend as much time on SBCs to get trivial issues solved on the other side, they've to accept that if they're not willing to invest time to fix things on their own/help us figuring out what's wrong, I'm not willing to waste my time with their issues.
 
 
The first iteration of the new mandatory parts for opening a topic in technical support was a failure:
 
the new version with:
is at least not as harsh anymore.. but as @zador.blood.stained and @martinayotte showed  (https://forum.armbian.com/topic/9400-does-not-see-emmc-after-component-change/) here, there's still room for improvement. Maybe it needs some days/weeks/months until we have a solution which is "more or less" satisfying but I still think setting some pressure to people to provide armbianmonitor in their starter isn't a bad thing. Cause it is annoying to ask always for it and hope that he gets it after you asked for it 10 times..  (and it's also annoying to find different polite forms of the part from the "personal non rational rant" )
 
For me this thread should be merged with "Improve 'Support over Forum' situation" - IMO it belongs to it. If nobody disagrees on that let's move it there.

Yes. In the early days, about linux 4.17 when the first initial support for Allwinner H6 from Armbian came, it was limited to 1,5GHz but I remember a patch for 4.18 which rised the max frequency to 1810MHz and it ran well. I did benchmark without cooling whatsoever and it survived. Over a longer period of time on heavy load I would think about some kind a cooling though,

I guess this speaks for yourself...

Technical support section is mainly a feedback to improve Armbian as operating system. We can only deal with Armbian images and our tweaks. That's plenty of work and we have to do something about that.

"If you deal with everything you fix nothing"
 
Common issues sections is already on the edge/outside since mainly contains generic Debian/Ubuntu problems, which we don't have intention nor resources to deal with. Armbian specific problems are already enough. I am seriously thinking to move it to less restricted "community" area, where only general restriction apply.
 
More topics in technical support could also mean developers are doing a lousy job in making Armbian. But since overall user base is growing and since we people are lazy by default (I also belong to that tribe), this section also grow. No forum around is happy on opening more topic for the same issue. Over and over again. Technical support questions are specific. They need to contain certain things or they are useless.
 

That was also intendenten. When you are putting a pressure and wasting precious time, you are making a damage and if you are aware of this, a progress was made. For all of us. It's like traffic regulations.
 

Yes, that's all about. All this is just yet another SPAM filter. One out of many that we already use.

It is the same SoC so yes, it may suffer from all these issues as well.

@thexman
Thank you very much for recognizing the problem and your github bash files! They are really heplful!
I have Orange Pi PC server at home, which serves as dlna server and also tvheadend and samba store.  So after last update I was really upset when it occurred I can't connect with server anymore through SSH. Fortunately I installed Webmin few months ago and thanks to that I was able to get to webmin virtual console and easy repair the systemd thanks to your files.
 
It just came to me that I've got two Opi Zeros, running as dlna players and they have auto updates on. But yesterday they worked fine. I hope this bug won't happen to them.

I don't know, but this leave me in big doubts, since this 0x03000030 doesn't point to any kind of registers in the Allwinner datasheets or specs
 
EDIT : It seems that only "compatible" change is required, although this is pretty much a hack, since it doesn't use H6 compatible that @Icenowy delivered ...

@martinayotte I remember in mainline Linuc I killed sun50i-h6-emac in driver, and it only exists as a fallback compatible string.

Forums must remain accessible without pay (we had this discussion years ago) but perhaps an option for paid support might be added. Currently, I don't see possibility nor willingness to provide such services.
 
When we start talking about paying for 1st class support and the time for that, list prices kicks in. Those are not amateur/community friendly while average folks on the other hand see: "5 EUR for the monthly support? That's 1/3 of the board price. Outrage!" It would be ideally to rely financing from community not corporate. 100 x 5 EUR is better and safer than 1 x 500 EUR.
 
Whether you pay for support or not, you will still need to provide required info and obey certain rules. If you would waste more time than you pay for support, support provider would inevitably make a loss which can only lead to bankruptcy or stop providing such service. If support provider hire incompetent people to deal with you, you will not be satisfied ... 
 

Yes, that was the intention! If you are to lazy to supply logs and tick acknowledgements and expect an answer, which might save you weeks, you simply don't deserve it. From anyone.
 
I am sure this idea could be polished and can be polished, but I don't think it's a bad one until somebody convince me it's bad.
 
 
Yes, community is important - I don't want to waste it's time.  As you can see this is not about me or about the team. Nobody can answer questions which lack vital informations. Those measures should save time. Everything is community driven - only technical support section have more restriction. 
 

 

Application is disabled until text is polished out, than if will be limited only by content count, days as a member, ...
 
Hacking and bringing boards to life is the funniest part  But somebody, besides me, has to be accountable also for the not so fabulous and interesting work  Not to mention dealing with idiots/spam on all levels, which came with the project recognition.

The text all looked fine to me, unless you mean you're still working on the definitions of tasks.

Hey @Igor  Here's an alternative version of the board maintainer text.   Feel free to tune as you see fit.

https://gist.github.com/lanefu/7c54235264d0f8e442c8799249220bf6

Great! Thanks. Its enabled.
 

I keep forgetting we already move DEV branch to 4.20.y, but haven't tried H6 support yet. Porting to 4.19.y ... not sure if there is a point in that and if I want to get my hands dirty  

New features and restrictions for "Technical support" area:
 
 1. Validating users, those who just register are unable to reply to topics. They are forced to open a new topic.
 2. All users have to accept conditions (cookie last one day): 1. Call to use docs and search 2. Call to support us 3. Call to provide info
 3. Each time a topic is created, you need to add: armbianmonitor and accepty several conditions
 4. Auto lock topics is now set to 365 days, pinned and featured are exempt, ... and it will take a few days before locking will be completed.