All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nic Rodgers <nic@bbmcarlson.com>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB on PPC (YellowDog) ?
Date: Tue, 11 Nov 2003 17:55:12 +0000	[thread overview]
Message-ID: <marc-lartc-106857501122164@msgid-missing> (raw)

I'm at a bit of a loss. I've followed the lartc.org howto and read the stuff
on docum.org too, but still can't get HTB working on my PowerPC-based
YellowDog linux system.

I've compiled a custom kernel:

Linux 2.4.20 #1 Tue Nov 11 11:52:48 GMT 2003 ppc ppc ppc GNU/Linux


The relevant options I used in my linux .config file are:

ONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y


I have rebooted with this kernel but don't seem to have HTB:


I have QOS enabled for sure:

[root@bsd3 iproute2]# grep qdisc_get_rtab /proc/ksyms
c0158c58 qdisc_get_rtab_R3adce61c

But no HTB:

[root@bsd3 iproute2]# grep htb_qdisc_ops /proc/ksyms
[root@bsd3 iproute2]#


When I try eg:

[root@bsd3 iproute2]# tc qdisc add dev eth0 root handle 1: htb default 15
Unknown qdisc "htb", hence option "default" is unparsable

What do I need to do?


Many thanks,
Nic.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-11-11 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 17:55 Nic Rodgers [this message]
2003-11-12  1:09 ` [LARTC] HTB on PPC (YellowDog) ? Damjan

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=marc-lartc-106857501122164@msgid-missing \
    --to=nic@bbmcarlson.com \
    --cc=lartc@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.