Bug 121223 - hwbrowser correctly identified the graphics card as a Qudro 4 900 series; but the driver selected for it was Nvidia GeForece 4 MX (generic)
Summary: hwbrowser correctly identified the graphics card as a Qudro 4 900 series; but...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kudzu
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-19 13:13 UTC by Alex Bruno
Modified: 2014-03-17 02:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-19 16:34:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Bruno 2004-04-19 13:13:48 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
When looking at a hwbrowser window of installed components, it
correctly id's the graphics card as a Quadra 4 900 series card.  It
loaded, however, Nvidia GeForece 4 MX (generic) drivers for the card.
 There isn't any apparent corruption or loss of graphical abilities,
but the probed results are not being correctly passed to the driver
selection for X.

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

How reproducible:
Always

Steps to Reproduce:
1.Have Quadra 4 900 series card.
2.Proceed through a graphical installation; noting the probed values given
3.Post-install, look at the output of hwbrowser and compare what was
detected, and what driver was installed.
    

Actual Results:  Same as described in bug description

Expected Results:  Should have ID'd a Quadra 4 900 series, and
installed a Quadra driver for X.

Additional info:
Comment 1 Bill Nottingham 2004-04-19 16:34:07 UTC 
Fixed in hwdata CVS. May appear in a future update release if we
rebuild for other reasons, otherwise, will be in RHEL 4.
Note You need to log in before you can comment on or make changes to this bug.