Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!news.mathworks.com!news.kei.com!nntp.coast.net!howland.reston.ans.net!blackbush.xlink.net!news.uni-mainz.de!news.th-darmstadt.de!brewhq.swb.de!thorin.swb.de!news.gni.net!ichtys!subloch.swb.de!maulwurf Date: 10 Jan 1996 03:21:00 +0100 From: maulwurf@subloch.swb.de (Stefan Huerter) Newsgroups: comp.unix.bsd.freebsd.misc Message-ID: <60aahLBjoRB@subloch.swb.de> Subject: ncr-dead/hangs on ASUS-SP3 Keywords: ASUS,SP3,ncr,SCSI X-Newsreader: CrossPoint v3.1 R/C2188 Organization: die wahre Antwort: 42 Lines: 32 Guckux after upgrading from FreeBSD 2.0 to 2.1, I am very confused. After installing the new system, I remembering only the sentence: Don't touch a running system. The problem was: my SCSI-ncr controller on the ASUS SP3 Board was dead, hanging if I have exhausivst disk-transfers. After a long call with Stefan Esser (one of the ncr-developer for Free- BSD), testing one tag, he give me the advice, to deactivate different PCI- options. (completly deactivated the Block in the BIOS PCI-burst-DRAM etc, 3 options; named: CPU To DRAM write Buffer CPU To PCI write Buffer PCI Memory Burst Write ). Since this time, the System is running fine, while not confused from the buggy Intel-Chipset. Jordan, perhaps it is possible to mention this in the Hardware FAQ, it seems to be only with exhausivt disk-transfers on the ASUS SP3 (not!!! SP3G) Board. The problem was in FreeBSD 2.0, too, but only sometimes, not definitly reconstructable. The 2.1 System seems to be more PCI-extensive, to get more performance, so it was reconstructable. sorry for my bad expression, I hope it was possible to understand :-) Bye Stefan