From: Will Trives <will@trivescon.com.au>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
yannick.dirou@axetic.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size
Date: Wed, 12 Dec 2007 19:16:06 +1100 [thread overview]
Message-ID: <1197447366.3467.10.camel@Athas> (raw)
In-Reply-To: <475F98C9.6080804@gmail.com>
On Wed, 2007-12-12 at 17:16 +0900, Tejun Heo wrote:
Will Trives wrote:
> > Hello guys,
> >
> > Yannick does it work ok for you when you try to blank a dvd+rw disc ?
> > Mine no longer jams up the drive now but it does say that the media or
> > drive does not support blanking. I'm thinking its either because these
> > discs just do multisession so this is what was meant to happen all along
> > or there's still something going on.
>
> Does the kernel complain about anything?
>
Nope.
> This drive or media does not support the 'BLANK media' command
> > wodim: Cannot blank disk, aborting.
> > wodim: Some drives do not support all blank types.
> > wodim: Try again with wodim blank=all.
>
> wodim suggests "blank=all", does it work?
>
Nope same thing happens.
"dvd+rw-format /dev/sr0 -force" Works ok though.
This is the media info after the format
dvd+rw-mediainfo /dev/sr0
INQUIRY: [BENQ ][DVD DD DW1640 ][BSRB]
GET [CURRENT] CONFIGURATION:
Mounted Media: 1Ah, DVD+RW
Current Write Speed: 4.0x1385=5540KB/s
Write Speed #0: 4.0x1385=5540KB/s
Write Speed #1: 2.4x1385=3324KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 4.0x1385=5540KB/s@[0 -> 264671]
Speed Descriptor#0: 00/264671 R@5.2x1385=7181KB/s W@4.0x1385=5540KB/s
Speed Descriptor#1: 00/264671 R@5.2x1385=7181KB/s W@2.4x1385=3324KB/s
READ DVD STRUCTURE[#0h]:
Media Book Type: 00h, DVD-ROM book [revision 0]
Media ID: MKM/A02
Legacy lead-out at: 264672*2KB=542048256
READ DISC INFORMATION:
Disc status: complete
Number of Sessions: 1
State of Last Session: complete
Number of Tracks: 1
BG Format Status: suspended
READ FORMAT CAPACITIES:
formatted: 264672*2048=542048256
26h(0): 2295104*2048=4700372992
READ TRACK INFORMATION[#1]:
Track State: complete
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Track Size: 2295104*2KB
FABRICATED TOC:
Track#1 : 14@0
Track#AA : 17@2295104
Multi-session Info: #1@0
READ CAPACITY: 2295104*2048=4700372992
next prev parent reply other threads:[~2007-12-12 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 3:12 [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size Tejun Heo
2007-12-12 3:21 ` [PATCH #upstream-fixes] libata: fix ATAPI draining Tejun Heo
2007-12-18 1:43 ` Jeff Garzik
2007-12-12 8:05 ` [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size Will Trives
2007-12-12 8:16 ` Tejun Heo
2007-12-12 8:16 ` Will Trives [this message]
2007-12-12 8:38 ` Tejun Heo
2007-12-12 8:50 ` Will Trives
2007-12-12 8:48 ` Yannick Dirou
2007-12-18 1:37 ` Jeff Garzik
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=1197447366.3467.10.camel@Athas \
--to=will@trivescon.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=yannick.dirou@axetic.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;
as well as URLs for NNTP newsgroup(s).