Your message dated Tue, 17 Jun 2008 17:15:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#486651: dmidecode: Wrong values apparently returned
for memory controller; bug or wrong information?
has caused the Debian Bug report #486651,
regarding dmidecode: Wrong values apparently returned for memory controller;
bug or wrong information?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486651
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dmidecode
Version: 2.8-4
Severity: normal
Below, I reproduce the output from dmidecode. It claims that the maximum
memory module size is 32MB and the total maximum system memory is 64MB,
but as you can see below, it correctly reports two 512MB cards installed.
Is this a dmidecode bug, or incorrect information reported by the
BIOS?
Handle 0x0005, DMI type 5, 20 bytes
Memory Controller Information
Error Detecting Method: None
Error Correcting Capabilities:
None
Supported Interleave: One-way Interleave
Current Interleave: Four-way Interleave
Maximum Memory Module Size: 32 MB
Maximum Total Memory Size: 64 MB
Supported Speeds:
70 ns
60 ns
Supported Memory Types:
Standard
EDO
Memory Module Voltage: 5.0 V
Associated Memory Slots: 2
0x0006
0x0007
Enabled Error Correcting Capabilities: None
Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A0
Bank Connections: 0
Current Speed: 60 ns
Type: Other SDRAM
Installed Size: 512 MB (Single-bank Connection)
Enabled Size: 512 MB (Single-bank Connection)
Error Status: OK
Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A1
Bank Connections: 2
Current Speed: 60 ns
Type: Other SDRAM
Installed Size: 512 MB (Single-bank Connection)
Enabled Size: 512 MB (Single-bank Connection)
Error Status: OK
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages dmidecode depends on:
ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
dmidecode recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.8-4
[Reuben Thomas]
> Hmm, I think that's a bad idea: firmware upgrades are sufficiently
> risky that I don't try them unless I have a real bug of some sort to
> fix, rather than merely wrong information...
OK. Personally, I try to upgrade the firmware to make sure any bugs
detected by the vendor do not linger in my systems, but would be
reluctant to do so if it was my only computer. The risk of bricking
it is non-zero. :)
> But thanks for your answer!
OK. Closing this, as it isn't really a bug in dmidecode.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
