All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Hernandez" <ph@digitalquake.com>
To: "Jeff Garzik" <jgarzik@pobox.com>,
	"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: Mon, 21 Oct 2002 07:20:08 -0700	[thread overview]
Message-ID: <NEBBKAFGCLJCEABADOEOOEJACAAA.ph@digitalquake.com> (raw)
In-Reply-To: <3DB1FD1A.4020109@pobox.com>


Jeff and Felipe,

I naturally tried the default e100 first when I
installed SuSE 8.1 and only tried the eepro100.c
when the e100 failed identically. The e100 is harder
to debug w/o MII so felt the e100pro with MII might
shed some light.

Any suggestions. I'll happily assist in resolving this.

				Paul Hernandez  408-374-8686 x202
				Campbell, CA

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, October 19, 2002 17:47 PM
To: Felipe W Damasio
Cc: Paul Hernandez; Linux-net; netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP


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-21 14:20 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
2002-10-21 14:20     ` Paul Hernandez [this message]
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=NEBBKAFGCLJCEABADOEOOEJACAAA.ph@digitalquake.com \
    --to=ph@digitalquake.com \
    --cc=felipewd@terra.com.br \
    --cc=jgarzik@pobox.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.