linux-kernel - Re: BIOS detects 4 GB RAM, but kernel does not

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0607281902560.4972@yvahk01.tjqt.qr>
Date:	Fri, 28 Jul 2006 19:03:10 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Robert Hancock <hancockr@...w.ca>
cc:	ravibt@...il.com, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BIOS detects 4 GB RAM, but kernel does not

>
> Essentially I don't think there is much you can do about this on this board.
> The memory space starting at around 3.2GB is being used by the memory-mapped IO
> regions for the PCI and PCI Express devices and motherboard resources and
> therefore "covers up" the RAM in that part of the address space. The solution
> to this is for the system to remap the affected memory above the 4GB mark,
> which is possible with Athlon 64/Opteron CPUs and on some of the Intel server
> chipsets. However, I don't think any Intel desktop chipsets support this for
> some unfathomable reason.

Maybe PAE can help?


Jan Engelhardt
-- 
-
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/