> Since kernel >2.1.107, i.e. ncr53c8xx-3.0e, linux does no longer boot
> on this machine:
>
> - IBM DCHS39100-UW, 9GB hard disk, id 1, autostart active,
> active termination, parity + TISN active
> | 25cm uw/68pin ribbon-cable
> - SYM8751SP scsi adapter
> | 31cm 50pin ribbon
> - toshiba XM-3401B cd-rom, id 4, no term, parity enabled,
> Burst: 4.2MBytes/sec(sync), 1.5MB/s(async)
> | 35 cm
> - IBM DFHS34320, 4.5GB hard disk, id 0, autostart,
> active termination, parity + TISN active
>
> This works pretty well since 14 months, up to kernel 2.1.107.
>
> Newer kernels give
>
> > ncr53c875-0-<0,0>: M_REJECT received (75:8).
The value 75 in this message from the driver is quite weird.
It does not look like a legal SCSI message.
It should normally be identical to the second value (which is a NOOP
message) or be an IDENTIFY message which is > 80 (all values in hexa).
Could you confirm me it is the message the driver actually displayed.
> Last .config for 2.1.119 says:
>
> > CONFIG_SCSI_NCR53C8XX=y
> > CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=1
> > CONFIG_SCSI_NCR53C8XX_MAX_TAGS=4
> > CONFIG_SCSI_NCR53C8XX_SYNC=0
> > # CONFIG_SCSI_NCR53C8XX_PROFILE is not set
> > # CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
DEFAULT_TAGS >= 8
MAX_TAGS = 32
SYNC = 20
Is a better config for your hard disks, IMHO.
> There is no (scsi) error when i disconnect the XM-3401B cd-rom.
>
> There is no error, as long as the XM-3401B is disconnected, when i add
> both a HP 35480A dat drive (typ: 366-732kB/sec), id 3 and a fujitsu
> m2511a MO disk drive (Burst: 4.0MB/sec/sync, 2.7MB/s/async), id 2.
>
> I may even reduce cabling distance to 10cm, with 170cm total length and
> use passive termination at the scsi II end without getting errors for
> 2.1.11[79], as long as the cd-rom is not connected.
>
> Any hints (besides discarding that outdated 2.2 speed caddy needing
> cd-rom drive)?
I still use such a CD. It is a bit slow but is a high quality device.
It never failed for me for 3 years.
It should be interesting to try other driver versions on your system,
I suggest to try first:
1 - kernel 2.1.119 + driver 2.5f (just have to replace driver files by
kernel 2.1.107 driver files)
2 - kernel 2.1.107 + driver 3.0g (get driver files from linux-2.1.119)
3 - kernel 2.1.119 with latest driver version available at:
ftp.tux.org/pub/roudier/896/ (1 tar + 3 patches).
and to let me know which configs fail and which succeed.
Regards,
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html