Re: memory recognition
I installed the bigmem kernel ( 2.6.24-1-686 ). Thought this is the same kernel version that my system has been running on, when I try to boot to the bigmem kernel, the boot process creeps along at an incredibly slow rate and appears to hang during dev assignment / configuration, though it seems that if I would have left it going for a half an hour it might have made it further. My question is simple. Am I naive to think that the bigmem version of the same kernel version would be similar enough to the standard kernel to have no issues with my hardware? On Fri, May 2, 2008 at 2:56 PM, | Dominique H. Schramm (ML) | < [EMAIL PROTECTED]> wrote: > Hi, > > ChadDavis schrieb: > > > I have 8gb of memory, bios sees it. Lenny only sees 3.2 gb. > > Is there a different version of the kernel or parameter to make it see > > all of my memory? > > > > If you compile your kernel by hand, look at menuconfig for > CONFIG_HIGHMEM64G > > -- > > Viele Grüße > > Dominique H. Schramm| Linux Administrator > schwarz-weiss.cc| Life between PuTTy and reality > ihr-linuxadmin.eu | Commercial Admin Service > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a > subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: memory recognition
Hi, ChadDavis schrieb: I have 8gb of memory, bios sees it. Lenny only sees 3.2 gb. Is there a different version of the kernel or parameter to make it see all of my memory? If you compile your kernel by hand, look at menuconfig for CONFIG_HIGHMEM64G -- Viele Grüße Dominique H. Schramm| Linux Administrator schwarz-weiss.cc| Life between PuTTy and reality ihr-linuxadmin.eu | Commercial Admin Service -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: memory recognition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/02/08 15:34, ChadDavis wrote: > I have 8gb of memory, bios sees it. Lenny only sees 3.2 gb. > > Is there a different version of the kernel or parameter to make it see > all of my memory? Yes. $ apt-cache search bigmem | grep ^linux | sort - -- Ron Johnson, Jr. Jefferson LA USA We want... a Shrubbery!! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIG32pS9HxQb37XmcRAoJoAJ9k2r0WVmvjV/kfzBtr+t35oTgBTgCeJzeh HGYxp+foLHhUurxmGNcPHyg= =x46y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
memory recognition
I have 8gb of memory, bios sees it. Lenny only sees 3.2 gb. Is there a different version of the kernel or parameter to make it see all of my memory?
Re: Memory recognition problem / large mem
dman posts :
> | even more interesting...
> | the 2.2.20 kernel reports:
> | total:used:free: shared: buffers: cached:
> | Mem: 994078720 42676224 951402496 10178560 8065024 21536768
> | MemTotal:970780 kB
>
> use 'free -m' to see smaller (easier to read) numbers.
>
The command `vmstat' reports virtual memory statistics on a sampling
sort of method.
--
/(__ __|\ ragOO, VU2RGU<->http://gnuhead.dyndns.org/<->GPG: 1024D/F1624A6E
(\/ __)_ Helping to keep the Air-Waves FREE Amateur Radio
) (_ / Helping to keep your Software FREE the GNU Project
/___/ Helping to keep the W W W FREE Debian GNU/${kernel}
Re: Memory recognition problem / large mem
--begin quoted message from dman, > On Sat, Jan 19, 2002 at 01:54:04PM -0500, Noah Massey wrote: > | --begin quoted message from dman, > > | > On my system I have 256MB real RAM. > | > > | > It shows a total of only 249MB. dmesg shows : > | > > | > $ dmesg | grep Memory > | > Memory: 255676k/262080k available (k kernel code, 6016k reserved, > | > 300k data, 228k init, 0k highmem) > | > | 2.4.16-k7 shows: > | Memory: 897676k/917504k available (815k kernel code, 19440k reserved, 233k > data, 212k init, 0k highmem) > | > | 2.2.20 shows: > | Memory: 970628k/983040k available (1756k kernel code, 412k reserved, 10092k > data, 152k init) > | > | neither of which is the 1048576k that I'd expect. > | > | given that each kernel consistently shows the same amount of mem, and > | that they disagree with each other on what that amount is, does this > | look like a kernel bug? or is there something that I'm just not doing? > > I just went back to the manual > (/usr/src/kernel-source-2.4.17/Documentation/Configure.help) and I > this must be your problem. Kernel 2.2.20 gives exactly 960MB for you. I > don't know why 2.4.16 shows a little less. duh! that's the something that I'm just not doing. re-compiling kernel now. Thanks a bundle. > # Choice: himem > High Memory support > CONFIG_NOHIGHMEM > > If you are compiling a kernel which will never run on a machine with > more than 960 megabytes of 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. > > If more than 4 Gigabytes is used then answer "64GB" here. This > selection turns Intel PAE (Physical Address Extension) mode on. > PAE implements 3-level paging on IA32 processors. PAE is fully > supported by Linux, PAE mode is implemented on all recent Intel > processors (Pentium Pro and better). NOTE: If you say "64GB" here, > then the kernel will not boot on CPUs that don't support PAE! > > The actual amount of total physical memory will either be auto > detected or can be forced by using a kernel command line option such > as "mem=256M". (Try "man bootparam" or see the documentation of your > boot loader (grub, lilo or loadlin) about how to pass options to the > kernel at boot time.) > > If unsure, say "off". -- Noah Massey | fingerprint : 90AD 7AAB 0768 46AF 8C52 0695 03A2 C74D E1ED C2BF The goal of Computer Science is to build something that will last at least until we've finished building it. Attached is a digital signature which can be used to authenticate this email. For details consult www.gnupg.org or www.pgpi.org pgpwQBgjbsQ5d.pgp Description: PGP signature
Re: Memory recognition problem / large mem
On Sat, Jan 19, 2002 at 01:54:04PM -0500, Noah Massey wrote: | --begin quoted message from dman, | > On my system I have 256MB real RAM. | > | > It shows a total of only 249MB. dmesg shows : | > | > $ dmesg | grep Memory | > Memory: 255676k/262080k available (k kernel code, 6016k reserved, | > 300k data, 228k init, 0k highmem) | | 2.4.16-k7 shows: | Memory: 897676k/917504k available (815k kernel code, 19440k reserved, 233k data, 212k init, 0k highmem) | | 2.2.20 shows: | Memory: 970628k/983040k available (1756k kernel code, 412k reserved, 10092k data, 152k init) | | neither of which is the 1048576k that I'd expect. | | given that each kernel consistently shows the same amount of mem, and | that they disagree with each other on what that amount is, does this | look like a kernel bug? or is there something that I'm just not doing? I just went back to the manual (/usr/src/kernel-source-2.4.17/Documentation/Configure.help) and I this must be your problem. Kernel 2.2.20 gives exactly 960MB for you. I don't know why 2.4.16 shows a little less. # Choice: himem 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 960 megabytes of 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. If more than 4 Gigabytes is used then answer "64GB" here. This selection turns Intel PAE (Physical Address Extension) mode on. PAE implements 3-level paging on IA32 processors. PAE is fully supported by Linux, PAE mode is implemented on all recent Intel processors (Pentium Pro and better). NOTE: If you say "64GB" here, then the kernel will not boot on CPUs that don't support PAE! The actual amount of total physical memory will either be auto detected or can be forced by using a kernel command line option such as "mem=256M". (Try "man bootparam" or see the documentation of your boot loader (grub, lilo or loadlin) about how to pass options to the kernel at boot time.) If unsure, say "off". 4GB CONFIG_HIGHMEM4G Select this if you have a 32-bit processor and between 1 and 4 gigabytes of physical RAM. 64GB CONFIG_HIGHMEM64G Select this if you have a 32-bit processor and more than 4 gigabytes of physical RAM. -D -- All a man's ways seem innocent to him, but motives are weighed by the Lord. Proverbs 16:2
Re: Memory recognition problem / large mem
On Sat, Jan 19, 2002 at 01:54:04PM -0500, Noah Massey wrote: > 2.4.16-k7 shows: > Memory: 897676k/917504k available (815k kernel code, 19440k reserved, 233k > data, 212k init, 0k highmem) > > 2.2.20 shows: > Memory: 970628k/983040k available (1756k kernel code, 412k reserved, 10092k > data, 152k init) > > neither of which is the 1048576k that I'd expect. > > given that each kernel consistently shows the same amount of mem, and > that they disagree with each other on what that amount is, does this > look like a kernel bug? or is there something that I'm just not doing? Possible. Talk to the kernel people - they might want to know this. And the hardware that you are running on. - Adam PS. Try 2.4.17-i386 just for fun.. If it detects 917504k again then it is probably a kernel problem. If not, then it might have to do with 2.4.16 or Athlon optimization thing [compiler?].
Re: Memory recognition problem / large mem
--begin quoted message from dman, > On Sat, Jan 19, 2002 at 12:31:10PM -0500, Noah Massey wrote: > > use 'free -m' to see smaller (easier to read) numbers. > > Check dmesg -- some memory is used for the kernel itself and isn't > available for processes to use. thanks. those are both much prettier. > On my system I have 256MB real RAM. > > It shows a total of only 249MB. dmesg shows : > > $ dmesg | grep Memory > Memory: 255676k/262080k available (k kernel code, 6016k reserved, > 300k data, 228k init, 0k highmem) > 2.4.16-k7 shows: Memory: 897676k/917504k available (815k kernel code, 19440k reserved, 233k data, 212k init, 0k highmem) 2.2.20 shows: Memory: 970628k/983040k available (1756k kernel code, 412k reserved, 10092k data, 152k init) neither of which is the 1048576k that I'd expect. given that each kernel consistently shows the same amount of mem, and that they disagree with each other on what that amount is, does this look like a kernel bug? or is there something that I'm just not doing? -- Noah Massey | fingerprint : 90AD 7AAB 0768 46AF 8C52 0695 03A2 C74D E1ED C2BF Don't take problems to bed with you, they make very poor bedfellows. Attached is a digital signature which can be used to authenticate this email. For details consult www.gnupg.org or www.pgpi.org pgpygZXCSLWYK.pgp Description: PGP signature
Re: Memory recognition problem / large mem
On Sat, Jan 19, 2002 at 12:31:10PM -0500, Noah Massey wrote: | --begin quoted message from Adam Majer, | > Did you try a different kernel? | | even more interesting... | the 2.2.20 kernel reports: | | total:used:free: shared: buffers: cached: | Mem: 994078720 42676224 951402496 10178560 8065024 21536768 | MemTotal:970780 kB | ... use 'free -m' to see smaller (easier to read) numbers. | which is better, but still inaccurate... (and not what I told it) Check dmesg -- some memory is used for the kernel itself and isn't available for processes to use. On my system I have 256MB real RAM. $ free -m total used free sharedbuffers cached Mem: 249175 74 0 5 65 -/+ buffers/cache:104145 Swap: 243 68175 It shows a total of only 249MB. dmesg shows : $ dmesg | grep Memory Memory: 255676k/262080k available (k kernel code, 6016k reserved, 300k data, 228k init, 0k highmem) The "missing" memory is used by the kernel. -D -- Dishonest money dwindles away, but he who gathers money little by little makes it grow. Proverbs 13:11
Re: Memory recognition problem / large mem
--begin quoted message from Adam Majer, > On Fri, Jan 18, 2002 at 12:43:27PM -0500, Noah Massey wrote: > > ok, first the problem: > > my computer has 1024 M of RAM installed. > > /proc/meminfo reports: > > > > total:used:free: shared: buffers: cached: > > Mem: 923058176 460623872 4624343040 33697792 172601344 > > Swap: 31749038080 3174903808 > > MemTotal: 901424 kB > > ... > > > > I'm running woody, with the 2.4.16-k7 kernel > > > > Redhat 7.1, with a 2.4.2-2 kernel had no problem detecting all my mem. > > neither did memtest86 (no errors on the full test suite) > > Did you try a different kernel? even more interesting... the 2.2.20 kernel reports: total:used:free: shared: buffers: cached: Mem: 994078720 42676224 951402496 10178560 8065024 21536768 MemTotal:970780 kB ... which is better, but still inaccurate... (and not what I told it) -- Noah Massey | fingerprint : 90AD 7AAB 0768 46AF 8C52 0695 03A2 C74D E1ED C2BF This software comes with ABSOLUTELY NO WARRANTY. Even if it erases your hard drive, too bad. Although we did fix that bug from the last release. -README from a long-ago release of DJGPP Attached is a digital signature which can be used to authenticate this email. For details consult www.gnupg.org or www.pgpi.org pgpeeebTEHIFb.pgp Description: PGP signature
Re: Memory recognition problem / large mem
On Fri, Jan 18, 2002 at 12:43:27PM -0500, Noah Massey wrote: > ok, first the problem: > my computer has 1024 M of RAM installed. > /proc/meminfo reports: > > total:used:free: shared: buffers: cached: > Mem: 923058176 460623872 4624343040 33697792 172601344 > Swap: 31749038080 3174903808 > MemTotal: 901424 kB > ... > > I'm running woody, with the 2.4.16-k7 kernel > > Redhat 7.1, with a 2.4.2-2 kernel had no problem detecting all my mem. > neither did memtest86 (no errors on the full test suite) Did you try a different kernel?
Memory recognition problem / large mem
ok, first the problem: my computer has 1024 M of RAM installed. /proc/meminfo reports: total:used:free: shared: buffers: cached: Mem: 923058176 460623872 4624343040 33697792 172601344 Swap: 31749038080 3174903808 MemTotal: 901424 kB ... I'm running woody, with the 2.4.16-k7 kernel Redhat 7.1, with a 2.4.2-2 kernel had no problem detecting all my mem. neither did memtest86 (no errors on the full test suite) using lilo to pass 'mem=1024M' or 'mem=0x4000' does not change the mem reported. same for passing those args at the lilo prompt. however, passing 'mem=512M' does drop the mem reported, so I know the kernel is seeing the arguments. according to 'man bootparam' >> 'mem=...' If you have more than 64MB of RAM installed, you can use this boot arg to tell Linux how much memory you have. The value is in decimal or hexadecimal (prefix 0x), and the suffixes `k' (times 1024) or `M' (times 1048576) can be used. Here is a quote from Linus on usage of the `mem=' parameter. ``The kernel will accept any `mem=xx' parameter you give it, and if it turns out that you lied to it, it will crash horribly sooner or later. The parameter indicates the highest addressable RAM address, so `mem=0x100' means you have 16MB of memory, for example. For a 96MB machine this would be `mem=0x600'. << has this been changed? any other ideas how I can get it to admit that I have more mem? -- Noah Massey | fingerprint : 90AD 7AAB 0768 46AF 8C52 0695 03A2 C74D E1ED C2BF It is better to sleep on what you intend doing than to stay awake over what you've done. Attached is a digital signature which can be used to authenticate this email. For details consult www.gnupg.org or www.pgpi.org pgpA6xGEOlMyX.pgp Description: PGP signature
Re: Memory Recognition Problem
On Fri, 9 Jul 1999 18:59:52 -0400, "Jonathan D. Proulx" <[EMAIL PROTECTED]> wrote: >The bios reports 3716k RAM with >1M memory checking enabled >there's 4 30pin simms installed. > >Linux sees 1936k available (free and top). > >Anyone know what can be causing this? The memory reported does not include the memory occupied by the kernel. I had similar readings on a similar machine, and it was practically unusable. I'd advise you to compile a custom kernel (on a different machine!) with only what you need in it, and of that the stuff you don't need all the time moved to modules. Dpkg makes it easy to make a debian package of the custom kernel and modules, to install on the low-mem machine. My 4M 386 now has 3260K available memory, and functions without problems as an IP-masqerading host. Gertjan. -- Gertjan Klein <[EMAIL PROTECTED]> The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html
Memory Recognition Problem
Hi, I've just installed Slink (using low memory disk) on a 486 with AMIBIOS V1.1 The bios reports 3716k RAM with >1M memory checking enabled there's 4 30pin simms installed. Linux sees 1936k available (free and top). Anyone know what can be causing this? TIA, Jon -- Email: [EMAIL PROTECTED] [EMAIL PROTECTED] ICQ: 39679408
