Red Hat Bugzilla – Bug 140844
Display Settings Does not Allow for VideoRam Configuration
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
The video chip vendor (VIA) documentation recommends the setting of
the xorg.conf video driver parameter VideoRam in order to take
advantage of Shared RAM that is available on the Motherboard. My MSI
KM3M-V motherboard can support up to 64MB. When selecting my video
driver (VESA (Generic), or S3 Unichrome) using the
system-config-display panel, it does not include any fields for
assigning values to this configuration parameter.
VIA literature demonstrates the setting of this value on an older
version of Redhat, probably in the installation process.
I have manually set this value in the xorg.conf file to the following
value (for 32MB):
in order to take advantage of the 32MB Shared RAM setting on the BIOS.
Needless to say, video performance has improved significantly.
Please make this setting available in the Display Settings panel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open the Display Settings panel
2. Click on the Hardware Tab
3. Click on the Configure button for the Video Card
4. Select the desired Driver, then click OK.
Actual Results: The driver is selected, but there are no fields
available for more detailed driver settings.
Expected Results: Fields should appear for more specific
configuration options, such as using Shared RAM for the video driver.
To my recollection, detailed driver settings such as this were
available in Redhat9.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.