Re: 2.0.27 major problems #1 -- 3c59x driver.

Brian Lalor (blalor@hcirisc.cs.binghamton.edu)
Thu, 13 Feb 1997 10:15:25 -0500 (EST)

I'm currently using the 2.1.25 kernel and I'm running into some SCSI
problems. I'm using an IBM PS/2 Model 95 (MCA) with an IBM MCA SCSI host
adapter. I've been able to boot using an MCA-patched 2.0.7 kernel and
the machine has worked flawlessly. Now that I'm using the newer kernel,
my drives (w hard drives and 1 CD-ROM) appear as different luns on ID 0
and the CD-ROM doesn't work at all. The first time I booted after
installing the CD-ROM drive, it was recognized as (I believe) lun 3 on ID
0, but subsequent boots fail to get it to be recognized at all. The
CD-ROM is a Sony CDU-76S set to id 2 with parity enabled and
allow/disallow (?) removed.

This is from /var/log/messages:
Feb 13 08:44:38 blalor kernel: IBM MCA SCSI: IBM SCSI Adapter w/Cache found in s
lot 1, scsi id=7.
Feb 13 08:44:38 blalor kernel: IBM MCA SCSI: logical device found at ldn=0.
Feb 13 08:44:38 blalor kernel: IBM MCA SCSI: logical device found at ldn=1.
Feb 13 08:44:38 blalor kernel: IBM MCA SCSI: logical device found at ldn=2.
Feb 13 08:44:38 blalor kernel: scsi0 : IBMMCA
Feb 13 08:44:38 blalor kernel: scsi : 1 host.
Feb 13 08:44:38 blalor kernel: Vendor: IBM Model: 0661467 Rev:
G o
Feb 13 08:44:38 blalor kernel: Type: Direct-Access ANSI
SCSI revision: 02
Feb 13 08:44:38 blalor kernel: Detected scsi disk sda at scsi0, channel 0, id 0,
lun 0
Feb 13 08:44:38 blalor kernel: Vendor: FUJITSU Model: M2684S-512 Rev:
2035
Feb 13 08:44:38 blalor kernel: Type: Direct-Access ANSI
SCSI revision: 02
Feb 13 08:44:38 blalor kernel: Detected scsi disk sdb at scsi0, channel 0, id 0,
lun 2
Feb 13 08:44:38 blalor kernel: scsi : detected 2 SCSI disks total.
Feb 13 08:44:38 blalor kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 776456 [379 MB] [0.4 GB]
Feb 13 08:44:38 blalor kernel: SCSI device sdb: hdwr sector= 512 bytes.
Sectors= 1039329 [507 MB] [0.5 GB]

I'd appreciate any help you can give me.

I'm also getting some "oops"'s on boot. What's the best way to capture
these, as they don't seem to appear in /var/log/messages?

Thanks in advance,
Brian

_____________________________________________________________________________
B r i a n L a l o r blalor@hcirisc.cs.binghamton.edu
http://hcirisc.cs.binghamton.edu/~blalor consp32@binghamton.edu