Problem after upgrade kernel 6.1.67-1

horvjoe · 2023-12-15 15:48:25

I have tried to upgrade my kernel as described in the news section.

After restart the kernel stayed the same as was before update - not the 6.1.67-1

7 packages can be upgraded. Run 'apt list --upgradable' to see them.
linux-image-amd64:
Installed: 6.1.67-1
Candidate: 6.1.67-1
Version table:
*** 6.1.67-1 500

I am not able to send all of the message cos its forbidden to post links.

joe@Asus:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
linux-headers-amd64 pipewire
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

So I need some help with detailed instruction.
Thank you

Sector11 · 2023-12-15 18:55:32

horvjoe wrote:

So I need some help with detailed instruction.
Thank you

Later you will be able to post links.
But you could have copy and pasted the terminal output into Code blocks
Make sure "BBCode: on", below your reply window, is actually on.
Click on it, a new tab will open showing what you can do

For example ↓↓↓

[code]copy past terminal output here[/code]

What is output of this:

apt policy linux-image-amd64

horvjoe · 2023-12-15 19:35:32

Thank you I will do as You wrote.

joe@Asus:~$ apt policy linux-image-amd64
linux-image-amd64:
  Installed: 6.1.67-1
  Candidate: 6.1.67-1
  Version table:
 *** 6.1.67-1 500
        500 https://deb.debian.org/debian bookworm-proposed-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     6.1.55-1~bpo11+1 100
        100 https://deb.debian.org/debian bullseye-backports/main amd64 Packages
     5.10.197-1 500
        500 https://deb.debian.org/debian bullseye/main amd64 Packages
     5.10.191-1 500
        500 https://deb.debian.org/debian-security bullseye-security/main amd64 Packages

Sector11 · 2023-12-16 01:09:41

There you go, you have the kernel install already:

  Installed: 6.1.67-1
  Candidate: 6.1.67-1

johnraff · 2023-12-16 02:20:14

You appear to have the new kernel metapackage 6.1.67-1 installed.

But I see from your other "apt policy" output that you are using Debian Bullseye (ie BunsenLabs Beryllium).
The issue posted in Announcements was with Debian Bookworm which the upcoming BunsenLabs Boron will use.

Fixing this could be a little tricky because downgrading Debian packages is difficult.
You have the option of keeping 6.1.67-1 on your Bullseye system, but that might cause subtle problems.

In your case I would suggest going back to your previous kernel, which is probably still installed.

Let's check:

uname -r

will tell you the kernel you are currently using. On this machine I am using Bullseye too, and I see '5.10.0-26-amd64'. That is the kernel brought in by linux-image-amd64 version 5.10.197-1, the latest on Debian Bullseye.
If you see that too, don't reboot.

On the other hand, if you see '6.1.0-15-amd64' it means you are already running the kernel brought in by linux-image-amd64 6.1.67-1.
(Yes, kernel version and package numbering is a bit complicated.)

Before doing anything else, see what kernels you still have installed, with 'find':

john@beryllium:~$ find /boot -name 'vmlinuz*'
find: ‘/boot/efi’: Permission denied
/boot/vmlinuz-5.10.0-25-amd64
/boot/vmlinuz-5.10.0-26-amd64

Don't worry about permissions for /boot/efi - we can see that I have two kernels: 5.10.0-25-amd64 and 5.10.0-26-amd64. I'm using "26" but apt has left "25" on the system in case it's needed.

If you've installed linux-image-amd 6.1.67-1 then I would expect to see /boot/vmlinuz-6.1.0-16-amd64 in that list, but if you've also got /boot/vmlinuz-5.10.0-26-amd64 then you can reboot using that, and remove the unnecessary new kernel.

So:
1) If you're already running 6.1.0-15-amd64, reboot and at the Grub boot screen don't choose the default entry but choose the "Advanced options" menu, then the next kernel version down. (Skip "recovery mode" entries.)
But if you're still running 5.10.0-26-amd64, go on to 2).

2) Back in your system using a 5.* kernel, check with 'uname -r' that that is really the case. Then delete the line in /etc/apt/sources.list which added the bookworm-proposed-updates.

3)

sudo apt update

4)

apt policy linux-image-amd64

should now show a priority of 100, not 500, and the bookworm-proposed-updates line should be gone.

5) Temporarily remove linux-image-amd64:

sudo apt remove linux-image-amd64

If the system also offers to remove linux-image-6.1.0-16-amd64 then so much the better, otherwise:

sudo apt autoremove

should remove the orphaned kernel package.

6) Now you can install the metapackage again:

sudo apt install linux-image-amd64

You should be back with the correct kernel package for Debian Bullseye, and that should be the default entry in your Grub boot menu.

If you don't understand any of these steps please ask!

NOTE: If you've already rebooted and are running the 6.1.0-16 kernel, then coming back down to the usual 5.10.0-26 is quite a big jump. It should be OK, but you also have the option of staying with 6.1.0-16 and seeing how it goes. I would still recommend removing the bookworm-proposed-updates line from apt sources.list though, because it might later pull in something that breaks your Bullseye sytem. I would also recommend upgrading to BunsenLabs Boron as soon as possible.

