Bug 9712 - [mga] 32MB video ram not detected
Summary: [mga] 32MB video ram not detected
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/mga (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2007-01-19 11:31 UTC by Michal Suchanek
Modified: 2018-06-12 19:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
the log (34.22 KB, text/plain)
2007-01-19 11:33 UTC, Michal Suchanek
no flags Details
another card type, another log (33.37 KB, text/plain)
2007-01-19 11:37 UTC, Michal Suchanek
no flags Details

Description Michal Suchanek 2007-01-19 11:31:37 UTC
On my card with 32MB video ram only 16MB is detected.
Comment 1 Michal Suchanek 2007-01-19 11:33:13 UTC
Created attachment 8454 [details]
the log
Comment 2 Michal Suchanek 2007-01-19 11:37:45 UTC
Created attachment 8455 [details]
another card type, another log

Here I specified the memory manually. 
But earlier I had a nice log where it says VideoRam is 16MB and a bit later it
reads from bios that it is 32MB.
Comment 3 Daniel Stone 2007-02-27 01:35:51 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 Jesse Adkins 2010-11-20 11:55:16 UTC
Adding [mga] so I can see that this is for mga when looking down the bug list. Additionally, are you still having this issue for a newer version of xserver? Can you also provide the log mentioning the discrepancy between memory amounts?
Comment 5 Adam Jackson 2018-06-12 19:06:02 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


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.