From: Bill Davidsen <davidsen@tmr.com>
To: Marc Perkel <marc@perkel.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hardware Problem - Asus A8N-VM CSM
Date: Sat, 28 Oct 2006 19:14:31 -0400 [thread overview]
Message-ID: <4543E457.80203@tmr.com> (raw)
In-Reply-To: <454236C0.2070805@perkel.com>
Marc Perkel wrote:
>
>
> Langsdorf, Mark wrote:
>>>> The problem. 2 out of the 4 sees all 4 gigs of ram. The other 2 see
>>>> only 2.8 gigs of ram. And it's hardware related because in the bios
>>>> setup the ones that show 2.8 show it in the bios.
>>>>
>>>> The motherboards were not prchased at the same time. All have
>>>> different brands of ram. And the processors are different. The 2
>>>> that don't see all the ram are the newest ones.
>>>>
>>>> I tried swapping ram between one that saw 2.8 gigs and one that saw
>>>> 4 gigs and the problem stays with the motherboard.
>>>> I haven't yet swapped out the processors.
>>>>
>>>> So - I'm a little stumped. Can someone point me in the right direction?
>>>>
>>
>> Usually, missing memory comes from the PCI I/O hole, or the
>> IOMMU/AGP/framebuffer overlays. Does your BIOS have an
>> options for creating a memory hole or hoisting memory? If
>> so, are the settings between the 4G machines different from
>> the 2.8G machines?
>>
>> Also, do you have an IOMMU aperture enabled and if so, how
>> large?
>>
>> Are there any hardware differences between the systems, like
>> different AGP or PCI graphics cards?
>>
>>
>>> Answering my own question perhaps. Could it be related to whether or
>>> not the processor is a "revision e" chip?
>>>
>>
>> Possibly, but I'd expect the RevE parts to see more DRAM than
>> the earlier parts.
>>
>>
>>
>
> I fixed the problem. It wasn't a Revision E issue after all. I just
> pulled the battery and when it came up clean it saw all the memory.
> Thanks for your help.
>
Would have been interesting to use the "reset to factory defaults"
option, just to see if some bit isn't set to known state doing that.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-10-28 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 13:30 Hardware Problem - Asus A8N-VM CSM Marc Perkel
2006-10-26 14:34 ` Marc Perkel
2006-10-26 16:33 ` Langsdorf, Mark
2006-10-27 16:41 ` Marc Perkel
2006-10-28 23:14 ` Bill Davidsen [this message]
2006-10-29 4:05 ` Marc Perkel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4543E457.80203@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox