I got all the files into: /lib/firmware/ap6256/ and got an Set Public Address for hci0 failed with status 0x11 (Invalid Index)
Does it have to be in /lib/firmware/ ?
Or anything else I do wrong? I got the BT Support from armbian-config active
Edit, moved the files:
root@orangepi3:/lib/firmware# btmgmt public-addr 00:03:19:9e:8b:00
Set Public Address for hci0 failed with status 0x11 (Invalid Index)

Hello GilGonGan,
I've quite struggled on this (on several successive topics) (more than it should have been), due to this poor support of online sources over time, that have lead on my side to a lot of experiments trying to repair / correct the Jessie archive URL (hence a lot of waste of time).
Indeed, i've in the end upgraded my previous Jessie armbian to Stretch without reinstalling.
Sadly i haven't taken any notes about it ...
Basically i did, as far as i can remember (after the unsuccessful experiments while still being on Jessie) :
- upgraded what i could while still being on jessie + removed a few packages to clean up the system
- changed my /etc/apt/sources.list to :
- put in comment the content of /etc/apt/sources.list.d/armbian.list and hypriot.list, as it seems they are not available anymore (it's the only two additional sources files i had)
- upgraded the whole system with
- resolve several issues, i don't remember all of them (and maybe there are not only related to the upgrade process, but rather to the pine64 support for Stretch). For example i had a lot of issues about the wlan (with debug messages that were printed all the time due to two wlan cards being now discovered ... took some time to figure), now i have (i think it's the most relevant part but i did a lot of other things like disabling IPv6) :
to be added in /etc/network/interfaces in order to disable the second wlan1 interface (and i'm using wlan0 in auto/dhcp mode) (as seen here : https://github.com/ayufan-pine64/linux-build/blob/master/package/root/etc/network/interfaces.d/wlan1)
And for IPv6, in /etc/sysctl.conf :
In the end i still have a running armbian Stretch on my PINE64 box (with octoprint).
Fore reference, my PINE64 board has been bought during the kickstarted and is a PINE A64 model (with mem 2GB).
Good luck in your upgrade process.

Sorry for double posting. Hope this post is here in the right thread.
Hello,
I have installed Armbian 5.8.2 (strectch) with with 5.1.0 rc1 kernel (on internal emmc) onto a X96Max box.
I want to use the box as NAS to substitute an old dockstar device.
NFS and SMB is running well.
But i have problems with the USB3 port, a powered USB3 hub disappears under heavy load. And with it all 4 connected drives.
The drives are all powered with it's own power supply.
The USB2 port runs like in slow motion. Much less then the expected USB2 speed.
An unpowered USB2 hub connected to the USB3 port runs stable with all the drives with the expected speed.
I think it is a firmware issue. So i have two questions.
How can i update the firmware of the box and how can i update the kernel to 5.2 without doing a fresh install into the emmc.
I am lucky that the system runs in emmc after a lot of tries.
Regards
cyber

Maybe you could bring me on line what problems you experience with the newer kernels?
I assume it is the problem that with a bootloader for 1000 MHz you have instabilities? If I´m right then a new bootloader will not help with this. What you can test, commenting out the avs in the dts file, compile a dtb and then test if the kernel is working for you.

That is the reason why we can't update our EspressoBins to kernel 4.19.4x and above anymore without experiencing crashes.
Hopefully the new bootloader released by marvell recently will be able to handle the new frequencies in the system.

I haven´t tried an armbian kernel for a while now. I will look into this sometime in the next weeks. But as far as I followed the upstream fix should be in the kernel 4.19.xx.
It is just one fix missing regarding a too low voltage, which @sqpr found. I will see if I can point the right people at this patch.

On S905x2 (it's a close platform with S922) eMMC works with this kernel. Perhaps the reason for the settings or is it the result of using a removable connector for the eMMC on the N2. I noticed that if you copy the data in manual parts no more than 500MB, with an intermediate "sync" , everything is copied correctly.

Did you ever solve this? I may have a similar issue, I've been googling for hours and just found your reply.
https://forum.armbian.com/topic/10480-attempted-jessie-to-stretch-failed-likely-dead-on-reboot/

Hello!
I tried to update jessie dismally, here:
https://forum.armbian.com/topic/9984-apt-get-update-pointing-to-404-not-found-ip-151101240204-80/?do=findComment&comment=79685
Since then, I have been attempting to update to strech, I feel like I got close, but it's failed and I strongly suspect, my next reboot will hose it.
(I will not reboot it, linux is wondeful!!)
I updated my sources.list file to have the following 4 values.
deb http://httpredir.debian.org/debian stretch main contrib non-free
deb http://httpredir.debian.org/debian stretch-updates main contrib non-free
deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
the apt-get update and apt-get upgrade (appear) to be working fine.
apt-get dist-upgrade will spit out the following:
Errors were encountered while processing:
network-manager
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Upon further investigation I have done the following tips in this post precisely
http://forums.debian.net/viewtopic.php?p=122113#p122113
These have failed, it outright refuses to get network-manager on there.
Job for NetworkManager.service failed because the control process exited with error code.
See "systemctl status NetworkManager.service" and "journalctl -xe" for details.
journalctl -xe will produce the following:
May 25 15:33:28 orangepizero systemd[17220]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Bad file descriptor
-- Subject: Process /usr/sbin/NetworkManager could not be executed
When I begin to google that information I start reaching even less google hits and possibly even a bug?
https://www.google.com/search?rlz=1C1GCEA_enAU767AU767&ei=K9ToXI64A6LYz7sPvr2qwAE&q="NetworkManager.service"+"bad+file+descripor"&oq="NetworkManager.service"+"bad+file+descripor"&gs_l=psy-ab.3..33i160l2.9570.14812..14992...3.0..0.276.4626.0j13j10......0....1..gws-wiz.......0j0i22i30j33i21.bL0kzS4p6yg
Finally, when I log in to the system remotely it even says :
"ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i"
"Kernel was updated, please reboot "
However, I feel this is very unwise, until I can be certain that the update and upgrades and clean and autoremove and all the commands to maintain the system at least spit back results indicating success.

I remember trying to install a usb wifi dongle in the past and while it gave me lots of headaches, i did manage to make it work.
It's been a while since i used wifi (it's been a while since i used the SBC too to be honest).
Today i decided to power it up at least just to update it. When it was installing kernel related stuff, it gave an error stating it couldn't build the 8192cu module (or something like that), the specific log says
scripts/Makefile.build:432: recipe for target '/var/lib/dkms/8192cu/1.10/build/8192cu.o' failed
make[1]: *** [/var/lib/dkms/8192cu/1.10/build/8192cu.o] Error 1
Makefile:1368: recipe for target '_module_/var/lib/dkms/8192cu/1.10/build' failed
make: *** [_module_/var/lib/dkms/8192cu/1.10/build] Error 2
make: Leaving directory '/usr/src/linux-headers-3.4.113-sun8i'
Among a long list of errors.
Anyway, i tried using the usb dongle. While it seems to work at first, it has a strange behavior.
First of all, now instead of only showing only a wlan1 interface, it also shows a wlxxxxxxxxxxxx one. Sometimes it auto connects to my wifi network on one, sometimes it connects with the other. Another strange thing: When it connects, it gets an ip and i can confirm in my router stats page that it's connected but as soon as i disconnect the lan cable, it looses connection with the router.
I have tried most of the things i tried last time i made it work like compiling the rtl8192cu-fixes sources and installing them.
I have 8192cu active in modules.conf, lsmod says that 8188eu is also active.
I'm a newbie in linux and i already lost 3 hours trying to fix this. What am i missing? is the wlxxxxxxxxxxx supposed to show up?
I guess you have all the info you need in the armbianmonitor file, if not, ask away.
Thanks in advance.
Damn, just noticed i probably posted this in the wrong section
[EDIT: Pressed "send" by mistake while still writting)

For Lite2, latest Armbian Bionic\Stretch will not boot to video vs OrangePi Lite2 image which has working display driver. Is there work being done on getting video driver working for the Armbian image?

I had hoped the information might be useful for bisecting which kernel update might be responsible. Is the source of the problem known and fixed, or is the fix being referenced only disabling the 5.85 release? Is it useful for me to search for the older nightlies and narrow it down?