[ale] multi-processor vs. Tape Drive

[Greg Freemyer]

On 5/25/05, James McFarland <stalax at earthlink.net> wrote:
> 
> When I  use "modprobe st "It shows up under lsmod.  However, the device (/dev/st0) is not available.  Do I need to create it manually?  If so, can you point to someplace with the appropriate instructions?
> 
> It also isn't present under /proc/scsi/scsi:
> 
> SMP Kernel:
> [root at pheonix ~]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
>   Vendor: ADAPTEC  Model: oldmail-RAID5    Rev: V1.0
>   Type:   Direct-Access                    ANSI SCSI revision: 02
> 
> 
> SP Kernel:
> [root at pheonix ~]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
>   Vendor: ADAPTEC  Model: oldmail-RAID5    Rev: V1.0
>   Type:   Direct-Access                    ANSI SCSI revision: 02
> Host: scsi0 Channel: 02 Id: 06 Lun: 00
>   Vendor: QUANTUM  Model: DLT VS160        Rev: 2500
>   Type:   Sequential-Access                ANSI SCSI revision: 02
> 

I would say that it not showing up in /proc/scsi/scsi is a kernel bug.

FYI: With SuSE's recent 2.4 kernel's I see my tape drive in boot.log
(similar to above), but I don't get /dev/st0 until I run stinit.  That
requires a config file that maps the above Vendor/Model/Rev to
specific tape drive capabilities.  Thus step 1 is to get the SCSI
recognition, step 2 is to get the /dev/st0 device setup.

Greg