similar to: Samba running slow

Dear All, I have an onboard Realtek RTL8111/8168B NIC. from lspci -vv : 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ???????

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

Hi all, I'm seeing slow transfers to/from my samba server. I just tried to copy a 270MB file from a samba share to an XP machine. At first, the estimated time displayed as 141 minutes :( The odd thing is that if I then flood-ping from the server (in this case, I pinged my dsl router), the transfer completes in about 10 seconds. Hitting F5 repeatedly when browsing a share on the server

Hi, I have a really strange problem with a driver disk (http://wiki.centos.org/HardwareList/RealTekRTL8111b) on amd64. I'm remotly booting the system via isolinux-files, so I unfortunatly do not have access to relevant logs, all I can see the the primary console/screen. With i386, the driver disk works just fine and I can install via http. But with amd64, the installer complains no driver

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hi all, Another FYI-mail (and just to verify that I'm not going insane here); I recently purchased an ASUS M3A78-EMH HDMI -board with a tri-core Phenom. This is a small uATX-board with all the garnish integrated motherboards are supposed to come with, and fairly well supported in CentOS 5 and other modern distros. When I installed it (~2 months ago) the NIC was not supported; Ethernet

Hi : I am trying to do PCIe passthrough on HVM domu. I have window XP as a HVM domu and xen-4.0. dom0 and domU (without device assign) works fine. I have more than one NIC card. I want to passthrough 03:00.0 to domu here are the list of my nic cards: lspci | grep -i eth 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

I am experiencing poor network performance on Dom0. When i ping other hosts on the same LAN, packets are out of order, and they show response times ranging from < 1 ms to several seconds, and some packets get lost. For example, a typical ping result looks like this: 87 packets transmitted, 80 received, +3 errors, 8% packet loss, time 86038ms rtt min/avg/max/mdev =

I am trying to transport a dd image between to hosts over a cross linked gigabit connection. Both hosts have an eth1 configured to a non routable ip addr on a shared network. No other devices exist on this link. When transferring via sftp I received a stall warning. Checking the logs I see this: dmesg | grep eth e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:f2:1f:bb

Thanks Anna, this was also quite interesting for me. Did you mean that I just have to eliminate the else branch or raise arround "All devices behind the uppermost PCI/PCI-X bridge must be co-assigned to the same guest." or do I have to eliminate more in order to prevent an FLR (whatever that is). For my board it''s definitely necessary to move PCI devices in different guests,

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

We have an HP DL360 server with dual on-board Tigon3 ethernet cards. We are using eth0, eth1 is unused at the moment. Sometimes when the network interface is under heavy load, for example moving large file transfers over rsync or NFS, the network interface stops working and we lose all connection to the server. The only solution at this point is to jump on the console and restart the network

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [

The 8168B (02) NIC works well except that it does not go into promiscuous mode despite advertising itself in that mode after being so directed with ifconfig. Unfortunately, the little box is destined to be an IDS monitor, so that function is essential. The board is an Intel Atom 330 run as x86_64, the nic is internal. We tried three drivers: the one in the 2.6.18-128.1.10.el5 kernel yields

Howdy, It appears that CentOS 5.2's support for the RTL8111B/C chip is incomplete. The wiki has some blanket statements regarding this support: http://wiki.centos.org/AdditionalResources/HardwareList/CentOS5/RealTek/r1000 http://wiki.centos.org/AdditionalResources/HardwareList/RealTekRTL8111b I could dive in an make the changes *I* think need to happen but I'd like to talk to people

Dear Friends of the Community Here by I request some help, now Install Centos 5.0 in DELL 3020 one machine installation took correctly, but after installation I find that the network card that brings integrated computer does not recognize the eth0. 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem:

Hello, We can see # lspci 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) I have used a custom kernel to start with centos 5.1 as an initial installation Our customer on this kernel has experienced slow pref on samba shares (50 seconds to open a file) So I have decided to updrade to centos 5.2 that have the right