Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!howland.erols.net!blackbush.xlink.net!fu-berlin.de!news-ber1.dfn.de!news-ham1.dfn.de!news-han1.dfn.de!news-koe1.dfn.de!main.Germany.EU.net!Dortmund.Germany.EU.net!not-for-mail From: bs@Germany.EU.net (Bernard Steiner) Newsgroups: comp.unix.bsd.freebsd.misc Subject: ahb woes Date: 18 Dec 1996 16:07:54 +0100 Organization: EUnet Deutschland GmbH, Dortmund, Germany Lines: 17 Message-ID: <5991ca$87k@Germany.EU.net> NNTP-Posting-Host: qwerty.germany.eu.net Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32747 Hi, I am running (ahem.. *was* running, that is) 2.1.5R. Until very recently I used an Adaptec 1542c on a 486DX50 VL board with a SCSI-2 disk without any problems. Then, I upgraded to an EISA board (with some sort of 486@100) and an Adaptec 1740 controlling a wide scsi disk through a wide->narrow connector. It's switched to enhanced mode. Now, I can boot the kernel (generic and custom), it will execute init and sh, but when fsck (or anything else) is run and tries to read anything larger than one block at a time and then wait for a while the controller switches on its BUSY light and *stays* busy even through a soft-reboot. Any help, anyone ? Thanks Bernard