Generated.

[homepage.git] / blog / archive / 2013 / 06 / 06.rss

diff --git a/blog/archive/2013/06/06.rss b/blog/archive/2013/06/06.rss
index 2a53f3f222e498ba71b0535b6dad00ba834070c0..630638ad8f4d11f21c24c5c78f6d65c6cd2ed6b1 100644 (file)
--- a/blog/archive/2013/06/06.rss
+++ b/blog/archive/2013/06/06.rss
@@ -50,7 +50,7 @@ info: did not find any firmware files requested by loaded kernel modules.  exiti
 </pre></p>
 
 <p>It could use some polish, but it is already working well and saving
-me for time when setting up new machines. :)</p>
+me some time when setting up new machines. :)</p>
 
 <p>So, how does it work?  It look at the set of currently loaded
 kernel modules, and look up each one of them using modinfo, to find
@@ -94,7 +94,7 @@ suite, I discovered that we had forgotten to adjust our PXE setup to
 cope with the new names and paths used by the netboot d-i packages.
 When Internet connectivity was available, the installer fall back to
 using wget to fetch d-i boot images, but when offline it require
-working packages to get it working.  And ad the packages changed name
+working packages to get it working.  And the packages changed name
 from debian-installer-6.0-netboot-$arch to
 debian-installer-7.0-netboot-$arch, we no longer pulled in the
 packages during installation.  Without our test suite, I suspect we
@@ -480,6 +480,12 @@ developers did to handle this, and this can give a clue to the KDE
 developers?  Or you know where in KDE the screen brightness is changed
 during login?  If so, please update the BTS report (or get in touch if
 you do not know how to update BTS).</p>
+
+<p>Update 2013-07-19: The correct fix for this machine seem to be
+acpi_backlight=vendor, to disable ACPI backlight support completely,
+as the ACPI information on the machine is trash and it is better to
+leave it to the intel video driver to control the screen
+backlight.</p>
 </description>
        </item>