similar to: Issues with r8169 gige on boot.

Me again. The ASUS P5N32-SLI motherboard in my new machine has dual NICs but CentOS has only detected one of them. I've tried rebooting with the network plugged in only to the second one, but kudzu still doesn't find it. Any suggestions?

I have a bug report in (0002288) on an install failure on my decTOPs (Centos 4.5 installed on them). I have tried a lot of combinations and it is getting tiring. What what happen, or rather how do I get the following to work: Put my HD into a computer (Compaq SSF that I have installed Centos 5 on with no trouble), install Centos 5, move the HD to the decTOP. Different Video card. No PS/2

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The

I've go a Compaq Presario (SR5110NX) that I've loaded CentOS 5 on and all is well except for the sound card. I understand that OSS supports the chipset but it's not being detected an loaded properly and I've invested a significant amount of time already. I've probably got an old supported card lying around here somewhere but I hat to give up on the principal. I would rather

Hi all, I am having problems to get the SeaLevel IO card to work with CentOS distro. Basically the card is being recognised and shown by lspci BUT /proc/devices file is not updated with the new devices does anyone know why. ? Could someone tell me what/where infos are needed to get /proc/devices to be updated. The reason I require the /proc/devices infos is because I want to run a mknod

Hello all, I'm going to tackle learning C this week, and start writing my first * add-on/contribution; assuming it's actually worthy of contributing once it's done.. I think I've chosen a hefty project for my first go round here... I'd like to get some feedback from everyone on a FindMe/FollowMe spec I've put together. Before you read on, let me say, I don't want

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

My HP 4010 and the IGP 350M video card. I can only get it to go into 800x600 mode. At one time, Resolution Display (gnome desktop) was giving me an option of 1024x768 and if I selected it the monitor went crazy. Now I don''t even get that higher resolution as an option. I have searched far and wide for information on this card and the Radeon linux driver. No help at all. My

I have a newly built drive with 5.2 fresh install (that I will be cloning shortly) in my DECtop and it is failing with X the same way the upgrade from 5.1 drive did (not too supprising there). In 5.1 X worked. I could startx from init 3 and get into GNOME. Also VNC into the box and have a GNOME screen. With 5.2, I get a kernel panic. Well I guess it is a kernel panic because once I run

My OQO has a VIA chipset. From the hwconf: class: VIDEO bus: PCI detached: 0 desc: "VIA Technologies, Inc. CX700M2 UniChrome PRO II Graphics" vendorId: 1106 deviceId: 3157 subVendorId: 1106 subDeviceId: 3157 pciType: 1 pcidom: 0 pcibus: 1 pcidev: 0 pcifn: 0 When I install Centos, I default to the vesa driver, and it operates at the monitor's native 800x480. Of course I

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Dear colleagues, experimenting with new amd64-based router we found strange re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most

Hi, I'm having trouble getting networking to work and I'm not sure what I'm doing wrong. The network interface of the host is connected to a switch-port that is configured as trunk and allows tagged traffic for vlan id 10. The host itself has the interfaces eth1.10 and eth1 defined. eth1.10 is configured with the primary ip address of the host system and eth1 is slave of the bridge

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

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

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

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? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

Thanks for you reply. I have installed asciidoc with "pkg_add asciidoc" And it returns something: # asciidoc fgh asciidoc: FAILED: input file /root/nut/fgh missing # which asciidoc /usr/local/bin/asciidoc Maybe there is any way to skip building man pages. This is not the such main thing as a new devices support. I also could built the driver that I need # make riello_ser but I don't

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