Ubuntu :: 10.04 : Sudden Shutdown When Battery At 43% Level?
Jan 17, 2011
I run Ubuntu 10.04 on a HP dv2000 laptop with 2GB RAM. I see a strange problem with my system. When running on battery and the level hits about 43% (+- 1%), the system shuts down suddenly. No warning and no information in logs either. Temperature of both cores are below 50 C. I have tried cleaning the dust withing the laptop chasis but no progress.
I have done quite some research on this and other forums but haven't found anybody else with similar problem.
How can I adjust the levels at which the battery is considered to be critically low?ight now it seems this is set at 5 or 10%. I want to make it 20 or 25%This is for Gnome. I am using Lucid x86
Is there any USB mouse battery indicators for Ubuntu that can tell me the battery level of my Logitech USB mouse? (something like a laptop battery one) I want to add it the panel.
I just did a clean reinstall of Ubuntu (10.04 --> 10.10). After the install, any time I do CPU intensive work, my PC is suddenly shutting down like it's overheating. Everything was working fine for months, and started having problems immediately after the reinstall. so this is not a problem with my hardware, and it's not a problem with my fans needing cleaning -- it's a problem with software. So please don't tell me "that sounds like overheating, clean your fans". Something is different in software-land between 10.04 and 10.10 that is causing this to happen.
I have checked my log files, and can't find anything related to overheating -- searches for things related to lm_sensors, "temp", and "thermal" are not turning up anything in the system logs (syslog, kern.log, or messages). I also looked at the logs around the times of the sudden shutdown, and couldn't find anything unusual. How can I diagnose this? I'd like to file a bug report, but since I can't find anything in the logs, I honestly have no idea how to go about providing useful information. Is there anything besides overheating that might be causing my laptop to suddenly shut off? (I am using a Gateway M-6888u laptop, btw)
I have an user space application that performs file I/O operations, when a SIGKILL is captured, some routines are done first to ensure that all I/O operations are completed before rebooting the application or system. My question is, this won't work if the power button is pressed or the power supply is disconnected, so there can be incomplete I/O operation or corrupted data written into the file, so is there a way to prevent data corruption or at least complete any ongoing operation when this scenario happens? Assuming there is at most 1 second before the power really went out, can I/O be still completed?' I'm running the application on a busybox 2.6.14 kernel on an embedded system board.
I have an Archos Vision A15VS mp3 player which I am recharging through the usb connection of my laptop. Unfortunately, as far as I can see, there is no way of checking the battery state during the process as the screen of the player only shows a usb icon when the lead is connected.
This means that I don't have a visual confirmation that the battery is actually charging!
Obviously I could simply unmount the device, check the microscopic battery icon on the screen, and if not showing "full" repeat the process.
I have installed Fedora 14 LXDE in my netbook (HP 210 mini) and all works fine.I have only one isse, the battery level is not showed in the panel.What I shoud to install or configure to have the battery level on desktop ?
I just did a clean reinstall of Ubuntu (10.04 --> 10.10). After the install, any time I do CPU intensive work, my PC is suddenly shutting down like it's overheating.Everything was working fine for months, and started having problems immediately after the reinstall. so this is not a problem with my hardware, and it's not a problem with my fans needing cleaning -- it's a problem with software. So please don't tell me "that sounds like overheating, clean your fans". Something is different in software-land between 10.04 and 10.10 that is causing this to happen -- I assure you that the upgrade did not magically fill my fans with cat hair.
I have checked my log files, and can't find anything related to overheating -- searches for things related to lm_sensors, "temp", and "thermal" are not turning up anything in the system logs (syslog, kern.log, or messages). I also looked at the logs around the times of the sudden shutdown, and couldn't find anything unusual.How can I diagnose this? I'd like to file a bug report, but since I can't find anything in the logs, I honestly have no idea how to go about providing useful information.Is there anything besides overheating that might be causing my laptop to suddenly shut off?
I have searched every now and then (every time the batteries act up) to find a way to get the battery level from my keyboard and mouse. It seems like the most basic thing, but it also seems unsolved in all the threads I have found.
Mouse: Microsoft Intellimouse Explorer 2.0 [Model:1007] Keyboard: Microsoft Wireless Photo Keyboard [Model:1027] Ubuntu 9.10 Kernel 2.6.31-22-generic Gnome 2.28.1
I recently purchased a UPS (Tripp-lite Internet 550U)to shutdown my PC during a power outage when unattended. This model of UPS is connected to the PC with USB. Upon plugging in the UPS USB cable the Gnome Power Manager started up and it appears to correctly show the condition of the UPS. During a power outage it showed battery discharge right down to the battery going critical, but never shutdown the PC. I have set the options in the power manager for low & critical battery shutdow. Seems something is blocking the Gnome Power Manager from shutting down, but I have no idea where to start looking..
PC: Abit mobo with Phoenix bios Ubuntu 8.04 UPS: Trtipp-Lite Internet 550U
I have looked all over the place but I can't find if this is possible. I am running Debian 6 as a media server (SMB) and it is tied to a UPS, I used gnome power management to set up a low battery shutdown but this UPS also is powering another embedded computer. So, I was wondering if it was possible to have a script run (to log in and shut down the embedded system) before gnome power management shuts down the Debian server. I know I could probably get it to run on every shutdown, but I am looking for low power only.
is there a way to configure shutdown on critically low battery to give me a bit of time before actually shutting down?I've set Gnome to shutdown on low battery. Problem is, I don't get any notification about battery running low, and as soon as battery level reaches the critical threshold, the system starts shutdown without me having any possibility to quickly complete some tasks. Of course, I'd increase battery level thresholds accordingly.
Broadcom 4312, dell inspiron 1545.Earlier i was running on battery power and the laptop shut down when the battery got low. When i got back to it and restarted there was no wireless network. It's grayed out and says wireless disabled. How do i fix this?
I'm trying to make my system automatically shutdown once the battery level is low, but still without success. I've tried kpowersave, gnome-power-manager, kpower, klaptop but none of these worked for me. Well, I can't imagine I would be that stupid, but simply it doesn't work. In all cases mentioned above (kpower, klaptop, gnome-power-manager) I've tried to setup the laptop to shutdown once the defined level is reached, but the laptop never actually switched off unless all the battery was drained.
Btw. I think all the above mentioned apps only work once the user is logged in. But I'd like the solution to work also when the PC is on without anyone logged in. I thought I could write a bash script based on parsing of acpitools output and define it as a service, which would monitor the battery level, but I simply don't believe there isn't any functional solution to this.
I'm trying to make the power manager NOT automatically shutdown / sleep / hibernate when battery power of my laptop reaches critical
I am surprised there isnt an 'NO ACTION' option for that in power manager
I've tried editing the acpi-supper in /etc/default bu couldn't find a solution in there nor in the /home/user/.gconf/apps/gnome-power-manager/ directory
I've been able to kludge a kill script which finds the correct pid for the kdeserver (or gnome server) after my system comes up in run level 5 so I can drop back to run level 3 mode. Lots of experimentation showed me that using telinit 3 and telinit 5 would occasionally leave the video memory in a mess and I would have the black screen of death.
I set the security parameter setting to autologin for me since I am the only user of my machine, but I still have to kludge the default setting under sysconfig (the DEFAULT_WM) under Window Manager to pick a certain window manager, so it takes time to manually switch the desktop.
Right now I can leave the gui and drop back to cli, but painful experimenting showed me that killing the X server is a no no. Right now I kill the kde server, which sends the SIGTERM to the X windows manager, which then figures out that it has to shut down.
Questions: Is there a better way of doing this? Apparently openSUSE figures that we have multiple users logging into the gui desktop, so the gui is always kept running and a login window with the desktop manager option forces the user to login in. With autologin, this never happens, but no choice of desktop is possible on the fly.
Can some type of script be set up to painlessly enable this to happen? And what is the best way of bringing either the Gnome or KDE desktop manager down gracefully? I do get lots of error messages as the system attempts to recover and X shuts down. It appears that apparently the single user with autologin is left out in the cold.
I want to install a software called TinyOS which is an operating system designed for wireless sensor embedded networks in my account. The problem is it has instructions to install the software as an administrator since i'm not an admin of the department network i can not able to install. Is there any method to install this software as an user level rather than admin level.
Just installed 9.10 followed by a 10.04 upgrade (wouldn't work as a 10.04 clean install). The install and upgrade all seemed to go well.
But now when booting I get a message saying "checking battery state" and then it boots no further. This is a laptop without a battery installed, running permanently from the mains through the charger.
How can I disable this check so that the laptop will still boot without a battery fitted?
hello everyone, im having a problem when my computer enters in the run level 4 as the default when i start slackware. The strange thing is that it not seems that is a X window problem, it looks like more like a configuration problem in some part of the kde script to initialize the log in, because if i manually start the X service it works fine, i dont know what is the source. Thank you in advance for the help.
I want to know what are the advantages and disadvantages for accessing spi(serial peripheral inerface )from kernel level and user level. like methods of doing it, speed ,memeory utilization etc
getting back to our laptop, the stability window is ~3.2V. Meaning that when you operate the battery above this the electrolyte is oxidized on the positive electrode and reduced on the negative electrode. Remember that we only want to oxidize and reduce the active materials and don't want to do anything else. All these reactions other than the ones we want are called side reactions and these are really bad for the battery. The nominal voltage of a laptop battery is 3.7 V which means that something bad wants to happen as we use the battery.So long story short, stuff (e.g., passive layers and poor kinetics of reactions) happens and things are not as bad as they seem and you can increase the voltage up to 4.2V without bad things really happening. All chargers for Li-ion cells today cut the battery off when it reaches 4.2V. What you have to realize is that at 4.2V, these side reactions are present in finite amounts and start to chemically kill the battery, but its not that dramatic.
Operating to 4.1V makes things better and extends the life, 4.0 V is even better and so on. So why don't battery manufacturers cut the voltage off at, say, 4 V to get better battery life? Because every time you cut this voltage down you decrease the capacity of the battery and its run time. The 4.2V cutoff is a compromise between good run time and decent (read "not pathetic) life.On the other hand, if you charge the battery and then pull the plug (so to speak), the battery discharges some, the voltage drops, and these reactions become less of a problem and your battery life goes up. So the best things you can do is to charge the laptop (or cell phone, camera etc.) and once its charged, pull the plug. Your battery will thank you for it.As a matter of fact, if you own a Lenovo Thinkpad, you can actually change the state of charge to which you charge the battery using the Battery Maintenance utility. You can change this from charging to 100% state (where the voltage is 4.2V) to 90% so that your voltage is less. You lose some energy is doing that, but atleast you can change it to 100% when you need battery power and put it back down to 90% when you can plug in. I wish my Mac has the same feature.
I typically use the battery for a while (say 1/2 hour to 1 hour), then plug it in and wait to fully charge it, then I pull the plug and use it again for 1/2 hour to 1h and then I repeat this. Takes some getting used to and I forget to do this, but I try.
you can find a cutout of an output generated by "iwlist s" command for a cell. Does anybody know what Quality, Signal level and Noise level mean? What is the definition of them? I searched for it and could not find good information on it. What do these Extra:*** fields for? What does it show in the example above? How were those values computed?
I am running F10 x86_64 with Nvidia Quadro FX 3400. I installed the drivers and it worked just fine. No errors generated according to Nvidia log files. However, while in run level 5 when I try to switch to run level 3 by typing "telinit 3" or "init 3" the X server goes down and I get a blank screen. Same thing happens when I try to switch to a different tty session by <ctrl>+<alt>+F2 (or any F key for that matter). I also noticed that when I shut down my system I can't see any more the screen where services are shutting down and their status ([OK] or [failed]).
Hey Guys, I'am new here and request your help on this: After installing emacs and a few dependencies on my RHEL 5, on restarting the system, the keyboard was not able to work. I restarted several times in vein.
However, when I start in single mode, it works perfectly. I have tried looking for a solution from google, but in vein.
I have a 3 year old laptop with the original battery and its drained pretty bad. The "Battery may be broken" popup was driving me insane and this is how you disable it, in case you are in the same situation as me. Open terminal
Code: gconf-editor Drill down to... apps --> gnome-power-manager --> notify
uncheck the low_capacity checkbox. This should disable the popup for you if your battery has little life left in it. Now, if any knows how to disable the Avahi popup, let me know.
I have a directory that has a another directory inside it. The top directory is rather redundant since it only contains the one other one. Is there a way to delete the top level directory and have the contents simply "move up a level"?
I have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
I just upgraded to the 10.04 and everything works just fine as before (except for skype but that really doesn't matters as it has already been 3 years I'm using ubuntu and I managed to get it to work only once, for miracle I believe ^^). The only real issue I have is this: when I start up my laptop, after the log-in, no sound will be heared as the "speaker" volume level in alsamixer is set to 0; if I raise it from the terminal running alsamixer (as I don't know any other alternative) everything plays just fine, but the next time I boot I do have to do it all over again... So, how can I change the default startup level of the "speaker" in alsamixer?
PS: by the way I do have the very same issue with the screen luminosity but the other way round as is always starts at maximum brightness and I can't manage to get it to start at the minimum, as it did before. At least reducing the backlight if far more quick but a couple of times I forget it and the battery lasted something like half an hour
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
