PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : schreibender zugriff auf cd-writer bricht ab



chimaera
06.01.03, 10:45
hi.. ich hatte vor einiger zeit mein system neu aufgesetzt (debian sid, 2.4.20) und bin erst jetzt dazu gekommen meinen brenner zu testen.. lesend kann ich auf beide cd-laufwerke ohne probleme zugreifen (beide scsi-ide). beim versuch irgendetwas zu schreiben bricht sowohl cdrecord als auch cdrdao mit gleicher fehlermeldung ab. im syslogsteht auch noch einiges.. der brenner funktioniert aber wintendo, einen hardware-defekt kann man wohl ausschliessen, und auch unter debian hatte ich ihn schon am laufen.. nachfolgend die ausgaben von cdrecord, cdrdao und etwas passendes im syslog (stört euch nicht an den uhrzeiten.. das waren verschiedene vesruche, allerdings tauchen die syslog-einträge immer dann auf wenn ich versuche schreibend auf den brenner zuzugreifen..)

cdrecord
-----------------------
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.24
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.7'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'SONY '
Identifikation : 'CD-RW CRX140E '
Revision : '1.0n'
Device seems to be: Generic CD-ROM.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC-2 SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 4183808 = 4085 KB
FIFO size : 16777216 = 16384 KB
0.23% done, estimate finish Sun Jan 5 16:47:34 2003
0.46% done, estimate finish Sun Jan 5 16:47:34 2003
0.70% done, estimate finish Sun Jan 5 16:47:34 2003
0.92% done, estimate finish Sun Jan 5 16:47:34 2003
1.15% done, estimate finish Sun Jan 5 16:47:34 2003
1.38% done, estimate finish Sun Jan 5 16:47:34 2003
1.62% done, estimate finish Sun Jan 5 16:47:34 2003
1.84% done, estimate finish Sun Jan 5 16:47:34 2003
2.07% done, estimate finish Sun Jan 5 16:47:34 2003
2.30% done, estimate finish Sun Jan 5 16:47:34 2003
2.54% done, estimate finish Sun Jan 5 16:47:34 2003
2.76% done, estimate finish Sun Jan 5 16:47:34 2003
2.99% done, estimate finish Sun Jan 5 16:47:34 2003
3.22% done, estimate finish Sun Jan 5 16:47:34 2003
3.46% done, estimate finish Sun Jan 5 16:47:34 2003
Track 01: data 424 MB
Total size: 487 MB (48:17.92) = 217344 sectors
Lout start: 487 MB (48:19/69) = 217344 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type B, low Beta category (B-) (4)
ATIP start of lead in: -11768 (97:25/07)
ATIP start of lead out: 359775 (79:59/00)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 64
Manufacturer: MPO
Blocks total: 359775 Blocks current: 359775 Blocks remaining: 142431
Starting to write CD/DVD at speed 8 in dummy SAO mode for single session.
Last chance to quit, starting dummy write in 2 seconds.
 1 seconds.
 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ...
input buffer ready.
Sending CUE sheet...
/usr/bin/cdrecord: WARNING: Drive returns wrong startsec (0) using -150
Writing pregap for track 1 at -150
Starting new track at sector: 0

Track 01: 0 of 424 MB written.
3.68% done, estimate finish Sun Jan 5 16:48:55 2003

Track 01: 1 of 424 MB written (fifo 99%) [buf 33%] 34.2x.
3.91% done, estimate finish Sun Jan 5 16:48:50 2003

Track 01: 2 of 424 MB written (fifo 100%) [buf 59%] 36.6x.
4.14% done, estimate finish Sun Jan 5 16:48:46 2003
4.38% done, estimate finish Sun Jan 5 16:48:42 2003

Track 01: 3 of 424 MB written (fifo 98%) [buf 83%] 35.5x.

Track 01: 4 of 424 MB written (fifo 99%) [buf 98%] 0.3x.
4.60% done, estimate finish Sun Jan 5 16:56:36 2003

Track 01: 5 of 424 MB written (fifo 100%) [buf 97%] 8.0x.
4.83% done, estimate finish Sun Jan 5 16:56:11 2003
/usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 0B 24 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 06 00 00 00 00 12 00 00 00 00 29 00 00 00
Sense Key: 0x6 Unit Attention, Segment 0
Sense Code: 0x29 Qual 0x00 (power on, reset, or bus device reset occurred) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 5.063s timeout 200s
Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00
write track data: error after 5840896 bytes
Writing time: 33.908s
Average write speed 86.5x.
Min drive buffer fill was 97%
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
Fixating time: 0.002s
/usr/bin/cdrecord: fifo had 347 puts and 93 gets.
/usr/bin/cdrecord: fifo was 0 times empty and 22 times full, min fill was 96%.

