From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: "Lars Hagström" <lars@update.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: forcedeth on MSI K8N Neo Platinum
Date: Sat, 24 Jul 2004 14:29:58 +0200 [thread overview]
Message-ID: <41025646.6020108@gmx.net> (raw)
In-Reply-To: <40EC7FB1.4020906@update.uu.se>
Hi Lars,
Lars Hagström schrieb:
> Hi linux-kernel and Carl-Daniel,
>
> I have just put together a system with a MSI K8N Neo Platinum
> motherboard, and I've been having trouble getting the network up and
> running. The chipset is the NVIDIA nForce 3 250Gb.
>
> I'm using gentoo, and have compiled kernel 2.6.7 (gentoo-dev-sources, if
> you're familiar with gentoo) with the forcedeth-bk4 and
> forcedeth_gigabig_try19 patches. I have compiled the forcedeth driver as
> a module (It is the 10/100 forcedeth driver that is patched to handle
> 1000, right?).
> When I try to start up the network I get the following messages in my
> syslog:
> eth0: phy init failed to autoneg
> eth0: no link during initialization
> (I had the NIC connected to a switch at the time, in case that is what
> is meant by the "no link" bit)
> Is there something simple that I missed, like module parameters, or is
> this a more complicated issue?
>
> Tonight I will try to enable debugging in the code, to see if I can get
> some more information for you. I would be more than willing to help you
> out with any testing you need.
Could you please try Linux 2.6.8-rc2 without any driver patch? It has the
latest version of forcedeth and I am very interested in any bug reports/
side effects of the update.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2004-07-24 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 22:56 forcedeth on MSI K8N Neo Platinum Lars Hagström
2004-07-24 12:29 ` Carl-Daniel Hailfinger [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=41025646.6020108@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=lars@update.uu.se \
--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