Hi, Note that as of May 2003 I've decided to advise users to turn to <cdwrite@other.debian.org> on support matters. Subscribe page is at http://lists.debian.org/cdwrite/, archive - at http://www.mail-archive.com/cdwrite%40other.debian.org/. > Hi, I have a Pioneer DVR-A07XLA and Debian Sarge (testing). The > dvd+rw-format program formats up until 100%, then hangs up on formatting > DVD+RWs and DVD-RWs. After that, the growisofs program gets between 18 > and 50% done and then the write hangs up entirely. The same thing > happens with DVD+/-R discs. Quoting dvd+rw-tools page: "When submitting report, provide versioning information, exact command line, exact output generated by the program and complement it with dvd+rw-mediainfo output for resulting recording." > I'm more than competent at programming, and I'm willing to fix the > problem myself if you don't have time, but I have no idea how to hack at > these drives. How do you figure out what you need to add to get a > particular drive to work? Quoting "hardware compatibility notes" page: "...one of dvd+rw-tools design rules is to be a "common denominator" for all units. So that whenever you see an announcement that "new update adds support for some particular unit," it doesn't actually mean that e.g. growisofs recognizes the unit in question and modifies its behaviour accordingly. It rather means that it permits for some particular vendor dialect/interpretation without breaking backward compatibility." So far "dialect variations" were limited to commands issued prior first write command. In other words if recording has started, then it was observed to work all the way (with exceptions for media incompatibility issues). At least so far and I find it hard to believe that DVR-A07 needs that different treatment and it was reported to be working by a couple of users... > This seems like a buffer underrun problem or > something like that to me instinctively, since it happens at a different > place on the disc each time. growisofs explicitly and unconditionally instructs unit to handle underruns. If firmware fails to handle them, then it's most likely firmware problem (e.g. poor media support) or deficient hardware. Well, given that it won't turn out to be an automounting problem... > I see nothing from the scsi bus that would > indicate that the device is being reset, and I certainly have no > automounter daemon running. Any ideas? Not all automounting solutions are "daemon"-based. I mean it's not necessarily a system service which is started through a /etc/init.d script or similar. It can as well be a mount point, supermount or submount one... A.