Igor

Any better way to boot SD with attached eMMC than nuking its boot part?

[connection-mac-randomization] ethernet.cloned-mac-address=random wifi.cloned-mac-address=random After adding this part, connections starts to go cycle up / down / up / down ... checked on three different drivers. Ralink, Atheros, Mediatek. http://sprunge.us/MLdL

I noticed problems with external adapters first. There are not many working ones and if those working ones are further crippled by this feature, there are no woking left Well, let's do some more tests.

Yes, it's related. Shall we add this by default?

DT is only for mainline kernels and it resists in /boot/dtb/ directory. There are usually more than one DT since the kernel is made for more boards at the same time. Which one has to be loaded is defined in u-boot. You can override this in armbianEnv.txt which is loaded by u-boot start script (boot.scr). If you by mistake started with the legacy kernel, there is no DT but Allwinner way of defining things. We can only cover onboard hardware. Even that proves to be an extremely hard job. 3rd party hardware is on your own, but perhaps you could find people, who have done this, here.

Automount works out of the box on desktop image. Or: https://www.google.com/search?q=usb+automount+debian+server

If you ran the latest beta: armbian-config -> software -> install headers https://github.com/armbian/documentation/blob/master/docs/images/armbian-config-6.png

Why not. It has onboard WiFi which can be configured as AP. It's not very powerful one and can't handle many clients at once.

If you are trying to add anything to BSP package you need to create that folder. https://github.com/armbian/build/blob/master/config/sources/meson64.conf#L57-L61 We are creating a deb file in tmp. https://github.com/armbian/build/blob/master/lib/makeboarddeb.sh#L214

It looks pointless to me - only big red or toxic yellow signs might help, like Thomas suggested Its all written but people failed to read the text. You also failed to read or understand my recommendation. Stock image is also not for usage, but for other reasons. If you like your time and data, you will need to set up everything yet again.

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.