linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Block <bebl@mageta.org>
To: linux-modules@vger.kernel.org
Subject: Can't load modules with parameters given
Date: Thu, 19 Dec 2013 19:31:36 +0100	[thread overview]
Message-ID: <52B33B88.2090306@mageta.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Hi,

I have a rather strange problem currently. I am trying to load a module
with some parameters (bnx2x with disable_tpa=1) and it fails because
this parameter is unknown according to dmesg. But modinfo lists this
exact paramter and it is also included in the source. And while this is
not an in-tree driver, I could also replicate the same behavior with
in-tree device drivers (like bonding with the parameter tx_queues):

$ modprobe bonding # works fine
$ rmmod bonding
$ modprobe bonding tx_queues=32
modprobe: ERROR: could not insert 'bonding': Unknown symbol in module,
or unknown parameter (see dmesg)

and dmesg tells me:
	bonding: Unknown parameter `tx_queues'
and nothing else (as with bnx2x, this parameter is listed by modinfo).

Is there some obvious kernel-config-option I could have messed up or
something else like this?

I am using a Gentoo-Userspace kmod (v15) with a Ubuntu-Kernel (3.8.13.13
- this is a version with some ubuntu-patches applied) - I know, the
combination is rather strange. Any ideas?

best regards,
- Benjamin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

             reply	other threads:[~2013-12-19 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 18:31 Benjamin Block [this message]
2013-12-22 21:16 ` Can't load modules with parameters given Lucas De Marchi
2013-12-22 23:15   ` Benjamin Block

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=52B33B88.2090306@mageta.org \
    --to=bebl@mageta.org \
    --cc=linux-modules@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;
as well as URLs for NNTP newsgroup(s).