On 26/2/18 1:12 am, Patrick O'Callaghan wrote:
On Sun, 2018-02-25 at 13:00 +1100, Stephen Morris wrote:
On 25/2/18 12:15 am, Patrick O'Callaghan wrote:
On Sat, 2018-02-24 at 15:43 +1100, Stephen Morris wrote:
Are all these taint messages, and all the reasons for a taint message
being produced
On Sun, 2018-02-25 at 13:00 +1100, Stephen Morris wrote:
> On 25/2/18 12:15 am, Patrick O'Callaghan wrote:
> > On Sat, 2018-02-24 at 15:43 +1100, Stephen Morris wrote:
> > > Are all these taint messages, and all the reasons for a taint message
> > > being produced saying that if we have to build ou
On 25/2/18 1:21 pm, Ed Greshko wrote:
On 02/25/18 09:46, Stephen Morris wrote:
[ 10.395281] razermouse: loading out-of-tree module taints kernel.
[ 10.395344] razermouse: module verification failed: signature and/or required
key missing - tainting kernel
[ 10.874905] nvidia: module license
On 25/2/18 1:21 pm, Ed Greshko wrote:
On 02/25/18 09:57, Stephen Morris wrote:
On 24/2/18 11:12 pm, Ed Greshko wrote:
On 02/24/18 12:43, Stephen Morris wrote:
Thanks Ed. Is there any documentation anywhere on what each bit represents?
You mean other than the URL I've supplied at kernel.org a
On 02/25/18 09:57, Stephen Morris wrote:
> On 24/2/18 11:12 pm, Ed Greshko wrote:
>> On 02/24/18 12:43, Stephen Morris wrote:
>>> Thanks Ed. Is there any documentation anywhere on what each bit represents?
>> You mean other than the URL I've supplied at kernel.org and the comments
>> within
>> tai
On 02/25/18 09:46, Stephen Morris wrote:
> [ 10.395281] razermouse: loading out-of-tree module taints kernel.
> [ 10.395344] razermouse: module verification failed: signature and/or
> required
> key missing - tainting kernel
> [ 10.874905] nvidia: module license 'NVIDIA' taints kernel.
> [
On 25/2/18 12:15 am, Patrick O'Callaghan wrote:
On Sat, 2018-02-24 at 15:43 +1100, Stephen Morris wrote:
Are all these taint messages, and all the reasons for a taint message
being produced saying that if we have to build our own drivers into the
kernel to be able to use our hardware, and hence
On 24/2/18 11:12 pm, Ed Greshko wrote:
On 02/24/18 12:43, Stephen Morris wrote:
Thanks Ed. Is there any documentation anywhere on what each bit represents?
You mean other than the URL I've supplied at kernel.org and the comments within
tainted.c ?
I haven't seen tainted.c as yet so I'm not sure
On 24/2/18 3:43 pm, Stephen Morris wrote:
On 24/2/18 2:25 pm, Ed Greshko wrote:
On 02/24/18 10:21, Stephen Morris wrote:
On 23/2/18 8:59 am, Ed Greshko wrote:
On 02/23/18 05:27, Stephen Morris wrote:
From the responses I am getting it seems that the meaning of
'taints the kernel'
has morph
On Sat, 2018-02-24 at 15:43 +1100, Stephen Morris wrote:
> Are all these taint messages, and all the reasons for a taint message
> being produced saying that if we have to build our own drivers into the
> kernel to be able to use our hardware, and hence put us into the
> situation of potentially
On 02/24/18 12:43, Stephen Morris wrote:
> Thanks Ed. Is there any documentation anywhere on what each bit represents?
You mean other than the URL I've supplied at kernel.org and the comments within
tainted.c ?
>
>
> With bit 13 being set reflecting the loading of an unsigned module into a
> ker
On 24/2/18 2:25 pm, Ed Greshko wrote:
On 02/24/18 10:21, Stephen Morris wrote:
On 23/2/18 8:59 am, Ed Greshko wrote:
On 02/23/18 05:27, Stephen Morris wrote:
From the responses I am getting it seems that the meaning of 'taints the
kernel'
has morphed into something else?
Here is the defini
On 02/24/18 10:21, Stephen Morris wrote:
> On 23/2/18 8:59 am, Ed Greshko wrote:
>> On 02/23/18 05:27, Stephen Morris wrote:
>>> From the responses I am getting it seems that the meaning of 'taints the
>>> kernel'
>>> has morphed into something else?
>>
>> Here is the definitive list of what tain
On 23/2/18 9:04 am, Joe Zeff wrote:
On 02/22/2018 01:27 PM, Stephen Morris wrote:
From the responses I am getting it seems that the meaning of 'taints
the kernel' has morphed into something else?
Here's my understanding of it from when I had nVidia graphics. Let's
say that you have a kernelo
On 23/2/18 8:59 am, Ed Greshko wrote:
On 02/23/18 05:27, Stephen Morris wrote:
From the responses I am getting it seems that the meaning of 'taints the
kernel'
has morphed into something else?
Here is the definitive list of what taints the kernel. This is from the 4.14
documentation but is
On 02/23/18 05:59, Ed Greshko wrote:
> The numbers in the list correspond to the bit positions in the value supplied
> by "cat
> /proc/sys/kernel/tainted"
That actually should have said "number - 1" corresponds to the bit position in
the
value returned by the cat command.
--
A motto of mine i
On 02/22/2018 01:27 PM, Stephen Morris wrote:
From the responses I am getting it seems that the meaning of 'taints
the kernel' has morphed into something else?
Here's my understanding of it from when I had nVidia graphics. Let's
say that you have a kerneloops, but haven't rebooted. Your ker
On 02/23/18 05:27, Stephen Morris wrote:
> From the responses I am getting it seems that the meaning of 'taints the
> kernel'
> has morphed into something else?
Here is the definitive list of what taints the kernel. This is from the 4.14
documentation but is also valid for 4.15 kernels.
https
On 20/2/18 7:41 am, Stephen Morris wrote:
Hi,
I'm using the nvidia drivers from negativo17. I have the nvidia
source module registered with dkms and it seems to be being compiled
when I get a new kernel, if that is the case what do I need to do to
resolve the following messages shown by "
On 02/20/2018 12:59 PM, Stephen Morris wrote:
Looking at dmesg again this morning, and searching for the work 'taints'
I get the 2nd message listed above but not the first message (why?), and
this search displays a message in the same format as the first message
for my wifi driver which is also
On 02/21/18 08:23, Tim wrote:
> Allegedly, on or about 21 February 2018, Stephen Morris sent:
>> I been in the situation of compiling kernel modules in other linux
>> distributions where you could put statements in your source to stop
>> these messages, but I have forgotten what they were.
> A in
Allegedly, on or about 21 February 2018, Stephen Morris sent:
> I been in the situation of compiling kernel modules in other linux
> distributions where you could put statements in your source to stop
> these messages, but I have forgotten what they were.
A install is tainted by having certain k
On 02/21/18 04:59, Stephen Morris wrote:
> On 20/2/18 8:54 am, Ed Greshko wrote:
>> On 02/20/18 04:41, Stephen Morris wrote:
>>> I'm using the nvidia drivers from negativo17. I have the nvidia source
>>> module
>>> registered with dkms and it seems to be being compiled when I get a new
>>> ke
On 20/2/18 8:54 am, Ed Greshko wrote:
On 02/20/18 04:41, Stephen Morris wrote:
I'm using the nvidia drivers from negativo17. I have the nvidia source
module
registered with dkms and it seems to be being compiled when I get a new kernel,
if
that is the case what do I need to do to resolve t
On 02/20/18 04:41, Stephen Morris wrote:
> I'm using the nvidia drivers from negativo17. I have the nvidia source
> module
> registered with dkms and it seems to be being compiled when I get a new
> kernel, if
> that is the case what do I need to do to resolve the following messages shown
> b
Hi,
I'm using the nvidia drivers from negativo17. I have the nvidia
source module registered with dkms and it seems to be being compiled
when I get a new kernel, if that is the case what do I need to do to
resolve the following messages shown by "dmesg"?
[ 14.934074] nvidia: loading o
26 matches
Mail list logo
