[Gigabyte GA-970A-UD3 (rev. 3.0)] Ubuntu 12.04 LTS lshw sees 12gb RAM but system only using 8gb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Gigabyte replaced my dead GA-870A-UD3 motherboard with a GA-970A-UD3. However, "free" and cat /proc/meminfo only show 8GB of RAM:
cat /proc/meminfo
MemTotal: 8155016 kB
MemFree: 253264 kB
...
However, lshw does see all 12gb:
lshw | grep -m 1 -A 50 "*-memory"
*-memory
physical id: 2c
slot: System board or motherboard
size: 12GiB
*-bank:0
slot: Node0_Dimm0
size: 4GiB
width: 64 bits
clock: 667MHz (1.5ns)
*-bank:1
slot: Node0_Dimm1
size: 4GiB
width: 64 bits
clock: 667MHz (1.5ns)
*-bank:2
slot: Node0_Dimm2
size: 2GiB
width: 64 bits
clock: 667MHz (1.5ns)
*-bank:3
slot: Node0_Dimm3
size: 2GiB
width: 64 bits
clock: 667MHz (1.5ns)
Upstream URL http://
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-63-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb00000 irq 16'
Mixer name : 'VIA VT2020'
Components : 'HDA:11060441,
Controls : 48
Simple ctrls : 24
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xfea40000 irq 76'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 6
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card2.Amixer.info:
Card hw:2 'Generic_
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 6
Simple ctrls : 1
Card2.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Wed May 21 16:34:53 2014
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcEnviron:
TERM=xterm-color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.79.14
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-05-06 (745 days ago)
dmi.bios.date: 01/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.
dmi.board.name: 970A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
summary: |
- Ubuntu 12.04 LTS lshw sees 12gb RAM but system only using 8gb + [Gigabyte GA-970A-UD3 (rev. 3.0)] Ubuntu 12.04 LTS lshw sees 12gb RAM + but system only using 8gb |
description: | updated |
tags: | added: utopic |
affects: | linux (Ubuntu) → procps (Ubuntu) |
Changed in procps (Ubuntu): | |
status: | Incomplete → New |
description: | updated |
Oops, I should have also mentioned:
Of course, all 12gb were being recognized before the motherboard (MB) replacement. No kernel updates or any other kind of updates were applied during the 2-3 day period between when I installed the new MB and noticed the lacking 4gb of RAM.
I did force a kernel reinstall (i.e., "dpkg --reinstall install ...") but that did not correct the problem.
At least two kernel updates have been applied since reinstalling the MB (which occurred about 4-5 weeks ago). No updates seems to have corrected the problem, either.