Bug 51348 - Roswell unable to recognize Sanyo CRD-1332P CDROM
Summary: Roswell unable to recognize Sanyo CRD-1332P CDROM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-09 18:52 UTC by Wendy Hung
Modified: 2007-04-18 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-09-04 18:05:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Wendy Hung 2001-08-09 18:52:38 UTC
Description of Problem:
Unable to install RH 7.1 on an IBM Netfinity 5000 system,
Boots off of CD OK, but cannot read CD at selecting CD media screen.
Install using boot diskette also fails.
Installing with "linux ide=nodma" works.

contents of cat /proc/ide/hda/model :
SANYO CD-ROM CRD-1332P

How Reproducible:
Every time.

Actual Results:
Cannot read CD at selecting CD media screen.  Installation cannot proceed.

Expected Results:
CDROM model should have been added to the blacklist  per Bugzilla #45169.

Comment 1 Glen Foster 2001-08-09 20:01:19 UTC
This defect is considered MUST-FIX for Fairfax.

Comment 2 Arjan van de Ven 2001-08-13 14:16:03 UTC
Added to the blacklist in 2.4.7-0.14.1

Comment 3 Wendy Hung 2001-08-21 19:11:56 UTC
Still unable to install without having to pass "linux ide=nodma" when 
installing RH 7.2 RC1.

Comment 4 Arjan van de Ven 2001-08-22 06:56:52 UTC
As it appears that the blacklist is ignored in this case, I'd love to know which
chipset (eg IDE driver) this is, so I can check the driversource for this.

Comment 5 Wendy Hung 2001-08-23 18:15:43 UTC
Reliance Open South Bridge (ROSB3) chipset

Comment 6 Wendy Hung 2001-09-04 18:05:13 UTC
Works with RH 7.2 RC2.

Comment 7 Arjan van de Ven 2001-09-04 18:06:47 UTC
Works with RH 7.2 RC2. -> closing as fixed


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