Bug 28336 - [aic7xxx]SCSI CDROM not found by cdrecord -scanbus. SCSI Zip drive is found and it is found in 7.0 release.
Summary: [aic7xxx]SCSI CDROM not found by cdrecord -scanbus. SCSI Zip drive is found ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Doug Ledford
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-19 20:11 UTC by Sean McHenry
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-02-21 15:07:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Sean McHenry 2001-02-19 20:11:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.16-22 i686)


Under 7.0, all SCSI devices are found.  Under fisher, ZIP is found but not
CDROM at 0,0,0.  Could burn CDs under 7.0.  Uses Aic7xxx.o.  Loading but
not finding device 0.

Reloaded 7.0 to make sure it wasn't something I did.  Found CDROM again.

Reloaded fisher, again not found.

oddly enough however, I was given an entry in fstab for both CDROM and
CDROM1.  System seems to be aware it exists but aicxxx isn't allowing it to
be seen?

Reproducible: Always
Steps to Reproduce:
1.  Load fisher
2.  try to read from CDROM
3.  run cdrecord -scanbus
	

Actual Results:  CDROM not found but had fstab entries

Expected Results:  read and record CDROMs

Comment 1 Sean McHenry 2001-02-19 20:18:44 UTC
Forgot to mention, I have both an IDE and SCSI cdrom drives, hence the 2 entries
in fstab.  they were listed correctly, as IDE and SCSI.

Sean

Comment 2 Sean McHenry 2001-02-19 20:20:02 UTC
Last thing, my system is the same as listed in bug 28334.  Sean

Comment 3 Sean McHenry 2001-02-19 20:22:30 UTC
Last thing, my system is the same as listed in bug 28334.  Sean

Comment 4 Glen Foster 2001-02-21 15:07:19 UTC
We (Red Hat) should really try to resolve this before next release.

Comment 5 Doug Ledford 2001-02-21 23:41:50 UTC
This was a bug in aic7xxx-6.0.8BETA that has been resolved by aic7xxx-5.2.3 and
aic7xxx-6.1.0 and later.


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