On Sun, 2005-07-10 at 19:34 +0200, Stefan Richter wrote:
> Jul 10 18:30:17 shuttle kernel:   Type:   Unknown                            
> ANSI SCSI revision: 02

Sorry, that's expected: I had a patch that would identify it as RBC, but
there was another different one from someone else, and neither got
applied.  Can you try this:

http://sourceforge.net/mailarchive/message.php?msg_id=11828307

> Then silence.

Hmm, it sounds like the driver's not binding.  If you do a

ls -l /sys/class/scsi_device/<device>/device/driver

On this, do you see anything (it should be a link to the bound driver).

If there's nothing there, it sounds like sd.c is missing the RBC
attachment code, which was this hunk of the patch:

  @@ -1533,7 +1551,7 @@
        int error;
  
        error = -ENODEV;
 -      if ((sdp->type != TYPE_DISK) && (sdp->type != TYPE_MOD))
 +      if (sdp->type != TYPE_DISK && sdp->type != TYPE_MOD && sdp->type != 
TYPE_RBC)
                goto out;
  
        SCSI_LOG_HLQUEUE(3, printk("sd_attach: scsi device: <%d,%d,%d,%d>\n", 

Could you check that that's in sd.c

Thanks,

James


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to