Thanks to all for your help, I finally recompilled my kernel with the option High Memory set to 4GB.
Now the kernel sees all the memory. Thanks again! Jose El S�bado 03 Noviembre 2001 16:32, Rony Shapiro escribi�: > Hi, > > As people have written, you might want to add mem=1024M to the lilo.conf > file (don't forget to run lilo aferwards!). > > The kernel configuration option is: > > High Memory support > CONFIG_NOHIGHMEM > Linux can use up to 64 Gigabytes of physical memory on x86 systems. > However, the address space of 32-bit x86 processors is only 4 > Gigabytes large. That means that, if you have a large amount of > physical memory, not all of it can be "permanently mapped" by the > kernel. The physical memory that's not permanently mapped is called > "high memory". > > If you are compiling a kernel which will never run on a machine with > more than 1 Gigabyte total physical RAM, answer "off" here (default > choice and suitable for most users). This will result in a "3GB/1GB" > split: 3GB are mapped so that each process sees a 3GB virtual memory > space and the remaining part of the 4GB virtual memory space is used > by the kernel to permanently map as much physical memory as > possible. > > If the machine has between 1 and 4 Gigabytes physical RAM, then > answer "4GB" here. > > > From the Linux FAQ: > > > 1.8. Minimum and Maximum Memory Requirements. > At least 4MB, and then you will need to use special installation procedures > until the disk swap space is installed. Linux will run comfortably in 4MB > of RAM, although running GUI apps is impractically slow because they need > to swap out to disk. > > Some applications, like StarOffice, require 32 MB of physical memory, and > compiling C++ code can easily consume over 100 MB of combined physical and > virtual memory. > > There is a distribution, ``Small Linux,'' that will run on machines with > 2MB of RAM. Refer to the answer to: ``Where Are the Linux FTP Archives?'' > > A number of people have asked how to address more than 64 MB of memory, > which is the default upper limit in most standard kernels. Either type, at > the BOOT lilo: prompt: > > mem=XXM > > > > Or place the following in your /etc/lilo.conf file: > > append="mem=XXM" > > > > The parameter ``XXM'' is the amount of memory, specified as megabytes; for > example, ``128M.'' > > If an ``append='' directive with other configuration options already exists > in /etc/lilo.conf, then add the mem= directive to the end of the existing > argument, and separated from the previous arguments by a space; e.g.: > > # Example only; do not use. > append="parport=0x3bc,none serial=0x3f8,4 mem=XXM" > > > > Be sure to run the ``lilo'' command to install the new configuration. > > If Linux still doesn't recognize the extra memory, the kernel may need > additional configuration. Refer to the > /usr/src/linux/Documentation/memory.txt file in the kernel source as a > start. > > For further information about LILO, refer to the manual pages for lilo and > lilo.conf, the documentation in /usr/doc/lilo, and the answer for: > ``Boot-Time Configuration.'', below. > . > > From the Linux FAQ: > > 1.8. Minimum and Maximum Memory Requirements. > At least 4MB, and then you will need to use special installation procedures > until the disk swap space is installed. Linux will run comfortably in 4MB > of RAM, although running GUI apps is impractically slow because they need > to swap out to disk. > > Some applications, like StarOffice, require 32 MB of physical memory, and > compiling C++ code can easily consume over 100 MB of combined physical and > virtual memory. > > There is a distribution, ``Small Linux,'' that will run on machines with > 2MB of RAM. Refer to the answer to: ``Where Are the Linux FTP Archives?'' > > A number of people have asked how to address more than 64 MB of memory, > which is the default upper limit in most standard kernels. Either type, at > the BOOT lilo: prompt: > > mem=XXM > > > > Or place the following in your /etc/lilo.conf file: > > append="mem=XXM" > > > > The parameter ``XXM'' is the amount of memory, specified as megabytes; for > example, ``128M.'' > > If an ``append='' directive with other configuration options already exists > in /etc/lilo.conf, then add the mem= directive to the end of the existing > argument, and separated from the previous arguments by a space; e.g.: > > # Example only; do not use. > append="parport=0x3bc,none serial=0x3f8,4 mem=XXM" > > > > Be sure to run the ``lilo'' command to install the new configuration. > > If Linux still doesn't recognize the extra memory, the kernel may need > additional configuration. Refer to the > /usr/src/linux/Documentation/memory.txt file in the kernel source as a > start. > > For further information about LILO, refer to the manual pages for lilo and > lilo.conf, the documentation in /usr/doc/lilo, and the answer for: > ``Boot-Time Configuration.'', below. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jose Luis Vazquez > Gonzalez > Sent: Saturday, November 03, 2001 12:21 PM > To: Expert > Subject: [expert] Physical memory calculation in Linux > > > Hi, > > I would like to understand what is the calculation that Linux makes to say > how much memory does the system have as it is a lot less that the BIOS and > Windows says. I have just upgraded to 1GB (2x256 +1x512) and this are the > results: > > Win98 (only boots in failsafe mode, otherwise it reboots by itself) > ->1024MB RAM > > W2000 > -> 1048.028KB RAM > > BIOS > -> 1048576KB RAM (Memory test) > > Linux (it depens where you look) > From 896MB to 921MB > > I know 1 KB should be 1024 bytes , and 1MB should be 1024 x 1024, so 1GB is > 1024�= 1073741824 = 1048576K (so the BIOS seems right). > > 1) Is linux detecting problems in my memory and discounting the 'bad > memory' part? I haven't detected any error message. > 2) How is the calculation being made? > > Thanks in advance! > > Jose
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
