Date: Fri, 22 Dec 2006 12:38:57 +0500 From: "Sergey N. Voronkov" <serg@tmn.ru> To: Luigi Rizzo <rizzo@icir.org> Cc: stable@freebsd.org Subject: Re: burncd 'blank' not terminating ? Message-ID: <20061222073857.GA10704@tmn.ru> In-Reply-To: <20061221092717.A6431@xorpc.icir.org> References: <20061221092717.A6431@xorpc.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 21, 2006 at 09:27:17AM -0800, Luigi Rizzo wrote: > just noticed, after upgrading to 6.2RC1, that > > luigi# burncd -f /dev/acd0 -v blank > blanking CD, please wait.. > > stays there forever. Eventually i gave up and ctrl-C and > the application terminates, and i was able to write to > the disk a valid image, which probably means that the > disk had been blanked. > > I browsed through the mailing lists and it seems to be an > old problem, related to the driver not reporting the status info. > > Not sure if it is related to particular hardware, just in case here > is what i have: > > ad0: 238475MB <MAXTOR STM3250620A 3.AAD> at ata0-master UDMA100 > acd0: DVDR <HL-DT-ST DVDRAM GSA-H10N/JL10> at ata0-slave UDMA33 > > note, if i kldload atapicam, and try the blank on /dev/cd0 i get this: > > luigi# burncd -f /dev/cd0 -v blank > burncd: ioctl(CDRIOCGETBLOCKSIZE): Inappropriate ioctl for device > > Any ideas ? > This old report says the problem is in the ioctl... > > http://www.freebsd.org/cgi/query-pr.cgi?pr=44803 See my report: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/95344 And: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/104270 The last one contain a fix. Serg. P.S.: Don't use burncd. Use cdrecord!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061222073857.GA10704>