mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: David Wagner <daw@cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Checking module parameters
Date: Sun, 18 Jan 2009 02:47:53 +0300	[thread overview]
Message-ID: <b6fcc0a0901171547o26a2cd1l86dc09fcb28a667@mail.gmail.com> (raw)
In-Reply-To: <200901172226.n0HMQEEJ024690@taverner.cs.berkeley.edu>

On Sun, Jan 18, 2009 at 1:26 AM, David Wagner <daw@cs.berkeley.edu> wrote:
> Is there a way to tell what options have been applied to a currently
> loaded kernel module?

/sys/module/[module name]/parameters/ (if i remember correctly)

> I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created
> a file /etc/modprobe.d/local containing:
>  options libata force=1.5Gbps
> However my SATA drive gets loaded at 3Gbps.  I'm trying to figure out how
> to debug this so that I can tell whether the option got correctly applied
> to the libata module, and if not, how to force the SATA link to 1.5Gbps.
> Any suggestions or ideas?
>
> (I can't set libata.force=1.5Gbps as a kernel argument because on my
> Fedora kernel, libata is loaded as a module rather than built into the
> kernel.  I can't run "modprobe libata force=1.5Gbps" by hand because
> I've got SATA drives, so the libata module is automatically loaded before
> I get shell access.)

This may not work if libata module is loaded from initrd.

  reply	other threads:[~2009-01-17 23:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 22:26 David Wagner
2009-01-17 23:47 ` Alexey Dobriyan [this message]
2009-01-18  0:22 ` Robert Hancock
2009-01-18 15:59 ` Yanko Kaneti
2009-01-18 18:58 ` Alan Cox
     [not found] <bVsVO-15X-19@gated-at.bofh.it>
2009-01-19  9:38 ` Nick Craig-Wood
2009-01-19 10:19   ` Stefan Richter
2009-01-19 12:44     ` Nick Craig-Wood
2009-01-19 13:06       ` Stefan Richter

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=b6fcc0a0901171547o26a2cd1l86dc09fcb28a667@mail.gmail.com \
    --to=adobriyan@gmail.com \
    --cc=daw@cs.berkeley.edu \
    --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

Powered by JetHome