From: Petter Reinholdtsen Date: Thu, 24 Sep 2015 19:33:41 +0000 (+0200) Subject: Generated. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/c6996136567a133cc3742f9846fed4e7d9cadc74?hp=58e496cad186593c9543ea474af4d38e383a5784 Generated. --- diff --git a/blog/The_life_and_death_of_a_laptop_battery.html b/blog/The_life_and_death_of_a_laptop_battery.html index 0e0e3086b0..d7eaa3183a 100644 --- a/blog/The_life_and_death_of_a_laptop_battery.html +++ b/blog/The_life_and_death_of_a_laptop_battery.html @@ -50,8 +50,8 @@ available in Debian.

battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:

+when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:

 #!/bin/sh
@@ -76,7 +76,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
 	for f in $files; do \
 	    printf "%s," $(cat $f); \
@@ -111,7 +111,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu

I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.

But why is this happening? Why are my laptop batteries always @@ -145,6 +145,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.

+ +

Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.

Tags: debian, english.
diff --git a/blog/archive/2015/09/09.rss b/blog/archive/2015/09/09.rss index 4d3f6ab26e..dae6543148 100644 --- a/blog/archive/2015/09/09.rss +++ b/blog/archive/2015/09/09.rss @@ -39,8 +39,8 @@ available in Debian.</p> battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:</p> +when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:</p> <pre> #!/bin/sh @@ -65,7 +65,7 @@ fi log_battery() { # Print complete message in one echo call, to avoid race condition - # when several log processes run in parallell. + # when several log processes run in parallel. msg=$(printf "%s," $(date +%s); \ for f in $files; do \ printf "%s," $(cat $f); \ @@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu </pre> <p>I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.</p> <p>But why is this happening? Why are my laptop batteries always @@ -134,6 +134,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.</p> + +<p>Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.</p> diff --git a/blog/archive/2015/09/index.html b/blog/archive/2015/09/index.html index 3200288c01..c153975f8d 100644 --- a/blog/archive/2015/09/index.html +++ b/blog/archive/2015/09/index.html @@ -57,8 +57,8 @@ available in Debian.

battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:

+when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:

 #!/bin/sh
@@ -83,7 +83,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
 	for f in $files; do \
 	    printf "%s," $(cat $f); \
@@ -118,7 +118,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu

I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.

But why is this happening? Why are my laptop batteries always @@ -153,6 +153,14 @@ to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.

+

Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.

+
diff --git a/blog/index.html b/blog/index.html index 476598e320..51aa92a415 100644 --- a/blog/index.html +++ b/blog/index.html @@ -50,8 +50,8 @@ available in Debian.

battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:

+when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:

 #!/bin/sh
@@ -76,7 +76,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
 	for f in $files; do \
 	    printf "%s," $(cat $f); \
@@ -111,7 +111,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu

I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.

But why is this happening? Why are my laptop batteries always @@ -145,6 +145,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.

+ +

Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.

diff --git a/blog/index.rss b/blog/index.rss index e9e3a29be8..ccbf39e425 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -39,8 +39,8 @@ available in Debian.</p> battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:</p> +when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:</p> <pre> #!/bin/sh @@ -65,7 +65,7 @@ fi log_battery() { # Print complete message in one echo call, to avoid race condition - # when several log processes run in parallell. + # when several log processes run in parallel. msg=$(printf "%s," $(date +%s); \ for f in $files; do \ printf "%s," $(cat $f); \ @@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu </pre> <p>I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.</p> <p>But why is this happening? Why are my laptop batteries always @@ -134,6 +134,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.</p> + +<p>Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.</p> diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index b9e70406da..71c98d4e1a 100644 --- a/blog/tags/debian/debian.rss +++ b/blog/tags/debian/debian.rss @@ -39,8 +39,8 @@ available in Debian.</p> battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:</p> +when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:</p> <pre> #!/bin/sh @@ -65,7 +65,7 @@ fi log_battery() { # Print complete message in one echo call, to avoid race condition - # when several log processes run in parallell. + # when several log processes run in parallel. msg=$(printf "%s," $(date +%s); \ for f in $files; do \ printf "%s," $(cat $f); \ @@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu </pre> <p>I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.</p> <p>But why is this happening? Why are my laptop batteries always @@ -134,6 +134,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.</p> + +<p>Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.</p> diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index 268a5bfd6b..77da79ed85 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -56,8 +56,8 @@ available in Debian.

battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:

+when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:

 #!/bin/sh
@@ -82,7 +82,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
 	for f in $files; do \
 	    printf "%s," $(cat $f); \
@@ -117,7 +117,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu

I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.

But why is this happening? Why are my laptop batteries always @@ -152,6 +152,14 @@ to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.

+

Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.

+
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index a2fb0d3312..85d697331b 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -39,8 +39,8 @@ available in Debian.</p> battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:</p> +when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:</p> <pre> #!/bin/sh @@ -65,7 +65,7 @@ fi log_battery() { # Print complete message in one echo call, to avoid race condition - # when several log processes run in parallell. + # when several log processes run in parallel. msg=$(printf "%s," $(date +%s); \ for f in $files; do \ printf "%s," $(cat $f); \ @@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu </pre> <p>I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.</p> <p>But why is this happening? Why are my laptop batteries always @@ -134,6 +134,14 @@ speed change over time, or if this stay the same. I did not yet try to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.</p> + +<p>Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.</p> diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 48fb45b750..e5f74e794a 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -56,8 +56,8 @@ available in Debian.

battery stats ever since. Now my /var/log/hjemmenett-battery-status.log file contain around 115,000 measurements, from the time the battery was working great until now, -when it is unable to charge above 7% of original capasity. My -colletor shell script is quite simple and look like this:

+when it is unable to charge above 7% of original capacity. My +collector shell script is quite simple and look like this:

 #!/bin/sh
@@ -82,7 +82,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
 	for f in $files; do \
 	    printf "%s," $(cat $f); \
@@ -117,7 +117,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu

I wrote a small script to create a graph of the charge development -over time. This graph depicted above show the slow death of mylaptop +over time. This graph depicted above show the slow death of my laptop battery.

But why is this happening? Why are my laptop batteries always @@ -152,6 +152,14 @@ to write a tool to calculate the derivative values of the battery level, but suspect some interesting insights might be learned from those.

+

Update 2015-09-24: I got a top to install the packages +acpi-call-dkms and tlp (unfortunately missing in Debian stable) +packages instead of the tp-smapi-dkms package I had tried to use +initially, and use 'tlp setcharge 40 80' to change when charging start +and stop. I've done so now, but expect my existing battery is toast +and need to be replaced. The proposal is unfortunately Thinkpad +specific.

+