[Kernel-packages] [Bug 1462822] Re: Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

2015-06-24 Thread Doug Smythies
The kernel configuration is O.K. with respect to this issue as of kernel
4.1, and dmidecode works. Thanks.

** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1462822

Title:
  Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

Status in linux package in Ubuntu:
  Fix Released

Bug 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 changing from #CONFIG_DEVMEM is not
  set to CONFIG_DEVMEM=y myself and now dmidecode works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462822/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1462822] Re: Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

2015-06-07 Thread Doug Smythies
** Description changed:

  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 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.
+ By the way, I compiled 4.1RC6 changing from #CONFIG_DEVMEM is not set
+ to CONFIG_DEVMEM=y myself and now dmidecode works fine.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1462822

Title:
  Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

Status in linux package in Ubuntu:
  Confirmed

Bug 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 changing from #CONFIG_DEVMEM is not
  set to CONFIG_DEVMEM=y myself and now dmidecode works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462822/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1462822] Re: Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

2015-06-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1462822

Title:
  Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

Status in linux package in Ubuntu:
  Confirmed

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462822/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1462822] Re: Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

2015-06-07 Thread Doug Smythies
You do not need the apport stuff for this bug report, it is not
relevant.

** Changed in: linux (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1462822

Title:
  Kernel configuration parameter CONFIG_DEVMEM is not set, it should be

Status in linux package in Ubuntu:
  New

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462822/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp