From: Chr <chunkeey@web.de>
To: linux-ide@vger.kernel.org
Cc: chunkeey@web.de
Subject: Re: libata: ATA_PIIX missing ICH8M PCIIDs.
Date: Mon, 18 Jun 2007 15:52:37 +0200 [thread overview]
Message-ID: <200706181552.37776.chunkeey@web.de> (raw)
In-Reply-To: <20070618144207.751a254b@the-village.bc.nu>
On Monday, 18. June 2007, Alan Cox wrote:
> On Mon, 18 Jun 2007 15:20:06 +0200
> Chr <chunkeey@web.de> wrote:
>
> > Hi,
> >
> > I got a new laptop and I had a little problem that the DVD drive wasn't recognized by
> > libata's piix driver (but the old IDE Subsystem found it!).
> >
> > So, after adding the new pciid 8086:2850 it works!
> > But, I don't know if it's ich_pata_100 or ich_pata_133 since the
> > dvd/cd drives only goes up to udma2 speeds.
>
> Its ich_pata_133 - all the newer chips are. They work even better if you
> set them into AHCI mode in the BIOS and then they should "just work" with
> recent kernels as the AHCI driver now matches by class.
>
> Alan
>
>
No go.. I've tried 2.6.20-1-amd64 (debian sid) and a vanilla 2.6.22-rc5.
(The "problem" is that there are no options for that in the BIOS.
The BIOS itself is only useful on these laptops, if you want to set a BIOS
password, setting the system clock or change the boot order... and nothing else)
Thanks,
Chr.
next prev parent reply other threads:[~2007-06-18 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 13:20 libata: ATA_PIIX missing ICH8M PCIIDs Chr
2007-06-18 13:42 ` Alan Cox
2007-06-18 13:52 ` Chr [this message]
2007-06-18 17:57 ` Gaston, Jason D
2007-06-18 18:49 ` Chr
2007-06-18 18:57 ` Gaston, Jason D
2007-06-18 19:47 ` Jeff Garzik
2007-06-18 20:14 ` Chr
2007-06-24 12:18 ` [PATCH] libata: adding ICH8M PCIIDs to ATA_PIIX Chr
2007-06-18 20:44 ` libata: ATA_PIIX missing ICH8M PCIIDs Alan Cox
2007-06-18 19:14 ` Chr
2007-06-18 18:00 ` Gaston, Jason D
2007-06-18 20:41 ` Alan Cox
[not found] <39B20DF628532344BC7A2692CB6AEE07016FE54D@orsmsx420.amr.corp.intel.com>
2007-06-18 20:10 ` Chr
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=200706181552.37776.chunkeey@web.de \
--to=chunkeey@web.de \
--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).