Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265108 > unrolled thread
| Started by | Gary Dale <gary@extremeground.com> |
|---|---|
| First post | 2023-12-21 20:30 +0100 |
| Last post | 2023-12-22 05:50 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
Is there a problem with Linux-image-6.1.0-16? Gary Dale <gary@extremeground.com> - 2023-12-21 20:30 +0100
Re: Is there a problem with Linux-image-6.1.0-16? Greg Wooledge <greg@wooledge.org> - 2023-12-21 21:00 +0100
Re: Is there a problem with Linux-image-6.1.0-16? Charles Curley <charlescurley@charlescurley.com> - 2023-12-22 05:50 +0100
| From | Gary Dale <gary@extremeground.com> |
|---|---|
| Date | 2023-12-21 20:30 +0100 |
| Subject | Is there a problem with Linux-image-6.1.0-16? |
| Message-ID | <HNwU1-f9jj-1@gated-at.bofh.it> |
Several days ago my main server upgraded to kernel 6.1.0-16 but various other devices that are also running Bookworm seem stuck at 6.1.0-13. They are all using the same architecture. Some are using the same mirror as the server that upgraded. I haven't set any special policies on upgrades. Can anyone explain what's going on?
[toc] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-12-21 21:00 +0100 |
| Message-ID | <HNxn4-f9tA-7@gated-at.bofh.it> |
| In reply to | #265108 |
On Thu, Dec 21, 2023 at 09:02:34AM -0500, Gary Dale wrote: > Several days ago my main server upgraded to kernel 6.1.0-16 but various > other devices that are also running Bookworm seem stuck at 6.1.0-13. They > are all using the same architecture. Some are using the same mirror as the > server that upgraded. I haven't set any special policies on upgrades. > > Can anyone explain what's going on? Did you run a command? Which command was it? What did it tell you? "apt upgrade" or "apt-get dist-upgrade" should work. There are other ways as well.
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2023-12-22 05:50 +0100 |
| Message-ID | <HNFDX-feAt-3@gated-at.bofh.it> |
| In reply to | #265108 |
On Thu, 21 Dec 2023 09:02:34 -0500 Gary Dale <gary@extremeground.com> wrote: > Several days ago my main server upgraded to kernel 6.1.0-16 but > various other devices that are also running Bookworm seem stuck at > 6.1.0-13. They are all using the same architecture. Some are using > the same mirror as the server that upgraded. I haven't set any > special policies on upgrades. I saw similar here. Of four machines here running Bookworm, three have kernels: linux-image-6.1.0-15-amd64 6.1.66-1 linux-image-6.1.0-16-amd64 6.1.67-1 but one has: linux-image-6.1.0-13-amd64 6.1.55-1 linux-image-6.1.0-15-amd64 6.1.66-1 However, I found that the latter machine has the following in /etc/apt/sources.list: # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports # Line commented out by installer because it failed to verify: #deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware whereas the others three have: # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware Uncommenting the bookworm-updates line got me the missing kernel. You might try the same. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web