|
Bugzilla – Full Text Bug Listing |
| Summary: | Kpowersave shows very wrong battery time | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | vegard myrvang <vegard.myrvang> |
| Component: | Mobile Devices | Assignee: | Danny Al-Gaaf <dalgaaf> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P4 - Low | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot
lshal -m lshal -s lshal |
||
|
Description
vegard myrvang
2009-02-02 21:20:42 UTC
Created attachment 269395 [details]
screenshot
screenshot
Please run 'lshal -m' on a console over e.g. 30 or 60 minutes and attach the output to this bug. And please provide also the output of lshal Created attachment 271263 [details]
lshal -m
output from lshal -m
Created attachment 271265 [details]
lshal -s
output from lshal was too long.
hope it's okey with the short version, lshal -s
(In reply to comment #4) > Created an attachment (id=271265) [details] > lshal -s > > output from lshal was too long. > hope it's okey with the short version, lshal -s no, the short version is complete useless. Created attachment 271290 [details]
lshal
the output from lshal is about 5000 lines. the file above is what i was able to get from cli. anyway to redirect the output to a file ? Hopefully the attachment will be enough vegard I need the full output. You can use 'lshal > /tmp/lshal' and attach /tmp/lshal to this bug. There is nothing we can do, looks like a hardware (battery) or bios bug. The battery.charge_level.last_full value is permanently changing. This value should be stable over discharging. This value has an affect on the remaining time calculation. Another problem is that the battery.charge_level.last_full (something around 730) and battery.charge_level.current value is massively lower than the value for battery.charge_level.design (38802) You may should report the problem to the vendor of the machine. I have to close the bug, since this isn't a software problem. |