Date: Tue, 14 Apr 1998 21:03:34 -0500 From: Edwin Culp <eculp@ver1.telmex.net.mx> To: Mike Smith <mike@smith.net.au>, freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 Message-ID: <35341576.55BF3975@ver1.telmex.net.mx> References: <199804142348.QAA01470@dingo.cdrom.com> <3533F8BA.6D8A6085@ver1.telmex.net.mx>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike,
Thanks a lot. It works fine. There were two problems.
1. cdrecord 1.6a12 compiled with current would
always give the bad system call. I changed
it to one compiled with 2.2.6 and the bad
system call went away.
2. You also have to do a s/link from /dev/cd0c
to /dev/scgx and everything is beautiful.
I burned and tested FreeBSD cdrom set with
no problems.
Thanks again.
ed
P.D. We can add the MCA-CDRW 226 from mitsubishi to the
good list.
Edwin Culp wrote:
>
> Mike Smith wrote:
> >
> > > 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: <Adaptec 2940 Ultra SCSI host adapter> 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: <MITSBISH CDRW226 1.20> 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.
>
> Unfortunately it is current/current as of Sunday. New cvsup and Make
> world.
>
> Thanks
>
> ed
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35341576.55BF3975>