David Ford wrote:
>
> > > Do the tulip driver updates address the increasingly common NETDEV timeout
> > > repots?
> >
> > In general you can answer this yourself by reading
> > drivers/net/tulip/ChangeLog.
> >
> > I don't see increasingly common timeout reports.. with which hardware?
> > They
Matti Aarnio wrote:
> I think they are separate problems.
> The first is power-management suspend/resume issue, and possibly
> PCMCIA problem at software re-insert of card (which never was taken
> out *physically*).
>
> If I pull the cardbus card out, make sure the "dhcpcd eth0" has
>
On Tue, Jan 23, 2001 at 11:13:48AM +, David Ford wrote:
> > > The three cardbus cards are slightly different in numerous ways. For
> > > them they normally fault with an APM event, an eject/insert cycle via
> > > software will reset hem and a link down/up won't fix it. For the PCI
> >
Matti Aarnio wrote:
> On Tue, Jan 23, 2001 at 10:48:16AM +, David Ford wrote:
> > The three cardbus cards are slightly different in numerous ways. For
> > them they normally fault with an APM event, an eject/insert cycle via
> > software will reset hem and a link down/up won't fix it. For
On Tue, Jan 23, 2001 at 10:48:16AM +, David Ford wrote:
> The three cardbus cards are slightly different in numerous ways. For
> them they normally fault with an APM event, an eject/insert cycle via
> software will reset hem and a link down/up won't fix it. For the PCI
> cards most times a
> > Do the tulip driver updates address the increasingly common NETDEV timeout
> > repots?
>
> In general you can answer this yourself by reading
> drivers/net/tulip/ChangeLog.
>
> I don't see increasingly common timeout reports.. with which hardware?
> They are likely on the newer LinkSys 4.1
Do the tulip driver updates address the increasingly common NETDEV timeout
repots?
In general you can answer this yourself by reading
drivers/net/tulip/ChangeLog.
I don't see increasingly common timeout reports.. with which hardware?
They are likely on the newer LinkSys 4.1 cards, and
On Tue, Jan 23, 2001 at 10:48:16AM +, David Ford wrote:
The three cardbus cards are slightly different in numerous ways. For
them they normally fault with an APM event, an eject/insert cycle via
software will reset hem and a link down/up won't fix it. For the PCI
cards most times a link
Matti Aarnio wrote:
On Tue, Jan 23, 2001 at 10:48:16AM +, David Ford wrote:
The three cardbus cards are slightly different in numerous ways. For
them they normally fault with an APM event, an eject/insert cycle via
software will reset hem and a link down/up won't fix it. For the PCI
On Tue, Jan 23, 2001 at 11:13:48AM +, David Ford wrote:
The three cardbus cards are slightly different in numerous ways. For
them they normally fault with an APM event, an eject/insert cycle via
software will reset hem and a link down/up won't fix it. For the PCI
The PCI
Matti Aarnio wrote:
I think they are separate problems.
The first is power-management suspend/resume issue, and possibly
PCMCIA problem at software re-insert of card (which never was taken
out *physically*).
If I pull the cardbus card out, make sure the "dhcpcd eth0" has
died
David Ford wrote:
Do the tulip driver updates address the increasingly common NETDEV timeout
repots?
In general you can answer this yourself by reading
drivers/net/tulip/ChangeLog.
I don't see increasingly common timeout reports.. with which hardware?
They are likely on the
12 matches
Mail list logo
