All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: gnychis@cmu.edu
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.4.32: unresolved symbol unregister_qdisc
Date: Sat, 08 Apr 2006 15:54:30 -0700 (PDT)	[thread overview]
Message-ID: <20060408.155430.111013393.davem@davemloft.net> (raw)
In-Reply-To: <32947.128.2.140.234.1144536454.squirrel@128.2.140.234>

From: "George P Nychis" <gnychis@cmu.edu>
Date: Sat, 8 Apr 2006 18:47:34 -0400 (EDT)

> Hey,
> 
> I have a kernel module that uses unregister_qdisc and register_qdisc, whenever i try to insert the module I get:
> /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: unresolved symbol unregister_qdisc
> /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: unresolved symbol register_qdisc
> 
> Am i missing some sort of support in the kernel?

Make sure CONFIG_NET_SCHED is enabled and that you compiled your module against
that kernel.

Where does this sch_xcp come from?  It's not in the vanilla sources.

Also, please direct networking questions to the netdev@vger.kernel.org
mailing list which I have added to the CC:.

  reply	other threads:[~2006-04-08 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 22:47 2.4.32: unresolved symbol unregister_qdisc George P Nychis
2006-04-08 22:54 ` David S. Miller [this message]
2006-04-08 23:18   ` George P Nychis
2006-04-08 23:37     ` Randy.Dunlap
2006-04-09 17:37       ` George P Nychis
2006-04-09 20:03         ` Randy.Dunlap
2006-04-09 20:06           ` George P Nychis
2006-04-10  2:05           ` George P Nychis
2006-04-10  2:29             ` Randy.Dunlap
2006-04-10  2:49               ` George P Nychis
2006-04-10  2:59                 ` Randy.Dunlap
2006-04-10  3:20                   ` George P Nychis
2006-04-10  3:29                     ` Randy.Dunlap
2006-04-10  4:24                       ` Willy Tarreau
2006-04-10  5:03                       ` George P Nychis

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=20060408.155430.111013393.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gnychis@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.