Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9066] New: 8139TOO - faulty behaviour
Date: Mon, 04 Jul 2016 12:35:21 +0000	[thread overview]
Message-ID: <bug-9066-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9066

            Bug ID: 9066
           Summary: 8139TOO - faulty behaviour
           Product: buildroot
           Version: 2016.02
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mgross at stephan-gmbh.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I've built a Linux for a PC/104 module equipped with a Geode LX800.
NIC is a Realtek 8139DL.
In the kernel-config I chose the 8139TOO driver to be built in the kernel.
It is possible to set the interface up via 

ifconfig eth0 up 

and to assign an IP address with

ifconfig eth0 192.168.10.2 netmask 255.255.255.0

Unfortunately pinging another system is not possible.
Every time I try it puts out a message like:

[  130.720092] 9139too 000:00:0e.0 eth0 link up, 100MBps, full-duplex, lpa
0xC5E1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-07-04 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 12:35 bugzilla at busybox.net [this message]
2016-07-24 20:45 ` [Buildroot] [Bug 9066] 8139TOO - faulty behaviour bugzilla at busybox.net

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=bug-9066-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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