Re: Cannot see update to recent linux kernel 5.10.19-1~bpo10+1 (from 5.10.13-1~bpo10+1)
Hi,
Sorry for the late reply.
Thanks everyone for providing answers to me.
22 mars 2021, 04:00 de geoff.reidy@gmail.com:
> You're probably missing the metapackage, linux-image-amd64.
>
You are right!
Now I've installed linux-image-amd64 but my system still doesn't notify me regarding any kernel updates...
22 mars 2021, 08:31 de didier.gaumet@gmail.com:
> There is a linux-image-5.10.0-0.bpo.3-amd64 package but linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded (linux-image-5.10.0-0.bpo.4-amd64-unsigned is there already)
>
Still true today. Signature seems to take time...
22 mars 2021, 12:17 de andreimpopescu@gmail.com:
> When Linux has significant updates the package name changes as well to
> signal that e.g. out-of-tree modules must be recompiled.
>
> Try this instead:
>
> apt list linux-image-5*
>
$ apt list linux-image-5*
Listing... Done
linux-image-5.10.0-0.bpo.3-686-dbg/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-686-pae-dbg/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-686-pae-unsigned/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-686-pae/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-686-unsigned/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-686/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-amd64-dbg/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-amd64-unsigned/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-amd64/buster-backports,now 5.10.13-1~bpo10+1 amd64 [installed]
linux-image-5.10.0-0.bpo.3-cloud-amd64-dbg/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-cloud-amd64-unsigned/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-cloud-amd64/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-rt-686-pae-dbg/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-rt-686-pae-unsigned/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-rt-686-pae/buster-backports 5.10.13-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.3-rt-amd64-dbg/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-rt-amd64-unsigned/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.3-rt-amd64/buster-backports 5.10.13-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-686-dbg/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-686-pae-dbg/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-686-pae-unsigned/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-686-unsigned/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-amd64-dbg/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-amd64-unsigned/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-cloud-amd64-dbg/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-cloud-amd64-unsigned/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-rt-686-pae-dbg/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-rt-686-pae-unsigned/buster-backports 5.10.19-1~bpo10+1 i386
linux-image-5.10.0-0.bpo.4-rt-amd64-dbg/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.4-rt-amd64-unsigned/buster-backports 5.10.19-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-686-dbg/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-686-pae-dbg/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-686-pae-unsigned/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-686-pae/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-686-unsigned/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-686/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-amd64-dbg/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-amd64-unsigned/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-amd64/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-cloud-amd64-dbg/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-cloud-amd64-unsigned/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-cloud-amd64/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-rt-686-pae-dbg/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-rt-686-pae-unsigned/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-rt-686-pae/buster-backports 5.9.15-1~bpo10+1 i386
linux-image-5.9.0-0.bpo.5-rt-amd64-dbg/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-rt-amd64-unsigned/buster-backports 5.9.15-1~bpo10+1 amd64
linux-image-5.9.0-0.bpo.5-rt-amd64/buster-backports 5.9.15-1~bpo10+1 amd64
We can see that there is nothing more recent than what I already have installed:
linux-image-5.10.0-0.bpo.3-amd64/buster-backports,now 5.10.13-1~bpo10+1 amd64 [installed]
> To have apt install the latest *signed* kernel from a given archive you
> should install the corresponding 'linux-image-amd64' package.
>
Done now (see my first comment above)
22 mars 2021, 23:53 de wanderer@fastmail.fm:
> @OP: Is linux-image-5.10.0-0.bpo.4-amd64 available in your configured
> repositories? If so, what versions is it available with?
>
> It's possible that the 5.10.19-1~bpo10+1 version may be available only
> under the updated .4 package name, not under the .3 package name you're
> checking.
>
See above, linux-image-5.10.0-0.bpo.4-amd64 is not available for me, on the contrary, linux-image-5.10.0-0.bpo.4-amd64-unsigned is (but I'm not interested as I'm running Secure Boot and need the signed version)...
By the way, what is image-5.10.0-0.bpo.4* serie for?Is it only related to "Change ABI number to 0.bpo.4"? Do I need that?
23 mars 2021, 17:45 de deblis@lionunicorn.co.uk:
> But the OP is, perhaps, relying on the upgrade mechanism provided by
> the linux-image-amd64 metapackage. However, that's supporting only
> the signed versions, and buster-backports doesn't (yet) have any
> 5.10.19 signed versions:
>
So you think that's the correct answer (no update because the package is not ready yet)?
If so, I'll simply wait for it. I just wanted to make sure my conf is OK (and obviously it wasn't configured in such a way to get the latest kernel versions from backports)...
Thanks in advance.
Best regards,
l0f4r0
Reply to: