Bug 9968

Summary: Radeon Mobility detects memory incorrectly
Product: xorg Reporter: Jim Duchek <jim.duchek>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: cweyl
Version: git   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log attached none

Description Jim Duchek 2007-02-13 16:14:30 UTC
The Radeon FireGL 7800 detects memory incorrectly (half-sized, half-channels).  On my 64M, 128bit DDR setup (IBM Thinkpad A31p), a 32M 64bit memory size is detected.  A similar issue has been noted for the Radeon Mobility 9000 (http://lists.freedesktop.org/archives/xorg/2006-December/020223.html).

Suggestion is that it could be a powersaving feature?
Comment 1 Michel Dänzer 2007-02-14 00:02:54 UTC
Please attach (as opposed to paste) a full Xorg.0.log showing the problem. Are there any Powerplay or generally power management related options in the BIOS setup?
Comment 2 Jim Duchek 2007-02-14 07:28:52 UTC
Created attachment 8704 [details]
Xorg.0.log attached

The line in question is:  

(II) RADEON(0): Detected total video RAM=32768K, accessible=65536K...

The line before that (ignore that one) and two lines after that are some debug I stuck in:

(II) RADEON(0): 55420042 5133a3a0   < -- RADEON_SDRAM_MODE_REG, RADEON_BUS_CNTL
(WW) RADEON(0): 2d000002, 00000005   <-- RADEON_MEM_CNTL, info->ChipFamily

I would like to get the docs on this chip but ATI seems to be routing my email to /dev/null...

With regards to any settings in the BIOS... there really aren't any.  This is a Thinkpad A31p (IBM isn't known for giving you lots of switches to fiddle with), and as far as I know, this chip isn't used in any other machine.

Jim
Comment 3 Daniel Stone 2007-02-27 01:36:24 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 4 Alex Deucher 2007-10-06 23:31:25 UTC
I think this may be bios related.  Does this happen when more readily with suspend/resume than a straight boot?  the ram type and size usually gets written to the hardware by the bios during post.  Another possibility is that the bios may have different init sequences depending on the power saving features.
Comment 5 Alex Deucher 2008-12-02 23:49:00 UTC
no feedback in over a year.  closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.