But I should still see 4GB without any patch. Right? Windows only see 1.92GB as “Installed Memory (RAM)” in Control Panel->System. I am happy for the system to see up to 4GB only.
From: Zoran Stojsavljevic [mailto:zoran.stojsavljevic@gmail.com] Sent: Tuesday, 7 June 2016 1:13 PM To: Naveed Ghori Cc: coreboot Subject: Re: [coreboot] Windows only seeing 2GB of 4G (Seabios
Hello Naveed,
For you to read: https://en.wikipedia.org/wiki/Physical_Address_Extension
Important: With PAE, IA-32https://en.wikipedia.org/wiki/IA-32 architecture is augmented with additional address lines used to select the additional memory, so physical address size increases from 32 bits to 36 bits.
Then, after reading, this can/will help you: https://wj32.org/wp/2011/02/23/pae-patch-updated-for-windows-7-sp1/https://linkprotect.cudasvc.com/url?a=https://wj32.org/wp/2011/02/23/pae-patch-updated-for-windows-7-sp1/&c=E,1,4TzuPPEqEt09bfSHLiacrY50KGLRosTpaWTwnQSnoSKs3XZAVCm1oYCwQgdB0tNnt34H5_afYQx62tS0zDeEB4hnXiXrwGbJe3QaP4bkeTL8zwo,&typo=1
Zoran
On Tue, Jun 7, 2016 at 6:23 AM, Naveed Ghori <naveed.ghori@dti.com.aumailto:naveed.ghori@dti.com.au> wrote: Hi all,
I am booting a 32 bit Win 7 image (via Seabios).
Windows is detecting only 1.92GB (even though there is 8GB of memory available. Being a 32 bit OS I would have expected it to see at least 4GB.
Coreboot logs shows: Available memory below 4GB: 0x7ae00000 (1966M) Available memory above 4GB: 6144M
What can cause the full 4GB to not be seen. Should I install only 4GB of memory instead of 4GB? I have ordered some to try in any case.
Best Regards, Naveed
Naveed Ghori | Lead Firmware & Driver Engineer
DTI Group Ltd | Transit Security & Surveillance
31 Affleck Road, Perth Airport, Western Australia 6105, AU
P +61 8 9373 2905tel:%2B61%208%209373%202905,151 | F +61 8 9479 1190tel:%2B61%208%209479%201190 | naveed.ghori@dti.com.aumailto:naveed.ghori@dti.com.au
Visit our website www.dti.com.auhttps://linkprotect.cudasvc.com/url?a=http://www.dti.com.au&c=E,1,J7GyvbswEaQev6_KbGrjzW_wg8-uFxxIttLgm1oQAe7GLygg2StH0fqojPD1XOxuq65LXh6Ve5Jg07_7KtNhMMrMB5NE4RetHudpRDuwEoZcmFcq8N49KhKhTQ,,&typo=1
The information contained in this email is confidential. If you receive this email in error, please inform DTI Group Ltd via the above contact details. If you are not the intended recipient, you may not use or disclose the information contained in this email or attachments.
-- coreboot mailing list: coreboot@coreboot.orgmailto:coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboothttps://linkprotect.cudasvc.com/url?a=https://www.coreboot.org/mailman/listinfo/coreboot&c=E,1,-zPAXbIB1GaqteqcB4ldHnicKOOadECoYc6gjLplt2yW0lSvrBPxqVbmuTQtBzTIP3XeIOt-aqgE33ryMscBlipXKotlTSg8NaDJmo5ElJtg-CZnuGuyrz2T&typo=1
Hello Naveed,
On 07.06.2016 07:21, Naveed Ghori wrote:
But I should still see 4GB without any patch. Right?
no, I'm afraid not.
Windows only see 1.92GB as “Installed Memory (RAM)” in Control Panel->System.
This is correct as the 4GiB address space is not only used for RAM but shared with other resources on modern systems.
I am happy for the system to see up to 4GB only.
It might be possible to tune the configuration a little. But you'd never get the full 4GiB. About 3GiB is a common limit today if you really want to run a 32bit OS without PAE support.
Nico
Hello Nico,
I'll add more to your answer, and ask community to review my thoughts since not sure if I am putting them correctly (what do I know?).
Naveed,
Usually, boot-loaders are linear. "Linear" term means that MMU (Memory Management Unit HW) is not used/even initialized with (any) boot-loaders.
This implies that there is no OS (no virtual space, no TLBs, no HW TLB xlation), no kernel scheduler in place. Boot-loaders are translated to single linear HW thread, mostly INT disabled. They are bringing CPU/PCH/minimum platform internals up.
In this respect Coreboot is NOT responsible for memory allocation. It can ONLY see 4GB linear, after all. while MRC should take care (in x86 FSP) for all platform on-board memory (forgive me if I am wrong here). ;-)
OS is the one, which will start using MMU HW, and virtual space/TLB tables initialized (by OS MMU drivers). So, I would not blame either INTEL FSP, either Coreboot for what you see as DDR3 allocation in WIN7 32.
Zoran _______
On Tue, Jun 7, 2016 at 11:36 AM, Nico Huber nico.huber@secunet.com wrote:
Thanks Nico, What options should I be looking to tune? 3Gig should be fine as that is what I have seen in another product.
However in that product (non coreboot) It says for "Installed Memory (RAM)" as "4.00GB (2.89GB available)": So windows actually shows both what is installed and what is available.
Regards, Naveed -----Original Message----- From: Nico Huber [mailto:nico.huber@secunet.com] Sent: Tuesday, 7 June 2016 5:37 PM To: Naveed Ghori; Zoran Stojsavljevic Cc: coreboot Subject: Re: [coreboot] Windows only seeing 2GB of 4G (Seabios
Hello Naveed,
On 07.06.2016 07:21, Naveed Ghori wrote:
But I should still see 4GB without any patch. Right?
no, I'm afraid not.
Windows only see 1.92GB as “Installed Memory (RAM)” in Control Panel->System.
This is correct as the 4GiB address space is not only used for RAM but shared with other resources on modern systems.
I am happy for the system to see up to 4GB only.
It might be possible to tune the configuration a little. But you'd never get the full 4GiB. About 3GiB is a common limit today if you really want to run a 32bit OS without PAE support.
Nico
On 08.06.2016 04:26, Naveed Ghori wrote:
This depends heavily on the used hardware platform. I don't think all of them have an option in coreboot. But it might be just one line of code to change if you are lucky.
Sorry, I don't know Windows that well. Maybe it's taking DMI data into account (that's not always filled by coreboot).
Nico
To close out this topic.
Windows 7 (32bit) can address maximum of 4GB so the default setting of 2GB for MIMO will reduce the 4GB to 2GB. If I setup MIMO memory to be 1GB then I can see almost 3GB (2.92MB). The rest probably used by graphics etc.
Regards, Naveed.
-----Original Message----- From: Naveed Ghori Sent: Wednesday, 8 June 2016 10:27 AM To: 'Nico Huber'; Zoran Stojsavljevic Cc: coreboot Subject: RE: [coreboot] Windows only seeing 2GB of 4G (Seabios
Thanks Nico, What options should I be looking to tune? 3Gig should be fine as that is what I have seen in another product.
However in that product (non coreboot) It says for "Installed Memory (RAM)" as "4.00GB (2.89GB available)": So windows actually shows both what is installed and what is available.
Regards, Naveed -----Original Message----- From: Nico Huber [mailto:nico.huber@secunet.com] Sent: Tuesday, 7 June 2016 5:37 PM To: Naveed Ghori; Zoran Stojsavljevic Cc: coreboot Subject: Re: [coreboot] Windows only seeing 2GB of 4G (Seabios
Hello Naveed,
On 07.06.2016 07:21, Naveed Ghori wrote:
But I should still see 4GB without any patch. Right?
no, I'm afraid not.
Windows only see 1.92GB as “Installed Memory (RAM)” in Control Panel->System.
This is correct as the 4GiB address space is not only used for RAM but shared with other resources on modern systems.
I am happy for the system to see up to 4GB only.
It might be possible to tune the configuration a little. But you'd never get the full 4GiB. About 3GiB is a common limit today if you really want to run a 32bit OS without PAE support.
Nico
-
Naveed Ghori -
Nico Huber -
Zoran Stojsavljevic