From: Nick H. <li...@gm...> - 2007-07-29 13:46:18
|
ahoy list. after upgrading from 2.6.21.1+mactel to 2.6.22.1+mactel and getting suspend-to-ram working, i've noticed that i no longer have any battery info/stats. any suggestions on how to get them back? thanks! -Nick nick@wombat:~> cat /proc/acpi/battery/BAT0/state present: yes capacity state: ok charging state: discharging present rate: 0 mW remaining capacity: 0 mWh present voltage: 0 mV nick@wombat:~> cat /proc/acpi/battery/BAT0/info present: yes design capacity: 0 mWh last full capacity: 0 mWh battery technology: rechargeable design voltage: 0 mV design capacity warning: 250 mWh design capacity low: 100 mWh capacity granularity 1: 10 mWh capacity granularity 2: 10 mWh model number: serial number: battery type: OEM info: nick@wombat:~> cat /proc/acpi/battery/BAT0/alarm alarm: unsupported |
From: Jonas P. <jon...@xm...> - 2007-07-29 15:50:37
|
Hi Nick, Nick Hoffman wrote: > ahoy list. after upgrading from 2.6.21.1+mactel to 2.6.22.1+mactel and > getting suspend-to-ram working, i've noticed that i no longer have any > battery info/stats. any suggestions on how to get them back? Is this consistent for you? For me this happens on and off with (seemingly) any kernel after a while - IIRC it has occured even newly booted with most kernels, but I've never had it working for more than a week of normal use - typically 2 suspend cycles per day (though whether that is significant I have no idea). Same problem with Orwin's mbps2ram as with fairly recent suspend2 (though I've not tried it since the name change). Most of the time it works again after a clean boot, I usually reset the NVRAM at that stage and occasionally start OSX, just to double check that it still works properly there - it always seems to now. My first MBPC2D freaked after a while (some of you may really my mails) and then battery etc would fail in OSX too - and in the end it would only boot up after 30+ min of cooling down. This one has been fairly "stable" in this sometimes-working state. Possibly related: I use the gnome Sensors Apple (1.6) and it will occasionally report that a some (seemingly random) sensors (I watch all 11 I can get) are not readable, but they typically work again on the following poll. BTW: My fans are often spinning just below 6000 after a while (aka "hovering") - annoying is an understatement. Suspending (2ram) and immediately resuming usually reset them to ~2000 for a while, but they gradually climb to at least 4000 within an hour. Any ideas welcome - I'm on 2.6.22-rc5-mactel (Gentoo) with ATI-drivers 8.37.6-r1 using ndiswrapper 1.47 with net5416 (,12/13/2006,6.0.2.75). / Jonas -- Jonas Petersson | XMS Penvision | mailto:Jon...@xm... Box 3294, Västgötegatan 13, S-600 03 Norrköping | www.penvision.se Tel: +46 11 400 13 00 | Dir: +46 11 400 13 05 | Fax: +46 11 10 30 50 |
From: Nick H. <li...@gm...> - 2007-07-30 00:56:54
|
hi Jonas. > Is this consistent for you? For me this happens on and off with > (seemingly) any kernel after a while - IIRC it has occured even newly > booted with most kernels, but I've never had it working for more than a > week of normal use - typically 2 suspend cycles per day (though whether > that is significant I have no idea). Same problem with Orwin's mbps2ram > as with fairly recent suspend2 (though I've not tried it since the name > change). i got my 15" MBP C2D new in Feb/March, and not once has the battery info in /proc/acpi/battery/ stopped reporting values..until now. i've used Linux 2.6.{18,20,21,22}. with Linux <2.6.22, i *rarely* suspended to disk or RAM because i had issues with the touchpad. however, when i did, i can't recall a single instance when the battery info didn't persist. > Most of the time it works again after a clean boot, I usually reset the > NVRAM at that stage and occasionally start OSX, just to double check > that it still works properly there - it always seems to now. My first > MBPC2D freaked after a while (some of you may really my mails) and then > battery etc would fail in OSX too - and in the end it would only boot up > after 30+ min of cooling down. This one has been fairly "stable" in this > sometimes-working state. when i first noticed that the battery info had disappeared, i thought that rebooting or shutting down would fix it. unfortunately, neither has helped. i just booted into MacOS X and confirmed that it's able to query the battery for the proper info. i then rebooted into Debian and voila, the battery info's back. -Nick |