netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Felipe W Damasio <felipewd@terra.com.br>
Cc: Paul Hernandez <ph@digitalquake.com>,
	Linux-net <linux-net@vger.kernel.org>,
	netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP
Date: Sat, 19 Oct 2002 20:47:22 -0400	[thread overview]
Message-ID: <3DB1FD1A.4020109@pobox.com> (raw)
In-Reply-To: 1035064119.2912.31.camel@tank

Felipe W Damasio wrote:
> On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
> 
>>Hello,
>>
>>It was suggested to me that I forward this issue to you both.
>>
>>OS:                                   2.4.19.SuSE  SMP
>>Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
>>(latest bios off Intel site)
>>On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
>>Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
>>
>>dmesg output:
>>
>>e100: eth0: Intel(R) 8255x-based Ethernet Adapter
> 
> 
>>SIOCGMIIPHY on eth0 failed:
>>Operation not supported
>>no MII interfaces found
> 
> 
> 	Try using the eepro100.c driver from the kernel, and not the one from
> Intel (the driver from the kernel supports SIOCGMIIPHY).
> 
> 	Though it does not seem a problem with the driver, you should try using
> the one from the kernel and see if it helps.


I agree that comparison is useful, though it should be pointed out that 
ethtool is preferred for e100...

	Jeff




  reply	other threads:[~2002-10-20  0:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 16:57 NIC on 2.4.19 SMP Paul Hernandez
2002-10-19 21:48 ` Felipe W Damasio
2002-10-20  0:47   ` Jeff Garzik [this message]
2002-10-21 14:20     ` Paul Hernandez
2002-10-21 15:16     ` NIC on 2.4.19 SMP (mii-diag output) Paul Hernandez
2002-10-21 16:33       ` Paul Hernandez
2002-10-22 21:49       ` Felipe W Damasio
2002-10-23  2:20         ` Donald Becker
2002-10-23 22:32           ` Paul Hernandez
2002-10-21 14:21   ` NIC on 2.4.19 SMP Paul Hernandez

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=3DB1FD1A.4020109@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=felipewd@terra.com.br \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=ph@digitalquake.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;
as well as URLs for NNTP newsgroup(s).