/sys/power/state doesn't contain ram on the XO, so suspend to RAM won't work. This may require pulling in the olpc-pm patches
Making this more generic -- we don't have any of the OLPC power management support. This leads to 1) No suspend 2) No poweroff on shutdown 3) No battery status in hal 4) No other power management
*** Bug 466413 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As usual, this isn't an F10 bug, this is an ongoing bug, so the Bug Zapper did the wrong thing. It's just part of the standard worldwide QA strategy: to automatically declare all bugs "not worth looking at" until their release goes EOL and all bugs get automatically classified WONTFIX and closed. Nothing suspicious here, move along now. Our QA department resolves all our bugs, mostly without effort; just look at our stats! It appears that Red Hat has locked down their bugzilla so ordinary folks like me can't fix the bugs introduced by their buggy daemons, so I can't change this back to "rawhide" nor can I set it to "F11".
I've set it to 'rawhide' for you. Nice rant, btw.
Definitely not a release blocker, pulling it from there.
Keeping in mind that I have just inherited this bug from Jeremy Katz, do the olpc-pm patches live somewhere? We normally want to inherit such changes from the upstream kernel, is there any progress on pushing these patches into upstream?
This is waiting on OLPC getting olpc-pm upstream, which I don't think is happening for 2.6.32, but is still something we're interested in doing. (The XO-1.5 isn't affected, it exposes ACPI tables instead.)
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Sorry, I missed the F13 EOL warning email for this one. Please can someone with the right access: 1) reopen 2) set the release to rawhide 3) Change the description from "OLPC XO" to "OLPC XO-1" ...? The rationale is that, AFAICS, the XO-1 is still targeted using recent Fedora releases[1], and power management is still required[2]. 1. http://wiki.laptop.org/go/Release_notes/11.2.0#Purpose 2. http://wiki.laptop.org/go/Release_notes/11.2.0#Power_management