summaryrefslogtreecommitdiff
path: root/en/preparing
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-12-25 20:08:46 +0000
committerFrans Pop <elendil@planet.nl>2006-12-25 20:08:46 +0000
commit7b45786a24ade38b26b02b5c0ce612a890d10b50 (patch)
treeb90cb7f5143bfadcd464a8b0550c651ebe67b94e /en/preparing
parent62110794711177d6581d5bf3f81cb41c2d74d6c3 (diff)
downloadinstallation-guide-7b45786a24ade38b26b02b5c0ce612a890d10b50.zip
-Fix broken closing tag
- Remove references to deleted sections
Diffstat (limited to 'en/preparing')
-rw-r--r--en/preparing/pre-install-bios-setup.xml11
1 files changed, 0 insertions, 11 deletions
diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 03be8cd7b..224b66f8f 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -56,17 +56,6 @@ FIXME: more description of this needed.
</para><para arch="x86">
-The very best motherboards support parity RAM and will actually tell
-you if your system has a single-bit error in RAM. Unfortunately, they
-don't have a way to fix the error, thus they generally crash
-immediately after they tell you about the bad RAM. Still, it's better
-to be told you have bad memory than to have it silently insert errors
-in your data. Thus, the best systems have motherboards that support
-parity and true-parity memory modules; see
-<xref linkend="Parity-RAM"/>.
-
-</para><para arch="x86">
-
If you do have true-parity RAM and your motherboard can handle it, be
sure to enable any BIOS settings that cause the motherboard to
interrupt on memory parity errors.