On Wed, 21 Feb 2001, Neil Hollow wrote:

> Thanks for the reply.  No dmesg shows a scsi device found but nothing other
> than that, cat  /proc/scsi/scsi gives no devices.  A thought has occured to
> me do I need to remove ide support in the kernel ( I have 4 such devices) or
> is this just neat way of forcing emulation?  The sg module is only being
> loaded using insmod currently, I will hack the conf.modules file (I  boot
> from loadlin).  Ta.  NH
>
I forget the exact syntax, but you need something like "hdc=ide-scsi" as
part of your loadlin command line.  You do not have to remove IDE CD
support from your kernel.  The your CD-rom should apear in
/proc/scsi/scsi.  But your SCSI CD-burner should apeare in it now.  Did
you compile SCSI support in your kernel, or as a module?  (sr_mod)
generic SCSI support?  (sg module.)  I am assuming that it is apearing
as a module.

One other thing to check.  Does "ls -l /proc/scsi" produce two SCSI
adapters?  One for the real SCSI adapter, and one for the ide-scsi
emulator?  Here is one of my systems with two real SCSI adapters.

dr-xr-xr-x    2 root     root            0 Feb 21 09:18 advansys
-rw-r--r--    1 root     root            0 Feb 21 09:18 scsi
dr-xr-xr-x    2 root     root            0 Feb 21 09:18 sym53c8xx

[mikkel@slave mikkel]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: DCHS04U          Rev: 6464
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: DCHS04U          Rev: 6464
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
  Vendor: IBM OEM  Model: 0664M1H       YQ Rev: DG05
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
  Vendor: ARCHIVE  Model: Python 25501-XXX Rev: 5.45
  Type:   Sequential-Access                ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 06 Lun: 00
  Vendor: MATSHITA Model: CD-ROM CR-8005A  Rev: 4.0i
  Type:   CD-ROM                           ANSI SCSI revision: 02

Now, depending on the driver, /proc/scsi/<adapter name>/<0 or 1> may or
may not show what is connected to it.  The Symbios driver shows almost
nothing when you run "cat /proc/scsi/sym53c8xx/0", but the Advansys
driver shows about two pages of info when you run
"cat /proc/scsi/advansys/1".  The number on the end of the command is
determined by the order of the SCSI controllers.  On my system, the
Symbois controller comes first, and the Advansys controller in the
second one.  For you, the real SCSI controller will probably come first,
and the ide-scsi controller second, but it may be the other way around.
About the only difference it makes is what CD will be /dev/scd0 and
/dev/scd1.  The one off of controller 0 will be the first CD.

Here is what the entry for my CD writer looks like.  (Different
machine.)

[mikkel@master mikkel]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 05 Lun: 00
  Vendor: YAMAHA   Model: CRW4416S         Rev: 1.0g
  Type:   CD-ROM                           ANSI SCSI revision: 02

Your CD burner should show up as long as you compiled the right driver
for your SCSI card into the kernel.  It is independant of havign SCSI
CD, or SCSI tape support.  If it doesn't show, but the adapter does,
then you probably compiled in the wrong card, or it is an ISA card, and
the settings are wrong.  If you don't have a directory entry in
/proc/scsi for the card, then you definitly have the wrong card, or the
wrong settings.

Mikkel
-- 

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to