Tainted Kernel?

Trying to diagnose an issue which seems Unique to EOS so far.
fwupd is detecting the Linux kernel as Tainted.
Not particularly sure where to begin, may not even cause noticeable problems.
Shows as Untainted on vanilla Arch, and Fedora which are the other 2 distros i have tried.
Shows as tainted on the live boot media for EOS-endeavours, and EOS-Gemini which i still had on boot media.
But curiously only on my new computer, it’s fine on my other system’s.

Tainted doesn’t mean broken.

Are you using the proprietary nvidia drivers? That would cause the kernel to be tainted.

2 Likes

virtualbox also taints the kernel.

2 Likes

What command did you use for that output?

I might be on my current install.
that does not however explain the same output on EOS-Endeavour live boot media or EOS-Gemini boot media.
in both cases i am forcing the boot media to not boot using the Nvidia drivers,

As i said not an issue in regular Arch or redhat Fedora.

That was a screenshot of the firmware security tab from info center under KDE desktop environment.
there is probably a command to get the same result via terminal however.

Check dmesg:

[thomas@roamer ~]$ sudo dmesg | grep taint
[    1.511530] vboxdrv: loading out-of-tree module taints kernel.
[    1.511532] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[thomas@roamer ~]$ 
2 Likes

Tainted kernels: https://www.kernel.org/doc/html/v4.18/admin-guide/tainted-kernels.html

2 Likes

On the ISO we are loading some out-of-tree modules that are tainting the kernel.

However, we remove them from the installed system if they aren’t needed.

We are using the kernels from Arch so they are the same kernels.

If you want to know what is tainting your kernel, just check and see what it is.

We definitely favor compatibility over being purely open-source and will install drivers that taint the kernel if we detect the hardware.

That being said you can easily remove those things if that is your preference

5 Likes

Seems to be some Nvidia module that Endeavour is loading,
Didn’t have the same tainted message with Vanilla Arch.
Not a major though, and fixable when i have the time.

Appreciate the feedback, and apologies for the very late reply, busy month.

here is the paste from dmesg:

[danielp@Tuf-Unix ~]$ sudo dmesg | grep taint
[sudo] password for danielp:
[ 0.865407] nvidia: loading out-of-tree module taints kernel.
[ 0.865413] nvidia: module license ‘NVIDIA’ taints kernel.
[ 0.865414] Disabling lock debugging due to kernel taint
[ 0.865416] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 0.865417] nvidia: module license taints kernel.
[ 1.401374] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.

1 Like

Ended up solving it in the end.
Sadly anything Nvidia will just taint the kernel other than vulkan-nouveau.
Had hoped it was limited to the Proprietary Nvidia drivers,
but the taint returned when installing nvidia-open or nvidia-open-dkms.

same issue is not present in Vanilla arch where i replicated the package setup.
suspect it won’t happen on other Distros either.

Dunno what Endeavour is doing differently,
happy to post logs for dev purposes if it helps,
just tell me what you need.

Read here:

Kernel is tainted does not say it is broken or something is wrong in the first place.
It is tainted by out-of-kernel proprietary modules used.
It would not show that message (information) if you would remove these.