Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!hpg30a.csc.cuhk.hk!news.hk.net!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!solaris.cc.vt.edu!csugrad.cs.vt.edu!not-for-mail From: jaitken@csugrad.cs.vt.edu (Jeff Aitken) Newsgroups: comp.unix.bsd Subject: NCR PCI SCSI Problem Date: 13 Oct 1994 14:28:02 -0400 Organization: Virginia Tech Computer Science Dept, Blacksburg, VA Lines: 46 Message-ID: <37ju7i$2u5@csugrad.cs.vt.edu> Reply-To: jaitken@vt.edu NNTP-Posting-Host: csugrad.cs.vt.edu X-Newsreader: TIN [version 1.2 PL2] I recently ordered both a new Micropolis drive and the NCR PCI/Fast SCSI-II card for my PC (running FreeBSD-1.1.5). I installed the card and drive yesterday. I chose IRQ 11 for the card (for lack of any suggestions in the FAQ, I picked 11 because it "sounded right" :) and because the Adaptec line of cards use it) I finally got BIOS configured right (well maybe, DOS quit complaining ;) and then installed the DOS driver (just to test things out). After discovering a memory conflict with the ethernet card and the dos driver, all was well. I don't intend to let dos touch the new drive, but if/when I buy a CDROM it will be nice to use it for both OS's. Anyway, I then boot FreeBSD and grab the latest version of the ncr driver from freefall.cdrom.com. Read READ.ME, RELEASE.NOTES, and INSTALL.DOC a couple of times. Modify /sys/i386/conf/SYSTEMNAME as specified, patch autoconf.c, files.i386 (or whatever), and rebuild the kernel. I called the new kernel /386bsd.ncr Now, when I boot, I get the message from the NCR card about SDMS roms etc etc, then booteasy asks me which disk to boot from. I select disk 2, and boot FreeBSD. All appears to go well, and I get about 15 lines worth of stuff concerning PCI information. Looks like it found the NCR board just fine. Then, right after the message about "waiting for SCSI devices to settle", it starts spitting out error messages. There are (I think) two different messages, but they scroll by so fast I can't read them. I think one says something to the effect of ncr0: restart ??? and the other something like ncr0: fatal (maybe the word error in there?) followed by: 0xc000000000 or something like that. I'm not sure what could cause this. Just for grins, I grabbed the boot-copy floppy with the NCR driver compiled in. Same response. I even tried hard coding the IRQ in the config file: options "PCI_IRQ=0x000b" No luck - same problem. I have no further ideas as to what to do. Any help would be greatly appreciated. -- Jeff Aitken jaitken@vt.edu