From: Tejun Heo <tj@kernel.org>
To: Tomas Kindl <supp@kpo.zcu.cz>
Cc: linux-ide@vger.kernel.org
Subject: Re: Fwd: confusion about libata.force=80c
Date: Sun, 16 Nov 2008 18:45:43 +0900 [thread overview]
Message-ID: <491FEBC7.4090608@kernel.org> (raw)
In-Reply-To: <loom.20081112T153626-485@post.gmane.org>
Tomas Kindl wrote:
> Tejun Heo <htejun <at> gmail.com> writes:
>
>>> Is force=80c what I want? Should it work?
>> It should but is overridden by device side cable detection upto 2.6.25.
>> 2.6.26 will have it fixed. force=udma66 should work.
>>
>
> Hi, I get same error (Unknown boot option `libata.force=3:1.5': ignoring
> ) although I am trying it on 2.6.27.4 (MDV flavor - but still).
That's not a kernel problem but how module parameters are passed to
modules loaded from initrd and is distro specific. Please note that
kernel will spit the message even when the module parameter is later
picked up by initrd. So, please ping MDV for instructions on how to
pass kernel parameter via initrd.
--
tejun
prev parent reply other threads:[~2008-11-16 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 18:20 confusion about libata.force=80c Tom Sylla
2008-05-20 9:22 ` Fwd: " Tom Sylla
2008-05-21 5:57 ` Tejun Heo
2008-11-12 15:39 ` Tomas Kindl
2008-11-16 9:45 ` Tejun Heo [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=491FEBC7.4090608@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=supp@kpo.zcu.cz \
/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).