From: Vojtech Pavlik <vojtech@suse.cz>
To: Jorge Nerin <comandante@zaralinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot write a 90' cd
Date: Fri, 24 May 2002 00:57:54 +0200 [thread overview]
Message-ID: <20020524005754.I27005@ucw.cz> (raw)
In-Reply-To: <3CED69EB.2060003@zaralinux.com>
On Fri, May 24, 2002 at 12:15:07AM +0200, Jorge Nerin wrote:
> Hello, I tried with kernels 2.5.16, 2.5.15 and 2.4.18 with a ide cdburner:
>
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: SAMSUNG Model: CD-R/RW SW-208B Rev: BS03
> Type: CD-ROM ANSI SCSI revision: 02
>
> with cdrecord --version
> Cdrecord 1.11a19 (i586-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
> but it's a 1.11a21, and a 2x200mmx 96Mb. and the results were rather disapointing:
>
> - 2.5.15 & 2.5.16 both hung my machine the moment cdrecord tried to write.
> - 2.4.18 wrote ok, until 702MB, then a scsi stopped the procces, detailed log of
> the cdrecord session follows:
> Note that this was a traxdata 90' silver cd, in the instructions they said that
> it will be detected as a 80' and that you should enable overburnung, cdrecord
> without options said that -overburn should be active, this session is with
> -overburn active.
>
> I don't have more 90' cd to try. I only managed to get one.
90 minute CD-Rs have a tighter leading track, and only some CD-R drives
are able to cope with that. For example my Ricoh doesn't, failing some
54 minutes after start. There is nothing you can do about that.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-05-23 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 22:15 Cannot write a 90' cd Jorge Nerin
2002-05-23 22:57 ` Vojtech Pavlik [this message]
2002-05-23 23:25 ` Jorge Nerin
2002-05-24 2:17 ` Marc Wilson
2002-06-04 22:36 ` Ricky Beam
2002-06-04 22:56 ` Ricky Beam
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=20020524005754.I27005@ucw.cz \
--to=vojtech@suse.cz \
--cc=comandante@zaralinux.com \
--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