From owner-freebsd-scsi Mon Aug 28 2: 1:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-service.wias-berlin.de (descartes.wias-berlin.de [192.124.249.194]) by hub.freebsd.org (Postfix) with ESMTP id F074737B422 for ; Mon, 28 Aug 2000 02:01:28 -0700 (PDT) Received: from wias-berlin.de by mail-service.wias-berlin.de (8.8.8/1.1.22.3/16Mar99-0205PM) id LAA0000029684; Mon, 28 Aug 2000 11:01:26 +0200 (MET DST) Received: from localhost by wias-berlin.de (8.8.8/1.1.10.5/07Oct97-0932AM) id LAA0000014478; Mon, 28 Aug 2000 11:01:20 +0200 (MET DST) To: groudier@club-internet.fr, j@uriah.heep.sax.de, dkelly@hiwaay.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NCR SCSI controller problems with FreeBSD-4.1R From: Jens Andre Griepentrog Reply-To: griepent@wias-berlin.de In-Reply-To: References: <20000823105725P.griepent@hilbert.wias-berlin.de> X-Mailer: Mew version 1.94.1 on Emacs 19.33 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-Id: <20000828110119B.griepent@hilbert.wias-berlin.de> Date: Mon, 28 Aug 2000 11:01:19 +0200 X-Dispatcher: imput version 990905(IM130) Lines: 102 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear G=E9rard, David and Joerg! Thank you very much for your suggestions, especially yours, G=E9rard! Indeed, looking at the SC-200 board it was configured for PCI INT B! Setting the jumper to PCI INT A solved the problem, now I was able to install FreeBSD-4.1R successfully. Again reading the manual of both the motherboard and the controller card PCI INT A is the default setting, it was my mistake to trust on the the right setting without a simple check. But last for years there was no reason to have any look to the controller because the system has = worked flawlessly with all previous FreeBSD releases until now. Being happy I want to thank you again, Jens Griepentrog > > On Wed, 23 Aug 2000 14:25:06, G=E9rard Roudier suggests the following:= > > 1) Check that your SC-200 is configured for PCI INT A. > If it is not, change jumpers accordingly. > 2) Move you board to another PCI slot. > 3) Check/set SCSI termination properly. > = > If either (1) and/or (2) and/or (3) does not cure, then send me any dm= esg > you have. You also could try to catch manually driver messages that lo= ok > like complaint about something going wrong under FreeBSD and/or Linux = as > well. > > The fact that your system experiences the problem also under Linux and= > given that the ncr(4) driver (used in 3.4) also polls interrupts using= a > timer, it might well be that hardware interrupts are not functionning > properly for your SC-200 (just a guessing). > > Gerard. = > >> On Wed, 23 Aug 2000, Jens Andre Griepentrog wrote: >> >> Dear FreeBSD and SCSI experts! >> = >> I have tried to install FreeBSD 4.1 Release from CD-ROM (4.1-install.= iso). >> Using the boot floppies kern.flp and mfsroot.flp the system hangs up = during >> the detection and settlement of SCSI devices. None of my five SCSI de= vices >> connected to the ASUS SC-200 NCR SCSI controller appears in the boot = display >> messages. Here is the short list of relevant hardware components: > = >> ASUS P6NP5 Intel Pentium Pro 200 mother board, >> three IBM and Quantum SCSI hard drives, >> Tandberg SCSI QIC streamer, >> Plextor SCSI CD-ROM. >> = >> Using the same hardware this problem appears for the first time in my= >> four-year experience with successful installed releases 2.1, 2.2, 3.1= or 3.4. >> = >> From time to time I tried to install several Linux distributions to g= et >> the impression of a comparable OS but every time running into the sam= e >> trouble concerning the detection of SCSI devices. >> = >> The deeper reason could be a problem with the NCR SCSI controller bec= ause >> of reported code modifications after release 3.4. >> = >> It would be nice if you could give me hint. Let me know if you need m= ore >> details about my hardware or BIOS settings. For instance I can send a= dmesg >> log file from my current FreeBSD-3.4 installation. >> = >> So long, >> = >> Jens Griepentrog >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message