public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Carlo Wood <carlo@alinoe.com>, linux-kernel@vger.kernel.org
Subject: Re: ide0=noprobe, hda=noprobe, hda=none ignored?
Date: Mon, 11 Jun 2007 17:13:22 +0600	[thread overview]
Message-ID: <466D2E52.4000904@ums.usu.ru> (raw)
In-Reply-To: <20070610185439.GA12202@alinoe.com>

Carlo Wood wrote:
> I've been trying for months to get my box to boot faster
> by ignoring the not connected hda/hdb (ide0).
> 
> ansset:~>dmesg | egrep '(noprobe|ide0|hda|hdb)'
> 
> Kernel command line: root=/dev/hde3 ro ide0=noprobe
>     ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:pio
> Probing IDE interface ide0...
> hda: IRQ probe failed (0xfffffdb8)
> etc.
> 
> or
> 
> Kernel command line: root=/dev/hde3 ro hda=none hdb=none
>     ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:pio
> Probing IDE interface ide0...
> hda: IRQ probe failed (0xfffffdb8)
> 
> same for hda=noprobe hdb=noprobe
> 
> Nothing helps.
> 
> Is this a bug or not? I'd think that saying "noprobe" means
> "do NOT probe" - but it probes anyway.


If your kernel uses modular IDE drivers and an initrd/initramfs that loads 
them, your result is the expected one (i.e.: not a bug). One should add the 
following or similar options into /etc/modprobe.conf in the initrd in order 
to get the result:

options ide_core options="ide0=noprobe hda=noprobe hdb=noprobe"

If you don't use initrd, or have a non-modular IDE driver, please ignore 
this message.

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-06-11 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 18:54 ide0=noprobe, hda=noprobe, hda=none ignored? Carlo Wood
2007-06-11 11:13 ` Alexander E. Patrakov [this message]
2007-06-12 12:51   ` Carlo Wood

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=466D2E52.4000904@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=carlo@alinoe.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