Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Aug 1998 19:05:33 -0300 (ADT)
From:      Michael Richards <miker@scifair.acadiau.ca>
To:        scsi@FreeBSD.ORG
Subject:   Ada[ptec 2940U2W with a Seagate Cheetah 9.1 LVD drive
Message-ID:  <Pine.BSF.3.96.980807185023.199A-100000@scifair.acadiau.ca>

next in thread | raw e-mail | index | archive | help

Hi everyone.

I originally tried to install 3.0-current-cam on a jaz disk. Somehow I
ended up installing the non-cam version. Then I did a dumb thing, cvsup'd
the source and tried to compile a kernel. Very bad things, and to make
a long story short, I am starting over...

I just got one of those new fangled LVD 9.1 Gig Cheetah drives. Finally
something that my Adaptec 2940U2W will take advantage of... 

I ghosted my partions from my Quantum 6.4. 3 NTFS and 1 FAT partition.
FreeBSD wouldn't instll. Said that it couldn't create /dev/X. Figures
since I already had 4 primary partiions... Maybe this is an error that
needs to be addressed in sysinstall.

Anyway, I am all of a sudden getting:
panic: ahc0: brkadrint Data Path Parity error at seqaddr = 0x17d

This appears to be a bad thing since it auto-reboots. (The Panic part was
the first clue)

It happens when I am trying to boot from floppy with the latest boot CAM
floppy from CAM-19980712-SNAP.

The drive is the only one in the chain and I am using adaptec's cables
with their active terminator built in. The drive works correctly in NT. I
even yanked the cable for the SCSI-2 chain (6.4 gig drive, Jaz and CD-ROM)
and it comes up with the same problems.

So... Any ideas? Is it probable that this is a driver problem? What about
a hardware problem? I know NT had problems with IRQs.

Here is my hardware:
Tyan Tiger 2 MB
2 x 300MHX P II processors
Diamond Stealth G420 AGP graphics
Adaptec 2940U2W PCI controller
Seagate Cheetah 9.1G LVD SCSI drive
Quantum Fireball 6.4 gig SCSI-2 drive
IOMega Jaz
Pioneer SCSI CD-ROM
3Com network card (for DSL internet connection)
NE-32 Lance network card
196 MB RAM

I can't think of anything else that is relevant to this problem...

thanks
-Mike


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980807185023.199A-100000>