On Sat, 28 Aug 1999, Chuck Lever wrote:
First, quoting some debug infos:
> [<194|0:400|fe002038:86830000>TCCB=b20 STAT=85/ff
- STAT=85 means SELECTION TIMEOUT
- 194 is a quirk bitmap and should be zero.
- CCB=b20 should be c0088b20, but it is a driver misprinting.
So, only the 194 which is decimal (0xc2) is actually weird.
Could you confirm that value, please.
On Sat, 28 Aug 1999, Chuck Lever wrote:
> i'm still stuck with this Intel server that won't detect its SCSI drivers
> during system boot.
>
> the system:
>
> Intel quad P-III Xeon, 512K L2 cache, 500Mhz, 512Mb RAM
> S450NX mb with Intel 82450NX PCIset and PIIX4 ISA bridge
> built-in Symbios SCSI controllers - one NCR53c810A and
> two NCR53C896
> the drives are a 9.1G Seagate cheetah and two 4.2G barracudas
> all attached via SCA through a back-plane
>
> installing RH6.0 works fine, and the system detects and boots from the
> 9.1G drive. if i d/l and install any Linux kernel, 2.2.5 -> 2.3.15,
> the drive partition tables become corrupted, and all kernels refuse to
> boot.
>
> Doug suggested lilo problems. it turns out, that's half the problem. if
> i run "lilo" as soon as i boot up after installing RH6.0 with the
> installed /etc/lilo.conf unchanged, no partition table corruption occurs,
> and i can later install any kernel i want, and still switch back to the
> 2.2.5-15 kernel without difficulty.
>
> however, *only* the 2.2.5-15 kernel will detect the drives. no other
If you mean that a 2.2.5-15 kernel you build by your-self does boot, then
we should look into the difference between 2.2.5 and 2.2.5-15.
Could you confirm that ?
If you didn't tried building a 2.2.5-15 kernel by yourself, you should do
it, IMO, since comparing a not working 2.2.5 with a working 2.2.5-15 only
makes sense if we are using the same kernel configuration and tools to
build both of them.
> kernel i've booted on this machine will detect the drives. i've tried
> using initrd and the NCR module (that is, not built in to the kernel).
> i've tried using the Sym53C8xx driver. i've tried using 2.2 and 2.3
> kernels. i've tried disabling multi-LUN detection. nothing works.
> i enabled debugging in the NCR driver, and this is what i see when it
> tries to detect the drives... here's the last message, but they all look
> like this, even on devices that are supposed to be present, except
> "queuepos" goes up by one for each device, and of course, the device ID is
> different for each.
[ ... debug info at the beginning of this mail ]
G�rard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
