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

["Anand Gupta" <xen.mails@xxxxxxxxx>]

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