You are not logged in.
Pages: 1
Hi,
I've upgraded RAM on my notebook (Intel GM965) from 1G to 2G. BIOS does see it, but the system apparently isn't quite certain:
$ ls -lh /proc/kcore
-r-------- 1 root root 888M Apr 11 20:23 /proc/kcore
$ free
total used free shared buffers cached
Mem: 2065668 803260 1262408 0 44824 466880
-/+ buffers/cache: 291556 1774112
Swap: 4457996 0 4457996
Arch i686, stock kernel 2.6.31.
Why is /proc/kcore file shorter than it should be?
Offline
It's ... (:O ) 128 Terabytes here
~ $ ls -lh /proc/kcore
-r-------- 1 root root 128T Apr 11 19:56 /proc/kcore
What's this for ? (kcore) ?
Offline
What's this for ? (kcore) ?
Everything is a file, unless it's a process . In Linux kcore file represents RAM, so it's size should be equal to RAM size.
Offline
My kcore file is less than a third the size of my RAM. Both free and Gnome system monitor show the correct amount.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Give this a try
du /proc/kcore --block-size=1M
that should read it correctly
Certified Android Junkie
Arch 64
Offline
For a better indication of memory, try 'cat /proc/meminfo'. You should recognize some of the numbers as the same as those reported by top or htop.
Finding anything not over my head about the process file system (procfs) is difficult. There's a few complaints on the interweb that the proc manpage is inaccurate about /proc/kcore – kcore's size is no longer "the size of physical memory (RAM) plus 4KB." I wonder if 64-bit kernels have 'ls -l' always report the size of kcore as 128T. That's how my system reports it.
Offline
Pages: 1