From owner-freebsd-current Tue Apr 25 10:45:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA03367 for current-outgoing; Tue, 25 Apr 1995 10:45:37 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA03361 for ; Tue, 25 Apr 1995 10:45:35 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id MAA13932; Tue, 25 Apr 1995 12:45:20 -0500 Received: by olympus (4.1/TSS2.1) id AA03681; Tue, 25 Apr 95 12:45:19 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504251745.AA03681@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 12:45:18 -0500 (CDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251718.KAA10270@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 10:18:07 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 3681 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > 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 :-(). > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > >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 : 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 : 382MB (782600 512 byte sectors) : chip1 rev 3 on pci0:2 : vga0 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. 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 bios are as you sent them. Standard but with write-through amd ISA gating disabled. 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. Boyd Why the restriction? -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________