[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bulk] Re: [Xen-users] eth0 / device problem in dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Peter Fastré" <peter.fastre@xxxxxxxxx>
  • Date: Tue, 27 Mar 2007 16:47:43 +0200
  • Delivery-date: Tue, 27 Mar 2007 07:46:43 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=gdkph9k4GPaUXgipI7SnEqsn0qSlJB/cPgtqcowhFcw+oXCmc8mH+gSy0JGmUZmCzi3oq1yqaJ93sWS9RSYO8EVliBGKEk7EPlIcSlYyylZ45d5bNk2YL6p5XiafaTl8vgqPVgNiJeVp7ao5KwE7bKQZOCNTnRrBFlXIu2RnPs0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>



On 3/27/07, phcolaris <phcolaris@xxxxxxxxxxx> wrote:

00:04.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet
Controller (rev 05)

I have a recent supermicro server, and the Intel network cards weren't recognized by the 2.6.16.33 kernel either. You can get an updated driver from http://sourceforge.net/projects/e1000.

You can compile the driver as a module, as described in the driver install procedure. If you do that, however, you have to make sure you don't have the older e1000 driver compiled in your kernel. So recompile your Xen kernel WITHOUT the intel e1000 driver. It took me some time before I had figured that out.
You can also replace the driver in the 2.6.16.33-kernel by the files you got from sourceforge. This way, it's possible to compile the driver in the kernel, if you would like that.

Peter



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.