OPi Zero + H5 unable to update/upgrade from Bulleye Sunxi 64 Kernel 6.1.92 to 6.6.nn

[Hans Kurscheidt]

I had to freeze my device on Kernel 6.1.92 & Bullseye to remain operational. Now trying to update/upgrade to Kernel 6.6.nn I run into following probs:

1) Using Armbian-config defreeze and subsequently switch to kernel 6.6.nn works OK 4me, but subsequent apt-get update/upgrade throws me back to kernel 6.1.104. Armbian-config has changed significantly w/ No other Kernel available.

2) Using Armbian-config defreeze, only and going directly to apt-get update/upgrade throws me back to kernel 6.1.104 as well and from Bullseye back to Buster! Its a mess!

Will this eventually be corrected and when?

RGDS

Edited Sunday at 10:45 PM by Hans Kurscheidt
wrong pic

[Igor]

1 hour ago, Hans Kurscheidt said:

Will this eventually be corrected and when?

 

From this I can only see that you are using a code that is not supported on a hardware that is not supported. 

 

For some reason you have two kernels installed, legacy and current, and this is causing randomness at upgrade. Uninstall one variant alongside with DT and headers if installed. And upgrade to Buster, or rather start with a clean Bookworm image.

[Hans Kurscheidt]

vor 15 Stunden schrieb Igor:

Uninstall one variant alongside with DT and headers if installed.

Thank-you for reply. Sorry for the beginners question, but "How to"? I used armbian-config to move from 6.1.92 to 6.6.44 and I was assuming that 6.6.44 would replace 6.1.92; apparently it did not, as you said in your reply. So how can I make 6.6.44 the new 1 and only new kernel. I currently back to my old image w/ kernel 6.1.92 frozen and Debian Bullseye. I have a complex APP with tons of middleware and 3rd party SW; a fresh new installation would be a PITA.

Edited Monday at 04:00 PM by Hans Kurscheidt
typo, added pic

[robertoj]

cd /boot

ls -l

 

Look at the symlinks ZImage and uInitrd... are they pointing to the linux version you want

 

Also: "apt list --installed | grep linux" to see which linux armbian packages are installed

 

Look at all the suggestions here: https://forum.armbian.com/topic/38570-upgraded-to-latest-armbian-but-stuck-on-old-kernel/

 

[Hans Kurscheidt]

Hi there,

as expected, in my frozen image, they are pointing to 6.1.92. After unfreeze and apt-get update/upgrade I'm now lifted to 6.1.104 & Bullseye

However its not want I want, 6.644. a new issued apt-get update/upgrade has no effect.

 

 

 

looks like a security issue to me, now. https://github.armbian.... is not signed

RGDS

hk

 

Edited Monday at 08:16 PM by Hans Kurscheidt
amended

[robertoj]

You need to change those symlinks Image and uInitrd to the files ending with 6.6.44

 

In your case, make a copy of your microSD now and try sudoing this:

 

rm /boot/Image
ln -s /boot/vmlinuz-6.6.44-current-sunxi64 /boot/Image
rm /boot/uInitrd
ln -s /boot/uInitrd-6.6.44-current-sunxi64 /boot/uInitrd

 

I don't know why the dtb folder symlink is already good for 6.6.44

[Hans Kurscheidt]

OK, I can certainly do this, but is this supposed 2b the "normal way" or isn't there an issue w/ signing the package, so that "normal" apt ops would do the trick?

BTW thanks 4 Help

BR

hk

Edited Monday at 08:24 PM by Hans Kurscheidt

[SteeMan]

22 minutes ago, Hans Kurscheidt said:

OK, I can certainly do this, but is this supposed 2b the "normal way" or isn't there an issue w/ signing the package, so that "normal" apt ops would do the trick?

 

I think you have to go back to earlier in this thread where Igor stated:

20 hours ago, Igor said:

From this I can only see that you are using a code that is not supported on a hardware that is not supported. 

 

