-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Disabling firmware upgrades broken? #368
Comments
Could not reproduce with sunxi64. Did not test with rk35xx, maybe functionality was lost when merging this into rockchip64? Pure guess... |
Strange. We need to look into, yes. |
I thought it was only me, had this problem for a long time where everything but one "piece" (out of uInitrd, dtb, Image, vmlinuz & initrd.img) wouldn't update so that I have to boot from an SD-card and fix the symlink again. The missing version was never in apt, and I have just resorted to changing the faulty symlink to the previous version again, partly because I've had problems with having to recompile custom made overlay and partly because it worked fine before. I just ran apt and upgraded everything and even if the firmware is supposed to be on hold everything was upgraded BUT for the first time in like 2 months everything seems to be the same version. Sorry for a rambling post; I have looked everywhere for logs but as I've understood it the bootloader only saves the logs in ZRAM? The fact that the SBC tries PXE booting wouldn't help either I guess. If the logs for the bootloader is saved somewhere I would love to try to help with this, otherwise I apologize for this prolonged "yeah same here" :/ EDIT: Radxa Rock 4 SE |
I am facing a similar issue. On rock 5 irx board with bookworm os image, I am using a 6.1.75-vendor-rk35xx kernal. After changing the option using armbian-config, when I do apt update and apt upgrade, it is updating it to 6.1.8*(I don'trememberthis nimber)-vendor-rk35xx. Is this supposed to happen? |
Steps to reproduce / test functionality: Freezing: Checking:
Unfreezing: Checking:
Works as expected. Make sure you have latest armbian-config package. |
Board type : Rock 5 ITX
armbian-config version :
I updated the armbian-config using :
Everything is working fine where my raid card is getting dectected with
Now I am following the given steps :
Then :
If I proceed to upgrade the kernal is getting updated to :
The kernel drivers are not getting recognized. |
OK, it seems freezing doesn't work right. Looking into. |
Looking at the code, seems BRANCH variable is required. I added |
BRANCH variable is set at boot time. Did you perhaps changing kernels from current to vendor and / or vice versa before that? |
I have no BRANCH set. |
I can't find any
|
here you need to add RELEASE= |
By adding the lines
I will upgrade and post the update |
It works. 🎉 |
OK, great. I will implement some automation here to prevent this corners case to happen. Lets keep this open. |
What happened?
https://forum.armbian.com/topic/49253-correct-procedure-to-disable-kernel-updates/#comment-210648
How to reproduce?
apparently only armbian-firmware package is put on hold but not dtb, kernel and headers
On which host OS are you running the build script and observing this problem?
Other
Code of Conduct
The text was updated successfully, but these errors were encountered: