All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:48:49 -0500	[thread overview]
Message-ID: <43F0AA61.1000607@cfl.rr.com> (raw)
In-Reply-To: <20060213160024.5e01fa46@silver>

iSteve wrote:
> 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
>   

The media must be formatted first before you can write to it.  It looks 
like you just tried to write to an unformatted disc.  Use cdrwtool -q 
first to format it, then cdrwtool -f foo.img to write out your image. 



  reply	other threads:[~2006-02-13 15:49 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 [this message]
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=43F0AA61.1000607@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.