| 2015-06-07 23:52:01 |
Doug Smythies |
description |
There is a relatively new kernel configuration parameter, CONFIG_DEVMEM.
I do not understand why, but for some reason "is not set" for Ubuntu, and therefore dmidecode does not work.
I think that, in general, we want dmidecode to work.
I found this: https://lists.ubuntu.com/archives/kernel-team/2015-May/057250.html,
and so had expected it to be set to yes by now, but in Kernel 4.1RC6 it still isn't.
(And yes, I am talking mainline kernels here, which I know are not supported, but I am just trying to help.)
Is there a reason to have it not set?
On IRC apw asked me to enter this bug report and to assign it to him.
By the way, I compiled 4.1RC6 with CONFIG_DEVMEM=y and now dmidecode works fine. |
There is a relatively new kernel configuration parameter, CONFIG_DEVMEM.
I do not understand why, but for some reason "is not set" for Ubuntu, and therefore dmidecode does not work.
I think that, in general, we want dmidecode to work.
I found this: https://lists.ubuntu.com/archives/kernel-team/2015-May/057250.html,
and so had expected it to be set to yes by now, but in Kernel 4.1RC6 it still isn't.
(And yes, I am talking mainline kernels here, which I know are not supported, but I am just trying to help.)
Is there a reason to have it not set?
On IRC apw asked me to enter this bug report and to assign it to him.
By the way, I compiled 4.1RC6 changing from "#CONFIG_DEVMEM is not set" to "CONFIG_DEVMEM=y" myself and now dmidecode works fine. |
|