I think there is information you are not including about your setup.  The first screenshot indicates you are/were running Buster as the screenshot says "Debian end of life (Buster)".  Then later screenshots indicate you are running Bullseye.  It looks like you have attempted to upgrade from Buster to Bullseye during this process.  Armbian doesn't support userspace upgrades.  An error in doing an upgrade like that would potentially leave your apt signing keys out of sync.

[Hans Kurscheidt]

I'm sorry, but you misinterpreted the screenshots.

Please refer to my 1st line in my 1st post:

>>>>I had to freeze my device on Kernel 6.1.92 & Bullseye to remain operational. Now trying to update/upgrade to Kernel 6.6.nn <<<<

I was always on Bullseye since years now and Kernel 6.1.92  frozen since early this year. Trying to move from 6.1.92 to 6.6.42 (switching kernel after defreeze in armbian-config) created a mess including throwing me back onto Buster, God knows why and how!

May be, that I am using a code that is not supported on a hardware that is not supported, but normal Linux' way of upgrade should still work and for the time being, I am almost sure, that the upgrade doesn't work, because you guys haven't created the proper public key for apt.security to accept the upgrade.

RGDS

hk

 

Edited Monday at 09:24 PM by Hans Kurscheidt
clarification

[SteeMan]

Moved post from Supported to Community Maintained and adjusted the tag to reflect the correct board

[Igor]

7 hours ago, Hans Kurscheidt said:

but normal Linux' way of upgrade should still work and for the time being,

It does work. Sometimes. Out of lets say 1000 packages that are on your OS, you are telling people, who are maintaining 3 of those (that only deals with hardware aspects), to fix a problem on all 1000. Making an OS better then Debian in user-space sense, deal with tens of thousands of packages, that is another level. We "hack" this by providing you Armbian assembled from Ubuntu packages / repo. Which might be better in this. Becoming yet another maintainer of all free software packages is insane. And there is no warranty to control this process better.

 

7 hours ago, Hans Kurscheidt said:

God knows why and how!

 

Exactly. Try upgrade, but be ready to start from a new image is the only advise that is realistic. Personally, I don't even try. When its time to move to a new point release, I do a backup of dot files following by fresh install. What I need to run, I do it with help of scripts & armbian-config, running apt. It takes less time then upgrade, which has great chances of failure.

 

7 hours ago, Hans Kurscheidt said:

I am almost sure, that the upgrade doesn't work, because you guys haven't created the proper public key for apt.security to accept the upgrade.

 

apt.security folder was removed from upstream, from Debian main repo, to tell you that distro is EOL and there are no more security updates of (Debian assembled) packages. Once Debian maintainers decides to stop, there is nothing we / anyone can do about. Some distros claims to maintain this longer, but in reality it only has marketing / sales value.

 

Update and signing mechanism has been changed, not by us, but by upstream. At different time at different user space. If we fix for one, we have to fix for all. There is another aspect of why this software is not perfect. We are heavily under-staff since ever and there is close to no public funding to mitigate this. Join the project, dig into this upgrade problem, and (try to) fix it. Or at least improve, try many of possible scenarios and write instructions of best practices. Not for me/us, but for someone that might run into this. 

[robertoj]

20 hours ago, Hans Kurscheidt said:

I'm sorry, but you misinterpreted the screenshots.

Please refer to my 1st line in my 1st post:

>>>>I had to freeze my device on Kernel 6.1.92 & Bullseye to remain operational. Now trying to update/upgrade to Kernel 6.6.nn <<<<

I was always on Bullseye since years now and Kernel 6.1.92  frozen since early this year. Trying to move from 6.1.92 to 6.6.42 (switching kernel after defreeze in armbian-config) created a mess including throwing me back onto Buster, God knows why and how!

May be, that I am using a code that is not supported on a hardware that is not supported, but normal Linux' way of upgrade should still work and for the time being, I am almost sure, that the upgrade doesn't work, because you guys haven't created the proper public key for apt.security to accept the upgrade.

