From owner-freebsd-questions Fri Jul 19 16:29:52 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25879 for questions-outgoing; Fri, 19 Jul 1996 16:29:52 -0700 (PDT) Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA25872 for ; Fri, 19 Jul 1996 16:29:49 -0700 (PDT) Received: from post.demon.co.uk by relay-5.mail.demon.net id bc28211; 20 Jul 96 0:28 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa26368; 19 Jul 96 23:36 +0100 Received: (from fqueries@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id VAA07144; Fri, 19 Jul 1996 21:32:04 GMT Date: Fri, 19 Jul 1996 21:32:04 GMT Message-Id: <199607192132.VAA07144@jraynard.demon.co.uk> From: James Raynard To: searle@longacre.demon.co.uk CC: questions@freefall.freebsd.org In-reply-to: (message from Michael Searle on Fri, 19 Jul 1996 12:33:42 BST) Subject: Re: NCR controller problem? Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> Michael Searle writes: > > (ncr:6:0) COMMAND FAILED (6 2) @ f066f948 Judging from your dmesg output, this is your CDROM... > Does/could this mean that there is something wrong with my controller/drive? The first thing to do with any kind of SCSI problem is to check and double-check the cables and that all your devices are properly terminated. With CDROM drives, make sure they are absolutely horizontal and firmly fixed to their surroundings. The next thing is to carry out some kind of test. There is a scsi(8) command on FreeBSD, but it seems to assume quite a bit of knowledge about SCSI. Other than that, the only other thing I can think of is rebooting and using whatever facilities are available in the BIOS or even (gack!) under DOS. > (I guess my drive is OK, as it hadn't got as far as detecting it.) The only > other problems I have had with this machine are with floppies (They are slow, > occasionally use a lot of CPU, produce errors like 'input ready timeout' and > 'hard error at fsbn xxxx' (while reading and writing successfully) and at > least twice caused panics - but this may be the msdosfs, not the floppy.) Try installing the mtools package - it makes using DOS floppies almost bearable :-) -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk http://www.freebsd.org/~jraynard/