From: Steve Simitzis <steve@saturn5.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: e1000 problems in 2.6.x
Date: Sat, 14 Feb 2004 19:53:41 -0800 [thread overview]
Message-ID: <20040215035341.GF1040@saturn5.com> (raw)
In-Reply-To: <402EE603.8020106@tmr.com>
On 02/14/04, Bill Davidsen <davidsen@tmr.com> wrote:
> 1 - check your cables in case 2.6 is checking (or not) something
> 2 - set your NIC half to match the switch and see if there's a different
> problem.
rebooting to 2.4.22 results in a perfectly working network connection,
even with auto-negotiate on both the card and the switch. so i am
hestitant to blame the cables or the hardware. unless, of course, my
cables have the ability to detect which OS i'm running. :)
the result is 100% predictable: boot to 2.6.x, network problems. change
the settings on the device or the switch - network problems. boot
back to 2.4.22 with auto-negotiate everywhere, perfect connection. alas.
--
steve simitzis : /sim' - i - jees/
pala : saturn5 productions
www.steve.org : 415.282.9979
hath the daemon spawn no fire?
next prev parent reply other threads:[~2004-02-15 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 0:26 e1000 problems in 2.6.x Feldman, Scott
2004-02-15 2:32 ` Steve Simitzis
2004-02-15 3:22 ` Bill Davidsen
2004-02-15 3:53 ` Steve Simitzis [this message]
2004-02-15 8:16 ` Re[2]: " Elikster
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 4:17 Paul Blazejowski
2004-02-17 18:26 ` Anton Blanchard
2004-02-15 15:20 Re[2]: " Klaus Dittrich
2004-02-16 1:14 ` Re[3]: " Elikster
2004-02-16 2:12 ` Steve Simitzis
2004-02-14 11:13 Steve Simitzis
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=20040215035341.GF1040@saturn5.com \
--to=steve@saturn5.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.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.