netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@us.ibm.com>
To: hadi@cyberus.ca
Cc: Kosta Todorovic <kostodo@gmail.com>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Ben Greear <greearb@candelatech.com>,
	jgarzik@pobox.com, tulip-users@lists.sourceforge.net,
	netdev@oss.sgi.com
Subject: Re: Network card driver problem (znb.o/tulip)
Date: Mon, 21 Mar 2005 19:59:36 -0600	[thread overview]
Message-ID: <200503211959.36089.jdmason@us.ibm.com> (raw)
In-Reply-To: <1111346944.1094.91.camel@jzny.localdomain>

On Sunday 20 March 2005 01:29 pm, jamal wrote:
> On Sun, 2005-03-20 at 14:18, Kosta Todorovic wrote:
> > > I dont think mii-tool will tell you the truth with these cards.
> > > Like i was saying earlier - they use SYM PHYs.
> >
> > Either way, no traffic moved across them when I tried.
>
> Probably the stats display is your best bet for debugging.
>
> > > Does it work on 32 bit machines? I am assuming when you say "64 bit"
> > > you mean the architecture not PCI bus.
> >
> > Yes it does work on 32bit machines, but with the actual znb.o driver
> > thats supplied by ZNXY.
> > And yes i am refering to architecture and NOT pci bus.
>
> It works just fine for me with 32 bit machine with the standard tulip
> driver(sorry dont have 64 bit - too poor); does it work for you?
> i.e i dont use the Znyx driver at all. I always have mine running
> 100Mbps FDX.

My Linksys NC100 adapter works fine on my Athlon 64 system.  So, it is 
probably an adapter/driver interaction issue, and not a 64bit one.  

Kosta, Can you confrim that the tulip driver works for you on a 32bit system?


> If it works on 32 bit, then it maybe an issue with the tulip driver.
>
> cheers,
> jamal

Thanks,
Jon

  parent reply	other threads:[~2005-03-22  1:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  5:51 Network card driver problem (znb.o/tulip) Kosta Todorovic
2005-03-11  6:00 ` Ben Greear
2005-03-11  6:08   ` Kosta Todorovic
2005-03-19  5:33   ` Jon Mason
2005-03-19 10:29     ` Kosta Todorovic
2005-03-19 13:57       ` Jon Mason
2005-03-19 15:23         ` Francois Romieu
2005-03-20 14:05           ` jamal
2005-03-20 19:02             ` Kosta Todorovic
2005-03-20 19:09               ` jamal
2005-03-20 19:18                 ` Kosta Todorovic
2005-03-20 19:29                   ` jamal
2005-03-20 19:36                     ` Kosta Todorovic
2005-03-20 19:38                       ` jamal
2005-03-22  1:59                     ` Jon Mason [this message]
2005-03-22  7:18                       ` Kosta Todorovic
2005-03-22 14:56                         ` jamal
2005-05-19  8:02 ` Kosta Todorovic
2005-05-19 17:14   ` Ben Greear
2005-05-20  5:25     ` Kosta Todorovic
2005-05-20 16:07       ` Ben Greear
2005-06-03  5:45         ` Kosta Todorovic
2005-06-03  5:53           ` Ben Greear
2005-06-03  5:58             ` Kosta Todorovic
2005-06-03  6:25               ` Ben Greear

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=200503211959.36089.jdmason@us.ibm.com \
    --to=jdmason@us.ibm.com \
    --cc=greearb@candelatech.com \
    --cc=hadi@cyberus.ca \
    --cc=jgarzik@pobox.com \
    --cc=kostodo@gmail.com \
    --cc=netdev@oss.sgi.com \
    --cc=romieu@fr.zoreil.com \
    --cc=tulip-users@lists.sourceforge.net \
    /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).