| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 04 Jun 2007 15:45:54 -0400 From: Tom Moore <tmoore@...tial.ca> To: linux-kernel@...r.kernel.org Subject: Re: 4Gb ram not showing up Thank you for the reply back. Your answer makes perfect sense to me, and it is what I had suspected but was not sure about. The math seems to indicate that 4Gb of ram plus 1Gb of PCI address space equals 5Gb of memory space. So it does sound like I should have a larger kernel model. What confused me the most (and still does), is the help message string that is presented for the CONFIG_HIGHMEM4G option: "Select this if you have a 32-bit processor and between 1 and 4 gigabytes of physical RAM." Well that sounds like the amount of memory that I have, so that is what I selected. Also, although I know what PAE stands for, I don't know how to select it when building a kernel. Would I get this from the CONFIG_HIGHMEM64G option? The help text for that says: "Select this if you have a 32-bit processor and more than 4 gigabytes of physical RAM." This does not sound like it applies to my hardware. There is something wrong with my understanding, or with these message strings. I am still confused. Tom Lennart Sorensen wrote: > On Mon, Jun 04, 2007 at 11:14:40AM -0400, Tom Moore wrote: > >> I am having some difficulty trying to get my 4Gb of ram recognized by >> the system. I have tried googling around to get some information on how >> to do this configuration, but I have come up dry. I suspect that the >> reason that there is not much info on how to set things up is because >> usually it just works. However, on my system I don't think it is. >> >> By the way, I am not subscribed to this mailing list, so could you >> please CC me any replies. >> >> The basics are that I have an Athlon 64 X2 Dual core, 4Gb ram, ASUS >> M2N-MX motherboard. The bios has a configuration item for MTRR mapping, >> with options for CONTINUOUS and DISCRETE. I have selected CONTINUOUS, >> which explicitly describes the PCI hole as non-cacheable. The other >> option leaves the PCI hole undescribed. >> >> My config has selected >> CONFIG_HIGHMEM4G=y >> > > That supports of to 4GB memory space. > > >> free -m reports the following.... >> total used free shared buffers cached >> Mem: 2906 2794 112 0 275 31 >> -/+ buffers/cache: 2487 419 >> Swap: 4996 366 4630 >> >> >> /proc/mtrr contains the following.... >> >> reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 >> reg01: base=0x100000000 (4096MB), size=1024MB: write-back, count=1 >> reg02: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1 >> > > Your memory map however has 3GB at address 0 and 1GB at address 4GB (so > memory is places at address 0 - 3GB and 4-5GB. The addresses from 3 to > 4GB are reserved for PCI). > > If you run a 64bit kernel you will see it all, or you can use a kernel > configured for 64GB memory space. > > >> Relevant bootup messages include these.... >> Jun 3 13:50:52 fawkes Linux version 2.6.20-gentoo-r8 (root@...kes) (gcc >> version 4.1.1 (Gentoo 4.1.1-r3)) #6 SMP Tue May 15 10:18:59 EDT 2007 >> Jun 3 13:50:52 fawkes BIOS-provided physical RAM map: >> Jun 3 13:50:52 fawkes sanitize start >> Jun 3 13:50:52 fawkes sanitize end >> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000000000000 size: >> 000000000009fc00 end: 000000000009fc00 type: 1 >> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM >> Jun 3 13:50:52 fawkes copy_e820_map() start: 000000000009fc00 size: >> 0000000000000400 end: 00000000000a0000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000000e0000 size: >> 0000000000020000 end: 0000000000100000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000000100000 size: >> 00000000b7ec0000 end: 00000000b7fc0000 type: 1 >> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7fc0000 size: >> 000000000000e000 end: 00000000b7fce000 type: 3 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7fce000 size: >> 0000000000022000 end: 00000000b7ff0000 type: 4 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7ff0000 size: >> 0000000000010000 end: 00000000b8000000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000fec00000 size: >> 0000000000001000 end: 00000000fec01000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000fee00000 size: >> 0000000000100000 end: 00000000fef00000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000ff780000 size: >> 0000000000880000 end: 0000000100000000 type: 2 >> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000100000000 size: >> 0000000040000000 end: 0000000140000000 type: 1 >> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM >> Jun 3 13:50:52 fawkes BIOS-e820: 0000000000000000 - 000000000009fc00 >> (usable) >> Jun 3 13:50:52 fawkes BIOS-e820: 000000000009fc00 - 00000000000a0000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000000e0000 - 0000000000100000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 0000000000100000 - 00000000b7fc0000 >> (usable) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7fc0000 - 00000000b7fce000 >> (ACPI data) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7fce000 - 00000000b7ff0000 >> (ACPI NVS) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7ff0000 - 00000000b8000000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000fec00000 - 00000000fec01000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000fee00000 - 00000000fef00000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 00000000ff780000 - 0000000100000000 >> (reserved) >> Jun 3 13:50:52 fawkes BIOS-e820: 0000000100000000 - 0000000140000000 >> (usable) >> Jun 3 13:50:52 fawkes Warning only 4GB will be used. >> Jun 3 13:50:52 fawkes Use a PAE enabled kernel. >> > > Oh look, it even tells you right there that you have to use a PAE (>4GB > for 32bit machines) kernel to get all your ram. > > -- > Len Sorensen > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists