From owner-freebsd-questions Wed Jan 21 07:34:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03573 for questions-outgoing; Wed, 21 Jan 1998 07:34:18 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03564 for ; Wed, 21 Jan 1998 07:34:13 -0800 (PST) (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id KAA02967 for ; Wed, 21 Jan 1998 10:34:10 -0500 (EST) Date: Wed, 21 Jan 1998 10:34:10 -0500 (EST) From: Cliff Addy To: freebsd-questions@FreeBSD.ORG Subject: cdrom not configured? In-Reply-To: <199801211517.WAA12282@relay.kuzbass.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk I've installed FreeBSD on lots of machines and never had this problem: mount_cd9660 /dev/cd0a /cdrom mount_cd9660: /dev/cd0a: Device not configured the cdrom has always just *been* there, available for mounting, on other machines, I've never had to do anything special. This machine is like all the others, it's a SCSI cdrom hanging off an Adaptec 2940UW. Installation was also weird. The machine booted off the cdrom and FreeBSD's installation program ran fine until I selected cdrom as the installation media. At this point, it told me it couldn't find the cdrom! So I just walked over, mounted it on one of the other machines and installed over NFS. Could the "lack" of a cdrom at installation make FBSD think the cdrom is not usable? This machine is my personal workstation and is currently multi-booting DOS/Win31, WinNT, OS/2, and now FreeBSD 2.2.5. Only FBSD can't see the cdrom, so it doesn't seem to be a hardware problem. Help?