thr3ads.net - CentOS - [CentOS] Could not setup Speed and Duplex on CentOS 5.5 [Jan 2011]

If this information is useful, please help other people find it:
Share via:

Sikkandar Dulkarnai

2011-Jan-07 14:45 UTC

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

Greetings,

I recently installed CentOS 5 on Dell PE 1750 server. I have noticed that
the speed and duplex settings are 100 Half Duplex. I tried to change the
duplex settings to full, but no success. I got the error message "Cannot
get
current device settings: Operation not supported". Does anyone else
experience this issue?. Below is the error message and some more details
about my box. Any help will be highly appreciated.

[root at xentwo ~]# ethtool -s eth0 speed 100 duplex full autoneg on
Cannot get current device settings: Operation not supported
  not setting speed
  not setting duplex
  not setting autoneg

[root at xentwo ~]# ethtool -s eth0 speed 100 duplex full autoneg off
Cannot get current device settings: Operation not supported
  not setting speed
  not setting duplex
  not setting autoneg

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



[root at xentwo ~]# cat /etc/issue
CentOS release 5.5 (Final)
Kernel \r on an \m

[root at xentwo ~]# uname -a
Linux xentwo 2.6.18-194.32.1.el5xen #1 SMP Wed Jan 5 19:32:33 EST 2011 i686
i686 i386 GNU/Linux


[root at xentwo ~]# dmesg | grep eth0
eth0: Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)] (PCIX:133MHz:64-bit)
10/100/1000Base-T Ethernet 00:11:43:59:7c:ed
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[769f4000] dma_mask[64-bit]
ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3: eth0: Link is up at 100 Mbps, half duplex.
tg3: eth0: Flow control is off for TX and off for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
ADDRCONF(NETDEV_UP): peth0: link is not ready
tg3: peth0: Link is up at 100 Mbps, half duplex.
tg3: peth0: Flow control is off for TX and off for RX.
ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready
device peth0 entered promiscuous mode
xenbr0: port 2(peth0) entering forwarding state
eth0: no IPv6 routers present


[root at xentwo ~]# dmidecode | grep -i ether
        Type: Ethernet
        Description: Broadcom Gigabit Ethernet 1
        Type: Ethernet
        Description: Broadcom Gigabit Ethernet 2




[root at xentwo ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:43:59:7C:ED
          inet addr:192.168.30.124  Bcast:192.168.30.255  Mask:255.255.255.0
          inet6 addr: fe80::211:43ff:fe59:7ced/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:136658 errors:0 dropped:0 overruns:0 frame:0
          TX packets:512 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:43152822 (41.1 MiB)  TX bytes:75457 (73.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1522 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4285636 (4.0 MiB)  TX bytes:4285636 (4.0 MiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:137243 errors:0 dropped:0 overruns:0 frame:0
          TX packets:511 errors:0 dropped:0 overruns:0 carrier:0
          collisions:3 txqueuelen:1000
          RX bytes:43740268 (41.7 MiB)  TX bytes:76133 (74.3 KiB)
          Interrupt:18 Memory:fcf30000-fcf40000

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:514 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136671 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:75781 (74.0 KiB)  TX bytes:43153860 (41.1 MiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:7967 (7.7 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:135062 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:40981075 (39.0 MiB)  TX bytes:0 (0.0 b)


Regards,
Sikkandar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20110107/1cb65079/attachment-0003.html>

m.roth at 5-cent.us

2011-Jan-07 15:02 UTC

head link

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

Sikkandar Dulkarnai wrote:> Greetings,
>
> I recently installed CentOS 5 on Dell PE 1750 server. I have noticed that
> the speed and duplex settings are 100 Half Duplex. I tried to change the
> duplex settings to full, but no success. I got the error message
"Cannot
> get current device settings: Operation not supported". Does anyone
else
> experience this issue?. Below is the error message and some more details
> about my box. Any help will be highly appreciated.
>
> [root at xentwo ~]# ethtool -s eth0 speed 100 duplex full autoneg on
<snip>> [root at xentwo ~]# ethtool -s eth0 speed 100 duplex full autoneg off
Not sure about the "can't get device settings", and I'm just
not sure if
order is significant in the command, but the manpage, and past experience,
says that after the interface name, you *have* to have autoneg off,
otherwise forcing settings is a contradiction in terms.

The other question is what the switch you're connecting to is set to.

         mark

R Lists07

2011-Jan-09 23:27 UTC

head link

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

Sikkandar,
 
typically, we do this & put this text
 
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
 
in this file 
 
/etc/sysconfig/network-scripts/ifcfg-eth0
 
and any others files there as necessary
 
reboot unit or whatever is best for your admin situation...
 
you may have other issues that we cannot discern from your email
 
 - rh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20110109/e8bb20f2/attachment-0002.html>

Possibly Parallel Threads

Search for more possibly parallel threads

CentOS - Jan 2011 - Could not setup Speed and Duplex on CentOS 5.5

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

[CentOS] Could not setup Speed and Duplex on CentOS 5.5

Possibly Parallel Threads