forcedeth eth0 driver - how do I set to full duplex?

[beeze]

Hello!

I'm trying to get my ethernet driver to be 100Mhz Full duplex. I've got the "forcedeth" (version 0.29) driver. I'm running stock FC3 kernel (AMD 3500 in 32bit mode)

[root@serverwuss ~]# modinfo forcedeth
filename: /lib/modules/2.6.9-1.667/kernel/drivers/net/forcedeth.ko
parm: max_interrupt_work:forcedeth maximum events handled per interrupt
author: Manfred Spraul <manfred@colorfullife.com>
description: Reverse Engineered nForce ethernet driver
license: GPL
vermagic: 2.6.9-1.667 686 REGPARM 4KSTACKS gcc-3.4
depends:
alias: pci:v000010DEd000001C3sv*sd*bc*sc*i*
alias: pci:v000010DEd00000066sv*sd*bc*sc*i*
alias: pci:v000010DEd000000D6sv*sd*bc*sc*i*
alias: pci:v000010DEd00000086sv*sd*bc*sc*i*
alias: pci:v000010DEd0000008Csv*sd*bc*sc*i*
alias: pci:v000010DEd000000E6sv*sd*bc*sc*i*
alias: pci:v000010DEd000000DFsv*sd*bc*sc*i*
alias: pci:v000010DEd00000056sv*sd*bc*sc*i*
alias: pci:v000010DEd00000057sv*sd*bc*sc*i*
alias: pci:v000010DEd00000037sv*sd*bc*sc*i*
alias: pci:v000010DEd00000038sv*sd*bc*sc*i*

The normal tools of "mii-tool" and "ethtool" are not working with this driver (anyone know why???)

[root@serverwuss ~]# mii-tool eth0
SIOCGMIIPHY on 'eth0' failed: Operation not supported

root@serverwuss ~]# ethtool eth0
Settings for eth0:
Supports Wake-on: g
Wake-on: d
Link detected: no

If I cannot use these tools, the only way I can control "forcedeth" is using an option to the driver and put it in my /etc/modprobe.conf - According to the release notes :-

http://download.nvidia.com/XFree86/n...ule_parameters

I should be able to use "force_speed_duplex"....so....

[root@serverwuss ~]# modprobe forcedeth force_speed_duplex=4
[root@serverwuss ~]# tail /var/log/messages
Jun 5 20:29:01 serverwuss kernel: forcedeth: Unknown parameter `force_speed_duplex'
Jun 5 20:29:01 serverwuss kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.29.
Jun 5 20:29:01 serverwuss kernel: ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 5 (level, low) -> IRQ 5
Jun 5 20:29:02 serverwuss kernel: eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:05.0
Jun 5 20:29:02 serverwuss kernel: ip_tables: (C) 2000-2002 Netfilter core team

Can anyone help? I should not have to resort to "options" when loading the driver - I should be able to interact via mii-tool

Thanks for reading
Patrick/

[beeze]

Hmmm...I think the module optional parameters are for the "nvnet" module ...barking up the wrong tree

[beeze]

Ok - no takers???

Trying to see if there are any options for forcedeth to enable the user to force Speed and Duplex. And as my colleague pointed out to me

"use the source Luke!"

So I dug out forcedeth.c from the kernel 2.6.9 (forcedeth 0.29) - Hopefully its attached here in this mail.

It seems from looking at the src there's NO OPTIONS FOR THIS DRIVER. (am I right - please give the src code a "once over" and correct me).

Marvelous. I've got no control over this driver and I can't use mii-tool or /var/log/messages to see what the current config is.

Patrick/

[Dragoran]

there is a static int nv_update_linkspeed(struct net_device *dev) so the driver can be set to full duplex..
looking at the source it seems that it use some king of autodetect methods for the speed settings.

[beeze]

Yup - just as I thought. The driver works by autodetection (fair enough) - but I cannot use the "option" command in /etc/modprobe.conf to force the driver into certain modes (Speed, Duplex, Autoneg etc).

More frustratingly, I don't appear to be able to output the current settings of the driver! Using "mii-tool" I get "operation not supported" (despite the src having some mii interface code!) and "ethtool" doesn't work either.

Does anyone know if there is any cmd or GUI to determine what the speed/duplex/autoneg mode a particular driver is currently set to?

Thanks,
Patrick/

[Dragoran]

ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: externel
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes

I am using the forcedeth driver on nforce2 400 ultra.

[Dragoran]

output from dmesg (version):

forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.31.

[Shakes]

What is the advantage of this over the official Nvidia drivers?

[Dragoran]

no need to reinstall them every time you update the kernel.

[beeze]

I don't get any detailed info for "ethtool"

# ethtool eth0
Settings for eth0:
Supports Wake-on: g
Wake-on: d
Link detected: yes
# uname -a
Linux serverwuss 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 athlon i386 GNU

Ahhh..but my forcedeth is version 0.29 - Maybe I'll look into patching it

[dnar]

[root@Criten downloads]# /usr/sbin/ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: externel
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Link detected: yes

Full-duplex here. Abit NF7-S and FC3.

[beeze]

Yes - but I see your FC3 is a later kernel than my FC3. I installed my FC3 from CD. Did you upgrade your kernel level after installing stock FC3? Are you using the forcedeth driver? (lsmod | grep forcedeth)

I'm assuming that there's NO subsequent releases of FC3 into the community. If you come back and say "nope - I installed my FC3 from CD/DVD too" - then I'm confused. I assume there's a "stock" release of FC3 using kernel 2.6.9-1.667. (my current version). Otherwise me staying "stock FC3" is pointless if there's subsequent FC3 releases using later kernels.

My argument here is that I'm using a "stock" (i.e. "off the shelf") version of FC3 and I'm using the forcedeth ethernet driver version 0.29 - On my kernel (see above posts for version) using 0.29 forcedeth I don't get any (useful) diagnostics using ethtool nor mii-tool to for eth0. I'm completely blind as to what settings eth0 are(!) Nor can I have any control in order to override the autodetect setting the forcedeth goes in on bootup. This is normally done via an "option" line in my /etc/modprobe.conf

The (ver 0.29) src code (posted above) appears to have no user override parameters - it's all autodetect.

From what I've seen in this thread I would now proceed by either (i) upgrading my kernel level or (ii) staying put on my kernel level and seeking a forcedeth patch and re-testing to see if mii-tool/ethtool give me some more useful output than what I've posted (see above).

[dnar]

Fully up to date FC3, using forcedeth. Why have you not updated your kernel?

[beeze]

Ok - you've installed stock FC3 - then you've updated your kernel on top of what I call the "stock" release. Fine.

I only update when I need to - not just when there's a new version out. Personal preference. Now I need to update for this forcedeth driver - so I will do so

Thanks.
Patrick/

[dnar]

I would recommend (as would RedHat/the Fedora team) updating your Kernel to the latest Fedora kernel for FC3 which is 2.6.11-1.27.