All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Powell <medp@primagraphics.co.uk>
To: Aubrey Lee <aubrey1127@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: About Zebra Error
Date: Thu, 13 Jan 2005 09:18:09 +0000	[thread overview]
Message-ID: <41E63CD1.901@primagraphics.co.uk> (raw)
In-Reply-To: <7f834d4e0501130050666b757a@mail.gmail.com>

Aubrey Lee wrote:

> hi, In the PC(i686) system, I build and run zebra successfully. And now
>I'm porting it to the powerpc system. Cross-compiling finished without error.
>But when I run the zebra from my target board, it gives me  a big headache:
>--------------------------------------------------------------------------  
>bash-2.05b# /opt/zebra/sbin/zebra
>             sock: Address family not supported by protocol
>----------------------------------------------------------------------------
>And Up to now I cann't find the message in the souce 
>code files.  
>     The two ethx and their driver of my board is OK.
>     What shall I do?
>  
>
I had a similar message when running udhcpd. The problem was that some 
network drivers were built as modules. Adding the following to 
modules.conf cured my problem:

    # PF_PACKET support needed by udhcpc
    alias net-pf-17 af_packet

-- 
Mark Powell, Senior Software Engineer
Curtiss-Wright Controls Embedded Computing
Tel: +44 (0) 1763 852222
Email: medp@primagraphics.com

  parent reply	other threads:[~2005-01-13  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  8:50 About Zebra Error Aubrey Lee
2005-01-13  9:12 ` Eugene Surovegin
2005-01-13  9:18 ` Mark Powell [this message]
2005-01-13 17:07 ` Tolunay Orkun
  -- strict thread matches above, loose matches on Subject: below --
2005-01-13 10:00 About zebra Error Aubrey Lee

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=41E63CD1.901@primagraphics.co.uk \
    --to=medp@primagraphics.co.uk \
    --cc=aubrey1127@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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.