From owner-freebsd-hackers Tue Jul 8 16:29:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16094 for hackers-outgoing; Tue, 8 Jul 1997 16:29:21 -0700 (PDT) Received: from numachi.numachi.com (numachi.numachi.com [198.175.254.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16073 for ; Tue, 8 Jul 1997 16:29:14 -0700 (PDT) Received: (from reichert@localhost) by numachi.numachi.com (8.8.5/8.8.5) id TAA02265; Tue, 8 Jul 1997 19:29:03 -0400 (EDT) Message-ID: <19970708192857.54365@numachi.numachi.com> Date: Tue, 8 Jul 1997 19:28:58 -0400 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: xmcd-2.1 and NEC ATAPI drive Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.68 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't know if this was supposed to be a problem, but I had to do some arm-wrestling to get xmcd-2.1 to recognize my cdrom. What I have: 2.2.1-RELEASE wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, iordy wcd0: 689Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray The xmcd package was convinced that the 'proper' device was /dev/rcd0c, which is not the case at all on my box. I had to yank the device checks out of its guts, as well at it's install utility. Seems to be behaving at this point, although I can't get it to close the door. I might be able to solve that by editing it's config file. My question: has anyone else gotten any grief from this utility, or did I end up with a mutant box/intallation? -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Derry NH 03038-1713 USA Intel architecture: the left-hand path