From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Mikhail Kshevetskiy <kl@laska.dorms.spbu.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: eepro100/e100 broken in 2.6.13-rc3
Date: Wed, 13 Jul 2005 23:28:15 -0700 [thread overview]
Message-ID: <4807377b05071323286963bf3a@mail.gmail.com> (raw)
In-Reply-To: <20050714034954.52947263@laska>
On 7/13/05, Mikhail Kshevetskiy <kl@laska.dorms.spbu.ru> wrote:
> symptom
> =======
> modprobe e100
> ifconfig eth0 <ip> netmask <netmask>
>
> result:
> =======
> SIOCADDRT: Network is unreachable
>
> There were no such error in 2.6.13-rc2
odd, both e100 and eepro100 are broken? This might indicate something
wierd with the pci layer. Don't know what might cause the Network is
unreachable...
please send lspci -vvv of the e100 device in question and any output from dmesg
added netdev in case someone has an idea there.
next parent reply other threads:[~2005-07-14 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050714034954.52947263@laska>
2005-07-14 6:28 ` Jesse Brandeburg [this message]
2005-07-14 7:26 ` eepro100/e100 broken in 2.6.13-rc3 Grant Coady
2005-07-14 20:07 ` Horst von Brand
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=4807377b05071323286963bf3a@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=kl@laska.dorms.spbu.ru \
--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 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).