public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: "Brian D. McGrew" <brian@visionpro.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: jeremy@emperorlinux.com
Subject: Re: 2.6.16.16 Lost CD-ROM Drive
Date: Thu, 01 Feb 2007 17:37:12 -0600	[thread overview]
Message-ID: <45C279A8.9080501@shaw.ca> (raw)
In-Reply-To: <fa.Qe/B25xsBoYC29PSTYgHZvs0dwA@ifi.uio.no>

Brian D. McGrew wrote:
>> What am I missing to get the 2.6.16.16 kernel to see a SATA CD-ROM
> drive
>> in normal, non-legacy move?
> 
> Try booting 2.6.16 with the following options:
> 
> libata.atapi_enabled=1 ide0=noprobe ide1=noprobe
> -----
> 
> Still no go.  /dev/sda* is created for the hard drive but no CD-ROM and
> the same ATAPI error in dmesg.

If libata is built as a module, putting libata.atapi_enabled=1 on the 
kernel command line won't work. In that case, try putting

options libata atapi_enabled=1

in /etc/modprobe.conf. Of course if libata is being loaded from the 
initrd that may not work, in which case the easiest solution is likely 
to just build it into the kernel so that the kernel command line method 
will work.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-01 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.Qe/B25xsBoYC29PSTYgHZvs0dwA@ifi.uio.no>
2007-02-01 23:37 ` Robert Hancock [this message]
2007-02-01 15:48 2.6.16.16 Lost CD-ROM Drive Brian D. McGrew
2007-02-01 16:33 ` Stephen John Smoogen
  -- strict thread matches above, loose matches on Subject: below --
2007-02-01 15:00 Brian D. McGrew
2007-02-01 15:05 ` Jeremy L. Moles
2007-02-01 15:11   ` Rogelio_Noriega

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=45C279A8.9080501@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=brian@visionpro.com \
    --cc=jeremy@emperorlinux.com \
    --cc=linux-kernel@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