All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Raphael Jacquot <raphael.jacquot@imag.fr>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: problem with libata and ich6m - 2.6.14-rc5
Date: Sat, 22 Oct 2005 08:18:52 -0400	[thread overview]
Message-ID: <435A2E2C.4080205@rtr.ca> (raw)
In-Reply-To: <435A28C2.3000104@imag.fr>

Raphael Jacquot wrote:
> hi
> I have a Dell inspiron 6000 with the following hardware :
> 
> 0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA 
> Controller (rev 03) (prog-if 80 [Master])
>         Subsystem: Dell: Unknown device 0188
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
>
> problem is, it doesn't attach the dvd drive properly...

libata is being paranoid about ATAPI devices,
and as of 2.6.14* it refuses to manage them unless you
supply the atapi_enabled=1 parameter to the kernel.

For built-in libata, use "libata.atapi_enabled=1" in your /boot/grub/menu.lst,
and for libata as a loadable module, put "options libata atapi_enabled=1"
into your /etc/modprobe.conf file (or whatever the nom de jour is for that).

Cheers

      reply	other threads:[~2005-10-22 12:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  1:17 libata sata_sil broken on 2.6.13.1 izvekov
2005-09-14  1:22 ` izvekov
2005-09-14 19:48 ` izvekov
2005-09-14 20:36   ` izvekov
2005-09-14 23:46     ` Andrew Morton
2005-09-15  0:19       ` izvekov
2005-09-15  5:37   ` Jeff Garzik
2005-09-15 13:27     ` Alan Cox
2005-09-15 20:13       ` izvekov
2005-09-15 22:30         ` Alan Cox
2005-09-15 22:56           ` izvekov
2005-09-16  3:42           ` izvekov
2005-09-16  6:41             ` Jeff Garzik
2005-09-16 22:10               ` Matheus Izvekov
2005-09-22  2:46                 ` Jeff Garzik
2005-09-16  0:07     ` izvekov
2005-10-22 11:55     ` problem with libata and ich6m - 2.6.14-rc5 Raphael Jacquot
2005-10-22 12:18       ` Mark Lord [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=435A2E2C.4080205@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raphael.jacquot@imag.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.