After Update OMV4->5 Armbian kernel remained at 4.14
-
- OMV 5.x
- gelöst
- Upgrade 4.x -> 5.x
- FredK
-
-
Reboot?
-
I expected a kernel 4.19 but the kernel version continued at 4.14.
Actually now it's 5.4.
Just run -
-
Reboot?
Several times.
-
Nothing happens. Any repository missing?
Code
Alles anzeigen$ sudo omv-update Holen:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Holen:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Holen:3 file:/var/cache/openmediavault/archives Packages [1.076 B] Holen:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Holen:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) OK:6 http://httpredir.debian.org/debian buster InRelease OK:7 http://httpredir.debian.org/debian buster-updates InRelease OK:8 http://security.debian.org buster/updates InRelease OK:9 http://packages.openmediavault.org/public usul InRelease OK:10 http://httpredir.debian.org/debian buster-backports InRelease Ign:12 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease OK:13 https://openmediavault.github.io/packages usul InRelease OK:14 https://www.deb-multimedia.org buster InRelease Holen:15 https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release [4.363 B] OK:16 https://download.docker.com/linux/debian buster InRelease OK:11 https://apt.armbian.com buster InRelease Es wurden 4.363 B in 4 s geholt (1.015 B/s). Paketlisten werden gelesen... Fertig Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
-
arm boards don't necessarily get a newer kernel just because the distro is upgraded. Because a lot of the patches for these boards live outside the kernel, the kernel has to be patched to work and it is a lot of work to get patches to work with newer kernels.
-
-
I resolved the issue with information from the Helios4 support in the armbian forum:
https://forum.armbian.com/topi…findComment&comment=92673
Using armbian-config I can switch to another kernel
I chose the highlighted current kernel.After reboot:
-
@ryecoaaron
I had to learn my lesson the hard way:
After switching the kernel from 4.14 to 4.19 using armbian-config everything seemed o.k. up to the point where I inspected my docker containers. There was a problem with docker-ce which couldn't be started neither re-installed. I had to go back to 4.14. -
That's good to know, thanks FredK.
-
-
I just resolved the docker problem applying a hint in the Helios4 support in the armbian forum:
https://forum.armbian.com/topi…findComment&comment=91876after switching the kernel from 4.14 to 4.19 using armbian-config.
Now Usul 5.2.6-1 is running on the current kernel 4.19.84-mvebu. -
I just resolved the docker problem applying a hint in the Helios4 support in the armbian forum:
While I didn't think the kernel version caused this (I guess it does), this affects Armbian Buster images when creating a custom network - https://forum.openmediavault.o…MV-NextCloud-Rpi4-NanoPi/
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!