Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Sep 1999 13:49:11 +0200 (CEST)
From:      Nick Hibma <hibma@skylink.it>
To:        Soren Schmidt <sos@freebsd.dk>
Cc:        Christopher Masto <chris@netmonger.net>, "Daniel O'Connor" <doconnor@gsoft.com.au>, freebsd-hackers@FreeBSD.ORG, paulo@nlink.com.br
Subject:   Re: wormcontrol write speed
Message-ID:  <Pine.BSF.4.10.9909261346580.22025-100000@heidi.plazza.it>
In-Reply-To: <199909260824.KAA65733@freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help

And, oh while you are at it, why not create a CAM SIM that makes IDE
available through CAM. That would save me a lot of work :-)

Nick

On Sun, 26 Sep 1999, Soren Schmidt wrote:

> It seems Christopher Masto wrote:
> > On Wed, Sep 22, 1999 at 09:27:37AM +0200, Soren Schmidt wrote:
> > > Anyhow, I have some changes to the worm stuff, it needs to be dealt w=
ith
> > > to handle modern HW, and to deal with all the possible block formats
> > > thats possible on a CD nowadays. It will probably mean the death of
> > > the worm stuff as is now, but I'm the last user anyways so....
> >=20
> > Any chance of getting a passthrough or "SCSI emulation" so that
> > cdrecord could be used instead?  (Then you won't have to worry about
> > different CD-R quirks)
>=20
> If somebody writes it there is a chance. I dont have this on my TODO
> list. I could maybe be talked into providing a generic ATAPI interface
> that would give you a method of injecting ATAPI commands directly
> into the systemi, cdrecord etc could use that then.
>=20
> > I have an Acer CRW 6202A which doesn't seem to work with FreeBSD
> > (current as of five minutes ago, including the rev 1.19 of
> > atapi-cd.c).  "wormcontrol blank" (with a CD-RW of course) runs for a
> > little while, then aborts with an I/O error.  Also, all IDE devices
> > are completely locked up while it's running.
>=20
> What I/O error ?? its impossible to diagnose on no data...
> =20
> > The dd also sort of works for a while, then gets an I/O error.  Same
> > with fixate (which also locks up the IDE busses).
>=20
> What I/O error ?? its impossible to diagnose on no data...
> =20
> > I'm currently recompiling with ATAPI_DEBUG and ACD_DEBUG in the hopes
> > that I'll be able to produce a better bug report.  Any suggestions?
>=20
> Provide data, the system spits out lots of sensekey things and the
> like on errors, those are invaluable data to diagnose this...
>=20
> -S=F8ren
>=20
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>=20
>=20

--=20
e-Mail: hibma@skylink.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909261346580.22025-100000>