From: Manfred Spraul <manfred@colorfullife.com>
To: James Drabb <JDrabb@tampabay.rr.com>
Cc: netdev@oss.sgi.com, c-d.hailfinger.kernel.2004@gmx.net
Subject: Re: forcedeth
Date: Sun, 01 Aug 2004 21:14:40 +0200 [thread overview]
Message-ID: <410D4120.2020604@colorfullife.com> (raw)
In-Reply-To: <410D3377.3030505@tampabay.rr.com>
James Drabb wrote:
> jim@keelie $ uname -a
> Linux keelie 2.6.7-1 #1 Thu Jul 22 11:42:58 CEST 2004 i686 athlon i386
> GNU/Linux
There should be a message in the dmesg log about the driver version: If
it's less than 0.28: could you try a newer kernel? 0.28 is definitively
in 2.5.8-rc1-mm1 and later. I could also send you just the forcedeth.c
file, then you don't have to upgrade the whole kernel.
> However, if I reboot into WinXP, and then reboot right away back into
> FC2, the forcedeth driver works like a champ.
Probably the phy reset and/or the media detection do not work properly.
That part is completely rewritten in 0.28.
I'm interested in two infos:
- with 2.6.7 (probably version 0.25), after booting into winXP first:
what does
# ethtool eth0
report? Then unplug the network cable. Run ethtool again. Does it report
"Link detected: No"? What if you plug the network cable back in?
- The same thing with the 0.28 driver.
Note that the phy initialization in 0.28 is not perfect either: it seems
there is a race between the phy reset and the media detection. You might
have to wait 2 seconds or so between modprobe and ifup.
--
Manfred
next prev parent reply other threads:[~2004-08-01 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 18:16 forcedeth James Drabb
2004-08-01 19:14 ` Manfred Spraul [this message]
2004-08-01 22:01 ` forcedeth James Drabb
2004-08-02 19:38 ` forcedeth Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 13:07 forcedeth Richard
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=410D4120.2020604@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=JDrabb@tampabay.rr.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).