summaryrefslogtreecommitdiffstats
path: root/docs/install/t60_unbrick.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/install/t60_unbrick.html')
-rw-r--r--docs/install/t60_unbrick.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html
index d05078c..e92298b 100644
--- a/docs/install/t60_unbrick.html
+++ b/docs/install/t60_unbrick.html
@@ -26,7 +26,7 @@
Types of brick:
<ul>
<li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li>
- <li><a href="#recovery">Brick type 2: bad rom (or user error), machine won't boot</a></li>
+ <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li>
</ul>
</li>
</ul>
@@ -45,7 +45,7 @@
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/>
dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/>
dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/>
- (doing this makes the ROM suitable for use when flashing a machine that still has Lenovo BIOS running,
+ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running,
using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>.
(it says x60, but instructions for t60 are identical)
</p>
@@ -53,14 +53,14 @@
<div class="section">
- <h1 id="recovery">bad rom (or user error), machine won't boot</h1>
+ <h1 id="recovery">bad rom (or user error), system won't boot</h1>
<p>
- In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your machine from
- booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your machine is bricked and will not boot at all.
+ In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from
+ booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all.
</p>
<p>
- &quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the machine, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
+ &quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
</p>
<p>
@@ -156,7 +156,7 @@
<p>
Remove the shielding containing the motherboard, then flip it over. Remove these screws, placing them on a steady
surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the
- screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the machine:<br/>
+ screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the system:<br/>
<img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" />
<img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" />
</p>