From owner-freebsd-current Fri Jul 26 13:19:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21360 for current-outgoing; Fri, 26 Jul 1996 13:19:11 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21323; Fri, 26 Jul 1996 13:18:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02248 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00305; Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Message-Id: <199607261945.VAA00305@x14.mi.uni-koeln.de> From: Stefan Esser To: Michael Beckmann Cc: current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in sta In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Beckmann writes: > At 10:32 Uhr +0200 23.7.1996, Stefan Bethke wrote: > > >We have a similiar problem here: Asus SP3G-II (Neptune II chipset), > > I was under the impression that the SP3G had a Saturn II Chipset. Mine does :) > >It hangs sometimes on reboots, after clearing the screen. However, when it > >does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings > >:-( > > That happened to me, too, when I was still using an SP3G mainboard. The ASUS SP3G seems to need a "options BROKEN_KEYBOARD_RESET" line in the kernel config file. Mine does ... > Later I upgraded it with a Gigabyte 586 ATE/P mainboard, and recently with > a Gigabyte 586 HX mainboard; both equipped with an Asus SC-200 PCI > controller (NCR 53c810 based); and with both Gigabyte board / Asus > controller combinations I have never had a problem. That's not at all related to the SCSI controller. Regards, STefan