From: Andrew Morton <akpm@zip.com.au>
To: Rahul Karnik <rahul@genebrew.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3Com 556B Tornado not working
Date: Tue, 19 Mar 2002 21:49:01 -0800 [thread overview]
Message-ID: <3C9822CD.47ED9565@zip.com.au> (raw)
In-Reply-To: <33032.192.168.1.1.1016594386.squirrel@porsche.genebrew.com>
Rahul Karnik wrote:
>
> I have a HP Omnibook 500 with a 3Com 556B miniPCI ethernet/modem combo. Try
> as I might, I can't seem to get the card to connect to the network. My
> question is, how do I figure out what is the problem here? At this point, I
> do not know if the card or the kernel is at fault. Please CC me as I am not
> subscribed to the list.
>
Seems that link negotiation didn't go right.
> Mar 19 22:24:30 quicksilver kernel: eth0: Media override to transceiver 8
> (Autonegotiate).
How did you manage to get this message to come out with a modular
driver? Are there other driver options in modules.conf?
First-up you should avoid using any special negotiation and
transceiver options and just let the card work it out.
> ...
> Transceiver type in use: Autonegotiate.
> MAC settings: half-duplex.
Do you expect half-duplex?
> ...
> Able to perform Auto-negotiation, negotiation not complete.
> ...
> Link partner capability is 0001:.
> Negotiation did not complete.
Lots of bad things there. Remove any special options, then
re-run mii-diag and vortex-diag. If your cables and peer
are behaving then you should see happy output indicating the
desired duplex, speed and negotiation status.
If it still doesn't work, try statically assigning the IP
address (get rid of DHCP somehow). There were some workarounds
in later drivers for strange interactions between some hardware
combinations and some DHCP clients.
If it *still* doesn't work then it's time to sniff the connection
and try to see those arp messages.
And try different cables, different link peers.
And try another you-know-which operating system. If that works OK
then we know the hardware's good.
-
next prev parent reply other threads:[~2002-03-20 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 3:19 3Com 556B Tornado not working Rahul Karnik
2002-03-20 5:49 ` Andrew Morton [this message]
2002-03-21 15:50 ` Rahul Karnik
2002-03-22 21:32 ` Rahul Karnik
2002-03-22 22:06 ` Andrew Morton
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=3C9822CD.47ED9565@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@genebrew.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