#1 2023-11-18 03:53:45

pozric

Member

Registered: 2016-03-04

Posts: 112

[RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Hi I followed this tutorial https://forums.bunsenlabs.org/viewtopic.php?id=8295 and everything went fine I guess except the kernel is stuck on 4.19.0-13-686-pae i686, apt-cache policy shows linux-image-686 shows Candidate: 5.10.197-1.
I wonder if I can sudo apt install --reinstall linux-image-686, update-grub without breaking anything?

Thanks in advance

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,567

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

First try 'sudo apt update' then 'sudo apt upgrade'. Any message why linux-image-amd64 (note the package name) is not being upgraded? Some extra package dependency?

You might try 'sudo apt full-upgrade' which brings in all needed dependencies. That should have happened during the Lith>Ber upgrade process, but no harm running it again.

The current linux-image-amd64 Candidate is indeed 5.10.197-1
Anyway I don't see any reason why reinstalling it should cause a problem.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,659

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Please show

dpkg -l linux* | grep ii

pozric

Member

Registered: 2016-03-04

Posts: 112

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Hi and thanks, I did update , upgrade and full-upgrade but everything is updated etc.

When I do dpkg -l linux* | grep ii:
linux-base 4.6  all Linux image base package
linux-image-4.19.0-13-686 4.19.160-2  i386 Linux 4.19 for older PCs (signed)
linux-image-4.19.0-13-686-pae 4.19.160-2  i386 Linux 4.19 for modern PCs (signed).

If I do apt install --reinstall linux-image-686 can I just sudo rm the old kernels?

Btw everything feels great after I upgraded, it feels nice and smooth and my pc is very ancient like mega.

Thanks

Last edited by pozric (2023-11-18 14:56:26)

jeffreyC

Member

Registered: 2019-09-07

Posts: 192

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

If I do apt install --reinstall linux-image-686 can I just sudo rm the old kernels?

You should use apt to uninstall, that is what it is made for.
If you start using rm to remove Debian packages you will probably break your system.

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,659

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

You are missing the packages linux-image-686 and linux-libc-dev

So

sudo apt install linux-image-686 linux-libc-dev

then

sudo apt dist-upgrade

and the kernel should come.

Edit: sorry, I had misspelled the command...   

Last edited by unklar (2023-11-18 16:28:25)

pozric

Member

Registered: 2016-03-04

Posts: 112

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Hi I did sudo apt install linux-image-686 linux-libc-dev and its installed but I get this error:

/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-26-686:Error! echo
Your kernel headers for kernel 5.10.0-26-686 cannot be found at
/lib/modules/5.10.0-26-686/build or /lib/modules/5.10.0-26-686/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.

Thanks

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,659

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

When did you install the dkms package and for what purpose?
beryllium does not use such a package here.

apt policy dkms
dkms:
  Installiert:           (keine)
  Installationskandidat: 2.8.4-3
  Versionstabelle:
     2.8.4-3 500
        500 https://deb.debian.org/debian bullseye/main i386 Packages

dpkg -l linux* | grep ii
ii  linux-base                         4.6          all          Linux image base package
ii  linux-image-5.10.0-25-686          5.10.191-1   i386         Linux 5.10 for older PCs (signed)
ii  linux-image-5.10.0-26-686          5.10.197-1   i386         Linux 5.10 for older PCs (signed)
ii  linux-image-686                    5.10.197-1   i386         Linux for older PCs (meta-package)
ii  linux-libc-dev:i386                5.10.197-1   i386         Linux support headers for userspace development

Uninstall it.

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

^ This is correct.

sudo apt purge dkms

Keep your old kernel, it's always good to having a working backup.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

pozric

Member

Registered: 2016-03-04

Posts: 112

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Hi I really dont know and dont remember when I installed the dkms package,  but maybe I did it when I was installing nvidia legacy driver, cant remember but I remember that installing nvidia driver was a bit tough.
When I do dkms status it givs :
nvidia-legacy-340xx, 340.108, 4.19.0-13-686-pae, i686: installed
Is it safe to purge dkms?

Anyways I installed linux-image-5.10.0-26-686 but it didnt boot so I booted from the old kernel so yeah I guess its best too keep the old one. Cant I just leave it like this or do I have to fix it, because like I said everything works so far.

Thanks

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,567

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

1) The kernel metapackage name is not linux-image-686 it's linux-image-amd64, as I posted above.
If you run:

sudo apt install linux-image-amd64

you should get the current kernel for Debian 11 (ie Beryllium).

