Daisuke SUZUKI <daisuke@is26e1s08.jaist.ac.jp> wrote:
>>> "TANAKA" =3D=3D TANAKA Yoshitomo <serow@silkwood.rim.or.jp> writes:
>TANAKA> I just update 1.3.88 to 1.3.89 and BusLogic driver fails to
>TANAKA> initializing. Boot up console shows following.
>I have exactly same problem with BT-946C host adapter.
>My SCSI devices is following.
>>Attached devices:=20
>>Host: scsi0 Channel: 00 Id: 00 Lun: 00
>> Vendor: QUANTUM Model: EMPIRE_1080S Rev: 1220
>> Type: Direct-Access ANSI SCSI revision: 02
>>Host: scsi0 Channel: 00 Id: 02 Lun: 00
>> Vendor: RICOH Model: RO-3020E Rev: 2230
>> Type: Optical Device ANSI SCSI revision: 02
>>Host: scsi0 Channel: 00 Id: 06 Lun: 00
>> Vendor: TOSHIBA Model: CD-ROM XM-3501TA Rev: 2694
>> Type: CD-ROM ANSI SCSI revision: 02
>I have same HDD EMPIRE_1080S
**
>>Hmm,=20
>>I have had a problem with 1.3.1 driver.
>>I cannot Enable Tagged Queueing
>When Enable Tagged Queueing ( on 1.3.88 ), Boot Up console shows
>following errors...
[ deleted]
>Anyone have or had same problems?
>---daisuke
I have Problems with the Quantum Empire too;
I fisrt saw this Problems with my old configuration with an VLB 486-33
the Quantum was connected to an Adaptec 2842. With disconnect-reconnect=
i
enabled in hostadapter setup, the computer stopped during boot, while
probing for LUN=B4s. With disconnect disabled there were no problems. A=
s a
workaround , I added the drive to the "blacklist" in scsi.c.
FYI : with OS/2 there was the same Problem.
Lsst year I upgraded to an Asus TP4 board with P100 and NCR810
With the old Rev.4 NCR-driver I hadn=B4t any Problems ( It didn=B4t sup=
port
disconnect). When I upgraded to the recent rev17 NCR i got sometimes t=
he
Message: "emil kernel: attempt to access beyond end of device "and afte=
r
thst a corupted filesystem. I tracked down the problem and found :
The error only occured when accessing the Quantum _and_ accessing anoth=
er
sdsi-device at the same time. I tested this with Rel17 Rel16-1.2.13 and
NcrBsd2Linux with the same results. ... And OS/2 crashes too,without an=
y
error messages. I think now the QUANTUM Empire is broken, at least for
disconnect-reconnect. As a workaround I changed my partition scheme, no=
w
I can avoid concurrent accesses to the Empire ans another SCSI-Device
My current SCSI-configuration :
scsi-ncr53c7,8xx : at PCI bus 0, device 10, function 0
scsi-ncr53c7,8xx : NCR53c810 at memory 0xfbfe0000, io 0xe400, irq 10
scsi0 : burst length 8
scsi0 : NCR code relocated to 0x8c600 (virt 0x0008c600)
scsi0 : test 1 started
scsi0 : NCR53c{7,8}xx (rel 17)
scsi : 1 host.
scsi0 : target 0 accepting period 100ns offset 8 10.00MHz FAST SCSI-II
scsi0 : setting target 0 to period 100ns offset 8 10.00MHz FAST SCSI-II
Vendor: QUANTUM Model: LPS1080S Rev: 100D
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi0 : target 1 accepting period 100ns offset 8 10.00MHz FAST SCSI-II
scsi0 : setting target 1 to period 100ns offset 8 10.00MHz FAST SCSI-II
Vendor: Quantum Model: XP32150 Rev: 576D
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
scsi0 : target 4 accepting period 236ns offset 8 4.23MHz synchronous SC=
SI
scsi0 : setting target 4 to period 248ns offset 8 4.03MHz synchronous
SCSI
Vendor: TOSHIBA Model: CD-ROM XM-3401TA Rev: 0283
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
--=20
-----------------------------------------------------------------------=
-------
Markus <mk@emil.inka.de> (Markus Kossmann)
PS: Shouldn=B4t we move this thread to linux-scsi ?