diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index 9fc8d707d9..cfe647a842 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -3140,36 +3140,6 @@ quit</programlisting> </answer> </qandaentry> - <qandaentry> - <question id="reallybigram"> - <para>Why does &os; only use 64 MB of RAM when my system - has 128 MB of RAM installed?</para> - </question> - - <answer> - <para>Due to the manner in which &os; gets the memory size - from the BIOS, it can only detect 16 bits worth of - Kbytes in size (65535 Kbytes = 64 MB) (or less... - some BIOSes peg the memory size to 16 MB). If you have - more than 64 MB, &os; will attempt to detect it; - however, the attempt may fail.</para> - - <para>To work around this problem, you need to use the kernel - option specified below. There is a way to get complete - memory information from the BIOS, but we do not have room in - the bootblocks to do it. Someday when lack of room in the - bootblocks is fixed, we will use the extended BIOS functions - to get the full memory information... but for now we are - stuck with the kernel option.</para> - - <programlisting>options MAXMEM=<replaceable>n</replaceable></programlisting> - - <para>Where <replaceable>n</replaceable> is your memory in - Kilobytes. For a 128 MB machine, you would want to use - <literal>131072</literal>.</para> - </answer> - </qandaentry> - <qandaentry> <question id="kmem-map-too-small"> <para>My system has more than 1 GB of RAM, and I'm