|
|
|
|
|
|
|
|
|
|
xen-devel
[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@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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: [Xen-users] xen kernel and e1000 problem,
Anand Gupta <=
|
|
|
|
|