From: Jeff Garzik <jeff@garzik.org>
To: Tom Lanyon <tomlanyon@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Failure with SATA DVD-RW
Date: Thu, 06 Dec 2007 21:12:51 -0500 [thread overview]
Message-ID: <4758AC23.2080107@garzik.org> (raw)
In-Reply-To: <cd32a0620712041608o7733db74xf4975dec44925730@mail.gmail.com>
Tom Lanyon wrote:
> Hi list,
>
> Just built a new machine with a Pioneer SATA DVD drive and linux
> distro install CDs are not recognising it. The drive is connected to
> the ICH9R southbridge of an Intel P35 chipset motherboard.
>
> I can boot from the CD/DVD so the drive itself is working, but the
> kernel reports the following:
>
> scsi4: ahci
> ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: limiting speed to UDMA/44
> ata5: failed to recover some devices, retrying in 5 secs
> ata5: port is slow to respond, please be patient (Status 0x80)
> ata5: port failed to respond (30 secs, status 0x80)
> ata5: COMRESET failed (device not ready)
> ata5: hardreset failed, retrying in 5 secs
> ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: limiting speed to PIO0
> ata5: failed to recover some devices, retrying in 5 secs
> ata5: port is slow to respond, please be patient (Status 0x80)
> ata5: port failed to respond (30 secs, status 0x80)
> ata5: COMRESET failed (device not ready)
> ata5: hardreset failed, retrying in 5 secs
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: disabled
>
> This is 2.6.19 (probably with a few distribution patches) on an
> install CD. I also tried setting the SATA controller to a 'compatible
> IDE' mode and the hard drives and DVD drive are detected and work
> properly.
>
> Any ideas what to try to get it working under AHCI?
How does a remotely recent kernel behave? :)
There have been a metric ton^2 of fixes in this specific area, in the 12
months since 2.6.19 came out.
Jeff
prev parent reply other threads:[~2007-12-07 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 0:08 Failure with SATA DVD-RW Tom Lanyon
2007-12-06 1:33 ` Parag Warudkar
2007-12-07 0:39 ` Andrew Morton
2007-12-07 0:40 ` Andrew Morton
2007-12-10 9:45 ` Tejun Heo
2007-12-07 2:12 ` Jeff Garzik [this message]
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=4758AC23.2080107@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlanyon@gmail.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).