Igor

We are ready to go https://gitlab.com/armbian  It was working extremely slow and took ages to register. I guess everybody wants to escape the monster ASAP 

seems that you're not the only one

Run for your life...!!!

We are ready to go https://gitlab.com/armbian  It was working extremely slow and took ages to register. I guess everybody wants to escape the monster ASAP 

It was a minor/partial update, firmware blobs and armbian-config.
 
If you want to have latest stuff (which might break for no reason because it's untested) switch to the beta repository.

My addiction got the best of me and I picked up a RockPro 64 as well.  ;-)
 
OK, back to the cellar...

It exists as .csc target in the build system, while official support ... we haven't discussed. I tried it 1-2 weeks ago (kernel 4.17.RC something) just for fun: there is no HDMI, no DVFS, ... but boots, all four cores are up, USB works, wifi works ... and can be used for some simple tasks testings.

Yes, i no that! Probably this is my first post here, but i am one of the first armbian users
 
Well i change  CPU governor ondemand to performance, and incredible it works! No more green artefacts on screen but maybe more Electricity Costs
 
Thanks Igor for the project.
 

When it is done is done. Armbian is not a professional service and we have no particular interest nor resources to deal with this function. A project is open and if this is your pain, you are welcome to join and try to move patches from NEXT to DEVelopment "today". 

Next kernel is planned when upstream 4.17.y - 4.18.y changes in the area of particular interests are significant enough to move forward. Anything else is unpaid education or throwing resources straight into the trash bin.

Perhaps 2-3 months?

Solved in a simple manner: https://github.com/armbian/build/commit/442ab52d3e821fac5453fb21ec2ab294acb53dfd

Patches to support this function are only available in the 4.14.y NEXT. They are not yet in the development branches and it's not a simple copy/paste job.

Hi Igor,
 
I got what you mean.
 
Yeah, I saw many forums and feedbacks for the OrangePi Zero, NanoPi Duo etc with BAD Wifi connection.
 
Best regards.

No, that is not possible.

When you install your own kernel, you have to freeze kernel updates in armbian-config to prevent updating from our repository.

My problem has been solved，I compiled a new image ：Armbian_5.45_Orangepizeroplus2-h5_Debian_stretch_next_4.14.44.img .

Yes, but possible that upgrading will break since I forgot to merge few files. Now rebuilding once again - with new version.

Yes indeed. It will take another few hours to rebuild repository. Will see in the morning if everything went o.k.

What about solving ramlog this way:

- added cronjob on every 15 minutes
- if space is 75% full do:
logrotate --force /etc/logrotate.d/ write to SD card truncate and remove files It is better than now. Good enough for defaults?
 

Yes. Fixed.

Yes, you do. Sometimes, rarely we push update only to some critical sections. In this case, only armbian-config was updated, while Armbian internal number or a majority of packages remained the same. A version number is taken from BSP (board support package). This means it won't change until that package gets an update. This usually happens at the major upgrade. 

Nothing to worry.

If you find some specific problem with armbian-config, the best way is to open an issue ticket here: 
https://github.com/armbian/config/issues

Fixed but a bit different since it doesn't work the way we have before.

It seems they are not sorted at all - as they were added. We had many troubles with this plugin so my modification: manually order by importance without showing exotics - fell out. All variants have advantages and disadvantages. I'll adjust that asap.

I didn't notice. Perhaps enabling it would help? https://github.com/armbian/build/commit/c1cb1d77f0812978160506de9646c352df0c9d48

"committed 8 hours ago" 
https://github.com/armbian/build/commit/0e7681ee250a2beab744b854062ee558e4bf1e39
Updated package will be at next nightly rebuilt but since I just tear down build server it might take more than 24h before things are back in action.

Appears to be fine now.  Thank you!!!