misc
-----------------------
217344


cdrdao
-----------------------
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
0,1,0: SONY CD-RW CRX140E Rev: 1.0n
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0010)
Starting write simulation at speed 8...
Process can be aborted with QUIT signal (usually CTRL-\).
Writing track 01 (mode MODE1_RAW/MODE1_RAW )...
Wrote 1 of 29 MB (Buffer 100%).

Wrote 2 of 29 MB (Buffer 100%).

Wrote 3 of 29 MB (Buffer 100%).

Wrote 4 of 29 MB (Buffer 100%).

Wrote 5 of 29 MB (Buffer 100%).

Wrote 6 of 29 MB (Buffer 100%).

Wrote 7 of 29 MB (Buffer 100%).

Wrote 8 of 29 MB (Buffer 100%).

Wrote 9 of 29 MB (Buffer 100%).

Wrote 10 of 29 MB (Buffer 100%).

Wrote 11 of 29 MB (Buffer 100%).

Wrote 12 of 29 MB (Buffer 100%).

Wrote 13 of 29 MB (Buffer 100%).

Wrote 14 of 29 MB (Buffer 100%).

?: Input/output error. : scsi sendcmd: no error
CDB: 2A 00 00 00 18 9C 00 00 1A 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 C0
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid) error refers to command part, bit ptr 0 (not valid) field ptr 0
cmd finished after 0.037s timeout 180s
ERROR: Write data failed.
ERROR: Writing failed - buffer under run?
ERROR: Simulation failed.

syslog
---------------
Jan 5 18:22:05 kyuss kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:22:05 kyuss kernel: hdd: drive_cmd: error=0x04
Jan 5 18:22:46 kyuss kernel: hdd: DMA disabled
Jan 5 18:23:03 kyuss kernel: hdd: status error: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:23:03 kyuss kernel: hdd: status error: error=0x04
Jan 5 18:23:03 kyuss kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
Jan 5 18:23:19 kyuss kernel: hdd: status error: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:23:19 kyuss kernel: hdd: status error: error=0x04
Jan 5 18:23:19 kyuss kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
Jan 5 18:23:29 kyuss kernel: hdd: status error: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:23:29 kyuss kernel: hdd: status error: error=0x04
Jan 5 18:23:29 kyuss kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
Jan 5 18:23:34 kyuss kernel: hdd: status error: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:23:34 kyuss kernel: hdd: status error: error=0x04
Jan 5 18:23:34 kyuss kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
Jan 5 18:23:49 kyuss kernel: hdd: status error: status=0x51 { DriveReady SeekComplete Error }
Jan 5 18:23:49 kyuss kernel: hdd: status error: error=0x04
Jan 5 18:23:49 kyuss kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted

Jorge
06.01.03, 11:19
/dev/hdd verträgt scheinbar den DMA nicht, deshalb schaltet der Kernel es ab.Deaktiviere mal DMA für /dev/hdd und jage mal die " DriveReady SeekComplete Error" durch google, sollte sich was finden lassen.

chimaera
06.01.03, 12:09
dma zu deaktivieren bringt keine änderung..
eine suche bringt viele fragen und wenig/ungenaue antworten: probleme mit via chipsets, falsche/defekte ide-kabel, defekte geräte usw.. das kann ich aber ausschliessen, da der brenner a) unter wintendo funktioniert und b) auch unter woody gelaufen ist.

/edit

ok, definitiv ein problem mit dem chipsatz-treiber im 2.4.20er kernel.. wenn ich support für mein chipset entferne dann läuft das dingens! (könnte evtl sogar doch ein dma prob sein, da kein chipsatz-treiber -> kein dma.. (obwohl ichs vorher auch deaktiviert habe..))

chimaera
07.01.03, 17:50
lösung gefunden.. gepostet in debianforum.de


es gab hier ein problem mit dem via-chipsatz-treiber und dem vt8235.. das ganze wurde in der kml diskutiert und es gibt einen kleinen patch von pavlik:

http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=20021219112640.A21164%40ucw.cz.lucky.linux.ke rnel

jetzt läuft das dingens wieder.. ;-7