[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] XCP 1.0 beta Realtek 8168 nic not working
- To: Joe Linoff <jlinoff@xxxxxxxxxx>, Grant McWilliams <grantmasterflash@xxxxxxxxx>
- From: Le Van Thanh <lethanhf@xxxxxxxxx>
- Date: Tue, 5 Apr 2011 20:47:58 +0700
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 05 Apr 2011 06:49:32 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=ua1Ze6jUlEhxk26iE1Kt2CnI/80e8svVJJ4LC8XmfHHev64MmSXrMOQabqQHVNnZ5V VoqcSEsohlqT3u6sdspMYO5A8y5fpQmsa0ZSwJnI49UGjnBC+J0IgmEHdRMh0YvZULI2 nw/TMVn6ejSJQDnKk+x8FB2B2ZfBbuJFDGwVY=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Hi Grant, Joe I have same problem on: XCP 1.0 base 42052, ASUS M4A79XTD EVO, Phenom II X6-1055T.
searching in mailinglist I found a solution
Add a line
options r8169 use_dac=1
into file /etc/modprobe.conf
and reboot system. It solved
Hope it helps, Thanh
On Tue, Jan 4, 2011 at 12:40 AM, Joe Linoff <jlinoff@xxxxxxxxxx> wrote:
Hi Grant:
I probably can’t help much because I am Xen newbie but I am having a similar problem with the Xen 3.4.3 kernel. After googling I found this: http://elrepo.org/tiki/tiki-index.php?page=kmod-r8168 . Right now I am trying to configure the boot loader to load the new driver but I am using cobbler (also as a newbie) so things are proceeding slowly. If it works, I will let you know.
Regards,
Joe 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 Express Gigabit Ethernet controller (rev 03)
I also put in an Intel e1000 card in each box and it works. I booted off a live Ubuntu 10.04 CD and both network cards worked beautifully. I booted up on a CentOS 5.5 DVD and went into Rescue mode and both cards worked.
Is this a driver issue with XCP 1.0.0 beta?
If I plug a network cable into eth0 (the Realtek port) I get this from dmesg
r8169: eth0: link up xenbr0: port 1(eth0) entering forwarding state
Things seem fine. Output of ethtool
[root@cloud1 ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Half Port: MII PHYAD: 0 Transceiver: internal
Auto-negotiation: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes
ethtool says the device has auto-negotiate off and running half duplex. Any attempts to use ethtool to fix it fail.
So my biggest frustration is that this network card works on CentOS 5.5. The main difference between CentOS and XCP is kernel so is this a kernel issue or is there a configuration issue?
Grant McWilliams
Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|