[SOLVED] nvidia bad return status for module on kernel - nvidia dkms

Roken · 2018-08-02 19:00:29

Today, I had an upgrade to linux (4.17.11-2) and nvidia-dkms (396.45-4),

Now I'm getting:

Error! Bad return status for module build on kernel: 4.17.11-arch1-2-ARCH (x86_64)

Downgrading is now producing the same error wherever I go. First trouble I've had with nvidia, and I don't know where to start looking.

These are the packages I upgraded, and I've now downgraded to the previous version of each. I have no idea where the problem may be:

[2018-08-02 19:16] [ALPM] upgraded binutils (2.30-5 -> 2.31.1-1)
[2018-08-02 19:16] [ALPM] upgraded gcc-libs (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-02 19:16] [ALPM] upgraded gcc (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-02 19:16] [ALPM] upgraded gcc-fortran (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-02 19:16] [ALPM] upgraded haveged (1.9.1-4 -> 1.9.2-1)
[2018-08-02 19:16] [ALPM] upgraded lib32-glibc (2.27-3 -> 2.28-1)
[2018-08-02 19:16] [ALPM] upgraded lib32-gcc-libs (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-02 19:16] [ALPM] upgraded libtool (2.4.6+40+g6ca5e224-7 -> 2.4.6+42+gb88cebd5-1)
[2018-08-02 19:16] [ALPM] upgraded linux (4.17.11.arch1-1 -> 4.17.11.arch1-2)
[2018-08-02 19:16] [ALPM] upgraded linux-headers (4.17.11.arch1-1 -> 4.17.11.arch1-2)
[2018-08-02 19:16] [ALPM] upgraded mercurial (4.6.2-1 -> 4.7-1)
[2018-08-02 19:16] [ALPM] upgraded nodejs (10.7.0-1 -> 10.8.0-1)
[2018-08-02 19:16] [ALPM] upgraded npm (6.2.0-1 -> 6.3.0-1)
[2018-08-02 19:16] [ALPM] upgraded nvidia-dkms (396.45-3 -> 396.45-4)

Help, please.

Last edited by Roken (2018-08-04 08:20:16)

WorMzy · 2018-08-02 19:32:00

Please fix your topic title, and do the same with your previous topics where you have had this pointed out to you.

Check the build log, see why it failed.

Mod note: Moving to testing.

Roken · 2018-08-02 19:59:45

Not sure what you mean by "previous". It's not something that's ever been mentioned, to my recollection, but I'll expand it.

As for the build log, where exactly do I find that?

EDIT - Worth mentioning that pacman gives me no error until rebuilding the kernel module - which is something I've never encountered. Downgrading the kernel and nvidia-dkms didn't help. I had to revert all of tonights upgrades. I'm not looking for hand holding, just which may be responsible. From there, I'll fix myself.

EDIT2 - since I reverted and puit all the above on hold, glibc has come up with an upgrade that fails. Before I go through it all again, is there a chance that I've simply got my timing wrong, and managed an upgrade before other packages (official, not AUR) were avilable?

Last edited by Roken (2018-08-02 20:05:13)

loqs · 2018-08-02 20:16:09

/var/lib/dkms/<your_module_name>/<your_module_version>/build/make.log but if you already downgraded the packages the log will be gone.

Roken · 2018-08-02 20:17:49

I can allow the upgrades again. It will drag the glibc upgrade in this time, which may fix it. Let me test.

Roken · 2018-08-02 20:36:11

DKMS make.log for nvidia-396.45 for kernel 4.17.11-arch1-2-ARCH (x86_64)
Thu  2 Aug 21:32:17 BST 2018
make[1]: Entering directory '/usr/lib/modules/4.17.11-arch1-2-ARCH/build'
  SYMLINK /var/lib/dkms/nvidia/396.45/build/nvidia-modeset/nv-modeset-kernel.o
  SYMLINK /var/lib/dkms/nvidia/396.45/build/nvidia/nv-kernel.o

Compiler version check failed:

The major and minor number of the compiler used to
compile the kernel:

gcc version 8.1.1 20180531 (GCC)

does not match the compiler used here:

cc (GCC) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


It is recommended to set the CC environment variable
to the compiler that was used to compile the kernel.

The compiler version check can be disabled by setting
the IGNORE_CC_MISMATCH environment variable to "1".
However, mixing compiler versions between the kernel
and kernel modules can result in subtle bugs that are
difficult to diagnose.

*** Failed CC version check. Bailing out! ***

make[2]: *** [/var/lib/dkms/nvidia/396.45/build/Kbuild:180: cc_version_check] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1571: _module_/var/lib/dkms/nvidia/396.45/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/4.17.11-arch1-2-ARCH/build'
make: *** [Makefile:79: modules] Error 2

And from pacman.conf

 Pacman won't upgrady packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = ttf-ms-win10 ttf-ms-win10-japanese ttf-ms-win10-korean ttf-ms-win10-other ttf-ms-win10-sea ttf-ms-win10-thai ttf-ms-win10-zh_cn ttf-ms-win10-zh_tw python blender libreoffice-fresh  i

#binutils gcc-libs gcc gcc-fortran haveged lib32-glibc lib32-gcc-libs libtool linux linux-headers mercurial nodejs npm nvidia-dkms glibc

IgnoreGroup =

EDIT:

pacman -Ss gcc | grep 8.2
testing/gcc 8.2.0-2 (base-devel) [installed]

So why isn't it using it?

The libre/python/blender ignore are in respect of another problem, and the Windows TTF will probably be uninstalled. I don't see either making a difference, though.

Last edited by Roken (2018-08-02 20:38:26)

loqs · 2018-08-02 20:39:15

What is the output of `pacman -Q gcc`
Edit:
Already covered.
Edit2:
From the .BUILDINFO

installed = gcc-8.1.1+20180531-1-x86_64

The package was not built against testing and is incompatible with the gcc currently in testing.

Last edited by loqs (2018-08-02 20:43:13)

Roken · 2018-08-02 21:08:36

So sit back and wait? I can live with that if necessary. I'm surprised that they were all pushed out together, though.

Thank you, loqs. At least I know what to hold back and can get the rest updated. And I got around to removing the win 10 ttf packages, too.

Roken · 2018-08-04 08:19:59

The latest linux update has fixed, I assume now built against gcc 8.2.0.2

Arch Linux

#1 2018-08-02 19:00:29

[SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#2 2018-08-02 19:32:00

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#3 2018-08-02 19:59:45

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#4 2018-08-02 20:16:09

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#5 2018-08-02 20:17:49

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#6 2018-08-02 20:36:11

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#7 2018-08-02 20:39:15

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#8 2018-08-02 21:08:36

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

#9 2018-08-04 08:19:59

Re: [SOLVED] nvidia bad return status for module on kernel - nvidia dkms

Board footer