similar to: Problem with CentOS 5.1/xen/RTL8110

Hello: I'm having issues with my CentOS 5.1/Xen installation. If I run the xen-bridge, I seem to get flaky ethernet. By flaky I mean everything seems fine from the host machine, but if I attempt to contact the host machine from another remote machine (eg. my laptop which is on the same subnet as the xen machine, separated by 10 ft of cable and a router) I either get extremely high ping

I'd like to add a page for the Realtek r1000 NIC driver for the RTL8110SC (and others) chipset. This driver is not included in the kernel. I've previously posted to the general mail list: http://lists.centos.org/pipermail/centos/2007-February/075383.html I'm guessing this would go in the HardwareList section. Otherwise a page titled 'Realtek r1000 Driver' would work. my

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

Executive Summary: Realtek has an r1000 driver for the rtl8110sc NIC at http://www.realtek.com.tw/downloads I've posted this in the forums but it looks like all the action for CentOS really happens here on the mailing list. Plus I hope this might help some other lost soul since google failed to connect this motherboard to *any* mention of the r1000. I thought I found a great little

Could I get write access to http://wiki.centos.org/HardwareList/CentOS5/RealTek/r1000? There's a couple of things I'd like to copy over from my CentOS4 R1000 page. Wiki Name: kirkbocek Thanks, Kirk Bocek

What is the difference between these two fragments (taken from two different tblgen record dumps)? dag OutOperandList = (outs GPR:$rd); dag OutOperandList = (outs R2); The first is from the RISCV backend record dump. There will be a substitution at some point for $rd. In the second, I'm specifying R2, no substitution necessary. If I specify GPR64:R2 or i64:R2 in my Instruction def,

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

Hello I've just been hit by one of the chipsets described at http://wiki.centos.org/HardwareList/RealTekRTL8111b. Because a) it does not work with the stock driver included in Centos 5.1 and b) I am very lazy and I do not like manually compiling modules each time a new kernel is installed (not to mention that I never forget anything, except for the important things which always go

Hi, After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC refuses to handle large file transfers. pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' class = network subclass = ethernet Log

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

Remote box SNV93 (xVM kernel) 192.168.1.54 (NIC RTL8169) Attempts of ssh connection from CentOS 5.1 DomU 192.168.1.37 at SNV93 Dom0 (NIC RTL8110SC) # ssh user1@192.168.1.54 hangs .. TCPDUMP running on remote box (192.168.1.54) # tcdump -s 1600 -vv One entry generates for each ssh connection attempt. First:- 17:12:43.058821 IP (tos 0x0, ttl 64, id 19771, offset 0, flags [DF], proto TCP (6),

We recently had our PRI installed, we currently have 100 toll-free's pointing to it. I have almost everything working great but.. I have setup the first few numbers we want to use coming in from the PRI and they work great, but.. What I want to do is setup an extension with pattern matching to answer for any numbers called that are pointed to our system and PRI but not yet in

Hi, I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos. Thanks! --beast

Hi - I have a machine which was originally built with Centos 5.0 including xen. It has all the current updates and here are some questions: The current problem is: 1) If I boot the non-xen kernel - it runs fine. If I boot the xen kernel - it boots - but has no network connectivity - and I get the following errors continuously in the messages log: Time/date: C5 Kernel: vif0.0: received packet

Hello Kindred R Spirits... I'm trying to get a file (csv) from Dropbox using their shareable link concept. They issue a short URL that goes to a web page where you see a button that says "Download File". They don't really give you the URL of the file itself, just this page. Is there a way to coax R into getting such a file? I don't even really want the file per

Is there anyway to force an autopickup on a cisco 7940 / 60 from the dialplan ? My problem is that I am originating a call from the AMI, with the internal user being called first, and then connecting to external user. However, sometimes the internal user doesn't pick up the phone, so the call is never placed. I need to know the results of the call so I need to be able to either a) get

On Tue, 2007-09-04 at 23:32 +0100, Karanbir Singh wrote: > Hi, > > Phil Schaffner wrote: > > Karanbir provided driver disk images and indicated that kmod drivers > > would be in CentOS-5 Extras, but apparently these never materialized. > > The only src.rpm I could turn up was the last link above, and I did get > > CentOS-5 x86_64 kmod-style drivers to build from

Hi all, This is my first post! I'm newbie, yesterday I installed Asterisk@home, and I got lot of Kernel panics, after trying to reinstall it, this messages dissapeared. My problem now is that the default password for maint user in AMP is not working... I got this error message when I try to connect via another computer in the same network, after trying to log -> maint/password: FORBIDDEN

Hello, I am building a DRBD cluster with CentOS 4.4. Both nodes have RTL8169S-32 cards, Pheenet branded. I'm getting no more than 185 Mbps with the driver selected at installation (r8169). Downloading Realtek's r1000 climbs to some amazing 200Mbps. I am measuring performance with iperf, host to host, with a cat5e direct cable some 2.5ft long. Maybe disk I/O will be the bottleneck in my use

I'd like to add a page for the Realtek RTL8111b NIC. I'm not sure how you'd like to organize it since the page really could be relevant to both CentOS 4 and CentOS 5. I think a single page like: http://wiki.centos.org/HardwareList/RealTekRTL8111b Would work with links to both CentOS 4 *and* CentOS 5? However, if the wiki admins want two pages, that'll be fine too. Can you also