I have tried to search for this on this mailing list however haven''t
had any
luck with a solution.
The problem basically is as follows:
WoodCrest 5150
Intel s5000xvn Motherboard
4GB Ram
750 GB SATA
Now when i run centos 4.4 kernel, the onboard 2 Intel Gigabit ethernet work
out of the box.
However when i compile a xen kernel (tried "make dist", manual kernel
compile), the two ethernet stop working. It looks as though the system tries
to setup them as wireless cards. Here is the output of /etc/init.d/network
restart with xen enabled kernel.
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Error for wireless request "Set Encode"
(8B2A)
:
SET failed on device eth0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth0 ; No such device.
SIOCGIFFLAGS: No such device
Failed to bring up eth0.
[FAILED]
I also tried to manually build the kernel, and instead of making the intel
driver as module, compiled it into the kernel. However the problem remains
same. lspci shows both the cards present under xen kernel.
Can someone please tell me what can be done to resolve this issue ? Will
really appreciate it.
--
regards,
Anand Gupta
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Hi Roberto, thanks for the quick response. I will try to do that. Btw I had tried to load Ubuntu Edgy on this machine earlier and under that the card worked (i believe it has 2.6.17 series kernel). On 12/27/06, Roberto De Ioris <roberto@unbit.it> wrote:> > On mer, 2006-12-27 at 01:31 +0530, Anand Gupta wrote: > > I have tried to search for this on this mailing list however haven''t > > had any luck with a solution. > > > > The problem basically is as follows: > > > > WoodCrest 5150 > > Intel s5000xvn Motherboard > > 4GB Ram > > 750 GB SATA > > > > Now when i run centos 4.4 kernel, the onboard 2 Intel Gigabit ethernet > > work out of the box. > > > > However when i compile a xen kernel (tried "make dist", manual kernel > > compile), the two ethernet stop working. It looks as though the system > > tries to setup them as wireless cards. Here is the output > > of /etc/init.d/network restart with xen enabled kernel. > > > Probably your card is not supported by the e1000 driver in 2.6.16 > kernel. > > You can compile the latest e1000 module (taken from intel website) > > http://support.intel.com/support/network/adapter/1000/software.htm > > for kernel 2.6.16 > > > -- > Roberto De Ioris > http://unbit.it > JID: roberto@jabber.unbit.it > > >-- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand Gupta írta:> Hi Roberto, > > thanks for the quick response. I will try to do that. > > Btw I had tried to load Ubuntu Edgy on this machine earlier and under > that the card worked (i believe it has 2.6.17 series kernel). > > On 12/27/06, *Roberto De Ioris* <roberto@unbit.it > <mailto:roberto@unbit.it>> wrote: > > On mer, 2006-12-27 at 01:31 +0530, Anand Gupta wrote: > > I have tried to search for this on this mailing list however haven''t > > had any luck with a solution. > > > > The problem basically is as follows: > > > > WoodCrest 5150 > > Intel s5000xvn Motherboard > > 4GB Ram > > 750 GB SATA > > > > Now when i run centos 4.4 kernel, the onboard 2 Intel Gigabit > ethernet > > work out of the box. > > > > However when i compile a xen kernel (tried "make dist", manual > kernel > > compile), the two ethernet stop working. It looks as though the > system > > tries to setup them as wireless cards. Here is the output > > of /etc/init.d/network restart with xen enabled kernel. > > > Probably your card is not supported by the e1000 driver in 2.6.16 > kernel. > > You can compile the latest e1000 module (taken from intel website) > > http://support.intel.com/support/network/adapter/1000/software.htm > > for kernel 2.6.16 > > > -- > Roberto De Ioris > http://unbit.it > JID: roberto@jabber.unbit.it <mailto:roberto@jabber.unbit.it> > > > > > > -- > regards, > > Anand Gupta > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersIt should be some CentOS configuration issue as e1000 is working fine for me in two machines: Debian Etch, Xen 3.0/kernel 2.6.16 and Debian Etch, Xen 3.0/kernel 2.6.18. What should be noted with the bridged setup in Debian you don''t try to activate the interfaces at all, just the bridges you''ve configured on them. Good Luck! Geza _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 12/27/06, Gémes Géza <geza@kzsdabas.sulinet.hu> wrote:> > It should be some CentOS configuration issue as e1000 is working fine > for me in two machines: Debian Etch, Xen 3.0/kernel 2.6.16 and Debian > Etch, Xen 3.0/kernel 2.6.18. What should be noted with the bridged setup > in Debian you don''t try to activate the interfaces at all, just the > bridges you''ve configured on them. >I am sorry but i didn''t understand the meaning of this ? Why shouldn''t i activate the interfaces ? Btw i resolved the problem as per Roberto''s suggestion. I first tried to compile the nic drivers which came with the mb for linux, they didn''t compile. Then i got the latest drivers from http://sf.net/projects/e1000, drivers release dated 14th Dec, worked. I was able to compile them, issue modprobe, assign them an ip and i can now activate the interfaces and ping outside network. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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. Hope this helps you. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 12/26/06, Gémes Géza <geza@kzsdabas.sulinet.hu> wrote: <snip>> Etch, Xen 3.0/kernel 2.6.18. What should be noted with the bridged setup > in Debian you don''t try to activate the interfaces at all, just the > bridges you''ve configured on them. > > Good Luck! > > GezaCan you describe this a little more? I noticed this behavior last week after installing Etch/Xen. I couldn''t get any networking until I brought up a DomU, which in turn brought up the bridge. -- Matt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 2006-12-27 at 20:44 -0800, Matt Richardson wrote:> On 12/26/06, Gémes Géza <geza@kzsdabas.sulinet.hu> wrote: > <snip> > > Etch, Xen 3.0/kernel 2.6.18. What should be noted with the bridged setup > > in Debian you don''t try to activate the interfaces at all, just the > > bridges you''ve configured on them. > > > > Good Luck! > > > > Geza > > Can you describe this a little more? I noticed this behavior last > week after installing Etch/Xen. I couldn''t get any networking until I > brought up a DomU, which in turn brought up the bridge.Are you guys using the default network-bridge script? I have systems up with your configuration but can''t duplicate your problems.. my guess is that''s the root of it. Please let me know :) I''m about to take a whole rack of blades from sarge to etch.. and I''m thinking Ubuntu is the safest bet at this point. Nothing has changed in the related packages (as far as I can tell).. so something is really weird. Best, -Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand Gupta
2007-Mar-25 11:56 UTC
[Xen-devel] Re: [Xen-users] xen kernel and e1000 problem
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.
modprobe e1000
kobject_register failed for e1000 (-17)
[<c01dabfd>] kobject_register+0x5d/0x70
[<c022cabf>] bus_add_driver+0x6f/0xc0
[<c01e5fba>] __pci_register_driver+0x5a/0x90
[<c0121027>] printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83 [e1000]
[<c013e837>] sys_init_module+0x127/0x1d0
[<c0105461>] syscall_call+0x7/0xb
When i try to do ifup eth0
ifup
eth0
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
Error for wireless request "Set Encode" (8B2A)
:
SET failed on device eth0 ; No such
device.
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
Error for wireless request "Set ESSID" (8B1A)
:
SET failed on device eth0 ; No such
device.
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
ip_tables: (C) 2000-2006 Netfilter Core
Team
kobject_register failed for e1000
(-17)
[<c01dabfd>]
kobject_register+0x5d/0x70
[<c022cabf>]
bus_add_driver+0x6f/0xc0
[<c01e5fba>]
__pci_register_driver+0x5a/0x90
[<c0121027>]
printk+0x17/0x20
[<f4804046>] e1000_init_module+0x46/0x83
[e1000]
[<c013e837>]
sys_init_module+0x127/0x1d0
[<c0105461>]
syscall_call+0x7/0xb
SIOCGIFFLAGS: No such
device
Failed to bring up
eth0.
Any help on this will be appreciated.
On 12/27/06, Anand Gupta <xen.mails@gmail.com>
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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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@gmail.com> 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@gmail.com> 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@lists.xensource.com http://lists.xensource.com/xen-users