Date: Wed, 21 Jan 1998 10:48:07 -0500 From: Norman C Rice <nrice@emu.sourcee.com> To: Cliff Addy <fbsdlist@federation.addy.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: cdrom not configured? Message-ID: <19980121104807.38068@emu.sourcee.com> In-Reply-To: <Pine.BSF.3.95q.980121102429.1726B-100000@federation.addy.com>; from Cliff Addy on Wed, Jan 21, 1998 at 10:34:10AM -0500 References: <199801211517.WAA12282@relay.kuzbass.net> <Pine.BSF.3.95q.980121102429.1726B-100000@federation.addy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 21, 1998 at 10:34:10AM -0500, Cliff Addy wrote: > 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? > Please post the output of `dmesg'. If this doesn't identify the CD-ROM, what is its manufacturer and model? Is the appropriate controller and device enabled in the kernel? -- Regards, Norman C. Rice, Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980121104807.38068>