search for: 82572ei

...ith intel IOMMU working, everything works like a charm. Here's how I do it manually: root@kybrat (x86_64) ~]$ lspci -nn | grep net 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 06) 02:00.0 Ethernet controller [0200]: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] (rev 06) 05:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 05:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 06:00.0 Ethernet co...

...y eth1 network card any more. With kernel-xen-2.6.18-53.1.13.el5 everything is working as expected. With the two recent kernels I only get an Interface named __tmp786686833 which is not added to xenbr... lspci -v to the adapter in question says 02:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Intel Corporation PRO/1000 PT Desktop Adapter Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at febe0000 (32-bit, non-prefetchable) [size=128K] Memory at febc0000 (32-bit, non-prefetchable) [size=128K...

...king, everything works like a charm. Here's how I do it manually: > > root@kybrat (x86_64) ~]$ lspci -nn | grep net > 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 06) > 02:00.0 Ethernet controller [0200]: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] (rev 06) > 05:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) > 05:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) > 06:0...

...hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) 08:00.0 Ethernet controller: Intel Corporation 82573V Gigabit Ethernet Controller (Copper) (rev 03) Now when I look at the enumeration from dmesg, I get this: e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1e:68:58:00:4c <-- this is P...

I have a machine running Centos 5, x86_64. It has an Intel NIC: # lspci 15:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Fiber) (rev 06) The machine has two dualcore cpus. If I look at /proc/interrupts I get: CPU0 CPU1 CPU2 CPU3 0: 144873228 220741831 173615012 220733357 IO-APIC-edge timer 4: 269120 1203485 1964914 1528555 IO...

...work, unless I start writing multiple > > kickstart files, one per machine. > > > > Anyway, lspci reports this: > > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network > > Connection (rev 02) > > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet > > Controller (Copper) (rev 06) > > 08:00.0 Ethernet controller: Intel Corporation 82573V Gigabit Ethernet > > Controller (Copper) (rev 03) > > > > Now when I look at the enumeration from dmesg, I get this: > > e1000e 0000:00:19.0: eth0: (PCI Ex...

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...start file wouldn't quite work, unless I start writing multiple > kickstart files, one per machine. > > Anyway, lspci reports this: > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network > Connection (rev 02) > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet > Controller (Copper) (rev 06) > 08:00.0 Ethernet controller: Intel Corporation 82573V Gigabit Ethernet > Controller (Copper) (rev 03) > > Now when I look at the enumeration from dmesg, I get this: > e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) > 0...

...le > > > kickstart files, one per machine. > > > > > > Anyway, lspci reports this: > > > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit > Network > > > Connection (rev 02) > > > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet > > > Controller (Copper) (rev 06) > > > 08:00.0 Ethernet controller: Intel Corporation 82573V Gigabit Ethernet > > > Controller (Copper) (rev 03) > > > > > > Now when I look at the enumeration from dmesg, I get this: > > > e100...

When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what "fixed" the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo "[KICKSTART] Binding eth interfaces to the expected MAC address in UDEV" echo "## Created by

...<centos at centos.org> > Message-ID: <467F8136.3070503 at crc.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have a machine running Centos 5, x86_64. > > It has an Intel NIC: > > # lspci > 15:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet > Controller (Fiber) (rev 06) > > The machine has two dualcore cpus. > > If I look at /proc/interrupts I get: > > CPU0 CPU1 CPU2 CPU3 > 0: 144873228 220741831 173615012 220733357 IO-APIC-edge timer > 4: 2691...

...39;Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet ... em0@pci0:1:0:0: class=0x020000 card=0x10838086 chip=0x10b98086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82572EI PRO/1000 PT Desktop Adapter (Copper)' class = network subclass = ethernet ... [root@backup ~]# ifconfig re0 wol [root@backup ~]# ifconfig em0 wol [root@backup ~]# ifconfig em0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=19b<RXCSUM,TXCSUM,V...

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can