Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

[Doug Smythies]

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.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1462822

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Doug Smythies (dsmythies)]

You do not need the apport stuff for this bug report, it is not relevant.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Doug Smythies (dsmythies)]

The kernel configuration is O.K. with respect to this issue as of kernel 4.1, and dmidecode works. Thanks.