From owner-freebsd-questions Wed Feb 21 20:14:50 2001 Delivered-To: freebsd-questions@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 7F2C637B4EC for ; Wed, 21 Feb 2001 20:14:46 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1M4Cwi95542; Wed, 21 Feb 2001 23:12:58 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <009a01c09c85$d8a4db40$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Ralph Dratman" Cc: References: <000d01c09899$c045ec00$1401a8c0@tedm.placo.com> <009501c09c48$55d31890$1200a8c0@gsicomp.on.ca> <005f01c09c7a$7e42bce0$1200a8c0@gsicomp.on.ca> Subject: Re: ata1-master: CDROM device - NO DRIVER! Date: Wed, 21 Feb 2001 23:13:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 9:52 PM -0500 2/21/01, Matthew Emmerton wrote: > >I just scanned through some CR-58x specs on a Panasonic web site, and they > >claim that the 581 is a standard ATAPI device. If this is the case, then > >you don't need 'device matcd', but rather, 'device atapicd'... > > Unfortunately that didn't work either. Here's the new output of > dmesg. It's very similar to what I was getting from GENERIC: > > Note that all this MODE_SENSE_BIG stuff was not there without the > > device atapicd > > line in the config file, nor did I see it in FreeBSD 3.3, which > always accessed the CD-ROM without any problems. So I'm wondering if > something changed in the ATAPI driver between 3.3 and 4.2. All of the MODE_SENSE_BIG stuff is caused by the ATAPI probes to the CD-ROM (notice the "ata1: resetting devices ... done" lines), and the CD-ROM isn't acknowledging them. This causes the ATAPI cd driver to fail the init, and the "NO DRIVER" message is displayed. Since I happen to have a machine that's running 3.4 happily (and does the *exact* same thing when I install 4.x on it, due to the 4X Creative (aka Panasonic) ATAPI CD-ROM that it has), I'm going to do a quick backup-and-upgrade and start hacking through the ATAPI CD-ROM code. [ There are 15 possible "sense" results that a CD-ROM can return. The 4.x code checks for 5 of them. These older CD-ROMs are most likely returning a result that isn't being checked, which triggers the error output and causes the driver to fail during init. ] > Also, do you (or does someone) know what all that > > config> di sn0 > > and so forth means at the beginning of the boot message? Could it > have anything to do with this problem (doubtful)? I doubt it's got anything to do with this problem, but those lines are part of a kernel-configuration script in /boot/kernel.conf. Since you're not running GENERIC any more, you can edit out most of that file - especially the 'di' lines - to reduce the chatter. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message