| To: | James Drabb <JDrabb@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: forcedeth |
| From: | Manfred Spraul <manfred@xxxxxxxxxxxxxxxx> |
| Date: | Sun, 01 Aug 2004 21:14:40 +0200 |
| Cc: | netdev@xxxxxxxxxxx, c-d.hailfinger.kernel.2004@xxxxxxx |
| In-reply-to: | <410D3377.3030505@tampabay.rr.com> |
| References: | <410D3377.3030505@tampabay.rr.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.6) Gecko/20040510 |
James Drabb wrote: jim@keelie $ uname -a 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] ethtool_get_regs copy right number of bytes to user, Jeff Garzik |
|---|---|
| Next by Date: | Re: forcedeth, James Drabb |
| Previous by Thread: | forcedeth, James Drabb |
| Next by Thread: | Re: forcedeth, James Drabb |
| Indexes: | [Date] [Thread] [Top] [All Lists] |