Rock64 no longer boots after dist-upgrade

[KernelPanic]

mmcblk1 = sdcard
mmcblk0 = emmc

So am I right in saying it mounts the wrong efi by default?

That happens because images use the same partition titles, you could try changing the fstab to which ever device you want mounted.

Everything is working as before except for openvpn which can't initiate a connection anymore
ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)

try apt-get --reinstall install openvpn

If that doesn't work, it may be your openvpn config loading from the wrong partition

I think I figured it out after some more digging.  I'll post what I did here in case it might help someone else.

I think because I copied a kernel from the SDcard that I wasn't using before on emmc I am still missing some files I would've gotten with a normal install of the kernel. (In this case the modules in /lib/moduiles). 

Code:

sudo modprobe tun
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.120-rockchip-ayufan-209/modules.dep.bin'
modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.120-rockchip-ayufan-209
                                                                                                                                                                                                                                        -ayufan-209
cd /lib/modules/
/lib/modules$ ls -l
total 16
drwxr-xr-x 3 root root 4096 May 13 13:54 4.4.120-rockchip-ayufan-213
drwxr-xr-x 3 root root 4096 Jun 16 01:41 4.4.126-rockchip-ayufan-239
drwxr-xr-x 3 root root 4096 Jun 12 21:37 4.4.126-rockchip-ayufan-260
drwxr-xr-x 3 root root 4096 Apr 11 14:27 4.4.77-rockchip-ayufan-136

So I purged all the kernels and reinstalled the 213 kernel. After a reboot modprobe now doesn't return any more errors and OpenVPN works again.

Thanks!