2) It's OK to have dkms. Sometimes it gets brought in automatically when installing something that requires a custom kernel module. I think I had it in the past for an nvidia driver or something...

3) As @jeffreyC pointed out, don't use rm to remove unwanted packages! Once you've got the kernel you want ( 5.10.197-1  ) and are sure you can boot from it, you can run

sudo apt autoremove

to remove any unnecessary packages, including old kernels.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,659

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Again the information from TE in code-tags, whereby he has shortened it by the kernel 5.10.0-26-686:

dpkg -l linux* | grep ii
linux-base 4.6  all Linux image base package
linux-image-4.19.0-13-686 4.19.160-2  i386 Linux 4.19 for older PCs (signed)
linux-image-4.19.0-13-686-pae 4.19.160-2  i386 Linux 4.19 for modern PCs (signed)

sudo apt install linux-image-686 linux-libc-dev
...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-26-686:Error! echo
Your kernel headers for kernel 5.10.0-26-686 cannot be found at
/lib/modules/5.10.0-26-686/build or /lib/modules/5.10.0-26-686/source

@johnraff, you are sure that he has to install linux-image-amd64?

curl https://api.ftp-master.debian.org/madison?package=linux-image-686
linux-image-686 | 4.19+105+deb10u16  | oldoldstable       | i386
linux-image-686 | 5.10.127-2~bpo10+1 | buster-backports   | i386
linux-image-686 | 5.10.197-1         | oldstable          | i386
linux-image-686 | 6.1.38-4~bpo11+1   | bullseye-backports | i386
linux-image-686 | 6.1.55-1           | stable             | i386
linux-image-686 | 6.5.3-1~bpo12+1    | stable-backports   | i386
linux-image-686 | 6.5.10-1           | testing            | i386
linux-image-686 | 6.5.10-1           | unstable           | i386

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

1) The kernel metapackage name is not linux-image-686 it's linux-image-amd64, as I posted above.

Woah, woah, woah! OP is stuck on 4.19.0-13-686-pae. That's a 32-bit pae kernel. This is the current bookworm stable kernel for 32 bit, pae machines...

https://packages.debian.org/bookworm/li … ge-686-pae

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

I think the solution here is for @pozrik to go ahead and install the appropriate pae linux-image and linux-header packages. That way dkms shouldn't complain and they can leave it installed in case it's needed for an NVidia driver update.

https://packages.debian.org/bookworm/li … rs-686-pae

sudo apt install linux-image-686-pae linux-headers-686-pae

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

You can uninstall the linux-image-686 (non pae) package, I'm pretty sure.

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,659

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

@hhh, you master of distraction, this is not about i386 or i386pae.
It's about whether the linux-image-686 or linux-image-amd64 metapackage is used on a 32bit machine.

The TE has not even written whether the pae kernel or the NOT pae kernel is used.

This also has to do with the fact that you as a moderator simply do not require people to provide information about their machines with inxi -Fzx (or similar) right from the start. 

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Well, you're right that...

inxi -Fzx

... would help, we'd also have to teach them to wrap the output in code tags before pasting, and also how to copy/paste from whatever terminal they're using.

But the original post does state the kernel he's stuck on, and it's 686 pae, so we should probably work with upgrading that kernel?

... the kernel is stuck on 4.19.0-13-686-pae...

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

pozric

Member

Registered: 2016-03-04

Posts: 112

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Hello again Im sorry for not using the correct code tags. Its a 32 bit pc.
When it didnt boot before with the newer kernel it gave som nvidia error, always had trouble with installing the nvidia legacy driver, and why I didnt use the noveau driver was it always froze after a while but that was a long time ago.

https://packages.debian.org/bookworm/li … rs-686-pae
I dont have the bookworm repo in my sources.list

inxi -r
Repos:
  Active apt repos in: /etc/apt/sources.list 
  1: deb https://deb.debian.org/debian bullseye main contrib non-free
  2: deb https://deb.debian.org/debian bullseye-updates main contrib non-free
  3: deb https://deb.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/bunsen-bullseye-backports.list 
  1: deb https://pkg.bunsenlabs.org/debian bullseye-backports main
  Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
  1: deb https://pkg.bunsenlabs.org/debian beryllium main
  Active apt repos in: /etc/apt/sources.list.d/debian bullseye-backports.list 
  1: deb https://deb.debian.org/debian bullseye-backports main contrib non-free

inxi -v4

