© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Oh, and you probably did lose current_now because of 2.6.36. It comes directly from the kernel, so not many other components have a chance to make it go away. Battery hardware varies, so it's easy to have a battery bug only affect specific laptops. I'd recommend testing a mainline 2.6.35 kernel (to see if it's an Ubuntu patch that provides current_now), then bisecting to find the commit that made it go away. If/when you do find a bad commit, you should file a new bug.
My own battery has never reported current_now. Some batteries just don't report that data in a way that linux knows how to get it, and probably some aren't even capable of reporting that data.