From owner-freebsd-current@FreeBSD.ORG Tue Mar 15 10:58:30 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEA6716A4ED for ; Tue, 15 Mar 2005 10:58:30 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BB7743D41 for ; Tue, 15 Mar 2005 10:58:30 +0000 (GMT) (envelope-from sprsquish@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so2026925wra for ; Tue, 15 Mar 2005 02:58:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Wu0oXcQh81C/9g42/554TNc9JJwW6tVagBA8LsCSDfqVKmlNxhiMeqJFBNGYvS7bEfIV5x4ZbIFXIhISutOJAVHj+L79dVNajYSSwQuEOJL6pijPdlxnwYpJOnunWiKiTNJlMfTz3VLwnWt2BNiOPK9JFmbjjxCxvoRg1xp+A78= Received: by 10.54.40.2 with SMTP id n2mr5488109wrn; Tue, 15 Mar 2005 02:58:27 -0800 (PST) Received: by 10.54.16.49 with HTTP; Tue, 15 Mar 2005 02:58:27 -0800 (PST) Message-ID: <669ac2d05031502585f8230a@mail.gmail.com> Date: Tue, 15 Mar 2005 02:58:27 -0800 From: Jeff Smick To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 15 Mar 2005 13:07:25 +0000 Subject: ATAPICAM Problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jeff Smick List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 10:58:31 -0000 Frustration is starting to take hold. I've been banging my head against the wall with the problem for a few days now. I've read and searched everything I can find on the subject and have yet to solve the problem. Anton had a similar problem in this thread: http://lists.freebsd.org/pipermail/freebsd-current/2004-March/023575.html. However, his solution doesn't solve my problem. Here it is: I followed the instructions in the Handbook on how to get a CD-RW drive running using atapicam. However, it's not working. I don't see a cd0 in the /dev directory. There's no mention of cd0 in my dmesg and even when I do a "kldstat -v" neither the scd module nor the pass module are loaded (cam, however, is). While watching the boot process everything goes smoothly untill it hits "acd0: CDRW at ata1-master UDMA33" then it will wait a few seconds before continuing on to mounting the root partition. I've even tried kldload-ing the scd module; still nothing. I hope someone will be able to help with this. Thank you, --Jeff Smick PS: The following is every part of my dmesg having to do with ATA (nothing in it about cd0): atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 irq 18 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ad0: 58644MB [119150/16/63] at ata0-master UDMA100 ad1: 39083MB [79408/16/63] at ata0-slave UDMA100 acd0: CDRW at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a Here's what's enabled in my kernel config: # ATA and ATAPI devices device ata #device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives device atapicam # ATAPI CAM transport options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers #device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) And finally a bit from my "kldstat -v": 1 15 0xc0400000 37b310 kernel Contains modules: Id Name 28 xpt 29 probe 30 cam 31 da 32 isa/ata 33 pci/atapci 34 atapci/ata 35 acd