From: Nick Warne <nick@ukfsn.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: New CD/DVD drive - 80-wire cable detection failure
Date: Fri, 19 Oct 2007 23:04:23 +0100 [thread overview]
Message-ID: <200710192304.23749.nick@ukfsn.org> (raw)
In-Reply-To: <200710192344.27312.bzolnier@gmail.com>
On Friday 19 October 2007 22:44:27 Bartlomiej Zolnierkiewicz wrote:
>
> Ah, so the patch won't help (sorry, I didn't pay enough attention).
>
> Len's advices are worth the try, also please send the output
> of hdparm -I /dev/hdd.
>
> Thanks,
> Bart
Yes, Len's advice has me wondering now. Do I have a dodgy cable? I will have
to change that tomorrow.
But more info. The old drive played DVD movies etc. OK, but slowly it became
worse until I couldn't read any one of them 9 times out of 10. CD play
back/burning was OK 100% all the time though - so I guessed the dvd laser
(whatever it does) was dead - hence why I bought a new one.
The new drive works perfectly, but for the udma33 issue. If it was the cable,
why would it read/burn CD OK, but not DVD sometimes on the old drive?
hdparm -I
/dev/hdd:
ATAPI CD-ROM, with removable media
Model Number: TSSTcorp CDDVDW SH-S202J
Serial Number:
Firmware Revision: SB00
Standards:
Supported: CD-ROM ATAPI-3 -4 -5 -6 -7
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
Capabilities:
LBA, IORDY(cannot be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=383ns IORDY flow control=120ns
BTW, thanks for help all.
Nick
--
Free Software Foundation Associate Member 5508
next prev parent reply other threads:[~2007-10-19 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710181832.42906.nick@ukfsn.org>
[not found] ` <200710192049.07877.nick@ukfsn.org>
2007-10-19 20:28 ` New CD/DVD drive - 80-wire cable detection failure Bartlomiej Zolnierkiewicz
2007-10-19 21:03 ` Nick Warne
2007-10-19 21:07 ` Lennart Sorensen
2007-10-19 21:12 ` Nick Warne
2007-10-19 21:44 ` Bartlomiej Zolnierkiewicz
2007-10-19 22:04 ` Nick Warne [this message]
2007-10-19 22:12 ` Lennart Sorensen
2007-10-19 22:28 ` Bartlomiej Zolnierkiewicz
2007-10-20 9:37 ` Nick Warne
2007-10-20 12:22 ` Nick Warne
2007-10-23 23:33 ` Bartlomiej Zolnierkiewicz
2007-10-24 17:03 ` Nick Warne
2007-10-24 21:13 ` Alan Cox
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=200710192304.23749.nick@ukfsn.org \
--to=nick@ukfsn.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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).