errors building dkms modules with new kernel?

[Member stevesr0]

Hi all,

I just installed the 5.2.15 kernel and noticed that I got the following error messages:

Error! Bad return status for module build on kernel: 5.2.15-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.2.15-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.2.15-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.2.24/build/make.log for more information.

In searching online, there was a recent issue discussed on MX where the forced rebuilding of kernel modules was “prescribed”.

I just rebooted with the new kernel and don’t notice any problems.

Checking on my installed hardware, I don’t have a broadcom chip. I have the broadcom-sta-dkms package installed, but neither the broadcom-source or broadcom-common.

Checking on my installed packages, I don’t have virtualbox installed (just virtualbox-dkms).

I do have ndiswrapper packages installed (v1.61), but not the ndiswrapper-source package. This is recommended, so NOT absolutely necessary? (I also have TWO versions of the ndiswrapper-utils installed, but one is said to be a transitional dummy package and the other is the same 1.61 version as the other ndiswrapper packages.

So, my questions: (a) are the virtualbox and broadcom messages there because of the dkms packages (without anything else)? If so, will removing the packages get rid of those error messages?
(b) For ndiswrapper, is the error because of the two versions of the ndiswrapper-utils?

Finally, if I want to get rid of these errors, is there a specific code to rebuild DKMS, such as:
for i in $(dpkg-query -l |grep “\-dkms” |awk ‘{print $2’}); do dpkg-reconfigure $i |tee -a /var/log/rebuild-dkms.log; done
(from the antiX forum)

or something else…?

Thanks.

stevesr0

[Moderator caprea]

Helpful

Up

0

::

Most recent kernels often need newer versions of drivers and modules (broadcomsta , ndiswrapper, nvidia-driver,virtualbox ) and and it may take a while for them to appear in the sources.

As long as you don’t have the hardware that goes with it, it’s not of interest to you if the new kernel builds against a particular module or not.
The same applies if you don’t use virtualbox.
As you already mentioned there are no problems, because these modules are not needed by the hardware or by you.

If you nevertheless want to remove these modules, you could do so. Just remove ndiswrapper, broadcom-sta-dkms. If removing virtualbox-guest-dkms, you first have to remove virtualbox-guest-utils.

[Member stevesr0]

Helpful

Up

0

::

Thanks.

I was puzzled because the log files did not make me understand what was wrong. I guess they are not smart enough for someone who doesn’t know enough <g>.

As long as I am not experiencing problems, I will just leave things as they at this time.

stevesr0

[Forum Admin rokytnji]

Helpful

Up

0

::

I get weird error on not can open policy.kit folder on my boot screen on my chromebook with the

harry@biker:~
$ inxi -c10
CPU: Dual Core Intel Celeron 1007U (-MCP-) speed/min/max: 1401/800/1500 MHz 
Kernel: 5.2.3-antix.1-amd64-smp x86_64 Up: 5h 07m Mem: 1460.3/3882.0 MiB (37.6%) 
Storage: 14.91 GiB (43.1% used) Procs: 136 Shell: bash 4.4.12 inxi: 3.0.36 

Poked around in dmesg and used the locate command to poke around and see what was up. I did nothing though because I am posting just fine from this chromebook with all hardware working. Doing nothing to correct that .

Because looking at kernel.log in /var/log . Not much amiss there.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Author]

Posts