Date: Tue, 25 Apr 1995 11:10:46 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: faulkner@mpd.tandem.com (Boyd Faulkner) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G Message-ID: <199504251810.LAA10369@gndrsh.aac.dev.com> In-Reply-To: <9504251745.AA03681@olympus> from "Boyd Faulkner" at Apr 25, 95 12:45:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > > > > > > > > > > > > > > > > Rod, > > > > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > > > > boot floppy and the fixit disk do not. Everything is cool until the PCI > > > > > is found. > > > > > > > ... > > > > I tried all my boards here, and every one of them works. I will bring > > > > in a PCI/I-486SP3G this week and see if I can track this down. You > > > > mention that this works with a -current kernel, what happens if > > > > you put that kernel on floppy? Or if you copy the floppy kernel to > > > > hard disk as /kernel.flp and try to boot it? > > > > > > > I tried copying the boot floppy to the hard disk and it still will not boot. > > > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry > > > that I do not have in CATBURG. > > > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > > > > > Could this be it? > > > > Could be, but it worked here with the NCR810's on 4 different systems, > > and I am using the same disk drive you have (only more of them :-)). > > > > Do you have anything besides the DEC3053L disk on you scsi bus now? > > You also say that a -current kernel works fine, what happens if > > you build BOOTFLP from you -current sources and try to boot it? > > > > (I know, lots of questions and no real answers :-(). > > > > >From /var/log/messages > > : ncr0: restart (scsi reset). > : ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) > : ncr0 waiting for scsi devices to settle > : (ncr0:0:0): "CDC 94171-9 5955" type 0 fixed SCSI 1 > : sd0(ncr0:0:0): Direct-Access 286MB (586458 512 byte sectors) > : (ncr0:1:0): "MAXTOR MXT-1240S F02S" type 0 fixed SCSI 2 > : sd1(ncr0:1:0): Direct-Access > : sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > : 1183MB (2423457 512 byte sectors) > : (ncr0:2:0): "MAXTOR 7245-SCSI 1057" type 0 fixed SCSI 1 > : sd2(ncr0:2:0): Direct-Access 234MB (479656 512 byte sectors) > : (ncr0:3:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 Can you remove this easily? I have seen CD-ROM drives hang the NCR code up :-(. And turning off the sync negotiation seems to make the problem worse, not better :-(. > : cd0(ncr0:3:0): CD-ROM cd present.[12571 x 2048 byte records] > : (ncr0:4:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 > : st0(ncr0:4:0): Sequential-Access st0: Archive Viper 150 is a known rogue > : density code 0x0, drive empty > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > : sd3(ncr0:5:0): Direct-Access > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > : sd3 could not mode sense (4). Using ficticious geometry Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that does not understand a mode sense to page 4?? Very strange! > : 382MB (782600 512 byte sectors) > : chip1 <Intel 82378IB PCI-ISA bridge> rev 3 on pci0:2 > : vga0 <Display device> rev 0 on pci0:6 > : pci0: uses 8388864 bytes of memory from fb000000 upto fbfef0ff. > : pci0: uses 256 bytes of I/O space from e800 upto e8ff. > > The IBM is a new acquisition and I removed all drives but the cdrom and the > tape and it still didn't work. Of all the devices we have the most problem with it is CDROM and Tape drives, I know this is probably painfull to remove these, but it will help to track down the problem. > Could a jumper on the motherboard make a difference. I went through them to > make sure they made sense. Perhaps I should again. I don't remember if I > changed any or not. The board as shipped by me should have been set correctly, with perhaps the exception of the SCSI terminator since you are running both internal and external devices. Make sure you turned of the terminator on the motherboard. > The bios are as you sent them. Standard but with write-through amd > ISA gating disabled. Okay, good, that eliminates that set of questions! > I am rebuilding the boot floppy now and will try it tonight. If it fails, > I will rebuild with the > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > line removed and try that. Okay, thanks. > > Why the restriction? Attempt to fix some people's system that hang during sync negotiation due to devices that claim to be SCSI-2 compliant, but get this part of the spec wrong. Also fixes some very old SCSI-I devices that lock up if you try to do sync negotiation with them. It was suppose to make it better, but it may infact be making things worse :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504251810.LAA10369>