Date: Mon, 5 Aug 1996 19:38:33 +0200 (MET DST) From: Stefan Esser <se@zpr.uni-koeln.de> To: Jan Knepper <100626.3506@CompuServe.COM> Cc: "[FreeBSD current]" <freebsd-current@FreeBSD.ORG> Subject: Re: 2.1.5 v.s. 2.2-960801-SNAP Message-ID: <199608051738.TAA27351@x14.mi.uni-koeln.de> In-Reply-To: <960804135358_100626.3506_BHL52-1@CompuServe.COM> References: <960804135358_100626.3506_BHL52-1@CompuServe.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Jan Knepper writes: > Hi, > > > I am new to these mailing list, so I am sorry if I send this to the wrong list. No, you are perfectly right (since you mention the 2.2-SNAP, else freebsd-stable would have been more appropriate :) > Yesterday I downloaded 2.1.5 STABLE. I already have 2.1.0 running on a system > with NCR SCSI. Version 2.1.5 refuses to access the NCR SCSI. I get the following > message when booting from flop. (boot.flp) > > ncr0: aborting job > ncr0:2: ERROR (90:0) (8-0-0) (0/13) @ (c8c:50000000) > script cmd = 740a8700 > reg : de 00 00 13 47 00 06 0f 35 08 00 00 90 00 0f 02 > ncr0: restart (fatal erro) > sd0(ncr0:0:0) COMMAND FAILED (9/f) @ f0e71a00 Hmmm, sorry. This is most probably related to your drive, and there was a work-around in 2.1R and is in the 2.2 install kernel. (It should have been in the GENERIC 2.2 kernel, too, but I'll have to check!) What drive causes this problem ? (Best if you sent a complete log of boot messages from your 2.1R kernel). > I tried the 2.2-960801-SNAP kernel and that one seems to work. However once the > system is installed there is an other kernel in the root which causes the exact > same problem. Hmm, that shouldn't be the case ... The kernel on the boot floppy and the GENERIC kernel should both be configured with the option FAILSAFE, which disables some performance options (most notably tagged commands for the NCR, which has them enabled by default, else). Seems I forgot to bring over FAILSAFE into the -stable tree before the 2.1.5 release was made ... :( > Of course I could also download the complete SNAP distribution, but there might > be an other way around this?! It depends on whether you can boot the 2.1R kernel to build a customized kernel. Add options "NCR_MAX_TAGS=0" to your kernel config file, configure (using the 2.1.5 "config" program !!!) and build the kernel. Please send e-mail, if you need further help. Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608051738.TAA27351>