All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C110 builtin nic slow?
Date: Tue, 11 Nov 2003 11:45:56 +0000	[thread overview]
Message-ID: <3FB0CBF4.6010306@tiscali.be> (raw)
In-Reply-To: <Pine.LNX.4.58.0311110124220.2933@sal.ucc.ie>

Hi Max,

M. Grabert wrote:
> On Mon, 10 Nov 2003, Grant Grundler wrote:
> 
> 
>>On Mon, Nov 10, 2003 at 01:31:45PM +0100, Joel Soete wrote:
>>
>>>ie a Lasi_82596 (as Matthew mentioned in a previous mail).
>>
>>yeah - that's not going to perform as well as tulip.
>>And 10-Half is going to be substantially slower.
>>Sounds like it has a bug in the negotiation.
> 
> 
> Very likely!
> 
> My C200 is also very picky whether to enable 100MBit or not.
> I'm using a no-name 100MBit-Switch, and it works fine for all
> 5 other PCs in my house).
> 
> I was not able to force 100MBit by changing the settings in the
> PDC, but the following DID work:
> 
> 
>>mii-tool -A 100baseTx,10baseT eth0
> 
Ah interesting:
on my pc,
  # mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not supported
eth1: 10 Mbit, half duplex, no link

and eth1 is the nic I use to connect my c110 :) (don't see what no link 
means but that is the right setup that I need with c110)

otc on the c110:
# mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not supported
no MII interfaces found
:(

Thx a lot,
	Joel

  reply	other threads:[~2003-11-11 11:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 11:10 [parisc-linux] C110 builtin nic slow? Joel Soete
2003-11-10 12:31 ` Joel Soete
2003-11-10 14:00   ` Joel Soete
2003-11-10 17:35     ` Grant Grundler
2003-11-11 12:54       ` Joel Soete
2003-11-12  3:22         ` Grant Grundler
2003-11-15 19:41           ` Joel Soete
2003-11-15 22:56             ` M. Grabert
2003-11-15 23:22               ` [parisc-linux] Dual NICs on 9000/715, anyone? buggz
2003-11-15 23:34                 ` Matthew Wilcox
2003-11-15 23:50                   ` buggz
2003-11-16  1:51                 ` Grant Grundler
2003-11-16  4:16                   ` Shane G. Brodie
2003-11-16  4:32                     ` Grant Grundler
2003-11-15 23:58               ` [parisc-linux] C110 builtin nic slow? M. Grabert
2003-11-16 17:00                 ` Joel Soete
2003-11-21 21:44                   ` Joel Soete
2003-11-21 22:37                     ` Joel Soete
2003-11-16 16:53               ` Joel Soete
2003-11-10 17:37   ` Grant Grundler
2003-11-10 19:23     ` Joel Soete
2003-11-10 20:38       ` Joel Soete
2003-11-11  1:31     ` M. Grabert
2003-11-11 11:45       ` Joel Soete [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-26 16:49 Joel Soete
2003-10-26 17:25 ` Grant Grundler
2003-10-26 20:40   ` Joel Soete
2003-10-26 21:10     ` Joel Soete
2003-10-27 19:39       ` Grant Grundler
2003-10-27 20:13         ` Matthew Wilcox
2003-10-28  8:39         ` Joel Soete
2003-10-28 19:32           ` Joel Soete
2003-10-28 19:34             ` Matthew Wilcox
2003-10-29  6:43               ` Joel Soete
2003-11-10  4:36     ` Grant Grundler

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=3FB0CBF4.6010306@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xam@cs.ucc.ie \
    /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.