You are not logged in.
Pages: 1
Hello:
My Devuan Beowulf runs on a backported kernel:
~$ uname -a
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
groucho@devuan:~$
When I installed it I assumed it would be updated as it evolved, but I have just noted that it has not.
And that the latest version is 5.10.0-0.bpo.12-amd64.
I think I may omitted something when I installed it?
Some priority setting perhaps?
Please advise, don't want to screw up something.
Thanks in advance,
A.
Offline
There's no metapackage for backports kernels like there is for the main kernel. The only updates you would get would be if the kernel version didn't change. I don't know if that happens with backports kernels.
Offline
why not use the standard kernel?
sudo apt install -t chimaera linux-image-amd64
Offline
Hello:
... no metapackage for backports kernels ...
I'll take your word for it.
No idea what that does. 8^/
... only updates you would get would be if the kernel version didn't change.
I found out about this by chance while skimming through the synaptic lists, which I do every so often.
Otherwise I have become used to apt for updating and installing.
Maybe it is because the backported kernel was installed locally?
groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep installed
--- snip ---
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
linux-headers-5.10.0-0.bpo.3-common/now 5.10.13-1~bpo10+1 all [installed,local]
groucho@devuan:~$
groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64
--- snip ---
linux-headers-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-cloud-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-rt-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local] <--------------------
linux-headers-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$
Thanks in advance.
Best,
A.
Offline
Hello:
why not use the standard kernel?
First there's the issue of the nvidia-legacy-340xx drivers and then the demise of python 2.7.18.
There are a couple of applications that will not work in chimaera, which is why I use the backported kernel.
Thanks for your input.
Best,
A.
Offline
I also use the bpo kernel.
Generally I have to search for upgrades for it, linux-image... and if found grab the kernel headers packages too.
Currently,
glenn@GlennsPref ~ $ uname -a
Linux GlennsPref.net 5.16.0-0.bpo.4-amd64 #1 SMP PREEMPT Debian 5.16.12-1~bpo11+1 (2022-03-08) x86_64 GNU/Linux
pic from 1993, new guitar day.
Offline
Hello:
... use the bpo kernel.
... search for upgrades for it, linux-image...
... grab the kernel headers packages too.
I see.
apt says this:
groucho@devuan:~$ apt list | grep linux-image-5.10.0-0.bpo | grep -i amd64/oldstable
--- snip ---
linux-image-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$
and this:
groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64/oldstable
--- snip ---
linux-headers-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-cloud-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-rt-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$
This is what I have installed:
~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64 | grep installed
--- snip ---
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
~$
~$ apt list | grep linux-image-5.10.0-0.bpo | grep -i amd64 | grep installed
--- snip ---
linux-image-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
~$
So ...
I just do apt install linux-headers-5.10.0-0.bpo.12-amd64?
I'm assuming the matching linux-image gets dragged along although it seems it is unsigned:
~$ apt list | grep linux-image-5.10.0-0.bpo.12-amd64
--- snip ---
linux-image-5.10.0-0.bpo.12-amd64-dbg/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.12-amd64-unsigned/oldstable-backports 5.10.103-1~bpo10+1 amd64 <-------------
~$
Thanks in advance.
Best,
A.
Last edited by Altoid (2022-03-20 01:19:29)
Offline
There's no metapackage for backports kernels like there is for the main kernel. The only updates you would get would be if the kernel version didn't change. ...
I fear that is not 100% true. Besides the backports kernel you may also install the backports metapackage. In case of Beowulf:
# apt -t beowulf-backports install linux-image-amd64
Then you will lose the updates of the main kernel packages, but get the updates from backports. You can't have both. This way you get the signed versions of the backports kernels.
I am using backports headers and kernels only, my Chimaera is running now with 5.16.
rolfie
Last edited by rolfie (2022-03-20 13:19:37)
Offline
Hello:
Besides the backports kernel you may also install the backports metapackage.
I see ...
Sort of.
... you will lose the updates of the main kernel packages ...
... get the updates from backports.
I am using backports headers and images only, my Chimaera is running now with 5.16.
It would seem, if I understand correctly, that you have with your Chimaera) installation what I want to have with my Beowulf installation.
ie: Beowulf with a an up-to-date 5.10 backported kernel
Eventually, a couple of (or all, don't know yet) backported applications.
Not Chimaera because of the reasons posted previously.
How can I get this done?
Thanks in advance.
Best,
A.
Offline
How can I get this done?
Run the previously posted command, that will do the job.
rolfie
Offline
Hello:
Run the previously posted command, that will do the job.
Done.
But the system does not find the nvidia driver module so I cannot get a desktop.
Just command line.
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 63.984] Build Operating System: Linux 5.10.0-10-amd64 x86_64 Debian
[ 63.985] Current Operating System: Linux devuan 5.10.0-0.bpo.11-amd64 #1 SMP Debian 5.10.92-1~bpo10+1 (2022-02-03) x86_64
--- snip ---
[ 64.025] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 64.025] (EE) NVIDIA: system's kernel log for additional error messages and
[ 64.025] (EE) NVIDIA: consult the NVIDIA README for details.
Makes sense that it cannot find it.
ie: whereas there are 340xx modules in /lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms ...
~$ locate 340xx
--- snip ---
/lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms/nvidia-legacy-340xx-uvm.ko
/lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms/nvidia-legacy-340xx.ko
--- snip ---
... there is no /updates or /updates/dkms directory in /lib/modules/5.10.0-0.bpo.11-amd64
~$ ls /lib/modules/5.10.0-0.bpo.11-amd64
kernel modules.alias.bin modules.builtin.bin modules.dep modules.devname modules.softdep modules.symbols.bin
modules.alias modules.builtin modules.builtin.modinfo modules.dep.bin modules.order modules.symbols
~$
I did find this one via apt list but it is the one I have installed:
~$ apt list | grep nvidia-legacy-340xx | grep dkms
--- snip ---
nvidia-legacy-340xx-kernel-dkms/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
--- snip ---
~$
System's working with the previous version so it's not a serious problem.
But I don't get what has happened.
Thanks in advance.
Best,
A.
Last edited by Altoid (2022-03-20 16:26:49)
Offline
SCNR: Thats why I don't use NVidea at all.
Well, maybe you need to run a setup for your drivers that builds the modules. And you probably also need the headers for the new kernel to do that. I know that I need them for building the VBox kernel modules. Also a manual process.
Try that:
# apt -t beowulf-backports install linux-headers-amd64
rolfie
Offline
Hello:
... why I don't use NVidea at all.
The pair of cards were at a really great price.
Impossible to pass up or resist, for that matter.
... run a setup for your drivers that builds the modules.
... need the headers for the new kernel ...
... need them for building the VBox kernel modules.
Yes.
I saw from the terminal that the VM that runs pihole was not up and the printout when atempting to run /sbin/vboxconfig put me up to speed.
Much more verbose in that respect than the nvidia drivers. 8^/
... a manual process.
Sure.
Like installing a backported kernel.
Try that:
# apt -t beowulf-backports install linux-headers-amd64
Done.
Booted into my SLiM log-it as always.
groucho@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.11-amd64 #1 SMP Debian 5.10.92-1~bpo10+1 (2022-02-03) x86_64 GNU/Linux
groucho@devuan:~$
Apparently everything runs as it should.
There may be a problem with the wicd daemon not starting right away, I'll have to look into that.
Thanks a lot for your input.
Best,
A.
Offline
Pages: 1