Hi everyone --

I had posted a problem a week ago or so about a new Tekram DC 310 scsi
controller (uses the sym53c810 chip) that I'm trying to get working. 
Well, I think I've gotten a little further, but I'm still unsuccessful
at getting everything working.

The situation is, I have a Pentium-based Redhat 6 system, with a fresh
2.3.5 kernel.  I just re-built the kernel with support (not modular) for
the sym53c8xx and ncr53c8xx.  The only scsi device I have is a Umax
scanner...it has ID 1.  The controller is ID 0.  Sound simple enough?

Still, I get some errors during the boot process that I can't decipher. 
Take a look:

Jun 11 20:18:19 localhost kernel: sym53c8xx: at PCI bus 0, device 12,
function 0
Jun 11 20:18:19 localhost kernel: sym53c8xx: setting
PCI_COMMAND_PARITY...(fix-up)
Jun 11 20:18:19 localhost kernel: sym53c8xx: 53c810a detected with
Symbios NVRAM
Jun 11 20:18:19 localhost kernel: sym53c810a-0: rev=0x23,
base=0xdf800000, io_port=0xd000, irq=4
Jun 11 20:18:19 localhost kernel: sym53c810a-0: Symbios format NVRAM, ID
0, Fast-10, Parity Checking
Jun 11 20:18:19 localhost kernel: sym53c810a-0: initial
SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/ce/a0/01/00/00
Jun 11 20:18:19 localhost kernel: sym53c810a-0: final  
SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/ce/a0/00/08/00
Jun 11 20:18:19 localhost kernel: sym53c810a-0: resetting, command
processing suspended for 2 seconds
Jun 11 20:18:19 localhost kernel: sym53c810a-0: restart (scsi reset).
Jun 11 20:18:19 localhost kernel: ncr53c8xx: at PCI bus 0, device 12,
function 0
Jun 11 20:18:19 localhost kernel: ncr53c8xx: IO region 0xd000 to 0xd07f
is in use
Jun 11 20:18:19 localhost kernel: scsi0 : sym53c8xx - version 1.3c
Jun 11 20:18:19 localhost kernel: scsi : 1 host.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: command processing
resumed
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6
6@002ffe45 resid=5.
Jun 11 20:18:19 localhost atd: atd startup succeeded
Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a
ff) @c3fe7000.
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6
6@002ffe45 resid=5.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a
ff) @c3fe7000.
Jun 11 20:18:19 localhost kernel: scsi0 channel 0 : resetting for second
half of retries.
Jun 11 20:18:19 localhost kernel: SCSI bus is being reset for host 0
channel 0.
Jun 11 20:18:19 localhost kernel: sym53c8xx_reset: pid=1 reset_flags=1
serial_number=0 serial_number_at_timeout=0
Jun 11 20:18:19 localhost kernel: sym53c810a-0: resetting, command
processing suspended for 2 seconds
Jun 11 20:18:19 localhost kernel: scsi0: device driver called
scsi_done() for a syncronous reset.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: restart (scsi reset).
Jun 11 20:18:19 localhost kernel: sym53c810a-0: command processing
resumed
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6
6@002ffe45 resid=5.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a
ff) @c3fe7000.
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6
6@002ffe45 resid=5.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a
ff) @c3fe7000.
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6
6@002ffe45 resid=5.
Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a
ff) @c3fe7000.
Jun 11 20:18:19 localhost kernel: scsi : detected
total.                                                        


I don't know if these messages are good, bad, or just ugly.  I do know
that when I do a "cat /proc/scsi/scsi" I get a "Attached devices:
none".  I guess that means it can't see the scanner.  I do have the
scanner powered up before booting.  

Like I said, the only scsi devices are the scanner, which I know is
terminated, and the host adapter.  So what could the problem be?

Please help!  Getting desparate and growing old.

derek

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to