I have a machine, running SuSE 8.2, and it has an Intel PRO 1000 MT GB Copper Cat5 Desktop adapter. However, The txqueuelen is set at 100 (and, resetting it to 1000 doesn't seem to help, especially on reboot). Is there a way to force negotiation at 1000FD? (I'm not sure mii-tool will work for this speed). How else to set negotiation? Thanks! Robert Amodeo ra@math.ucla.edu eth1 ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:164970 errors:0 dropped:0 overruns:0 frame:0 TX packets:82609 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:249330568 (237.7 Mb) TX bytes:5838770 (5.5 Mb) Interrupt:16 Base address:0x2080 Memory:f5020000-f5040000
On Aug 4 at 10:40pm, Robert Amodeo wrote:
I have a machine, running SuSE 8.2, and it has an Intel PRO 1000 MT GB Copper Cat5 Desktop adapter. However, The txqueuelen is set at 100 (and, resetting it to 1000 doesn't seem to help, especially on reboot). Is there a way to force negotiation at 1000FD? (I'm not sure mii-tool will work for this speed). How else to set negotiation? Thanks!
How do you know the NIC _isn't_ operating at 1000FD? You are probably right about mii-tool, as at least the version I have only has strings for 10 and 100 Mbit MII's. The txqueuelen doesn't have anything (directly) to do with the negotiated speed on your NIC. The man page for 'ifconfig' says txqueuelen length Set the length of the transmit queue of the device. It is useful to set this to small values for slower devices with a high latency (modem links, ISDN) to prevent fast bulk transfers from disturbing inter active traffic like telnet too much. The man page doesn't say, but I suspect this count is in packets, and would specify how many packets may be queued and waiting for TX before the driver returns an error. Jim
participants (2)
-
Jim Cunning
-
Robert Amodeo