Richard Melville wrote:
On 5 June 2015 at 14:45, Richard Melville <richard.melvill...@googlemail.com
wrote:
I've just installed this package, and, having run through the build
instructions on the relevant page of the book, it seemed to me to be a very
convoluted approach, but maybe I'm wrong.
Why is it necessary to build a modular kernel first? Using my
statically-built kernel, I built and installed lm_sensors-3.3.5. Then I
ran "sensors-detect" which supplied me with the hardware info and the
relevant kernel drivers necessary to load. Only three devices were
detected, which was not surprising as it's an Intel mini-ITX embedded
motherboard. I had already built in the two most obvious drivers leaving
just a third (more obscure one) to compile in to the kernel. Even if I
hadn't installed *any* of the relevant drivers, "sensors-detect" would
still have supplied me with the complete list.
So, I can't see what benefit building an initial modular kernel would have
achieved. Maybe somebody can enlighten me.
Richard
Maybe I've partially answered my own question. I just ran "sensors-detect"
again and I noticed that at one stage there was a message: "Failed to load
module I2C-i801". However, this driver is already built into my kernel.
Does the message mean that lm_sensors doesn't recognise a driver unless
it's a module?
I haven't looked at this for a while, but I believe I remember that the
instructions show you how to determine which drivers are needed. After
you have identified all the ones you need, I think (not 100% sure) you
can build them into the kernel.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
