mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregoire Favre <greg@ulima.unil.ch>
To: linux-kernel@vger.kernel.org, cdwrite@other.debian.org
Subject: Any hope to have a working 2.5 kernels for writing DVD?
Date: Fri, 21 Mar 2003 19:13:08 +0100	[thread overview]
Message-ID: <20030321181308.GA23131@ulima.unil.ch> (raw)

Hello,

I have already reported this "bug" for an older kernel:

Cdrecord-ProDVD-Clone 2.0 (i586-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
Unlocked features: ProDVD Clone 
Limited  features: speed 
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.7'
Driveropts: 'burnfree'
atapi: 1
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : 
Vendor_info    : 'SONY    '
Identifikation : 'DVD RW DRU-500A '
Revision       : '1.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd).
Driver flags   : DVD SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8126464 = 7936 KB
FIFO size      : 67108864 = 65536 KB
Track 01: data  4129 MB        
Total size:     4129 MB = 2114048 sectors
Current Secsize: 2048
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 184448
Starting to write CD/DVD at speed 1 in dummy TAO mode for single session.
Last chance to quit, starting dummy write in 9 seconds.  0.24% done, estimate finish Fri Mar 21 19:09:11 2003
   8 seconds.  0.47% done, estimate finish Fri Mar 21 19:12:42 2003
   7 seconds.  0.71% done, estimate finish Fri Mar 21 19:13:52 2003
  0.95% done, estimate finish Fri Mar 21 19:14:27 2003
   6 seconds.  1.18% done, estimate finish Fri Mar 21 19:13:24 2003
   5 seconds.  1.42% done, estimate finish Fri Mar 21 19:13:52 2003
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Starting new track at sector: 0
Track 01:    4 of 4129 MB written (fifo  97%)  16.3x.cdrecord-prodvd: Success. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 00 08 B8 00 00 1F 00
status: 0x1 (GOOD STATUS)
resid: 63488
cmd finished after 0.010s timeout 100s

write track data: error after 4571136 bytes
Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00
Writing  time:    5.371s
Average write speed 585.1x.
Fixating...
Fixating time:   77.468s
cdrecord-prodvd: fifo had 1095 puts and 73 gets.
cdrecord-prodvd: fifo was 0 times empty and 1 times full, min fill was 96%.

The command that give me that was:

mkisofs -dvd-video -V $1 $2 | cdrecord-prodvd driveropts=burnfree -dummy -v dev=/dev/hdc fs=64m speed=1 tsize={$SIZE}s -

Thank you very much,
 
	Grégoire
________________________________________________________________
http://ulima.unil.ch/greg ICQ:16624071 mailto:greg@ulima.unil.ch

             reply	other threads:[~2003-03-21 18:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 18:13 Gregoire Favre [this message]
2003-03-21 20:10 ` Jens Axboe
2003-03-21 20:21   ` Gregoire Favre
2003-03-24 13:34 Joerg Schilling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030321181308.GA23131@ulima.unil.ch \
    --to=greg@ulima.unil.ch \
    --cc=cdwrite@other.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®