From owner-freebsd-questions Mon Aug 19 20:27:14 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09591 for questions-outgoing; Mon, 19 Aug 1996 20:27:14 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts9-line4.uoregon.edu [128.223.150.85]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA09578 for ; Mon, 19 Aug 1996 20:27:05 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id UAA00434; Mon, 19 Aug 1996 20:27:05 -0700 (PDT) Date: Mon, 19 Aug 1996 20:27:05 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "Jeffrey M. Metcalf" cc: questions@FreeBSD.org, metcalf@imagine.com Subject: Re: Mysterious device probe error In-Reply-To: <9607198404.AA840492699@ccgate0.bms.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Please remove the "joseph_m._o'connor" cc: until they fix their machine. It just rejects sendmail sessions. On Mon, 19 Aug 1996, Jeffrey M. Metcalf wrote: > After installing FreeBSD on a Pentium 100 machine, a disturbing > message appeared during the hardware probe. > > Aug 14 14:26:30 joes /kernel: pci0:11: CMD, device=0x0640, > class=storage (ide) [no driver assigned] This is _perfectly_ normal and may be ignored. See, my machine does it too: pci0:12: CMD, device=0x0640, class=storage (ide) int a irq 14 [no driver assigned] It means that the CMD controller doesn't have a specific driver to go with it (and it doesn't). Notice that the wdc0 driver works fine (which interfaces through the generic IDE interface). > The full device probe is shown below. I was wondering if the message > would be indicative of a CDROM problem I noticed. When copying > large programs from the mounted CDROM, the system would hang > indefinitely. A keyboard lockup would occur and a forced reboot > would be necessary. Do these symtoms (and/or message) suggest the > possibility of a simple recurring problem with an easy fix? Don't know about that. Sounds more like a cable or controller or IRQ clash than just a missing driver. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major