From: Phillip Susi <psusi@cfl.rr.com>
To: iSteve <isteve@rulez.cz>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: Packet writing issue on 2.6.15.1
Date: Mon, 13 Feb 2006 14:45:48 -0500 [thread overview]
Message-ID: <43F0E1EC.4050804@cfl.rr.com> (raw)
In-Reply-To: <20060213185112.79da8ecc@silver>
Hrm... the format appears to be failing with a seek error. My guess as
to the cause of this is either bad media or a bad drive. Are you sure
this drive can handle 80 min / 700 MB disks?
I'm not sure this switch does what I think it does because I don't have
the source code in front of me, but after blanking try:
cdrwtool -m 259808
If that did what I think it does, it should attempt to format the disc,
but not all of it. If the drive just doesn't like the outer edges, that
might work.
iSteve wrote:
> Tried. Tried also with setting -t 10 (the medium is 10x), without -p 1 (still
> trying fixed packet size, same size). Out of four attempts, all failed.
> ----[snipet]----
> # cdrwtool -d /dev/cdrw -q -p 1
> using device /dev/cdrw
> fixed packets
> 4690KB internal buffer
> setting write speed to 12x
> Settings for /dev/cdrw:
> Fixed packets, size 32
> Mode-2 disc
>
> I'm going to do a quick setup of /dev/cdrw. The disc is going to be blanked and
> formatted with one big track. All data on the device will be lost!! Press
> CTRL-C to cancel now. ENTER to continue.
>
> Initiating quick disc blank
> Disc capacity is 295264 blocks (590528KB/576MB)
> Formatting track
> wait_cmd: Input/output error
> Command failed: 04 17 00 00 00 00 00 00 00 00 00 00 - sense 05.64.00
> format disc: Illegal seek
> ---[/snipet]----
>
> DMESG:
> cdrom: This disc doesn't have any tracks I recognize!
>
> Please note that although I've been testing packet writing on 2.6.15.1, I'm
> performing the initial burning on 2.6.12.1(+ squashfs), I apologize for not
> mentioning this.
>
> The udftools are from Debian, in version 1.0.0b3-11.
>
next prev parent reply other threads:[~2006-02-13 19:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 9:35 Packet writing issue on 2.6.15.1 iSteve
2006-02-11 11:30 ` Peter Osterlund
2006-02-11 11:48 ` iSteve
2006-02-11 15:59 ` Peter Osterlund
2006-02-11 16:08 ` iSteve
2006-02-11 20:09 ` Phillip Susi
2006-02-11 20:14 ` iSteve
2006-02-12 1:10 ` Phillip Susi
2006-02-12 4:54 ` Ville Syrjälä
2006-02-12 8:07 ` Paul
2006-02-13 0:32 ` Phillip Susi
2006-02-13 4:40 ` Paul
2006-02-13 15:45 ` Phillip Susi
2006-02-12 8:23 ` iSteve
2006-02-12 10:32 ` Jan Engelhardt
2006-02-12 10:46 ` iSteve
2006-02-13 0:34 ` Phillip Susi
2006-02-13 15:00 ` iSteve
2006-02-13 15:48 ` Phillip Susi
2006-02-13 17:51 ` iSteve
2006-02-13 19:45 ` Phillip Susi [this message]
2006-02-13 19:55 ` iSteve
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=43F0E1EC.4050804@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=isteve@rulez.cz \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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