Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 72428 - Manually specified Video Ram value not used?
Manually specified Video Ram value not used?
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
Blocks: 67218 79579
  Show dependency treegraph
Reported: 2002-08-23 14:26 EDT by Dylan Pack
Modified: 2007-04-18 12:45 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-27 14:03:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dylan Pack 2002-08-23 14:26:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv: Gecko/20020508

Description of problem:
During the hard drive install it auto detects my graphics card correctly. 
TNT2 Nvidia card. However, it only detects 4mb of memory when it actually has
32mb. That's fine so I change it to 32mb and continue with the installation.
Later once its all done I go into "Display" on the Gnome menu and it says "4mb"
again I re-select 32mb and it works and runs much faster! Just an annoyance more
than anything. If I never checked it would be going slow the whole time. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Install select 32mb for video card
2.In display it shows 4mb
3.Change to 32mb

Expected Results:  Should change to 32mb in install

Additional info:
Comment 1 Michael Fulbright 2002-08-26 16:41:27 EDT
I'll look into this
Comment 2 Michael Fulbright 2002-12-09 15:31:12 EST
Appears to work for me now.
Comment 3 Michael Fulbright 2002-12-20 12:38:25 EST
Time tracking values updated
Comment 4 Jay Turner 2003-01-27 14:03:01 EST
Fix confirmed with re0127.nightly.

Note You need to log in before you can comment on or make changes to this bug.