From owner-freebsd-multimedia  Wed Aug 13 05:35:14 1997
Return-Path: <owner-freebsd-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA14611
          for multimedia-outgoing; Wed, 13 Aug 1997 05:35:14 -0700 (PDT)
Received: from pendor.McKusick.COM (root@pendor.bayarea.net [205.219.85.134])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14602
          for <freebsd-multimedia@freebsd.org>; Wed, 13 Aug 1997 05:35:10 -0700 (PDT)
Received: (from benco@localhost) by pendor.McKusick.COM (8.8.5/8.6.9) id FAA10214 for freebsd-multimedia@freebsd.org; Wed, 13 Aug 1997 05:35:05 -0700 (PDT)
Date: Wed, 13 Aug 1997 05:35:05 -0700 (PDT)
From: Ben Cottrell <benco@pendor.mckusick.com>
Message-Id: <199708131235.FAA10214@pendor.McKusick.COM>
To: freebsd-multimedia@freebsd.org
Subject: CD burner problems: HP 6020
Sender: owner-freebsd-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Thanks to all who advised me about getting a CD burner earlier! I settled
on an HP SureStore 6020i.

I'm noticing two problems with it. The first (rather unimportant, but I
felt it might hold a clue to the other one) is that I can't seem to mount
a CD-ROM:
	# mount -t cd9660 /dev/worm0 /cdrom0
	cd9660: Input/output error

I noticed Jean-Marc Zucconi's recent post to freebsd-hackers about a
problem that looked similar to this, but when I tried to apply the patch
he posted, it had already been applied--apparently that fix is contained
in -current as of a few weeks ago?

The second problem is that I can write short tracks with cd-write, but
if I try to write longer ones, I invariably get an infinite stream of:
	/kernel: worm0: oops not queued
	/kernel: biodone: buffer already done
and the write starts failing. This is with cd-write from the ports collection
running at 1x (2x has similar problems) with an Adaptec 2940 SCSI controller.
Testing with an audio track shows that when it does this, *some* data still
reach the disk, but only a small percentage of it. The resulting CD thus
"skips" because some correct data were written, then a lot of stuff got
dropped on the floor, then it resumed writing with data that should have come
a few seconds later.

If anyone has any suggestions, I'd love to hear them! Or else, failing that,
a "take it back to the store and get XYZ cd burner instead; it works better"
would also be helpful :>

Thanks a lot,
	~Ben