search for: r8169

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25). r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25). r8169 0000:03:00.0:...

...ansferring 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 e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: FFFFFF-0FF r8169 0000:01:00.0: eth1: RTL8168d/8111d at 0xffffc9000187c000, 00:0a:cd:1d:44:fe, XID 081000c0 IRQ 31 r8169 0000:01:00.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] ADDRCONF(NETDEV_UP): eth0: link is not ready device eth0 entered promiscuous mode r8169 0000:01:00.0: eth1: invalid fir...

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25). r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25). r8169 0000:03:00.0:...

Hi all. I have two servers 2.6.18-308.4.1.el5PAE CentOS release 5.7 (Final) Both have two external gigabit network cards (installed Planet with Realtek r8169 chipset). lspci 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 04:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) /var/log/messages May 3 15:00:22 ms7a kernel: r8169: eth1: link up May 3 16:05:27 ms7...

Hi all, I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up. After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now eth1 and eth1 is...

Bill, your CentOS 5 RTL8110 page should probably be updated. I've confirmed that there's a newer r8169 driver in the kernel that works with the RTL8110. RealTek's web site now carries the new r8169 instead of the r1000. The newer driver fixed a problem I was having on one host so we should probably recommend it over the older r1000. I've updated my CentOS 4 page. Kirk Bocek http://wiki.c...

...supported; Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) ...but Realtek provided a 2.6-kernel compatible r8168-driver; r8168-8.006.00 When the CentOS 5.2 updates were published, I saw to my happiness that the kernel-supplied r8169-driver now handled the NIC, and I had no reason to rebuild the r8168-driver to support the new kernel. Last time I rebooted, was July 2nd, to the 2.6.19-92.1.6.el5 kernel. Since then, the kernel supplied r8169-driver worked like a charm. The machine is a home file-server, serving files over NFS...

Hi, anybody know how to fix this. May 20 12:16:15 wolfpac kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out May 20 12:16:15 wolfpac kernel: Modules linked in: pf_ring(U) af_key iptable_nat ipt_LOG iptable_filter ip_tables nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6t_LOG xt_limit ip6table_filter ip6_tables bridge stp llc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_...

Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at speed 10, half-duplex. In the past for sk98lin driver I could pass a kernel mo...

I have no output in the logs, but /etc/init.d/network restart fixes the issue. I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS M3A78-EM (RTL8111B/C). It locks up around the 1.5GB Tx mark. If I ethtool -s eth0 autoneg off speed 100 duplex full it does not happen again. Ideas? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

lspci gives 02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8167 (rev 10) insmod r8169 loads the module but doesn;t pick the card up. Im connecting to internet using a live CD. how do i get centos 5(vanilla install) to recognise my lan card!? thanks R

...Also, please attach files or disable word-wrapping when you send logs in >> the future. >> > Ah - I thought most mailing lists scrub attachments. > > -- Saurabh. This is a complete lateral jump. In the El/Centos line of distros I've seen a lot of issues caused by using the r8169 driver on RTL8111/8168/8411 cards including things like DNS failures and network slowdowns and other more exotic issues. The card performs better (in EL/Centos) with the r8168 driver which does not come built into the kernel, unless Ubuntu has unified the two drivers under the r8169 banner. Yo...

.... https://bugzilla.kernel.org/show_bug.cgi?id=116851#c23 Based on that, rewrite the prefetch register values even when that appears unnecessary. We have confirmed this solution on all the affected models we have in-hands (X542UQ, UX533FD, X530UN, V272UN). Additionally, this solves an issue where r8169 MSI-X interrupts were broken after S3 suspend/resume on Asus X441UAR. This issue was recently worked around in commit 7bb05b85bc2d ("r8169: don't use MSI-X on RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an Aimfor-tech laptop that we had not yet patched. I suspect...

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 =

..., but if the version of XCP uses the hypervisor 3.4.2 neither appears on the list. ps: I had a RTL-8169 but stopped working with update 0.5 for 1.0. It seems that this happened also with those who have upgraded from 5.6.0 to 5.6.0 FP1 . I tried to modify /etc/modprobe.conf inserting "options r8169 use_dac=1", but without effect. Thanks Roberto - São Carlos - SP - Brasil _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

.... https://bugzilla.kernel.org/show_bug.cgi?id=116851#c23 Based on that, rewrite the prefetch register values even when that appears unnecessary. We have confirmed this solution on all the affected models we have in-hands (X542UQ, UX533FD, X530UN, V272UN). Additionally, this solves an issue where r8169 MSI-X interrupts were broken after S3 suspend/resume on Asus X441UAR. This issue was recently worked around in commit 7bb05b85bc2d ("r8169: don't use MSI-X on RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an Aimfor-tech laptop that we had not yet patched. I suspect...

...to install 5.2 x86_64 on a new Gigabyte GA-G31M-S2L. This motherboard has an RTL8111C NIC on-board. After PXE booting into the 5.2 installer, the installer hung while waiting for DHCP information. Checking the various consoles, it's clear that the installer identified the NIC and loaded the r8169 driver. But the driver obviously failed. After copying in Realtek's r8168-8.006.00 and manually installing it on the existing 5.1 installation, the NIC works fine. So the wiki pages need to be updated. Any ideas how to proceed? Kirk Bocek wiki user: kirkbocek

...ND 0x0017 CLASS 0x02 0x00 0x00 REVISION 0x10 BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x08 BASE0 0x0000a401 addr 0x0000a400 I/O BASE1 0xe1001000 addr 0xe1001000 MEM MAX_LAT 0x40 MIN_GNT 0x20 INT_PIN 0x01 INT_LINE 0x0a [root at intranet ~]# lsmod | grep 8169 r8169 77125 0 mii 38849 1 r8169 So the driver is there, or so it seems. rmmod r8169 dropped both NIC's and I had to reboot the (headless) server to get the D-Link working again. Removing, and re-adding the eth0 interface with system-config-network doesn't...

...baseT/Half 100baseT/Full ??????????????????????????????? 1000baseT/Full ??????? Supports auto-negotiation: Yes ??????? Advertised link modes:? 10baseT/Half 10baseT/Full ??????????????????????????????? 100baseT/Half 100baseT/Full ??????????????????????????????? 1000baseT/Full have change the driver r8169 with r8168 and follow the guide on CentOS wiki http://wiki.centos.org/AdditionalResources/HardwareList/RealTekRTL8111b but still it only get 100Mbps speed. I user kernel 2.6.18-274.3.1.el5 and 2.6.18-274.3.1.el5-PAE. on another machine with the same specs I use kernel 2.6.18-238.9.1.el5 and the g...

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After some fiddling with blacklisting the driver during the kickstart process, I was able to get the machine to boot up with the r8169 as eth3 (!!!) while the other two were correctly identified as...