From: Carlo Wood <carlo@alinoe.com>
To: linux-kernel@vger.kernel.org
Subject: ide0=noprobe, hda=noprobe, hda=none ignored?
Date: Sun, 10 Jun 2007 20:54:39 +0200 [thread overview]
Message-ID: <20070610185439.GA12202@alinoe.com> (raw)
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.
The documentation also tells me that =none should CERTAINLY
make it ignore the non-existant drives - but it keeps probing.
Shouldn't an explicitely added kernel parameter be taken a
little bit more serious by the kernel? Independent on whether
or not a drive is detected (or what the CMOS might think about
that), I think that the kernel should REALLY, totally ignore
an ide and/or hdX if so explicitely requested with a kernel
parameter.
Anything I missed?
--
Carlo Wood <carlo@alinoe.com>
PS Sorry if this is a FAQ (it seems so) -- I just can't find
a satisfactory answer anywhere as to why explicit parameters
like this are ignored and want to ask to change this. Or,
I cannnot find the solution for this problem and get my
damn ide0 NOT probed.
next reply other threads:[~2007-06-10 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 18:54 Carlo Wood [this message]
2007-06-11 11:13 ` ide0=noprobe, hda=noprobe, hda=none ignored? Alexander E. Patrakov
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=20070610185439.GA12202@alinoe.com \
--to=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