From owner-freebsd-hardware Tue Apr 14 16:53:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20773 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 16:53:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20747 for ; Tue, 14 Apr 1998 23:52:51 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01470; Tue, 14 Apr 1998 16:48:50 -0700 (PDT) Message-Id: <199804142348.QAA01470@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Edwin Culp cc: Mike Smith , freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 In-reply-to: Your message of "Tue, 14 Apr 1998 18:42:40 CDT." <3533F470.1B0807C2@ver1.telmex.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 16:48:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote: > > > > > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > > > everything would be routine:-) and my dmesg was what I expected: > > > > > > ahc0: rev 0x01 int a irq 10 on > > > pci0.15.0 > > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > > > scbus0 at ahc0 bus 0 > > > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > > > cd0 at scbus0 target 3 lun 0 > > > cd0: type 5 removable SCSI 2 > > > cd0: CD-ROM can't get the size > > > > > > I mounted a cd on /tmp and worked perfectly so I decided to > > > burn disk1 of Sunday's cvsup and make release. > > > > > > # cdrecord dev=0,3,0 test.raw > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > Bad system call (core dumped) > > > > > > I tried most of the drivers with the same results. > > > > > > I read "at" the manual and tried > > > > > > # cdrecord -scanbus > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > cdrecord: No target found. > > > > > > Does anyone know ir there is a problem with this drive? > > > > It doesn't sound like a problem with the drive, although the > > documentation doesn't indicate that the drive in question is supported. > > > > The 'bad system call' message is pretty ugly though; without knowing > > what the system call was it's hard to understand what's going on. > > > > You're not running CAM, I presume? Did you build cdrecord from source, > > or just install the package? If the latter, did you get the package > > from the 2.2 or -current collection? > > No not using CAM. Installed cdrecord from ports current version 1.6a12. "ports current"? You mean packages-current? Are you on -stable or -current? I ask simply because the only reasonable source of "bad system call" I can think of is running a binary built on a -current system on a -stable system. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message