mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100 driver update for 2.4
Date: Fri, 01 Dec 2000 13:55:25 +0100	[thread overview]
Message-ID: <3A279FBD.60EC5ADB@Hell.WH8.TU-Dresden.De> (raw)
In-Reply-To: <20001117172336.B27444@saw.sw.com.sg> <3A269F47.17336A69@Hell.WH8.TU-Dresden.De> <20001201175109.A4209@saw.sw.com.sg>

Andrey Savochkin wrote:
> 
> > eth0: card reports no RX buffers.
> > eth0: card reports no resources.

> It's a known issue.
> I've been promised that this issue would be looked up in Intel's errata by
> people who had the access to it, but I haven't got the results yet.

I just figured out something interesting. Apparently there's a small timing
problem with setting up the NIC: If I put in a sleep 1 between setting up
the interface and setting up the gateway route, everything works pretty well.

So things now look like this:

/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
 
/sbin/ifconfig eth0   a.b.c.d broadcast x.y.225.255    netmask 255.255.255.0
/sbin/ifconfig eth0:0 a.b.c.d broadcast 172.16.255.255 netmask 255.255.0.0
 
sleep 1 # This does the trick
 
/sbin/route add default gw a.b.c.d netmask 0.0.0.0 metric 1 


> The card itself doesn't report its revision in details.
> It can be checked by `lspci'.
> Rev 8 is 82559, if I remember, and rev 9 is 82559ER.

http://support.intel.com/support/network/adapter/pro100/21397.htm
has a list of Board-Assembly IDs and the corresponding chip revisions.

Regards,
Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-01 13:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17  9:23 Andrey Savochkin
2000-11-30 18:41 ` Udo A. Steinberg
2000-12-01  9:51   ` Andrey Savochkin
2000-12-01 12:55     ` Udo A. Steinberg [this message]
2000-12-01 21:45     ` Ion Badulescu
2000-12-04 13:16       ` Andrey Savochkin
2000-12-05 19:13         ` Ion Badulescu
2000-12-05 21:37           ` Udo A. Steinberg
2000-12-06 12:23           ` Andrey Savochkin
2000-12-08 19:44             ` Ion Badulescu
2000-12-08 20:25               ` Udo A. Steinberg
2000-12-08 20:57                 ` Ion Badulescu
2000-12-08 22:37                   ` Udo A. Steinberg
2000-12-08 22:47                     ` Josh Fryman
2000-12-10 23:34                 ` Anton Altaparmakov
2000-12-11  0:09                   ` Udo A. Steinberg
2000-12-11  3:16                     ` Ion Badulescu
2000-12-11  3:29                       ` Udo A. Steinberg
2000-12-11  8:19                     ` Anton Altaparmakov

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=3A279FBD.60EC5ADB@Hell.WH8.TU-Dresden.De \
    --to=sorisor@hell.wh8.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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

all inboxes | Powered by JetHome®