I have an I/O Concepts X-Direct 40 (a 40-session 3270 terminal emulator)
connected via the external SCSI to our Alpha 3000/500S; it worked under
OSF/1 1.3. It is supposed to look like a tape drive to the operating
system, but now under OSF/1 version 3.2 I'm having trouble with it. (It
apparently should work under either OSF/1 version 2.x or 3.0, but I jumped
from 1.3 to 3.2.) The I/O Concepts server process dumps core fairly
quickly when it tries to start. I suspect that I may need to make a SCSI
CAM entry, but I'm not sure...
When the kernel probes the device, these messages are logged (retrieved
via uerf):
tz8 at scsi1 bus 1 target 0 lun 0
_(KENN)cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sm_command
Invalid command phase
cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sim_err_sm
Target went to command phase
cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sim_err_sm
Target went to data in phase
fb0 at tc0cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sim_err_sm
Target went to status phase
cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sim_err_sm
Target went to message in phase
cam_logger: CAM_ERROR packet
cam_logger: bus 1 target 0 lun 0
sim_err_sm
Target went to bus free phase
When I use "scu" to "scan edt" and "show device" on the X-Direct's /dev
device, I get:
SCSI Bus ID: 1
SCSI Target ID: 0
SCSI Target LUN: 0
Peripheral Device Type: Sequential Access
Peripheral Qualifier: Peripheral Device Connected
Device Type Qualifier: 0
Removable Media: Yes
ANSI Version: SCSI-1 Compliant
ECMA Version: 0
ISO Version: 0
Response Data Format: ANSI SCSI-1
Additional Length: 16
Vendor Identification: KENN
Product Identification:
Firmware Revision Level:
If anyone has any ideas, I'd be grateful. I haven't heard back from I/O
Concepts about this yet :-(
Guy Helmer, Dakota State University Computing Services - ghelmer_at_alpha.dsu.edu
Received on Tue Apr 11 1995 - 10:11:29 NZST