![]() ![]() I can't track the cause of the corruption right now, but i suspect is Perfectly all is run wanderfully untill some events that screw up again It otherwhise will not start) the next boot all the ACPI events are logged Laptop with a needle (laptop unpowered, than use the power cord to start > I can confirm you that if you push the reset button on bottom of the I'm not in a position to try it right now. > Maybe resetting the BIOS to default values mught re-instate normal (not sure if before that the problem was present or not)īattery status (charging/discharging), as found in Grub booting from an USB disk, and from that moment I noticed the This messed up with the MBR and Grub, so I had to recover I noticed the problem after starting up erroneously the recovery > the BIOS somehow corrupting itself with respect to ACPI. is this Ubuntu corrupting things in the BIOS or is Lid closure, instead, is completely broken also if suspend works well.Ĭan't test in Windows as I wiped out the windows partition ) I worked around this problem byĪpplying an ugly patch to upowerd so that power status change is MAYBE in Windows power connect/disconnect is triggered by power adapterĬhanging status instead than by battery. Is "frozen" in the status after power on / resume after suspend. (the status of the power adapter) gets updated correctly, while theīattery status (charging/ discharging), as found in > instantaneous when all was well the night before. > recognised - but it takes several seconds rather than being almost > Windows, lid closure still fails but power connect/disconnect still > Power connect/disconnect fails to be acted upon properly by Ubuntu. Next morning, lid closurefails to be recognised by Ubuntu. Then, in Ubuntu 12.04, I suspended the system > recognition in both Windows and Ubuntu 12.04 and suspend on lid closure. > Yesterday, after updating the BIOS I tested power connect/disconnect > After BIOS update all was well for 15hours only!Īlso for me, things worked well (both lid and power status) during theįirst weeks of life of the laptop (a Series 5 Ultrabook). UpgradeStatus: No upgrade log present (probably fresh install) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) "lshal -m" doesn't report anything when I plug the charger in or out. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. So the state is the only thing that is incorrect. ![]() The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. When booted with charger disconnected and charger is now connected:īattery #1 : discharging, 47.00%, 00:53:43 When booted with charger disconnected and charger is still disconnected:īattery #1 : discharging, 47.00%, 01:39:44 ![]() When booted with charger connected and charger is now disconnected: When booted with charger connected and charger is still connected: Here is output from "acpitool -a -b" in various situations: Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. ![]()
0 Comments
Leave a Reply. |