Partially solved (was: Problems with AXi board)

"T. Ribbrock" <[email protected]>
Newsgroups gmane.linux.aurora.devel
Message-ID <[email protected]>
On Sat, Dec 27, 2003 at 03:08:46AM +0100, T. Ribbrock wrote:
[...]
> Also, I noticed that the external drive is not run as a UW drive, but
> just as "fast,wide". Excerpt from dmesg:
[...]
> sym53c875-2-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100.0 ns, offset 16)
> SCSI device sdb: 35566480 512-byte hdwr sectors (18210 MB)
>  sdb: sdb1
[...]

This part is solved - I remembered messing with SCSI drivers before in
one of my U5's and in fact writing about it to the list some time back.
The solution is the same as it was then: Instead of using the
"sym53c8xx" driver, I'm now using "sym53c8xx_2". The dmesg now looks
like this:

sym.128.2.0: setting PCI_COMMAND_PARITY...
sym.128.2.0: setting PCI_COMMAND_INVALIDATE.
sym.128.1.0: setting PCI_COMMAND_INVALIDATE.
sym.128.1.1: setting PCI_COMMAND_PARITY...
sym.128.1.1: setting PCI_COMMAND_INVALIDATE.
sym0: <810a> rev 0x23 on pci bus 128 device 2 function 0 irq 4,7c0
sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
sym0: SCSI BUS has been reset.
sym1: <875> rev 0x14 on pci bus 128 device 1 function 0 irq 4,7e0
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
sym2: <875> rev 0x14 on pci bus 128 device 1 function 1 irq 4,7e0
sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
sym2: SCSI BUS has been reset.
scsi0 : sym-2.1.17a
scsi1 : sym-2.1.17a
scsi2 : sym-2.1.17a
  Vendor: IBM       Model: DCAS-34330W       Rev: S65A
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor: EXABYTE   Model: EXB-85058HE-0000  Rev: 0112
  Type:   Sequential-Access                  ANSI SCSI revision: 02
  Vendor: PLEXTOR   Model: CD-ROM PX-32TS    Rev: 1.03
  Type:   CD-ROM                             ANSI SCSI revision: 02
sym1:1:0: tagged command queuing enabled, command queue depth 16.
  Vendor: HP        Model: 18.2GB C 80-F610  Rev:     
  Type:   Direct-Access                      ANSI SCSI revision: 02
sym2:0:0: tagged command queuing enabled, command queue depth 16.
Attached scsi disk sda at scsi1, channel 0, id 1, lun 0
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
sym1:1: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
SCSI device sda: 8467200 512-byte hdwr sectors (4335 MB)
Partition check:
 sda: sda1 sda2 sda3 sda4
sym2:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
SCSI device sdb: 35566480 512-byte hdwr sectors (18210 MB)
 sdb: sdb1

All is recognized the way it should be and the 18GB drive gives me a
nice 36MB/s now (according to hdparm). :-)

The SABRE0 error, however, is still present. I've checked again and it
seems to occur on almost every boot.

Cheerio,

Thomas
-- 
-----------------------------------------------------------------------------
                Thomas Ribbrock    http://www.ribbrock.org 
  "You have to live on the edge of reality - to make your dreams come true!"
_______________________________________________
Aurora-sparc-devel mailing list
[email protected]
http://lists.auroralinux.org/mailman/listinfo/aurora-sparc-devel
Aurora FAQ: http://www.ecs.soton.ac.uk/~mas01r/aurorafaq.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.