From owner-freebsd-hackers Mon Apr 10 10:15:53 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA12534 for hackers-outgoing; Mon, 10 Apr 1995 10:15:53 -0700 Received: from sgiblab.sgi.com (sgiblab.SGI.COM [192.82.208.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA12526 for ; Mon, 10 Apr 1995 10:15:50 -0700 Received: from bazooka.amb.org by sgiblab.sgi.com via UUCP (950215.SGI.8.6.10/911001.SGI) id KAA07150; Mon, 10 Apr 1995 10:15:51 -0700 Received: by bazooka.amb.org (Sendmail 5.65/AMB-1.4) id AA00030; Mon, 10 Apr 95 09:54:05 -0700 From: ti@bazooka.amb.org (Ti Kan) Message-Id: <9504101654.AA00030@bazooka.amb.org> Subject: Re: xmcd 1.4 [ LONG DEBUG INFO ] To: mmead@goof.com (matthew c. mead) Date: Mon, 10 Apr 1995 09:54:05 -0700 (PDT) Cc: hackers@FreeBSD.org In-Reply-To: <199504101506.LAA01098@goof.com> from "matthew c. mead" at Apr 10, 95 11:06:44 am X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1322 Sender: hackers-owner@FreeBSD.org Precedence: bulk matthew c. mead writes: > Yes. I've used xcdplayer just fine to change the volume while > playing a cd. Can you set modeSenseSetDBD to both True and False and run xmcd with the -debug option in both scenarios? I would like to see the results of that too. Also, from the debug output you sent, it is apparent that the driver is returning failure status to the "Test Unit Ready" command that xmcd sends. This would indicate that the drive is not ready (such as when no CD is loaded). But I wonder if this is really the case. Is /dev/rcd0 really the correct device node for your drive? Check its major and minor device numbers. Also, did you use xcdplayer on this very system using the very same device node, and have confirmed that it worked? A key difference between xcdplayer and xmcd is that for SCSI drives, xmcd uses the SCSI pass-through interface to control the CD-ROM drive instead of the CD-ROM driver ioctl interface that xcdplayer uses. Perhaps the SCSI pass-through interface is not properly handled with the Buslogic driver? I dunno... Another thing you can try is to increase the command timeout value. In libdi.d/os_frbsd.c there is a line in the pthru_send() function that looks like this: ucmd.timeout = 2000; /* 2 secs timeout */ Change it to: ucmd.timeout = 10000; /* 10 secs timeout */ Recompile and re-try. Does it work any better? -Ti -- /// Ti Kan Vorsprung durch Technik /// AMB Research Laboratories, Sunnyvale, CA. USA /// Internet: ti@amb.org ////// UUCP: ...!uunet!bazooka!ti /// URL: ftp://ftp.netcom.com/pub/tk/tkan/www/tikan/tikan.html