As some of you know, I've recently converted to a full scsi system.  I compiled
a 2.4.0-test8 kernel with the following options:

SCSI support
SCSI disk support
SCSI CD-ROM support
SCSI generic support
SCSI low-level-drivers --->Adaptec AIC7xxx support
SCSI low-level-drivers --->Enable Tagged Command Queuing

Thats it.  When I boot up things appear normal at first:

(scsi0) <Adaptec AIC-7892 Ultra 160/m SCSI host adapter> found at PCI 0/9/0
(scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 392 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.1/5.2.0
       <Adaptec AIC-7892 Ultra 160/m SCSI host adapter>
scsi : 1 host.
(scsi0:0:0:0) Synchronous at 160.0 Mbyte/sec, offset 63.
      Vendor: SEAGATE   Model: ST318451LW        Rev: 0003
      Type:   Direct-Access                      ANSI SCSI revision: 03
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:0:1:0) Synchronous at 20.0 Mbyte/sec, offset 8.
      Vendor: PLEXTOR   Model: CD-R   PX-W124TS  Rev: 1.05
      Type:   CD-ROM                             ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0
scsi : detected 1 SCSI cdrom 1 SCSI disk total.
sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.11
SCSI device sda: hdwr sector= 512 bytes. Sectors= 35843671 [17501 MB] [17.5 GB]
Partition check:
      sda: sda1 sda2 sda3

If I'm reading this right, it found my host adapter, found the HD, and the 
CD-ROM.  The partition check shows sda1 sda2 sda3.  All which appears right
to me.  Then the follow appears further down the dmesg sequence:

SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35843671 [17501 MB] [17.5 GB]
 sdb: sdb1 sdb2 sdb3

Excuse me?  sdb?  I only have one HD in the system which is broken into three
partitions.  Windoze, swap, linux.  What does the second entry mean?

OK, finally onto the woes part.  When I run cdparanoia -B (burn the entire cd
into individual files) I get the following interesting error:

Checking /dev/cdrom for cdrom...
      Testing /dev/cdrom for cooked ioctl() interface
            /dev/sr0 is not a cooked ioctl CDROM.
      Testing /dev/cdrom for SCSI interface
            No generic SCSI device found to match CDROM device /dev/sr0

Well, isn't that interesting? My user account belongs to the cdrom group so I
should have access to the following:

stimpy:~$ ls -l /dev/sr0
brw-rw----    2 root     cdrom     11,   0 Jul  5 12:44 /dev/sr0

stimpy:~$ ls -l /dev/cdrom
lrwxrwxrwx    1 root     root            3 Sep 22 07:11 /dev/cdrom -> sr0

So /dev/cdrom is pointing to the right place and I have access to sr0, dmesg
is showing that it recognizes the cdrom, I've included generic scsi support
in the kernel, why on earth isn't cdparanoia able to use it?  I hope I'm
missing something terrible simple because I'd hate to have spent all that money
to convert to a scsi system and not be able to use it. :(

Regards,

Wm

Reply via email to