WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-users] xen kernel and e1000 problem

To: "Xen Users" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] xen kernel and e1000 problem
From: "Anand Gupta" <xen.mails@xxxxxxxxx>
Date: Sun, 25 Mar 2007 18:20:40 +0530
Cc: roberto@xxxxxxxx, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gémes Géza <geza@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 25 Mar 2007 05:49:44 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=m6HxkXxG33QxSd6w3OTTMRIpQVJkBzRjvv3YGNbROXXuEzZvQNVXVSQQlrHHn3WHt6Ml+xBM8fpUryei5GCDdeoLigoifc9sB7ENVvPPJOeOBWRBhul5Whc8qUC04ZXlPjy90KjBYsA+CzIzB5JdJxpkosZaJknM4a9igh3ENaM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=c1ZmxLyRbrNY5oS+g1FqiaE/0vOJt2n43qbY4U8abAlaE+d7wenHikp+dojnHwwVmeb+anMOHgaAtJ5HQgzyBloobeHU5B3TuIyKdRE59cmrpvc+ISnP+kQjGLk1hh6Kv10+5KJxK8w54PK40iaLDHAdIcfM7H/EMmWS1IczBgo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <acb757c00703250456q1bbd2c36lfeda6b627be05667@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <acb757c00612261201o2207fa92t749c9432d3a1a99b@xxxxxxxxxxxxxx> <1167163618.7466.4.camel@hagrid> <acb757c00612261217u79a95e20hbd64a6266382a3d4@xxxxxxxxxxxxxx> <45919079.2080607@xxxxxxxxxxxxxxxxxxx> <acb757c00612262237v20882e92m359bdc59ba70f783@xxxxxxxxxxxxxx> <acb757c00612262254m3a15059eg988dd1232adbc1f0@xxxxxxxxxxxxxx> <acb757c00703250456q1bbd2c36lfeda6b627be05667@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Problem resolved.

The problem was caused because i had compiled e1000 drivers into the kernel. I changed it back to be compiled as modules and followed the procedure, thus network interface started to work.

On 3/25/07, Anand Gupta <xen.mails@xxxxxxxxx> wrote:
I have gotten in trouble with another woodcrest. This is a 5130.

I followed my own steps to compile a driver for e1000, however it didn't work.

On 12/27/06, Anand Gupta <xen.mails@xxxxxxxxx> wrote:
These are the steps i followed, incase someone else requires it.

1. Download e1000 latest driver from http://sourceforge.net/project/showfiles.php?group_id=42302. As on date, the latest drivers are dated Dec.14th, 2006.
2. Copy the file to /usr/src/. Extract it out. Go to /usr/src/e1000-x.x/src
3. Run "make install"
4. To ensure any old module has been removed, run "rmmod e1000"
5. Now run "modprobe e1000"
6. Assign an ip to the interface, "ifconfig ethx x.x.x.x"
7. See if you can ping the interface now.



--
regards,

Anand Gupta



--
regards,

Anand Gupta
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>