You are not logged in.
Pages: 1
Hi everyone! Hope you're all having a nice life!
I installed linux-image-5.8.0-0.bpo.2-amd64 from backports, didn't get any errors and the system "works fine" so far, however, after rebooting the kernel's not being used by the system but the previous one; linux-image-4.19.0-11-amd64.
Also,
$ dpkg --list | grep linux-image
ri linux-image-4.19.0-11-amd64 4.19.146-1 amd64 Linux 4.19 for 64-bit PCs (signed)
ii linux-image-5.8.0-0.bpo.2-amd64 5.8.10-1~bpo10+1 amd64 Linux 5.8 for 64-bit PCs (signed)
ii linux-image-amd64 4.19+105+deb10u6 amd64 Linux for 64-bit PCs (meta-package)
According to that, linux-image-4.19.0-11-amd64 isn't even installed.
$ dpkg --status linux-image-4.19.0.11-amd64
dpkg-query: package `linux-image-4.19.0.11-amd64' is not installed and there's no available information.
Use dpkg --info (= dpkg-deb --info) to examine archive files
Not installed? But
$ uname -r
4.19.0-11-amd64
So, what's going on? I don't know what to do here since this is the first time I see something like this. Thanks in advance for your answers.
Last edited by Tolkem (2020-12-08 23:08)
Offline
$ dpkg --list | grep linux-image ri linux-image-4.19.0-11-amd64 4.19.146-1 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-5.8.0-0.bpo.2-amd64 5.8.10-1~bpo10+1 amd64 Linux 5.8 for 64-bit PCs (signed) ii linux-image-amd64 4.19+105+deb10u6 amd64 Linux for 64-bit PCs (meta-package)
According to that, linux-image-4.19.0-11-amd64 isn't even installed.
$ dpkg --status linux-image-4.19.0.11-amd64 dpkg-query: package `linux-image-4.19.0.11-amd64' is not installed and there's no available information. Use dpkg --info (= dpkg-deb --info) to examine archive files
linux-image-4.19.0-11-amd64 from your dpkg --list query is not the same as
linux-image-4.19.0.11-amd64 in your dpkg --status query.
Offline
What is output of commands:
$ apt policy linux-image-4.19.0-11-amd64
$ dpkg --get-selections | grep linux-image
Did you install the new kernel using the command:
$ qinst-kernel-bpo
Offline
linux-image-4.19.0-11-amd64 from your dpkg --list query is not the same as
linux-image-4.19.0.11-amd64 in your dpkg --status query.
How so? Why do you say that? It's the same.
What is output of commands:
$ apt policy linux-image-4.19.0-11-amd64
apt policy linux-image-4.19.0-11-amd64
linux-image-4.19.0-11-amd64:
Instalados: 4.19.146-1
Candidato: 4.19.146-1
Tabla de versión:
*** 4.19.146-1 500
500 http://ftp.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg --get-selections | grep linux-image
dpkg --get-selections | grep linux-image
linux-image-4.19.0-11-amd64 deinstall
linux-image-5.8.0-0.bpo.2-amd64 install
linux-image-amd64 install
Did you install the new kernel using the command:
$ qinst-kernel-bpo
No, I didn't. I used
sudo apt-get install -t buster-backports linux-image-5.8.0-0.bpo.2-amd64
Should I used that one instead? By the way, I meant to ask this before bot forgot to, how do I choose a different kernel at boot? I tried pressing shift key like most distros do but it didn't work.
Offline
First edit the "/etc/default/grub" file, set values:
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=4
and run:
$ sudo update-grub
The 4.19 kernel seems to be half de-installed, so run the following:
$ sudo apt --purge reinstall linux-image-4.19.0-11-amd64
how do I choose a different kernel at boot?
"Esc" key should do the job.
Yes, we recommend to use the "qinst-kernel-bpo" script as it takes care about installing firmware from backports, which is more related to the kernel.
Reboot and post the result here please.
Last edited by q4osteam (2020-12-04 14:16)
Offline
First edit the "/etc/default/grub" file, set values:
GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=4
and run:
$ sudo update-grubThe 4.19 kernel seems to be half de-installed, so run the following:
$ sudo apt --purge reinstall linux-image-4.19.0-11-amd64Tolkem wrote:how do I choose a different kernel at boot?
"Esc" key should do the job.
Yes, we recommend to use the "qinst-kernel-bpo" script as it takes care about installing firmware from backports, which is more related to the kernel.
Reboot and post the result here please.
Thank you that worked!
dpkg --get-selections | grep linux-image
linux-image-4.19.0-11-amd64 install
linux-image-5.8.0-0.bpo.2-amd64 install
linux-image-amd64 install
And
uname -r
5.8.0-0.bpo.2-amd64
Thanks!
Offline
Tolkem wrote:$ dpkg --list | grep linux-image ri linux-image-4.19.0-11-amd64 4.19.146-1 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-5.8.0-0.bpo.2-amd64 5.8.10-1~bpo10+1 amd64 Linux 5.8 for 64-bit PCs (signed) ii linux-image-amd64 4.19+105+deb10u6 amd64 Linux for 64-bit PCs (meta-package)
According to that, linux-image-4.19.0-11-amd64 isn't even installed.
$ dpkg --status linux-image-4.19.0.11-amd64 dpkg-query: package `linux-image-4.19.0.11-amd64' is not installed and there's no available information. Use dpkg --info (= dpkg-deb --info) to examine archive files
linux-image-4.19.0-11-amd64 from your dpkg --list query is not the same as
linux-image-4.19.0.11-amd64 in your dpkg --status query.
I just saw what you meant and you're right. Seems like a typo since I used "-" and then "." and clearly they're not the same.
Offline
Thanks for the info. Please note, we don't recommend using other than the default Debian kernel because of stability, see https://www.q4os.org/dqa011.html#system.6
Offline
Thanks for the info. Please note, we don't recommend using other than the default Debian kernel because of stability, see https://www.q4os.org/dqa011.html#system.6
No problem. Thanks for the tip and the helpful link. I do have a question though, from that link I read:
If you prefer for some reasons the latest linux kernel, run the auto-installation script in terminal to easily install it from backports repository:
$ qinst-kernel-bpo
Does that mean the script will install the very latest kernel? For instance, linux-image-5.9.0-0.bpo.2-amd64-unsigned is the latest available in backports, but it's unsigned, I don't know what the implications of being "unsigned" are exactly but I presume "signed" is better. Would qinst-kernel-bpo install that one?
Last edited by Tolkem (2020-12-04 20:32)
Offline
I just saw what you meant and you're right. Seems like a typo since I used "-" and then "." and clearly they're not the same.
I tried to lay out the post to make it easier to see, and glad you found it.
Offline
Pages: 1