search for: e1000e

Have you experienced this? What's going on when this occurs? What do I need to do to keep it from occurring? Please advise. Thanks. Dec 4 10:18:17 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:19 localhost kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Dec 4 10:18:21 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:23 localhost kernel:

a previously rock solid reliable server of mine crashed last night, the server was still running but eth0, a Intel 82574L using the e1000e driver, went down. The server has a Supermicro X8DTE-F (dual Xeon X5650, yada yada). server is a drbd master, so that was the first thing to notice network issues. Just a couple days ago I ran yum update to the latest, I do this about once a month. /var/log/messages logged... (prior to...

I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) [root at fsdsigns2 ~]# more /etc/modprobe.conf alias eth0 e1000 alias eth1 forcedeth sometimes on boot the forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.

Folks I know that support for the network adaptors supported by the 'e1000' driver have been removed from the base distribution. However, I have exactly that controller (Broadcom Gigabit Ethernet PCI, not PCIe). Is there a way for me to add support for that on Centos 8.1? Perhaps a driver in an RPM package? Thanks David

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought up and ready almost immediately. For the record, I am using the following versions: - L0

KB and I were looking at repositories to import into git.centos.org recently, and we found the e1000e package -- a rebuild of the Intel e1000 driver for the x4c kernel. Does anyone know if this externally-build module is still necesssary for Linux 3.10? Or for Linux 3.14, which we're planning on moving to at some point in the near future? -George

This is a problem I've had on and off under CentOS5 and CentOS6, with both xen and kvm. Currently, it happens consistently with kvm on 6.5, e.g. with every kernel update. I *think* it generally worked fine with the 6.4 kernels. There are 7 VMs running on a 6.5, x86_64, 8GB RAM host, each with 512MB RAM and using the e1000 NIC. I picked this specific NIC because the default does not allow

Hi, I am trying to create a custom initrd that will work with PXE Booting on CentOS release 4.5 (Final) and Fedora Core 6. Can anyone point me to some documentation that will help with this ? The specific situation is that we have received some machines that need the latest e1000 Driver from Intel in order to detect the network card. If I install the systems without network and then do

Hi, I've been experiencing occassional network time-outs with the Intel Gigabit nic's (e1000) in Poweredge systems. I'm not sure if it's a hard or software problem but it occurs on different systems with Centos 4.2 and 4.3 and was wondering if there' s a workaround available like compiling an updated e1000 module or something. kind regards, Geert -------------- next part

One of the more promising solutions I'm looking at for my dual-ethernet dual-monitor workstation contains an Intel 82574L Ethernet controller. I found a LOT of postings regarding a bug in the driver for this controller: http://www.doxer.org/learn-linux/resolved-intel-e1000e-driver-bug-on-82574l-ethernet-controller-causing-network-blipping/ https://bugzilla.redhat.com/show_bug.cgi?id=632650 but there isn't any clear indication as to whether the bug has been resolved in mainline CentOS 6.4 or not. Has this bug been resolved? -G. -- Glenn Eychaner (geychaner at lc...

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

So far v2v did not read the model of network interfaces, resulting in "virtio" as the model for such interfaces. Start reading the model, if available, mapping only E1000 for now. There are also other models, e.g. PCNet32 or VmxNet3, but they are ignored for now: reading them as Source_other_nic would result in v2v rejecting OVAs previously converted. --- v2v/parse_ovf_from_ova.ml

Hi, I've set up a bridge using the 2.6.11.6 kernel. The machine is running Debian testing with three NICs in it. eth0 is a standard 100Mb Intel NIC, eth1 and eth2 are both Intel gigabit cards using the e1000 driver. I tested everything at 100Mb and it worked fine. I moved the machine into production, eth1 plugging into a dumb 100Mb D-link switch, eth2 plugging into a shiney new Cisco

On Fri, Mar 23, 2018 at 12:35:36PM +0100, Pino Toscano wrote: > So far v2v did not read the model of network interfaces, resulting in > "virtio" as the model for such interfaces. > > Start reading the model, if available, mapping only E1000 for now. Looks sensible, ACK. > There are also other models, e.g. PCNet32 or VmxNet3, but they are > ignored for now: reading

On 05/10/2018 02:53 PM, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed What is your definition of "becomes ready"? Are you looking at the output of "ip link show" in the guest? Or are you watching "brctl

Hi list It's my first message here, but I use CentOS from long time ago (sorry my language, I'm spanish from Colombia) I have a Intel board with an Integrated Network Card 82578DC. I've sucessfully installed the driver with the RPM kmod-e1000e; I've found it in ElRepo.org, and I've installed it via Yum. After I've installed the package (see this: http://lists.elrepo.org/pipermail/elrepo/2010-December/000416.html ), I do: ifdown eth1 modprobe -r e1000e ifup eth1 After these steps, my card works OK and get a valid IP address...

My system configuration: ASUS M2A-VM motherboard AMD Athlon 64 X2 4200+ 2.2 GHz 4x A-DATA 1GB DDR2 800 memory 2x Intel 10/100/1000 Pro/1000 GT Desktop Network Adapter 2x Seagate Barracuda 250GB HD (RAID 1, software RAID) CentOS 5 x86_64; Kernel 2.6.23 (custom built); Version 7.6.9.2 e1000 driver The symptoms of this problem are outlined at: http://e1000.sourceforge.net/wiki/index.php/Issues[1]

Hello all. I''ve upgraded my drives, and in doing so loaded FC8. Latest kernel-xen.x86_64 (2.6.21.7-5) and xen.x86_64 (3.1.2-5) available, using 2 Intel NICs with e1000 driver. All worked fine on FC5 with custom domU FC5 with pcifront and NIC drivers in kernel. Now, I''m unable to get the NICs to function inside my domU. The are visible in lspci, and ipconfig. DomU dmesg

We have a 10Gbps connection to our server so I need to be able to create VMs using the faster e1000 nics instead of the default Realtek 100Mbps ones but I''m not sure how to go about it. Is there a walkthrough or "howto" or can someone point me at some simple instructions? I''m using xen-3.0.3-105.el5_5.5 and Centos 5.5 kernel 2.6.18-194.32.1.el5.centos.plusxen VMs are

Greetings! I am currently building a PXE distro server for a company that I'm contracting for, but I'm having some problems. Here's the scoop: Some of the clients I want to install on are Angstrom blades with Intel e1000 NICs. Using the pxelinux.0 file on the FC6 distro, I can install FC6 just fine. However, FC4 bombs. The system pulls it's DHCP address just fine, and then