linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20 gets duplex wrong on NIC
Date: Tue, 03 Dec 2002 19:04:40 -0500	[thread overview]
Message-ID: <3DED4698.60209@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212031818310.1176-200000@oddball.prodigy.com>

Bill Davidsen wrote:
> In spite of modules.conf the system boots with the NIC in half duplex. I 
> verified this with the mii-tool, I can set it full with mii-tool and it 
> works right (copied a CD image 650MB), and the blade in the switch has 
> been set either full or auto without gain. Yes, I tried the e100 driver as 
> well.
> 
> Info I think shows this attached to prevent munging, let me know if more 
> is needed.


Lots of feedback/questions/response:

When you're on a network, more is always needed :)

Please give _plenty_ of details about what is on the other side of the 
cable: hub? switch? vendor of hub/switch?  crossover to another NIC? 
what is the port configuration and what are the capabilities of the 
other end?  is it set to autonegotiate (on the other end)?

Why do you force full duplex?  It is often the wrong thing to do.

For eepro100, you should use module option 'options' to specify 
10baseT-FD... full_duplex appears to be somewhat redundant in the 
context of your problem.

For e100, you should use 'e100_speed_duplex' module option to specify media.

Finally, I would be very interested to know the results of using ethtool 
to set, and get, your media settings.  It's in every distro these days, 
plus you can d/l it from http://sf.net/projects/gkernel/

	Jeff




  reply	other threads:[~2002-12-03 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 23:24 2.4.20 gets duplex wrong on NIC Bill Davidsen
2002-12-04  0:04 ` Jeff Garzik [this message]
2002-12-05 17:24   ` Bill Davidsen
2002-12-05 17:34     ` Mr. James W. Laferriere
2002-12-09  1:05       ` Bill Davidsen

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=3DED4698.60209@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).