Sponsored Content
Operating Systems Linux Red Hat red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb Post 302272829 by reborg on Thursday 1st of January 2009 07:18:01 AM
Old 01-01-2009
A 32 bit OS cannot natively address 16GB of RAM. You are simply seeing the amount of memory your OS can address. You will have to use the 64 it OS to see the full 16 GB.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How much RAM does RH Linux need?

I wish to install Red Hat linux 7.1 on a machine with 16mb of EDO Ram. When I enter the instalation process I am told 'You do not have enough memory'. Is there a way to install RHL with only the 16? Or will I have to upgrade and buy some very expensive EDO. ~ Paul (3 Replies)
Discussion started by: KrazyGuyPaul
3 Replies

2. Debian

what is the best linux ver for p100 16 ram

Hello all i own p100 16ram laptop , i would like to run linux on it i need it for gcc compilation and shell scripting , no gui. what version of linux should i install , i dont mind to install old one . tnx allot (5 Replies)
Discussion started by: umen
5 Replies

3. Solaris

getting available physical RAM

What command should I be using on Solaris 9 to get an accurate representation of the available physical RAM? (4 Replies)
Discussion started by: dangral
4 Replies

4. Shell Programming and Scripting

To find the RAM size for an Linux server.

Hi Gurus, Can someone let me know how to find the RAM size,ROM size and Number of processors for a linux server. Version :Linux 2.4.9-e.57smp Also what does "e.57smp" stands for? Thanks in advance gurus..... cheers. (3 Replies)
Discussion started by: navojit dutta
3 Replies

5. Solaris

RAM Physical Memory usage by each Process.

Hi All, I am trying to find the physical memory usage by each process/users. Can you please let me know how to get the memory usage?. Thanks, bsraj. (12 Replies)
Discussion started by: bsrajirs
12 Replies

6. Solaris

Solaris sun4v - how do you determine physical RAM?

I have a Sun T5120, and I want to programmatically determine how much RAM it has. # uname -a SunOS myhost 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5120 The box has 64Gb; I tried prtdiag and prtconf, but they give me bogus info prtconf gives me: # prtconf |grep -i... (12 Replies)
Discussion started by: thomn8r
12 Replies

7. Cybersecurity

root cannot write to Linux RAM

void main() { long ((long)(&array)); int x; for (;;) { (array) =+ 1023; printf("%c", array); } } What is wrong with this code to print Linux RAM? (13 Replies)
Discussion started by: Alux
13 Replies

8. Red Hat

Physical RAM

Hi, I have a server (BL460c) with 32G of physical RAM. It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications. If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies

9. Solaris

ZFS : Can arc size value exceed Physical RAM ?

Hi, kstat -p -m zfs -n arcstats -s size returns zfs:0:arcstats:size 8177310584 this values is approx (7.61 GB) but my Physical Memory size is only 6144 Megabytes. Can this happen ? if yes, then how can I find free memory on the system. BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies

10. Red Hat

Linux Red Hat AS3 Network card is not detecting ...

Dear Expert, I 've installed Redhat linux AS3, My machine having Inbuild network card (Intel(R) 82566DM-2 Gigabit Network Connection). I've downloaded e1000e-2.3.2 from Intel site, but its not working for my machine. I'm unable to configure the Network. ifconfig eth0 xx.xx.xx.xx netmask... (0 Replies)
Discussion started by: Mohammed Faiz
0 Replies
PAE(4)							 BSD/i386 Kernel Interfaces Manual						    PAE(4)

NAME
PAE -- Physical Address Extensions SYNOPSIS
options PAE DESCRIPTION
The PAE option provides support for the physical address extensions capability of the Intel Pentium Pro and above CPUs, and allows for up to 64 gigabytes of memory to be used in systems capable of supporting it. With the PAE option, memory above 4 gigabytes is simply added to the general page pool. The system makes no distinction between memory above or below 4 gigabytes, and no specific facility is provided for a process or the kernel to access more memory than they would otherwise be able to access, through a sliding window or otherwise. SEE ALSO
smp(4), tuning(7), config(8), bus_dma(9) HISTORY
The PAE option first appeared in FreeBSD 4.9 and FreeBSD 5.1. AUTHORS
Jake Burkholder <jake@FreeBSD.org> BUGS
Since KLD modules are not compiled with the same options headers that the kernel is compiled with, they must not be loaded into a kernel com- piled with the PAE option. Many devices or their device drivers are not capable of direct memory access to physical addresses above 4 gigabytes. In order to make use of direct memory access IO in a system with more than 4 gigabytes of memory when the PAE option is used, these drivers must use a facility for remapping or substituting physical memory which is not accessible to the device. One such facility is provided by the busdma interface. Device drivers which do not account for such devices will not work reliably in a system with more than 4 gigabytes of memory when the PAE option is used, and may cause data corruption. The PAE kernel configuration file includes the PAE option, and explicitly excludes all device drivers which are known to not work or have not been tested in a system with the PAE option and more than 4 gigabytes of memory. Many parameters which determine how memory is used in the kernel are based on the amount of physical memory. The formulas used to determine the values of these parameters for specific memory configurations may not take into account the fact there may be more than 4 gigabytes of memory, and may not scale well to these memory configurations. In particular, it may be necessary to increase the amount of virtual address space available to the kernel, or to reduce the amount of a specific resource that is heavily used, in order to avoid running out of virtual address space. The KVA_PAGES option may be used to increase the kernel virtual address space, and the kern.maxvnodes sysctl(8) may be used to decrease the number of vnodes allowed, an example of a resource that the kernel is likely to overallocate in large memory configurations. For optimal performance and stability it may be necessary to consult the tuning(7) manual page, and make adjustments to the parameters docu- mented there. BSD
April 8, 2003 BSD
All times are GMT -4. The time now is 05:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy