mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Darrell A. Escola" <darrell-kernel@descola.net>
To: Nilanjan Bhowmik <nilu@iomachine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.19: Tulip network card does not sync with Dumb 10/100 Linksys 8 port Etherfast switch
Date: Sat, 10 Aug 2002 11:04:05 -0700	[thread overview]
Message-ID: <20020810180405.GA31193@descola.net> (raw)
In-Reply-To: <000b01c24092$d0d0c160$63c8a8c0@arunachal>

Data point:

I have a server and firewall using 2.4.19-pre2-ac4 with Linksys LNE100TX nic's

firewall is 6x86 on Intel 430VX uptime 146 days
server is PII on Intel 440BX uptime 83 days

both report the nic as:
Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)

both autonegotiate 100 full duplex with a Seimens 5 port 10/100 switch

Maybe Linksys used different chipsets in their LNE100TX, or some change
since 2.4.19-pre2-ac4 is a problem


On Sat, Aug 10, 2002 at 01:24:42PM -0400, Nilanjan Bhowmik wrote:
> This happend on a working machine. After I have upgraded to 2.4.19, tulip
> driver
> will not work.  Only way to sync it is loading the driver couple of times
> and that too
> it will sync at 10/half.
> 
> This is working fine with the 2.4.7-10 stock redhat kernel.
> 
...
> 00:10.0 Ethernet controller: Lite-On Communications Inc LNE100TX [Linksys
> EtherFast 10/100] (rev 25)
> 
> nilu@calculator.nilu.net-5->cat /proc/ioports
...
> 1400-14ff : Lite-On Communications Inc LNE100TX [Linksys EtherFast 10/100]
>   1400-14ff : tulip
...
This matches my /proc/ioports entry for tulip

If you want any more info, just ask...

Darrell

      reply	other threads:[~2002-08-10 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10 17:24 Nilanjan Bhowmik
2002-08-10 18:04 ` Darrell A. Escola [this message]

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=20020810180405.GA31193@descola.net \
    --to=darrell-kernel@descola.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nilu@iomachine.com \
    /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®