From: David Wagner <daw@cs.berkeley.edu>
Message-Id: <200901172226.n0HMQEEJ024690@taverner.cs.berkeley.edu>
Subject: Checking module parameters
To: linux-kernel@vger.kernel.org
Date: Sat, 17 Jan 2009 14:26:14 -0800 (PST)
Secret-Bounce-Tag: 9a029cbee41caf2ca77a77efa3c13981
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1035
Lines: 21

Is there a way to tell what options have been applied to a currently
loaded kernel module?

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.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/