From: "Berck E. Nash" <flyboy@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: libata Intel PIIX/ICH fails to detect both PATA drives, spews ACPI errors
Date: Mon, 12 Mar 2007 17:40:22 -0600 [thread overview]
Message-ID: <45F5E4E6.7010600@gmail.com> (raw)
In-Reply-To: <45F546C0.1030502@gmail.com>
Tejun Heo wrote:
>>>>>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>>>>>> chip, and I've got two optical drives connected to it. The master drive
>>>>>> fails to detect. The slave detects and works properly.
>>>>> Can you test 2.6.20.1 and post full dmesg?
>>>> Here's 2.6.20.2... No ACPI errors, but still doesn't detect both drives.
>>> Please apply the attached patch and see if it works. If it works,
>>> please post the result of hdparm -I /dev/srX of the optical drive. Thanks.
>> You forgot to attach the patch :)
> Heh heh. Sorry about that. Here it is.
It works! I'm having trouble getting the hdparm info for you, it
doesn't seem to like the libata interface? Appears to be the newest
version of hdparm (6.9). Something I'm missing?
luna:~# hdparm -I /dev/sr0
/dev/sr0:
HDIO_DRIVE_CMD(identify) failed: Input/output error
luna:~# hdparm -i /dev/sr0
/dev/sr0:
HDIO_GET_IDENTITY failed: Inappropriate ioctl for device
luna:~# sdparm -i /dev/sr0
/dev/sr0: LITE-ON LTR-48246S SS0E [cd/dvd]
INQUIRY fetching VPD page=0x83 failed
next prev parent reply other threads:[~2007-03-12 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 16:19 libata Intel PIIX/ICH fails to detect both PATA drives, spews ACPI errors Berck E. Nash
2007-02-27 15:01 ` Tejun Heo
2007-03-11 12:40 ` Berck E. Nash
2007-03-12 7:09 ` Tejun Heo
2007-03-12 12:02 ` Berck E. Nash
2007-03-12 12:25 ` Tejun Heo
2007-03-12 23:40 ` Berck E. Nash [this message]
2007-03-13 1:53 ` Mark Lord
2007-04-28 16:20 ` Berck E. Nash
2007-03-14 1:46 ` Berck E. Nash
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=45F5E4E6.7010600@gmail.com \
--to=flyboy@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.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).