From: Jack Mitchell <ml@communistcode.co.uk>
To: linux-acpi@vger.kernel.org
Subject: Re: New motherboard not detecting all memory
Date: Sun, 30 Jun 2013 12:40:16 +0100 [thread overview]
Message-ID: <51D01920.5080103@communistcode.co.uk> (raw)
In-Reply-To: <51D0090C.90402@communistcode.co.uk>
On 30/06/2013 11:31, Jack Mitchell wrote:
> On 30/06/2013 10:23, Jack Mitchell wrote:
>> I recently bought a new AMD FM2 motherboard[1] and coupled it with an
>> AMD A4 APU. I put 2x2GB sticks of RAM in the board, and the UEFI bios
>> detects both sticks and reports 4GB. Now, when I boot into a fresh
>> install of Linux [2] only 1501MB is reported as available.
>>
>> I was told this may be an ACPI problem, I have updated the motherboard
>> to the latest BIOS revision which works. Could anyone shed any light on
>> this, or where I should make a start in helping to debug the problem?
>>
>> Kind Regards,
>> Jack.
>>
>> [1] http://www.gigabyte.com/products/product-page.aspx?pid=4383&dl=#ov
>> [2] Linux mediaserver 3.9.7-1-ARCH #1 SMP PREEMPT Thu Jun 20 22:45:32
>> CEST 2013 x86_64 GNU/Linux
>>
>>
>
> I have attached the dmidecode output in case that is of any help; I can
> see that it is only registering one bank of RAM, so detection of RAM
> seems to be the issue; but I don't know what is causing it.
>
> I have also attached a dmesg.
>
> Cheers,
> Jack.
>
Ok, I fiddled with the seating of the RAM and changing the slots; it
appears that one of the sticks is bad, but the motherboard will still
detect it in BIOS if it is coupled with the good stick. The bad stick on
it's own will not even get to the BIOS 'initialization' screen.
Apologies for the noise.
Cheers,
Jack.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2013-06-30 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 9:23 New motherboard not detecting all memory Jack Mitchell
2013-06-30 10:31 ` Jack Mitchell
2013-06-30 11:40 ` Jack Mitchell [this message]
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=51D01920.5080103@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=linux-acpi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).