public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: Phillip Susi <psusi@cfl.rr.com>
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 16:00:24 +0100	[thread overview]
Message-ID: <20060213160024.5e01fa46@silver> (raw)
In-Reply-To: <43EFD42D.6040102@cfl.rr.com>

On Sun, 12 Feb 2006 19:34:53 -0500
Phillip Susi <psusi@cfl.rr.com> wrote:
> So you want to write data to the disc without using pktcdvd?  cdrwtool 
> -f allows you to write an image file to the disc, though I don't see why 
> you don't want to use pktcdvd.  If you want to be able to read/write the 
> disc on the fly, you must either use pktcdvd or format the disc in MRW 
> mode.
> 

I tried that. Mostly, writing failed. At cdrwtool's end, it looked like this:
using device /dev/cdrw
fixed packets
setting speed to 10
write file /root/udftest.img
4690KB internal buffer
setting write speed to 10x
writing at lba = 0, blocks = 32
wait_cmd: Input/output error
Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense 05.24.00

At kernel's end:
cdrom: This disc doesn't have any tracks I recognize!

Once I, somehow, managed to write it. However, writing ISO9660 (yes, I know
that iso9660 doesn't support read/write; I use it for test though and I need
it working), attempt to read it returned this:

attempt to access beyond end of device
hdc: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
-- 
 -- iSteve

  reply	other threads:[~2006-02-13 15:00 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 [this message]
2006-02-13 15:48                         ` Phillip Susi
2006-02-13 17:51                           ` iSteve
2006-02-13 19:45                             ` Phillip Susi
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=20060213160024.5e01fa46@silver \
    --to=isteve@rulez.cz \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=psusi@cfl.rr.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