

FredK
-
Posts
62 -
Joined
-
Last visited
Reputation Activity
-
FredK reacted to Mangix in Helios4 doesn't boot after upgrading to linux-6.6.71 (linux-image-current-mvebu_25.2.0-trunk.343)
This is the command to flash the bootloader onto the SD card: https://wiki.kobol.io/helios4/uboot/#on-development-pc
As you can tell, it's basically offset by 1 on the SD card.
kernel 6.6.79 boots now.
-
FredK got a reaction from ManoftheSea in Upgrade to 22.05
System successfully upgraded. No problems detected (so far).
Thanks to the team.
-
FredK got a reaction from Igor in Upgrade to 22.05
System successfully upgraded. No problems detected (so far).
Thanks to the team.
-
FredK got a reaction from gprovost in HDDs dissapeared after restart, not detected by `lsblk` anymore
@Yolgie I bought this one: https://www.amazon.de/gp/product/B07Q72NBQK
-
FredK got a reaction from gprovost in Random system reboots
It's really missing. How to restore it?
EDIT: Restored via "apt-get reinstall".
-
FredK got a reaction from gprovost in Helios4 Support
Release of openmediavault 5 (Usul)
https://www.openmediavault.org/?p=2685
-
FredK got a reaction from sirleon in Helios4 Support
Release of openmediavault 5 (Usul)
https://www.openmediavault.org/?p=2685
-
FredK got a reaction from gprovost in Helios4 Support
I upgraded my Helios4 from OMV4/Armbian4.14 to OMV5 yesterday. After sorting out some minor glitches the system was operable.
Today I used armbian-config to switch the kernel to 4.19. Everything seemd o.k. until I tried to inspect my docker containers and I detect a problem with docker-ce which couldn't be started neither re-installed. I had to go back to 4.14. Now I'm rather reluctant to try out one of dev dev-kernels (5.4.x).
Any clue?
Edit:
as proposed by Koen solved the docker problem.