Error using mii-tool on 2.6-test, 2.4 okay
I've just switched another of my boxes over to 2.6-test; so
far, I've had only one problem -- attempts to force the network card (tulip-based) to full-duplex with mii-tool fail with:
SIOCGMIIPHY on 'eth0' failed: Operation not supported no MII interfaces found
The same command works fine in 2.4. This the packaged mii-tool
in Debian unstable (1.9 2000/04/28). I've tried rebuilding the package on another very similar machine, but the error remains. Ethtool also doesn't work, but I'm not sure it did with 2.4 and this card either.
One thing that caught my eye: I have CONFIG_MII set to "y".
Are mii-tool and CONFIG_MII mutually exclusive? CONFIG_TULIP is "m"; should CONFIG_MII be "m" too?
Signature · 4 lines
Joseph Fannin [email protected] "Linus, please apply. Breaks everything. But is cool." -- Rusty Russell.
Quoted 5 lines · Joseph Fannin
I've just switched another of my boxes over to 2.6-test; so
far, I've had only one problem -- attempts to force the network card (tulip-based) to full-duplex with mii-tool fail with:
Quoted 8 lines
SIOCGMIIPHY on 'eth0' failed: Operation not supported no MII interfaces found
The same command works fine in 2.4. This the packaged mii-tool
in Debian unstable (1.9 2000/04/28). I've tried rebuilding the package on another very similar machine, but the error remains. Ethtool also doesn't work, but I'm not sure it did with 2.4 and this card either.
Get the latest mii-tool (possibly from cvs). The one in Debian unstable doesn't use the official MII ioctls.
Quoted 1 line
Are mii-tool and
CONFIG_MIImutually exclusive?
No.
Jeff