You are not logged in.
I'm going to assume running uname -a lists the current running kernel as the 4.19 pae one, so
sudo apt install linux-image-686-pae
Reboot. Post back with the output of uname -a. Also look at the Advanced Boot Options in grub when you reboot and note what kernels are listed. Also, try installing the 686-pae headers package I've linked if dkms is still complaining.Poor @pozric is installing and uninstalling from 3 conflicting sources.
@pozric, check what uname -a lists, install the appropriate packages, reboot, and let us know how it went.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
uname -a
Linux nonexistent 4.19.0-13-686-pae #1 SMP Debian 4.19.160-2 (2020-11-28) i686 GNU/Linux
Offline
And if you install the 686-pae kernel I linked?
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Ok thanks I will sudo apt install linux-image-686-pae linux-headers-686-pae, reboot and report back.
Offline
Its always something with nvidia driver ahhh.
I get thuis while Im installing:
Unpacking linux-image-686-pae (5.10.197-1) ...
Setting up linux-compiler-gcc-10-x86 (5.10.197-1) ...
Setting up linux-image-5.10.0-26-686-pae (5.10.197-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-26-686
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-26-686
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-26-686-pae
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-26-686-pae
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-26-686-pae:
Kernel preparation unnecessary for this kernel. Skipping..
Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j2 modules KERNEL_UNAME=5.10.0-26-686-pae; env CCACHE_D
ISABLE=1 NV_VERBOSE=1 make -C uvm modules KERNEL_UNAME=5.10.0-26-686-pae KBUILD_EXTMOD=/va
r/lib/dkms/nvidia-legacy-340xx/340.108/build/uvm..................(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.0-26-686-pae (i686)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for more information.
.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-26-686-pae
Offline
I should have guessed it was this old NVidia driver. I've dealt with that driver before, it's a pain. It's not supported after buster...
https://packages.debian.org/sid/nvidia- … 0xx-driver
Man, the devil is in the details as well. You have a 64 bit capable machine running a 32 bit kernel, which is fine but support for 32 bits is being dropped (Ubuntu no longer supports it).
I don't know what to recommend here, you have a bunch of options but all are a mess. The best would be to backup your data and install the upcoming BunsenLabs 64-bit ISO from here...
https://forums.bunsenlabs.org/viewtopic.php?id=8714
That would give you a current stable system that would be supported with security updates from Debian until at least summer of 2028, but I can understand why you wouldn't want to wipe your current system.
The next best thing would be to remove the nvidia package, update to the bullseye kernel and see if the nouveau driver works OK. That will give you a secure kernel and OS until summer of 2026.
For now, use the 4.19 kernel and let's see what @unklar, @johnraff or others suggest.
I'm sorry if I've confused the issue more than I've helped.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Hi again man sorry for buggering you guys:)
It didn't boot I guess it has something to do with the nvidia drivers Ive installed before incorrectly.
Offline
Thanks hhh and the rest of you guys always friendly and helping:)
Yeah about the 64 bit capable machine I need to get more ram and such, well hell I need to upgrade everything...
I'm gonna go with your advice and wait maybe do a clean Install with the link you gave, but 64 bit is gonna be crappy on my pc because it so old and wimpy. The beauty of Bunsenlabs and crunchbang and puppy linux is that you can use it on a crappy old machine, that doesn't fly with windows.
Thanks again dudes, cheers
Last edited by pozric (2023-11-19 15:34:38)
Offline
Hey, there's a 32-bit link to Boron there as well.
What I did with that driver on bookworm way back was run 32-bit pae current debian stable and I installed the nvidia legacy driver and dependencies from sid, but that's really bad advice and I don't even know if it would work anymore. It could easily not install because of libc and pfft.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Haha nice yeah about 32-bit Boron, you guys think about the geezers with Mr. Magoo computers hehe so there is already a new bunsen on the way, got damn I waited so long to update to Beryllium!
Offline
@hhh, you didn't 'confuse' anything at all.
I agree with you, not understanding how to do these pull-ups on a 64bit capable PC, with "a 32bit distri". And, then also running pae or not pae kernel on the system.
But, well....
----
I'm amazed at how this works magically in code tags....
Very nice!
The problem of dkms to build the nVidia configuration is, in my opinion, that the corresponding header files of the 5.10.0-26-686 (resp.-686-pae) also missing on the system.
Three solutions to the dilemma (the repos seem to be ok to me):
either
1. uninstalling the kernel 5.10.0-26-686 (resp.-686-pae)
or
2. installation of the kernel header files of 5.10.0-26-686 (resp.-686-pae)
3.(my favorite, as suggested by @hhh) Reinstalling the 64bit ISO of Boron
The candidate chooses... also good, 32bit [ Boron ]
Offline
2. installation of the kernel header files of 5.10.0-26-686
This might work! Don't remove anything, run...
sudo apt install linux-headers-686
Reboot if all goes well.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Thanks for the help, so the best thing is to do a clean install of 64 bit Boron from here https://forums.bunsenlabs.org/viewtopic.php?id=8714
But I have so litte ram, dont I need more ram for 64 bit?
You guys can close this thread.
Last edited by pozric (2023-11-19 23:45:54)
Offline
Did you try @unklar's suggestion using the command I posted 2 posts ago? If not, did you see that there is a 32-bit ISO for Boron as well?
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
@johnraff, you are sure that he has to install linux-image-amd64?
No, no and again no! Humble apologies, I was asleep at the wheel.
My machine is 64bit and of course it told me there was no linux-image-686 package...
Anyway @unklar and @hhh seem to have this all well in hand.
My first suggestion would be the same, ie (if you're going to stay with 32bit and not do a fresh install) to:
1) choose if you want pae or non-pae (I don't think there's a huge difference)
2) install linux-image-686 or linux-image-686-pae
and
linux-headers-686 or linux-headers-686-pae
3) sudo apt update
sudo apt full-upgrade
But if Nvidia is still causing trouble, try uninstalling it and see if Nouveau works.
If you want the Nvidia software, install it again after upgrading the kernel.
---
But a fresh Boron install might be the way to go if you've got your data backed up. Choose i386 or amd64.
It's true that amd64 apps use more RAM, so if you're seriously low then 32bit is an option, good for a few more years. More and more software is dropping 32bit support though...
...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 )
Offline
unklar wrote:2. installation of the kernel header files of 5.10.0-26-686
This might work! Don't remove anything, run...
sudo apt install linux-headers-686
Reboot if all goes well.
That wouldn't help him, because that's just the meta package and, as we know, that's empty. If it were, then it would have to be:
sudo apt install linux-headers-5.10.0-26-686
I tested this and it pulls a rat tail of dependencies:
sudo apt install linux-headers-5.10.0-26-686 -s
[sudo] Passwort für unklar:
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden zusätzlichen Pakete werden installiert:
binutils binutils-common binutils-i686-linux-gnu gcc-10 libasan6 libbinutils libcc1-0 libctf-nobfd0 libctf0 libgcc-10-dev libitm1 libubsan1 linux-compiler-gcc-10-x86
linux-headers-5.10.0-26-common linux-kbuild-5.10
Vorgeschlagene Pakete:
binutils-doc gcc-10-multilib gcc-10-doc gcc-10-locales
Die folgenden NEUEN Pakete werden installiert:
binutils binutils-common binutils-i686-linux-gnu gcc-10 libasan6 libbinutils libcc1-0 libctf-nobfd0 libctf0 libgcc-10-dev libitm1 libubsan1 linux-compiler-gcc-10-x86
linux-headers-5.10.0-26-686 linux-headers-5.10.0-26-common linux-kbuild-5.10
0 aktualisiert, 16 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Inst binutils-common (2.35.2-2 Debian:11.8/oldstable [i386])
Inst libbinutils (2.35.2-2 Debian:11.8/oldstable [i386])
Inst libctf-nobfd0 (2.35.2-2 Debian:11.8/oldstable [i386])
Inst libctf0 (2.35.2-2 Debian:11.8/oldstable [i386])
Inst binutils-i686-linux-gnu (2.35.2-2 Debian:11.8/oldstable [i386])
Inst binutils (2.35.2-2 Debian:11.8/oldstable [i386])
Inst libcc1-0 (10.2.1-6 Debian:11.8/oldstable [i386])
Inst libitm1 (10.2.1-6 Debian:11.8/oldstable [i386])
Inst libasan6 (10.2.1-6 Debian:11.8/oldstable [i386])
Inst libubsan1 (10.2.1-6 Debian:11.8/oldstable [i386])
Inst libgcc-10-dev (10.2.1-6 Debian:11.8/oldstable [i386])
Inst gcc-10 (10.2.1-6 Debian:11.8/oldstable [i386])
Inst linux-compiler-gcc-10-x86 (5.10.197-1 Debian:11.8/oldstable [i386])
Inst linux-headers-5.10.0-26-common (5.10.197-1 Debian:11.8/oldstable [all])
Inst linux-kbuild-5.10 (5.10.197-1 Debian:11.8/oldstable [i386])
Inst linux-headers-5.10.0-26-686 (5.10.197-1 Debian:11.8/oldstable [i386])
Conf binutils-common (2.35.2-2 Debian:11.8/oldstable [i386])
Conf libbinutils (2.35.2-2 Debian:11.8/oldstable [i386])
Conf libctf-nobfd0 (2.35.2-2 Debian:11.8/oldstable [i386])
Conf libctf0 (2.35.2-2 Debian:11.8/oldstable [i386])
Conf binutils-i686-linux-gnu (2.35.2-2 Debian:11.8/oldstable [i386])
Conf binutils (2.35.2-2 Debian:11.8/oldstable [i386])
Conf libcc1-0 (10.2.1-6 Debian:11.8/oldstable [i386])
Conf libitm1 (10.2.1-6 Debian:11.8/oldstable [i386])
Conf libasan6 (10.2.1-6 Debian:11.8/oldstable [i386])
Conf libubsan1 (10.2.1-6 Debian:11.8/oldstable [i386])
Conf libgcc-10-dev (10.2.1-6 Debian:11.8/oldstable [i386])
Conf gcc-10 (10.2.1-6 Debian:11.8/oldstable [i386])
Conf linux-compiler-gcc-10-x86 (5.10.197-1 Debian:11.8/oldstable [i386])
Conf linux-headers-5.10.0-26-common (5.10.197-1 Debian:11.8/oldstable [all])
Conf linux-kbuild-5.10 (5.10.197-1 Debian:11.8/oldstable [i386])
Conf linux-headers-5.10.0-26-686 (5.10.197-1 Debian:11.8/oldstable [i386])
I agree with @johnraff, it's best to continue with Boron.
However, we don't know how much RAM it has and pae kernels are not necessary with the CPU, I don't think.
Offline
sudo apt install linux-headers-686
That wouldn't help him, because that's just the meta package and, as we know, that's empty.
@unklar, surely you know what a metapackage is?
https://packages.debian.org/bookworm/linux-headers-686
This package depends on the architecture-specific header files for the latest Linux kernel 686 configuration.
So right now, installing linux-headers-686 on Debian Bullseye will pull in the latest version of linux-headers-5.10.0-26-686 as a dependency. It might indeed pull in a lot of other dependencies - that can't be helped if you want to build kernel modules.
The generic metapackages are useful because you don't have to worry about the exact name of the current kernel package, and once installed on your system an apt upgrade will be enough to get the latest kernel. Kernel packages are a bit different from other packages in that each major kernel version becomes a new package, so a normal upgrade won't install it unless you have the metapackage.
...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 )
Offline
sudo apt install linux-headers-686
unklar wrote:That wouldn't help him, because that's just the meta package and, as we know, that's empty.
@unklar, surely you know what a metapackage is?
https://packages.debian.org/bookworm/linux-headers-686
Well, you're right, but so am I.
However, we are not dealing with a 'normal' installation here, because the TE has already installed kernel 5.10.0-26-686 (linux-image-5.10.0-26-686)
However, he cannot select it because dkms complains about missing header files when building the nVidia modules.
If he now installs the empty meta package linux-headers-686, for later automatic kernel updates, this does not help him because he needs the header files.
These are, as I wrote, in the header package of the kernel linux-headers-5.10.0-26-686
Offline
I only saw a single partition in your post for inxi, but gotta ask if you have updated grub?
If grub is on another partition/distro, you may need to boot into that distro and update grub for the new kernel to be shown on boot.
Maybe not relevant, but thought to check anyway.
Offline
^ Good point. I've forgotten about that in the past and it's a real "D'oh!" moment when you realize it.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline