From owner-freebsd-stable  Sun Jul 27 17:19:02 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA29590
          for stable-outgoing; Sun, 27 Jul 1997 17:19:02 -0700 (PDT)
Received: from mh1.cts.com (root@mh1.cts.com [205.163.24.66])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29583
          for <freebsd-stable@freebsd.org>; Sun, 27 Jul 1997 17:18:58 -0700 (PDT)
Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh1.cts.com (8.8.5/8.8.5) with ESMTP id RAA17431 for <freebsd-stable@freebsd.org>; Sun, 27 Jul 1997 17:18:57 -0700 (PDT)
Received: (from mdavis@localhost) by io.cts.com (8.8.5/8.8.5) id RAA00184; Sun, 27 Jul 1997 17:18:56 -0700 (PDT)
From: Morgan Davis <mdavis@io.cts.com>
Message-Id: <199707280018.RAA00184@io.cts.com>
Subject: Re: Support for ATAPI IDE-CDROMs (SOLUTION)
In-Reply-To: <199707271608.JAA01783@io.cts.com> from Morgan Davis at "Jul 27, 97 09:08:29 am"
To: mdavis@io.cts.com (Morgan Davis)
Date: Sun, 27 Jul 1997 17:18:56 -0700 (PDT)
Cc: freebsd-stable@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

The solution is to enable ATAPI_STATIC in your kernel config.
Otherwise, the probing at boot time will not see that you've got an
IDE CD-ROM drive, which means LKM support after booting will be
unsuccessful.

Thanks for all who helped.

--Morgan

Morgan Davis writes:
> OK, what's the trick for getting an ATAPI IDE CD-ROM drive to mount?
> I've looked through the Handbook, FAQ, etc.  Here's what I have so
> far:
> 
> 1. wdc0, wdc1, ATAPI, wcd0 and wcd1 in kernel.
> 2. sh MAKEDEV wcd0 wcd1
> 
> When doing a
> 
> 	mount_cd9660 /dev/wcd0c /cdrom
> 
> I get "Device not configured".
> 
> Physically, the IDE HDD's are on the Primary IDE Channel.  The CD-ROM
> is set to be the master device on the Secondary IDE Channel.  From
> DOS, the all the drives can be seen, including the CD-ROM drive using
> standard ATAPI drivers.  So I know that the problem is related to
> software/configuration settings.
> 
> Any hints?
> 
> --Morgan
>