tmihai20 wrote:I tried installing a newer 3.10 kernel on OMV based on Debian Jessie
What newer version?
HardKernel github is currently at Kernel 3.10.105 and so is the Kernel of this Debian Jessie image.
In fact I'm currently building a new 3.10 Kernel with the last two commits that happened since the last build of the Kernel.. there really isn't much going on.
Also question probably is where you got these "newer Kernels" from, cause that's probably the issue, installing Kernel that were not made for this image and simply conflict with the Kernels that are already installed.
tmihai20 wrote:and 4.9 kernel on the beta Ubuntu image.
As said before, the beta ubuntu image comes with its own repository for Kernels, just doing a regular system update will give you a newer Kernel, if available.
tmihai20 wrote:I mounted the boot partition on Debian Jessie, I remember that Ubuntu already had it mounted.
I think it's quite the opposite. On Debian bootfs is explicitly mounted to /boot/, while on Ubuntu it's not mounted and therefor autofs mounts it to /media/odroid/boot, or it's mounted to /media/boot, not quite sure, since I don't use Ubuntu.
Maybe you broke the update process with your "mounting" not quite sure.
But if you check /etc/fstab you'll find that boot (/dev/mmcblk0p1 should be mounted to /boot)
If you update to Kernel 4.9 you need to change /dev/mmcblk0p1 to UUID=<UUID-of-bootfs> since Kernel 4.9 does no longer always use /dev/mmcblk0p1 as the boot device.
tmihai20 wrote:I will use the latest available kernel for all of them for now, because I need it to be stable.
If you need stable, you shouldn't experiment with Kernels that were not made for the images you're using.. this will most likely cause issues and break the working update processes.