RGDS

hk

 

Can you post what exactly you DID and solved your problem? (In case someone suffers the same thing you suffered)

 

Or if you haven't solved your problem, at least we know that it is unsolvable and do the sane thing: restart from scratch, from a new armbian image.

 

Then highlight it as the solution.

[Hans Kurscheidt]

Well, I tried my very best to find a solution, just to run into other Armbian peculiarities. 

1st, the problem with the missing signature can be solved by telling apt to ignore it.

Zitat

UNSIGNED REPOSITORIES

If an archive has an unsigned Release file or no Release file at all current APT versions will refuse to download data from them by default in update operations and even if forced to download front-ends like apt-get(8) will require explicit confirmation if an installation request includes a package from such an unauthenticated archive.

You can force all APT clients to raise only warnings by setting the configuration option Acquire::AllowInsecureRepositories to true. Individual repositories can also be allowed to be insecure via the sources.list(5) option allow-insecure=yes. Note that insecure repositories are strongly discouraged and all options to force apt to continue supporting them will eventually be removed. Users also have the Trusted option available to disable even the warnings, but be sure to understand the implications as detailed in sources.list(5).

A repository which previously was authenticated but would loose this state in an update operation raises an error in all APT clients irrespective of the option to allow or forbid usage of insecure repositories. The error can be overcome by additionally setting Acquire::AllowDowngradeToInsecureRepositories to true or for Individual repositories with the sources.list(5) option allow-downgrade-to-insecure=yes.

Hence I created my apt.config settings in /etc/apt/apt.config.d as following:

 cat 99mysettings
Acquire::AllowInsecureRepositories "1";
Acquire::AllowWeakRepositories "0";
Acquire::AllowDowngradeToInsecureRepositories "1";

So apt started to work on it, giving the appropriate warnings:

 

 

which I ignored, so it started the upgrade:

just to learn, that I'm stuck again w/ Armbian. something w/ "unknown compression"

 

[SteeMan]

1 hour ago, Hans Kurscheidt said:

just to learn, that I'm stuck again w/ Armbian. something w/ "unknown compression"

 

[Igor]

1 hour ago, Hans Kurscheidt said:

something w/ "unknown compression"

This was not designed by Armbian. I replied here: https://github.com/armbian/configng/issues/265#issuecomment-2487678726

 

Workaround: remove armbian-config package, upgrade to Bookworm, and install it again. 

[Hans Kurscheidt]

OK, so I'm there!

but rather than doing a fresh install, I used the following method:

using armbian-config under kernel 6.1.92 to unfreeze

using armbian-config to switch to "other kernel" -> 6.6.44

That worked OK and gave me Debian Bullseye w/ kernel 6.6.44

I then edited /etc/apt/sources.list and /etc/apt/sources.list.d/armbian.list, replacing Bullseye w/ Bookworm. I then started apt-get update/upgrade. After a huge upgrade I ended up w/ Debian Bookworm, but had fallen back to kernel 6.1.104.

I then applied the method as described by robertoj to finally get Debian Bookworm w/ kernel 6.6.44 

 

Edited 23 hours ago by Hans Kurscheidt
typo

[Igor]

16 minutes ago, Hans Kurscheidt said:

but had fallen back to kernel 6.1.104.

Remove -legacy- kernels from the system.

[Hans Kurscheidt]

vor 2 Minuten schrieb Igor:

Remove -legacy- kernels from the system

I think, I asked you this question already. How to do this?? armbian-config doesn't have such cmd. Just deleting the legacy dirs in /boot??

RGDS

[Igor]

1 minute ago, Hans Kurscheidt said:

How to do this?? armbian-config doesn't have such cmd. Just deleting the legacy dirs in /boot??

 

No, it doesn't. This needs to be done beyond.

 

sudo apt purge linux-image-legacy-sunxi64 linux-dtb-legacy-sunxi64