On Wed, Aug 15, 2012 at 10:45 AM, Dominic Fandrey <[email protected]>wrote:
> On 15/08/2012 10:40, Andreas Nilsson wrote: > >> On Wed, Aug 15, 2012 at 10:36 AM, Dominic Fandrey <[email protected] >> >wrote: >> >>> For a while now "acpiconf -i0" always shows the battery state that >>> was correct when booting the system. It's never updated. >>> >>> snip >>> >> >> It wont solve the problem, but does the sysctl hw.acpi.battery.time update >> correctly? >> > > Thanks for the fast reply, right now it shows -1 (the system was plugged > in during boot). > > I just unplugged it and it still shows -1: > >> sysctl hw.acpi.battery >> > hw.acpi.battery.life: 99 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 0 > hw.acpi.battery.units: 2 > hw.acpi.battery.info_expire: 5 > > > -- > A: Because it fouls the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing on usenet and in e-mail? > Sounds like there is some acpi-problem then. On my thinkpad it takes maybe five seconds for it to go from -1 to an estimate. Also hw.acpi.battery.state=0 for me equals "AC plugged in and battery full". I have this in my .xinitrc to monitor my battery ( in a loop which then uses xsetroot to show the info ): case `sysctl -n hw.acpi.battery.state` in 0) batstate="AC full" ;; 1) batstate="`sysctl -n hw.acpi.battery.time` m" ;; 2) batstate="AC charing" ;; Best regards Andreas _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