Last edited by johnraff (2023-12-16 05:16:10)

Sector11 · 2023-12-16 03:13:04

OH DEAR!

I missed that.

Sorry

horvjoe · 2023-12-16 06:39:40

johnraff:

joe@Asus:~$ find /boot -name 'vmlinuz*'
find: ‘/boot/efi’: Permission denied
/boot/vmlinuz-6.1.0-16-amd64
/boot/vmlinuz-5.10.0-26-amd64

I didnt do anything else. Waiting to your answer.

Sector11:
No problem. I havent seen aswell (but I read it through). And its tricky... Im still learning.

johnraff · 2023-12-16 07:11:05

OK that means you still have the 5.10.0-26 kernel available to use.
Please now run:

uname -r

and post the answer. It will tell us what kernel you are currently running.

horvjoe · 2023-12-16 07:21:45

joe@Asus:~$ uname -r
6.1.0-16-amd64

johnraff · 2023-12-16 07:43:13

That means you're now using the new (too new in fact) kernel.

Now go to 1) in the list above, boot into the old kernel 5.10.0-26-amd64 and continue through operations 2) 3) 4) 5) and 6)

Ask if you get stuck at some point.

horvjoe · 2023-12-16 08:08:49

Done through, but 6.1.55-1 stayed

1.

joe@Asus:~$ uname -r
5.10.0-26-amd64

2. Deleted from the file.

3. sudo apt update - done
All package up to date.

4.

joe@Asus:~$ apt policy linux-image-amd64
linux-image-amd64:
  Installed: 5.10.197-1
  Candidate: 5.10.197-1
  Version table:
     6.1.55-1~bpo11+1 100
        100 https://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 5.10.197-1 500
        500 https://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     5.10.191-1 500
        500 https://deb.debian.org/debian-security bullseye-security/main amd64 Packages

johnraff · 2023-12-16 08:35:37

apt wrote:

Installed: 5.10.197-1

That looks good.

6.1.55-1~bpo11+1 is the backports kernel, but you haven't installed it, you've got 5.10.197-1 which is right.
The package you had before was 6.1.67-1 which is higher again, and belonged in Bookworm, not Bullseye.

Don't worry about the backports kernel unless you have very new hardware which needs it.

I think your system should be OK now.

horvjoe · 2023-12-16 08:41:34

Ok, but at boot it uses 6.1.0-16

joe@Asus:~$ uname -r
6.1.0-16-amd64

...and the kernel moduls error stayed at boot up after grub

Last edited by horvjoe (2023-12-16 08:42:40)

johnraff · 2023-12-16 09:01:30

Reboot and choose the low numbered kernel as you did before, so you're running 5.10.0-26-amd64.

Now, did you run 'sudo apt autoremove' at stage 5) above?
If nothing is removed by that, try:

sudo apt remove linux-image-6.1.0-16-amd64

(I guess apt was reluctant to leave you with only one kernel so hesitated to remove 6.1.0-16, which then got to the top of the menu.)

Last edited by johnraff (2023-12-16 09:09:11)

horvjoe · 2023-12-16 10:11:08

I did step 5. Nothing.

So after as You suggested:

sudo apt remove linux-image-6.1.0-16-amd64

solved.

Thank you very much.

johnraff · 2023-12-16 11:11:54

Sector11 · 2023-12-16 19:38:55

I'll stick to my conkys.

#1 2023-12-15 15:48:25

Problem after upgrade kernel 6.1.67-1

#2 2023-12-15 18:55:32

Re: Problem after upgrade kernel 6.1.67-1

#3 2023-12-15 19:35:32

Re: Problem after upgrade kernel 6.1.67-1

#4 2023-12-16 01:09:41

Re: Problem after upgrade kernel 6.1.67-1

#5 2023-12-16 02:20:14

Re: Problem after upgrade kernel 6.1.67-1

#6 2023-12-16 03:13:04

Re: Problem after upgrade kernel 6.1.67-1

#7 2023-12-16 06:39:40

Re: Problem after upgrade kernel 6.1.67-1

#8 2023-12-16 07:11:05

Re: Problem after upgrade kernel 6.1.67-1

#9 2023-12-16 07:21:45

Re: Problem after upgrade kernel 6.1.67-1

#10 2023-12-16 07:43:13

Re: Problem after upgrade kernel 6.1.67-1

#11 2023-12-16 08:08:49

Re: Problem after upgrade kernel 6.1.67-1

#12 2023-12-16 08:35:37

Re: Problem after upgrade kernel 6.1.67-1

#13 2023-12-16 08:41:34

Re: Problem after upgrade kernel 6.1.67-1

#14 2023-12-16 09:01:30

Re: Problem after upgrade kernel 6.1.67-1

#15 2023-12-16 10:11:08

Re: Problem after upgrade kernel 6.1.67-1

#16 2023-12-16 11:11:54

Re: Problem after upgrade kernel 6.1.67-1

#17 2023-12-16 19:38:55

Re: Problem after upgrade kernel 6.1.67-1

Board footer