Igor

Another bug. Haven't pinpointed yet but it most likely comes from upstream. Wireless connection (using nmtui-connect) timeouts on initial connect very often, while the exact same setup works perfectly fine on Ubuntu Xenial. When setting up an AP it works fine.

This device is not directly supported in this kernel. This might be helpful: https://github.com/armbian/build/blob/master/packages/extras/mt7601.sh This is Wifi only, no Bluetooth.

How is this related to development? You just want to solve your problem and move on. Yes it is support case. We (3rd time) dont provide it yet since we are to busy working to limit down support questions as much as possible, we cant support somethinf that changes every day ... before we provide stable builds. How to explain this to you without sound arrogant? Time is extremly scarce, there are way to many users with their own problems than people who are able to provide answer. Its always a trade. You follow rules. We help. You ignore rules. We kick your as You help. We help. And so on ... Wrote on mobile

Yes. Wrote on mobile

I have many problems. It's a trade. Once again. There is no end users support for boards that are still in development process.

Fixed.

I know. We had some changes and it broke ... fixing at this moment.

I already suspected there are slim chances that they will work ... Since those were the only one on a stock with the option to return I said "why not". After rebooting the server one of ethernet ports remain dead Strange. Well. I have absolutely no other option than exactly those: https://www.heise.de/preisvergleich/crucial-dimm-16gb-ct16g4rfs424a-a1345631.html Nothing else works. I have tried 3 different before.

https://www.facebook.com/groups/1483270805309190/search/?query=R69

Have you changed kernel perhaps? If you don't write an essay of what you were doing and supply logs you are wasting time. Start with: armbianmonitor -u

We are not clairvoyant or mind readers Please describe your setup as best as possible so we know what your operating environment is like. 1. Logs, when you can boot the board: armbianmonitor -u (paste URL to your forum post) 2. If your board does not boot, provide a log from serial console or at least make and attach a picture, where it stops. 3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem.

It's a good news. We are one step closer to farewell with junky Allwinner 3.4 kernels.

@o_flyer Is perhaps such display? https://github.com/TinkerBoard/debian_kernel/commit/ea22619e44dea9118442c45b33cf243ed2d85021 https://github.com/TinkerBoard/debian_kernel/commit/26a39a08af6382f0ea9afebf0b1630d46d94d550 Than some kernel patching is needed. Just to understand where you might need to start digging in ...

It's only on first boot. Then perhaps we should just leave that disclaimer always on? Some pop-up was planed - while my HTML/JS programming is rusted Haven't done that for years and even small things are hard and must read around. Yes, people do not read warnings anymore those days ... One option is to freeze kernel upgrades on those images by default and there is no need for extra warnings.

You are able to delete until there are no replies AFAIK. In other (rare) cases just approach to one of the staff and it will be done.

We are not clairvoyant or mind readers Please describe your setup as best as possible so we know what your operating environment is like. 1. Logs, when you can boot the board: armbianmonitor -u (paste URL to your forum post) 2. If your board does not boot, provide a log from serial console or at least make and attach a picture, where it stops. 3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem.

And you need to enable it (LCD) in DT. Speaking generally.

You need to get a driver to run and that driver is usually supplied by hardware maker. It's also possible that support exists in a kernel, but it's not enabled. It's on you to find out ...

What can be wrong in this part of the code: https://github.com/armbian/build/blob/master/config/templates/customize-image.sh.template#L19-L32 Is your script running on Ubuntu?

We don't deal with 3rd party hardware support. Board troubles are already over the top. Edit: Moved to Peer to Peer technical support

It's probably related to AP6212A problem .

Just read the documentation.

Yes. https://docs.armbian.com/User-Guide_Allwinner_overlays/ Untested - not for end users yet.

https://github.com/armbian/build/commit/e868c5ddfb611cc15cfe0168db4d83666e4537d9

I got modules today but the server does not like them That means upgrade costs jumped to 1k EUR. Buy cheap buy twice