Date: Mon, 12 Jul 1999 16:25:33 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: szoli@netvisor.hu (Sebestyen Zoltan) Cc: cjclark@home.com, freebsd-questions@FreeBSD.ORG Subject: Re: cdrecord Problems Message-ID: <199907122025.QAA24955@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <Pine.LNX.4.04.9907122146530.11922-100000@linux.intranet.netvisor.hu> from Sebestyen Zoltan at "Jul 12, 99 09:48:01 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Sebestyen Zoltan wrote, [Charset iso-8859-2 unsupported, filtering to ASCII...] > > > cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, disabling. > To avoid this warning, insert the following lines: > ##################################################################### > # POSIX P1003.1B > > # Real time extensions added int the 1993 Posix > # P1003_1B: Infrastructure > # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING > # _KPOSIX_VERSION: Version kernel is built for > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" Thanks, that did fix that one line, but in attepting to fixate the disks that only got partially written before gives, pc222# cdrecord -speed=2 -v -fix dev=2,0,2 Cdrecord release 1.8a22 Copyright (C) 1995-1999 J^vrg Schilling TOC Type: 1 = CD-ROM scsidev: '0,2,0' scsibus: 0 target: 2 lun: 0 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : Vendor_info : 'HP ' Identifikation : 'CD-Writer 6020 ' Revision : '1.07' Device seems to be: Philips CDD-2600. Using driver for Philips CDD-522 (philips_cdd522). Driver flags : cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00 00 00 00 00 Sense Bytes: F0 00 02 80 00 00 3E 0A 00 00 00 00 3A 00 00 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk -2147483586 (valid) cdrecord: No disk / Wrong disk! And then the drive hung. This could be because the data write actually didn't go well before or the fixation did previously damage the disk, but I'd like some idea if the above lines in the kernel config should have fixed my _whole_ problem before I sacrfice another blank CD. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907122025.QAA24955>