From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>
Subject: Re: Intel CSA Gigabit Bug in IC7-G Motherboards- Affects Windows/Linux
Date: Thu, 23 Feb 2006 09:32:50 -0800 [thread overview]
Message-ID: <4807377b0602230932n79dde5b7ue3851941bc15ca70@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602220527550.19732@p34>
On 2/22/06, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> Jesse,
>
> Any idea what is going on? MB defect? Driver defect?
well, no-napi shouldn't fail any worse than napi, so that may well be
a driver bug. Lets follow up offline or at mailing list e1000-devel %
lists.sf.net
otherwise no idea. There are a lot of people using these boards
without issues, it seems that ABIT even has some of this same board
that work for some people. If you can find someone that has one that
works you might try comparing your ethtool -e output to theirs. If you
change your eeprom however, thats you taking risks on your own, and we
can't support you. But it might be a useful thing to know, to give
more information to ABIT.
Jesse
prev parent reply other threads:[~2006-02-23 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 23:17 Justin Piszcz
2006-02-19 23:36 ` Justin Piszcz
2006-02-20 8:00 ` Jesse Brandeburg
2006-02-19 23:47 ` Lee Revell
2006-02-19 23:51 ` Justin Piszcz
2006-02-20 7:59 ` Jesse Brandeburg
2006-02-20 10:28 ` Justin Piszcz
2006-02-20 22:12 ` Justin Piszcz
2006-02-22 10:28 ` Justin Piszcz
2006-02-23 17:32 ` Jesse Brandeburg [this message]
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=4807377b0602230932n79dde5b7ue3851941bc15ca70@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=jpiszcz@lucidpixels.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
all inboxes | Powered by JetHome®