Networking :: Can't Change To 1000 Speed With Ethtool?
Aug 9, 2010
I have two onboard gigabit connections and a PCI-E gigabit card, none of which seem to want to run beyond 100M. Everytime I issue the command to change speed to 1000M, it does nothing. I have tried modifying the interfaces file to make sure the command line for ethtool gets done automatically, but still no luck.
Below is the output from the use of ethtool to change speed. Since I am having performance issues with my local area networking (e.g. Samba transferring slower than the internet), I have been trying to figure out how to debug my network performance, and this was an obvious thing that stood out. The router and card are gigabit, yet don't use their full transfer rates.
I have fedora 12 installed in VMWare ESX on a Dell Optiplex machine with a Intel GBit lan.While transfering from fedora's vsftpd to my workstation trough a sitecom gbit switch i get a real bad performance, mostly not higher then 8mb/s. (btw on the same ESX i have Windows 2008 from which i get around 60mb/s)I have tried to set the eth0 to 1000Mb/s full duplex using ethtools but this fails (ethtool -s eth0 speed 1000 duplex full autoneg off). I keep recieving the following error:
Code: Cannot get current device settings: Operation not supported not setting speed
I have a CentOS 5.5 machine (hosted at a remote hosting company) where "ethtool" reports that the eth0 device is currently in 10 Mbps mode, but the output indicates that it supports 100 Mbps. But if I try using ethtool to switch the device into 100 Mbps mode, it doesn't work; after running the command to switch it to 100 Mbps, ethtool reports the speed is still 10 Mbps:
[root@sls-eb5p17 network-scripts]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full
The man page at [URL]..ethtool seems to suggest that this should have worked. Any reason why the reported speed of the device didn't change? Changing other settings doesn't appear to work either, e.g. if I specify "duplex half" instead of "speed 100", eth0 still reports "Duplex: Full".
I am trying to set my gigabit NIC to 1000 MB setting using ethtool. The only way I can get it to register that way is to turn off auto negotiation and that just kills my signal. Below is the output of the current settings and the commands I have attempted with zero success.
I have a few computers on my home network and I want to get them running at 1000Mbs Both my Ubuntu Machine and my Mac already have the hardware to run at that speed but my switch is 100Mbs so I am going to buy a new 1000Mbs switch. Do I need to change any settings in Ubuntu 9.10 to allow for 1000Mbs networking?
I'm having problems enabling Wake-on-LAN using ethtool.I'm using ethtool 5.1 on Fedora 8. Ethtool reports that the card supports u,m,b,g for WOL modes. I can run "ethtool -s eth0 wol g", which completes without errors.If I run ethtool again, the Wake-on setting is changed to whatever I just set it to. However, when I actually shutdown the machine, the lights on the NIC don't stay on as they normally should, and any attempts to wake the machine have no effect. The machine dual-boot Windows XP, and I have enabled WOL in the driver there. When I shutdown the machine from XP, everything works just fine. The NIC lights remain on and the machine wakes up properly. So...I think I have my BIOS configured properly, and my WOL utility is working properly.
Hardware Info: ------------------------------------------------------------ Adapter: Intel Pro/1000 GT PCI (Vendor ID: 8086, Device ID: 107C Motherboard: Asus P5Q Pro
ethtool Output: ------------------------------------------------------------ Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full
dmesg Output: ------------------------------------------------------------ e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection ADDRCONF(NETDEV_UP): eth0: link is not ready e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Im trying to remote power on my debian machine with gnome with the wake on lan function. I enabled it on my mainboard and was configuring my ethtool. There i see:
root@lappy:~# ethtool eth0 Settings for eth0: Supports Wake-on: g Wake-on: d Link detected: yes
and after this command ethtool -s eth0 wol g i get this:
root@lappy:~# ethtool eth0 Settings for eth0: Supports Wake-on: g Wake-on: g Link detected: yes
So i enabled it on software and hardware. Now im trying to sent the magic packets with a windows tool "wake on lan" I see that the package has been sent but the pc wont turn on. So when i check the ethtool settings again i see that it turned to:
So I have tried looking on the web for a solution to this, but I can't find anything. I have only found 2 posts with the same problem and both went unanswered. So I want to set my ubuntu machine to WOL with both Magic Packet and Unicast (the g and u functions in ethtool wol) wol supported: pumbg (thus g and u are both supported) I use "sudo ethtool -s eth0 wol ug" and check to see if it changed, and it does
sudo ethtool eth0 "wol: ug"
After I suspend though, only magic packet will wake it up! I go back in and check with "sudo ethtool eth0" and low and behold, it is back to only being "wol g", which is the default. For some reason it must bump back to default before going into suspend. NOTE, this is with suspend, not even a reboot or a shutdown! Even suspend will reset it to default. I have worked on adding a script to /etc/init.d, adding lines to /etc/rc.local, and adding lines to /etc/networking/interfaces, all with no change.
Any idea what is going on and why it is resetting wol back to default?? I know I should be happy at LEAST it does magic packet, but I want to know why it wont change.
I just started learning network on linux platform. Today I came across two commands ethtool and miitool. Both of them seems to do similar kind of jobs. Now I am confused what is the difference between them.
I am running a test to determine when packet drops occur. I'm using a Spirent TestCenter through a switch (necessary to aggregate Ethernet traffic from 5 ports to one optical link) to a server using a Myricom card.While running my test, if the input rate is below a certain value, ethtool does not report any drop (except dropped_multicast_filtered which is incrementing at a very slow rate). However, tcpdump reports X number of packets "dropped by kernel". Then if I increase the input rate, ethtool reports drops but "ifconfig eth2" does not. In fact, ifconfig doesn't seem to report any packet drops at all. Do they all measure packet drops at different "levels", i.e. ethtool at the NIC level, tcpdump at the kernel level etc?nd am I right to say that in the journey of an incoming packet, the NIC level is the "so-called" first level, then the kernel, then the user application? So any packet drop is likely to happen first at the NIC, then the kernel, then the user application? So if there is no packet drop at the NIC, but packet drop at the kernel, then the bottleneck is not at the NIC?
I have a question regarding packet drops. I am running a test to determine when packet drops occur. I'm using a Spirent TestCenter through a switch (necessary to aggregate Ethernet traffic from 5 ports to one optical link) to a server using a Myricom card. While running my test, if the input rate is below a certain value, ethtool does not report any drop (except dropped_multicast_filtered which is incrementing at a very slow rate). However, tcpdump reports X number of packets "dropped by kernel". Then if I increase the input rate, ethtool reports drops but "ifconfig eth2" does not.
In fact, ifconfig doesn't seem to report any packet drops at all. Do they all measure packet drops at different "levels", i.e. ethtool at the NIC level, tcpdump at the kernel level etc? And am I right to say that in the journey of an incoming packet, the NIC level is the "so-called" first level, then the kernel, then the user application? So any packet drop is likely to happen first at the NIC, then the kernel, then the user application? So if there is no packet drop at the NIC, but packet drop at the kernel, then the bottleneck is not at the NIC?
I have a router that is 1000 Base T and two computers each with ethernet cards that support 1000 Base T. All are equipped with Cat 5e cable. Before I had a router that only went up to 100 Base T and I would setup one box with linux running proftpd. On the other box,I would use win xp pro and use firefox to ftp into the other box and download a file. Download speeds went up to 11.2 MB/sec. Now when I switched routers, I expected something like 120 MB/sec but I'm only getting 5.3 MB/sec. What do I need to change?
I'm operating a server running Slackware 12.1 and I need to install a PCI-E 10/100/1000 NIC, im just wondering if anyone has any recommendations for a card that has solid support under linux or is otherwise known working.
I am having trouble establishing a connection with my WPA wireless network at home. Other laptops at home can connect to this network and even the Eee PC can join free wifi networks. The problem seems to be only with WPA networks. When I enter the password for the WPA network, it tries to connect for a while and then shows me the password dialog box again. I don't get any IP during this time, its always 0.0.0.0 I reinstalled my Ubuntu netbook remix but that didn't help. This problem was occurring in the standard Ubuntu 10.04 too.
I am trying to get the RT2860 card in an Eee PC 1000 to work. I have tried Ubuntu 8.04 and 9.10, all the "fixes" below I can find on the web but nothing seems to work.
[URL] I downloaded the source code from Ralink and using module-assistant followed the instructions.
I can see the wireless network, it tries to connect but just keeps asking for the security key. I have tried WEP, WPA and no security at all but still no go. All works fine if wired. The F2 toggle seems to work OK, the WLAN is switched on in the BIOS. The "iwconfig" command shows the RT2860 in Ubuntu 9.10 but not in Ubuntu 8.04.
I have just installed Ubuntu 10.04 and the wireless connection on my Asus EeePC 1000HE is not working. Network is seen but connection is always rejected and pops up the dialog requesting my password. Password is entered properly and using proper protocol (WPA2) Network is working perfectly under Windows 7 and Fedora.
I use ubuntu netbook for an eee pc 1000h because windows is underpowered. I got it working perfectly in 10.04. I upgraded to 10.10 thinking, if they got it right with 10.04 then surely 10.10 should be fine. All function keys except wireless work.
1. After sleep, wireless turns off. Have to restart and re-enable in bios. 2. If I disable and the re-enable wireless networking it tries to connect but never does resulting in a reboot needed. Checking bios wireless is enabled and connects perfectly on reboot.
Just don't close the lid and sleep because you need a restart. Why would 10.04 be easy and the new version fail? I am windows user and linux does not do this kind of thing normally. MS screws things up with upgrades not linux surely.
Code: 03:00.0 Network controller : Intel Corporation Centrino Wireless-N 1000 [8086:0083] On Fedora 15, when I boot kernel 2.6.40, my laptop is unable to connect to my wireless-G AP. dmesg shows the following: Code: [ 43.866090] wlan0: direct probe to 00:27:19:14:c2:ca (try 1/3)
It works fine, however, when I boot using kernel 2.6.38 (from which I am posting) and in Windows. Also, I found some emails from the linux-wireless mailing list which appear to be talking about the same problem.
The system is fully updated. I've tried the 11n_disable=1 hint I came across on the ThinkPad wiki, but it didn't help. (I'm on an Asus K42Ja, in case it's relevant)
Although I'm fine with staying at 2.6.38 for now, are there workarounds/fixes for this?
I installed the netbook version of ubuntu 10. Problem is no wireless networks show up. So I have an eternet connecting. Only problem is when I plug that in, still no internet. I need to download drivers to make the wireless work.
In Windows (which I can happily say that I no longer have) I had a program called SpeedFan, which monitored the temperatures of my hardware and also my fan speeds. In Ubuntu I monitor my temperatures and fan speed through and AWN applet called Hardware Sensors; however I cannot find a program to change the fan speed. I think that it is just running at full speed in Ubuntu, I'm sure it was slower in Windows.
I've already got the b43-fwcutter package and a driver called 'b43' appears in System > Administration > Hardware Drivers but it does not seem to enable. Another, Broadcom STA wireless driver, does enable, but I'm not picking up the wireless signal.
Have been using Ubuntu Desktop Amd64 for 6months, on a dual boot alongside Vista64. Since first installing the OS, I have switched over to Ubuntu & use Windows only for heavy multimedia edition & the occasional gaming.I just bought a netbook and installed Ubuntu 10.04 LTS NBR. Works great, except for wlan. No propriety drivers available for my Intel Wifi Link 1000BGN.
I've spent hours trying to install iwlwifi, but the process is somewhat complicted for a noob such as myself.After much reading and trying, I've managed to download and install iwlwifi-1000-ucode-22.214.171.124.tgz, (following the http://intellinuxwireless.org/?p=iwl...=howto-iwlwifi instructions)and am now working on installing the mac80211 subsystem (following the http://intellinuxwireless.org/?p=mac...howto-mac80211 instructions)When running
I recently had my AE 1000 linksys wireless adapter driver installed, the info for which can be found here:
But today I was presented with 142 automatic updates already downloaded waiting to be installed on my computer. I installed the updates and restarted my computer for the updates to take effect. Well, since then my wireless adapter no longer registers at all, it doesn't even recognize my router let alone connect to it. It is as inoperable as the day I got it.
I am currently using a different computer in the house to get internet. Should I go about following the same directions I did before and reinstall the driver, or is there a more simple way?