Bug 52227 - PCI ID missing from pcitable in kudzu and supplemental drivers disk
Summary: PCI ID missing from pcitable in kudzu and supplemental drivers disk
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-21 20:01 UTC by Paul Timmins
Modified: 2014-03-17 02:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-21 20:49:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Paul Timmins 2001-08-21 20:01:32 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.7 i686)

Description of problem:
The GDT ICP Raid Controller Model GDT6518RS was not included, although the
gdth driver supports it.

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


How reproducible:
Always

Steps to Reproduce:
1. Insert a ICP GDT6518RS Raid controller into machine
2. Try to install on it (or if the machine is installed, watch kudzu not
detect it)
3. Bang head on table until you notice the pcitable is missing the entry
;-)
	

Actual Results:  Installer wouldn't work (It was the main drive in the
system)

Expected Results:  It should have installed (or detected in kudzu if you
pretend it's not the primary drive)

Additional info:

Suggested fix: Add the following line
0x1119  0x0138  "gdth"  "ICP Raid Controller|GDT 6518RS"
to the supplemental drivers diskette image's pcitable, as well as in
/usr/share/kudzu/pcitable
Comment 1 Bill Nottingham 2001-08-21 20:49:25 UTC 
Fixed in current roswell kudzu.
Note You need to log in before you can comment on or make changes to this bug.