RAM reporting : OS or BIOS issue (or both)?

[blueice007]

Hi,

 

Trying to resolve a RAM reporting issue.

 

Full system specs in signature (just added 2 more sticks identical RAM).

 

Bios version - Phoenix 6.00PG

 

XP Pro SP2

Core 2 x6800 2.93GHZ

4GB ram installed but NOT reported by OS ::(4x 1G dual channel)

Bios indicates 4GB ram, memory test confirms.SiSandra indicates 4GB.

Physical Address Extension (in system properties box)

 

Only 2.0GB RAM reported in System Properties.

Physcial Memory T:2095532 A:~1750000 SysCache:~175412

Kernel Memory T:~59000 Paged:~48000 NonPaged:~11500

Commit Charge T:206744 Limit:4033792 P:~650000

 

PageFile is set at 2046mb. (I tried reducing the

page file. No change to reported values in the task manager.)

 

boot.ini file, no /3gb or /pae switches. Everything has

been directed by the OS, no hacks. I tried the /3gb hack, but

nothing changed.

 

I've researched the 4GB ram issue in 32bit XP, but I still can't find a

clear answer to my concern. I just want to make sure that xp pro is actually

utilizing the physical memory over 2gb. I somewhat understand the nuances of how the OS maps the memory and uses the page file. My only real concern is just some evidence that my system is actually "seeing" (and using) the

physical ram above 2gb.

 

Any suggestions? Could it be the bios? Is this just a reporting issue with the OS?

 

Thanks.

[Reinvented]

There's many threads on this if you had used the search. I had posted about it before.

 

Yes, it will show up in bios, however there is a memory hole issue in the bios which causes Windows NOT to be able to access any of it beyond 2.0GBs. I have talked to the DFI Techs, and they are working on a fix for it.

[blueice007]

Thanks.

 

How do you know it's a memory hole issue in the bios?

[Reinvented]

Thanks.

 

How do you know it's a memory hole issue in the bios?

 

Reported by DFI Tech, a memory hole/mapping issue.

[blueice007]

Read threads. Interesting. Would have been easy to test this situation in the pre-production of the board. Curious about xp pro 64bit. Appears that would correct the issue. Your thoughts or experience?

[jzono1]

Got the same problem. A 64bit os just fails miserably, even though it detects all the memory.

[blueice007]

Anyone have 4GB RAM (at least more than 2GB RAM) reporting with XP OS or other 32bit OS?

[Angry_Games]

Linux will see all 4GB in 32-bit mode

 

Vista will see all 4GB in 32-bit mode

 

all 64-bit OS's will of course see it

 

Windows XP SP1 will see all 4GB

 

WindowsXP SP2 just won't. We've tried for months and months and have had probably 100+ guys coming back and telling us the same thing...it just won't work in XP SP2.

 

(be aware that you really don't want to go back to pre-SP2...just don't worry about seeing all 4GB at the moment as it is XP's problem, not any hardware problem....but Vista will relieve everyone of this problem, especially since 4GB in Vista will almost be a necessity)

[blueice007]

Thanks for the response.

 

I understand that it's not a hardware issue.

 

I realize it's a compatiblity issue with the current bios for this mobo and XP 32-bit SP2 OSs.

 

Are the DFI engineers trying to fix the memory mapping issues with the current bios for the DFI Infinity 975X/G?

 

It seems other people in my situation are under that impression. I just would like to know. If they aren't actually planning on fixing the problem, I'll need to switch to another motherboard.

 

Thanks much.

[blueice007]

to Happy Games

 

This site made me decide to stick with DFI.

 

I just installed xp pro 64 bit without a hitch. All ram is reporting.

 

Drivers working for all my needed applications. Maya and Adobe CS2 taking advantage of the extra ram. Rockin.

[jzono1]

Linux will see all 4GB in 32-bit mode

 

Vista will see all 4GB in 32-bit mode

 

all 64-bit OS's will of course see it

 

Windows XP SP1 will see all 4GB

 

WindowsXP SP2 just won't. We've tried for months and months and have had probably 100+ guys coming back and telling us the same thing...it just won't work in XP SP2.

 

(be aware that you really don't want to go back to pre-SP2...just don't worry about seeing all 4GB at the moment as it is XP's problem, not any hardware problem....but Vista will relieve everyone of this problem, especially since 4GB in Vista will almost be a necessity)

 

So, what's wrong with my setup then? Linux in 32bit mode sees it all, but due to them memory mapping issues, can't access it all. Linux in 64bit mode does bad stuff and fails to boot unless i limit it to 2GB of ram

[OJ287]

I have two HD, one with 32-bit Linux FC-1.90 and another with 64-bit

Linux FC-6.

 

BIOS sees all 4096 Mb memory, memtest86 detects 4Gb as well and finds

no errors.

 

When I boot from 32-bit Linux, FC-1.90, the system (/var/log/dmesg) reports

 

Warning only 4GB will be used.

Use a PAE enabled kernel.

3200MB HIGHMEM available.

896MB LOWMEM available.

Memory: 2056904k/4194304k available (2340k kernel code, 37848k reserved, 1035k data, 232k init, 1178496k highmem)

/tmp> free

total used free shared buffers cached

Mem: 2058232 503788 1554444 0 73072 54504

-/+ buffers/cache: 376212 1682020

Swap: 1050832 4 1050828

 

==> only 2Gb are visible

 

When I boot from 64-bit Linux, FC-6, the system reports:

 

BIOS-provided physical RAM map:

BIOS-e820: 0000000000000000 - 000000000009f400 (usable)

BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)

BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)

BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)

BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)

BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)

BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)

BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)

BIOS-e820: 0000000100000000 - 0000000180000000 (usable)

Nosave address range: 000000000009f000 - 00000000000a0000

Nosave address range: 00000000000a0000 - 00000000000f0000

Nosave address range: 00000000000f0000 - 0000000000100000

Nosave address range: 000000007fee0000 - 000000007fee3000

Nosave address range: 000000007fee3000 - 000000007fef0000

Nosave address range: 000000007fef0000 - 000000007ff00000

Nosave address range: 000000007ff00000 - 00000000e0000000

Nosave address range: 00000000e0000000 - 00000000f0000000

Nosave address range: 00000000f0000000 - 00000000fec00000

Nosave address range: 00000000fec00000 - 0000000100000000

Allocating PCI resources starting at 80000000 (gap: 7ff00000:60100000)

Memory: 4015068k/6291456k available (2409k kernel code, 177696k reserved, 1722k data, 204k init)

 

it boots, launches X-window, but no Internet. Debugging shows that the

network client, rp-pppoe-3.5.1 sends PADI requests to the ethernet card,

the internet card apparently directs them to modem, modem apparently

accept them, since it blinks and then the network client gets nothing back.

It expects to receive PADS packet. No connection, no ping, no internet

browsing. :-(

 

Then, I shutdown the OS, unplug power, wait for 15 seconds and remove 2 Gb

memory out of 4 Gb. Then I plug power, boot computer with 2 Gb memory,

and the network is working!

 

BIOS-provided physical RAM map:

BIOS-e820: 0000000000000000 - 000000000009f400 (usable)

BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)

BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)

BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)

BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)

BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)

BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)

BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)

Nosave address range: 000000000009f000 - 00000000000a0000

Nosave address range: 00000000000a0000 - 00000000000f0000

Nosave address range: 00000000000f0000 - 0000000000100000

Allocating PCI resources starting at 80000000 (gap: 7ff00000:60100000)

Memory: 2052644k/2096000k available (2409k kernel code, 42968k reserved, 1722k data, 204k init)

 

I did not run further tests.

 

Conclusion:

4 Gb memory with Infinity 975 X/G is useless with both 32 bit OS and 64 bit OS.

I can only suggest that either BIOS reports incorrect memory mapping or

Linux incorrectly interprets that report. Hint: Linux uses almost all

available memory not claimed by user process for buffers and caches.

 

Communicated with DFI Technical Support:

 

> Date: Tue, November 14, 2006 1:32

>

> There will be nothing solved inside 48 hours...suggest if you are on that short a

> window...that you make your decision accordingly...thank you.

>

> Sincerely,

> Robert Tech Support DFI Usa

> DO NOT POST OUR EMAIL ADDRESSES IN THE OPEN FORUM. WE GET 1,000's OF SPAM PER DAY WHEN YOU PEOPLE DO THIS. HOW WOULD YOU LIKE US TO POST YOUR EMAIL ADDRESS THAT YOU REGISTERED WITH OPENLY SO YOU COULD GET SPAM ALL DAY EVERY DAY?

 

THIS IS VERY RUDE, UNACCEPTABLE BEHAVIOR AND IT WILL NOT BE TOLERATED.

 

I AM GETTING TIRED OF WARNING YOU PEOPLE.

 

 

It is not clear from the reply of the technical representative whether

it is going to solve it at all.