New post.

[homepage.git] / blog / data / 2013-07-17-new-laptop.txt

diff --git a/blog/data/2013-07-17-new-laptop.txt b/blog/data/2013-07-17-new-laptop.txt
index af5bdc24da3c18fafa748b0a3fa724e3f4d11e27..92d3d66bfecb9110026a14d31abf73350c36d93b 100644 (file)
--- a/blog/data/2013-07-17-new-laptop.txt
+++ b/blog/data/2013-07-17-new-laptop.txt
@@ -55,7 +55,7 @@ parameters are tuned:</p>
 <li>Tell swap to use TRIM commands by adding 'discard' to
     /etc/fstab.</li>
 
-<li>Change I/O scheduler from cfq to deadline.</li>
+<li>Change I/O scheduler from cfq to deadline using a udev rule.</li>
 
 <li>Run fstrim on every ext3 and ext4 file system every night (from
     cron.daily).</li>
@@ -95,8 +95,9 @@ have not yet had time to investigate those parts.</p>
 there.</p>
 
 <p>As for the answer to the question in the title of this blog post,
-as far as I know, the only solution is to replace the disk.  It might
-be possible to flash it with Intel firmware instead of the Lenovo
-firmware.  But I have not tried and did not want to do so without
-approval from Lenovo as I wanted to keep the warranty on the disk
-until a solution was found and they wanted the broken disks back.</p>
+as far as I know, the only solution I know about is to replace the
+disk.  It might be possible to flash it with Intel firmware instead of
+the Lenovo firmware.  But I have not tried and did not want to do so
+without approval from Lenovo as I wanted to keep the warranty on the
+disk until a solution was found and they wanted the broken disks
+back.</p>