linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: nick@ukfsn.org
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:44:27 +0200	[thread overview]
Message-ID: <200710192344.27312.bzolnier@gmail.com> (raw)
In-Reply-To: <200710192212.30533.nick@ukfsn.org>

On Friday 19 October 2007, Nick Warne wrote:
> On Friday 19 October 2007 22:07:43 Lennart Sorensen wrote:
> > On Fri, Oct 19, 2007 at 10:03:09PM +0100, Nick Warne wrote:
> > > No change:
> > >
> > > ide_setup: hdd=ide-cd
> > >     ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
> > > hdd: TSSTcorp CDDVDW SH-S202J, ATAPI CD/DVD-ROM drive
> > > hdd: drive side 80-wire cable detection failed, limiting max speed to
> > > UDMA33 hdd: selected mode 0x42
> > > hdd: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
> >
> > Did you try another cable?  DId you try using both the old IDE drivers
> > and the new PATA libata drivers?  What is the hdd=ide-cd supposed to
> > do?  Do you have a device present as hdc and if not, then why not?
> > (Hint: ATA spec requires a master before you can have a slave, even
> > though it frequently does work with just a slave.  Of course cable
> > select seems even nicer since then the device at the end of an 80 wire
> > cable is automatically master, and any additional device added to the
> > middle connector on the cable becomes slave, and you should not connect
> > a device to the middle connector without one on the end).
> >
> > Also make sure the right end of the cable is connected to the mainboard,
> > just in case that matters.
> 
> I have (since 2.6.15 at least) hda, hdb, hdc, and hdd.
> 
> hda and hdb are mounted at boot.  hdc is not mounted, as I leave that drive 
> for backups and mount as needed.
> 
> All I done was replace a duff cd/dvd drive (hdd) with a new one.

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

  reply	other threads:[~2007-10-19 21:39 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 [this message]
2007-10-19 22:04             ` Nick Warne
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=200710192344.27312.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=nick@ukfsn.org \
    /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).