System:
  Host: nonexistent Kernel: 4.19.0-13-686-pae i686 bits: 32 compiler: gcc v: 10.2.1 
  Desktop: Openbox 3.6.1 Distro: BunsenLabs GNU/Linux 11 (Beryllium) 
  base: Debian GNU/Linux 11 
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5B-E Plus v: Rev 1.xx 
  serial: <superuser required> BIOS: American Megatrends v: 0638 date: 09/30/2008 
CPU:
  Info: Dual Core model: Intel Core2 6320 bits: 64 type: MCP arch: Core Merom rev: 6 
  L2 cache: 4 MiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 7466 
  Speed: 1610 MHz min/max: 1596/1862 MHz Core speeds (MHz): 1: 1610 2: 1600 
Graphics:
  Device-1: NVIDIA GT215 [GeForce GT 220] driver: nvidia v: 340.108 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution: 1600x900~60Hz 
  OpenGL: renderer: GeForce GT 220/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
  direct render: Yes 
Network:
  Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet vendor: ASUSTeK driver: sky2 
  v: 1.30 port: d800 bus ID: 02:00.0 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 00:1a:92:bb:2a:3e 
Drives:
  Local Storage: total: 938.84 GiB used: 913.91 GiB (97.3%) 
  ID-1: /dev/sda vendor: Samsung model: HD103UJ size: 931.51 GiB 
  ID-2: /dev/sdb type: USB vendor: Kingston model: DT microDuo size: 7.32 GiB 
Partition:
  ID-1: / size: 41 GiB used: 34.65 GiB (84.5%) fs: ext4 dev: /dev/sda1 
Info:
  Processes: 150 Uptime: 19h 05m Memory: 1.97 GiB used: 1.42 GiB (71.9%) Init: systemd 
  runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1836 Shell: Bash v: 5.1.4 inxi: 3.3.01

Last edited by pozric (2023-11-19 14:10:29)

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,043

Website

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

Oof, my bad. I didn't even check out your first link, that you're upgrading to bullseye. I didn't even check the title of this thread! The same packages should still apply. Can you post what the linux-* (linux-base, linux-image, linux-headers if you've installed them),  section of dpkg -l outputs?

@unklar, at least I didn't distract this thread with the discussion of apt policy!

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

pozric

Member

Registered: 2016-03-04

Posts: 112

Re: [RESOLVED] Kernel not updated after upgrade from Lithium to Beryllium

dpkg -l linux* | grep ii

ii  linux-base                             4.6          all          Linux image base package
ii  linux-image-4.19.0-13-686              4.19.160-2   i386         Linux 4.19 for older PCs (signed)
ii  linux-image-4.19.0-13-686-pae          4.19.160-2   i386         Linux 4.19 for modern PCs (signed)
ii  linux-image-5.10.0-26-686              5.10.197-1   i386         Linux 5.10 for older PCs (signed)
ii  linux-image-686                        5.10.197-1   i386         Linux for older PCs (meta-package)
ii  linux-libc-dev:i386                    5.10.197-1   i386         Linux support headers for userspace development.

dpkg -l linux*

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                   Version      Architecture Description
+++-======================================-============-============-====================>
ii  linux-base                             4.6          all          Linux image base pac>
un  linux-doc-4.19                         <none>       <none>       (no description avai>
un  linux-doc-5.10                         <none>       <none>       (no description avai>
un  linux-headers                          <none>       <none>       (no description avai>
un  linux-headers-686-pae                  <none>       <none>       (no description avai>
un  linux-headers-amd64                    <none>       <none>       (no description avai>
un  linux-headers-generic                  <none>       <none>       (no description avai>
ii  linux-image-4.19.0-13-686              4.19.160-2   i386         Linux 4.19 for older>
ii  linux-image-4.19.0-13-686-pae          4.19.160-2   i386         Linux 4.19 for moder>
un  linux-image-4.19.0-13-686-pae-unsigned <none>       <none>       (no description avai>
un  linux-image-4.19.0-13-686-unsigned     <none>       <none>       (no description avai>
ii  linux-image-5.10.0-26-686              5.10.197-1   i386         Linux 5.10 for older>
un  linux-image-5.10.0-26-686-unsigned     <none>       <none>       (no description avai>
ii  linux-image-686                        5.10.197-1   i386         Linux for older PCs >
un  linux-initramfs-tool                   <none>       <none>       (no description avai>
un  linux-kernel-log-daemon                <none>       <none>       (no description avai>
un  linux-latest-modules-5.10.0-26-686     <none>       <none>       (no description avai>
ii  linux-libc-dev:i386                    5.10.197-1   i386         Linux support header>