Huey

I set hold on both firmware packages on the commandline prompt. Until now no firmware updates, but not 100 percent sure it is why. Still it is my hunch that the omv updates the one nót set in armbian-config. Tried it on another machine and that seemed to confirm it though…

Hm, I retried with defreeze and freeze and now instead of armbian-firmware-full, the armbian-firmware got hold. For security I will also set again the armbian-firmware-full on hold... Better safe than sorry. Apologies, above happened on my rock64. Strange though: the rock64 image holds armbian-firmware, the rockpro64 holds armbian-firmware-full? Or is that because I added the headers as well on the rockpro64 and not on the rock64...? Hm, tried to update packages and the firmware using armbian-config, and it updates the full. Is it possible that the omv (installed using armbian-config...) uses a different update strategy and uses the armbian-firmware NOT full? Will set a hold on both to be sure...

Hi all, In armbian-config I have freeze on firmware. I can see that armbian-firmware-full is kept back. Still my kernel got updated. Kind of an issue as I use zfs (backports) on my omv install and I need to reinstall them to get the module recreated... Now I have a few questions: Is it because I have only armbian-firmware-full held back, and apt works in my case maybe with armbian-firmware? (Or do I misinterpret the list that says upgradable on the full) Or do I have to hold the specific versioned packages and will the armbian-firmware (meta?) package hold not work on the ones I have installed and get upgraded nonetheless? Tia