From owner-freebsd-current@FreeBSD.ORG Wed Jul 16 14:53:42 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 435F7106566C for ; Wed, 16 Jul 2008 14:53:42 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63908.mail.re1.yahoo.com (web63908.mail.re1.yahoo.com [69.147.97.123]) by mx1.freebsd.org (Postfix) with SMTP id CF5558FC16 for ; Wed, 16 Jul 2008 14:53:41 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 57682 invoked by uid 60001); 16 Jul 2008 14:27:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=dX2FAU9xYT8Xfdz3BMVSzfrYpeowSkaarusY0oMNYjlayKj8tnO9Ru6Gms68xoCAQP2/Ou7rxKvCDumbLffcnYal5F3NNYvo7kN1JWz0pzzqbFZplRhMTUBPvHYImjgkPgYsWrMq+JO2afCeOVAfO2KwTUqF5nQABI3TrY9Tj8Y=; Received: from [98.203.28.38] by web63908.mail.re1.yahoo.com via HTTP; Wed, 16 Jul 2008 07:26:59 PDT X-Mailer: YahooMailWebService/0.7.218 Date: Wed, 16 Jul 2008 07:26:59 -0700 (PDT) From: Barney Cordoba To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <334863.57605.qm@web63908.mail.re1.yahoo.com> Cc: sos@freebsd.org Subject: DVD-ROM problem with Freebsd 7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 14:53:42 -0000 I'm debugging a problem with an Intel Bigby chipset and a DVD-ROM drive. We've swapped it out with a regular CD-ROM and have the same problem, so its likely not the drive. It gets probed as ATA_I82801IB_AH6. The problem is that certain types of media don't work. Some work, some don't. We're going to build a LINUX system to try to see if its the driver or some physical thing, but the media works on our other systems so it appears to be the driver. In pouring over the drivers, I've noticed that the setmode function never seems to get called, and I'm wondering what the point of the setup variables are if they're never called. What should be the sequence of calls to properly set up the controller? Barney