Hullo...
Has anyone noticed that since moving from 2.4 to 2.6, the 'ethtool' tool has
stopped working for 3Com 3c905C's ?
I've experienced this behaviour on two seperate machines, one with 2.6.5 and
one with 2.6.6:
00:03.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev
78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management
NIC
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 1800 [size=128]
Memory at 44400000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
PCI: Found IRQ 11 for device 0000:00:03.0
PCI: Sharing IRQ 11 with 0000:00:07.2
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:03.0: 3Com PCI 3c905C Tornado at 0x1800. Vers LK1.1.19
fw-ws:~# ethtool eth2
Cannot get device settings: Operation not supported
fw-ws:~# ethtool -i eth2
driver: 3c59x
version: LK1.1.19
firmware-version:
bus-info: 0000:00:03.0
A 'strace' shows:
uname({sys="Linux", node="fw-ws", ...}) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
ioctl(3, 0x8946, 0xbffffd1c) = -1 EOPNOTSUPP (Operation not
supported)
dup(2) = 4
fcntl64(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
brk(0) = 0x804b000
brk(0x804b180) = 0x804b180
brk(0x804c000) = 0x804c000
fstat64(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40014000
_llseek(4, 0, 0xbffff704, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(4, "Cannot get device settings: Oper"..., 52Cannot get device settings:
Operation not supported
I'm using a Debian kernel 2.6.6 on this machine, and the two Intel NICs using
the e100 driver respond perfectly to ethtool get and set requests.
Does this sound familiar to anyone?
Cheers,
Gavin.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
