At 03:16 11/12/2000, Ion Badulescu wrote:
>On Mon, 11 Dec 2000, Udo A. Steinberg wrote:
>Anton Altaparmakov wrote:
> > > My card is an Ether Express Pro 100, lcpci says: Intel Corporation 82557
> > > [Ethernet Pro 100] (rev 04)
>
>So it's an i82558 A-step. That's interesting, the patch shouldn't h
Ion Badulescu wrote:
> This is an i82559 C-step. What kind of switch is it attached to?
It's a 3Com FDDI/Ethernet Linkswitch 2200 Rev 2.8
> Also, if you feel like experimenting, edit speedo_interrupt() and change
> outw(status & 0xfc00, ioaddr + SCBStatus);
> to
> outw(status &
On Mon, 11 Dec 2000, Udo A. Steinberg wrote:
> Anton Altaparmakov wrote:
>
> The problem here only ever happens at initialisation/first packets. Once the
> network interface has been initialised properly it never produces those
> messages anymore. Usually it helps to shut the NIC down with ifcon
Hi,
Anton Altaparmakov wrote:
> Just to say that the patch (including added 4) fixed the "card reports no
> resources" messages for me. - Looking at my logs the messages appeared once
> every 10-40 minutes. - Now the box is up for more than 5 hours with the
> patch and test12-pre7 and not a sing
At 20:57 08/12/2000, Ion Badulescu wrote:
>On Fri, 8 Dec 2000, Udo A. Steinberg wrote:
>
> > > + /* disable advertising the flow-control capability */
> > > + sp->advertising &= ~0x0400;
> > > + mdio_write(ioaddr, sp->phy[0] & 0x1f, sp->advertising);
> >
>
> * put cable in *
>
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
you know, this might be entirely unrelated, but i had the exact same type of
problem with a brand new machine running a not-so-brand n
Ion Badulescu wrote:
>
> Ok. Can you send me the entire dump? Also, it would be helpful if you
> could try to determine when exactly it happens (upon insmod, upon ifconfig
> up, or upon receiving some packets later).
I have the eepro driver compiled into a monolithic kernel. After rebooting
a co
On Fri, 8 Dec 2000, Udo A. Steinberg wrote:
> > + /* disable advertising the flow-control capability */
> > + sp->advertising &= ~0x0400;
> > + mdio_write(ioaddr, sp->phy[0] & 0x1f, sp->advertising);
>
>
Ion Badulescu wrote:
> The fact that apparently only the people using 82559 chips are seeing this
> seems to confirm my analysis above.
>
> If you could try the attached patch (and maybe pass it onto the other
> people who are experiencing this problem), that would be great.
> +
On Wed, 6 Dec 2000, Andrey Savochkin wrote:
> > > The sympthomes are that the card triggers Flow Control Pause condition (and
> > > interrupt) on the last stages of the initialization or right after.
> > > And it happens with flow control being explicitly turned off.
> > > High network load consi
Hello,
On Tue, Dec 05, 2000 at 11:13:27AM -0800, Ion Badulescu wrote:
> On Mon, 4 Dec 2000, Andrey Savochkin wrote:
>
> > > There is nothing relevant in the errata, unfortunately...
> >
> > Do you have it?
>
> I have the manual in the office, so I can look at it again in a couple of
> days. I'
Ion Badulescu wrote:
>
> Do you know if only one specific chip revision exhibits this problem? It
> would really help track down the problem. If I remember correctly, 82557
> doesn't have flow control at all, and 82558/9 have different
> implementations -- one is proprietary (82558) and one is st
On Mon, 4 Dec 2000, Andrey Savochkin wrote:
> > There is nothing relevant in the errata, unfortunately...
>
> Do you have it?
I have the manual in the office, so I can look at it again in a couple of
days. I've used it to hack on the BSDI driver...
> The sympthomes are that the card triggers F
Hello,
On Fri, Dec 01, 2000 at 01:45:24PM -0800, Ion Badulescu wrote:
> On Fri, 1 Dec 2000 17:51:09 +0800, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
>
> > 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 resul
On Fri, 1 Dec 2000 17:51:09 +0800, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
> 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.
There is nothing relevant in the errata, unfortunately...
> The card
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 someth
Hello,
On Thu, Nov 30, 2000 at 07:41:11PM +0100, Udo A. Steinberg wrote:
> I've been using an older EEPro100/B card until now and it's been working without any
> problems ever since the transmitter bugs were fixed. The boot output looked like
>this:
[snip]
> Today I've installed a new model with
Andrey Savochkin wrote:
> I've updated eepro100 driver for 2.4 kernel branch.
> So far, the most annoying initialization problem (expressing itself in "card
> reports no resources" messages) hasn't been fixed.
Hi Andrey,
I've been using an older EEPro100/B card until now and it's been working w
Hello,
I've updated eepro100 driver for 2.4 kernel branch.
So far, the most annoying initialization problem (expressing itself in "card
reports no resources" messages) hasn't been fixed.
The driver is available at
ftp://ftp.sw.com.sg/pub/Linux/people/saw/kernel/v2.4/eepro100.c
The main changes
19 matches
Mail list logo
