Hi Bjorn,
I think Timur's problem was solved. Here is the link http://old.nabble.com/how-to-start-wget-example--td33415431.html
In his case he just had to set the NIC driver in qemu, which he wasnt doing and so was getting assert.
I my case, I am using it on a real hardware where the Ethernet controller is present. The correct driver gets loaded by Ankh. But it fails when it tries to allocate the IRQ.
The Following is the log which shows what I am saying.
------------------------------------- ankh | <6>0000:00:01.0: eth0: (PCI Express:2.5GB/s:Width x1) 0x14815cM ankh | <6>0000:00:01.0: eth0: Intel(R) PRO/1000 Network Connection ankh | <6>0000:00:01.0: eth0: MAC: 3, PHY: 8, PBA No: ffffff-0ff ankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI ankh | <6>Copyright (c) 1999-2006 Intel Corporation. ankh | <6>net_namespace: 636 bytes ankh | open_network_devices() ankh | opening lo ankh | <6>device lo entered promiscuous mode ankh | set interface to promiscuous mode. ankh | opening eth0 ankh | <6>device eth0 entered promiscuous mode ankh | set interface to promiscuous mode. ankh | Thread 0xb0 for IRQ 10 ankh | Bind irq to icu failed with -2 ankh | claim_irq: failed to attach IRQ ankh | <3>0000:00:01.0: eth0: Unable to allocate interrupt, Error: -16 ankh | error opening eth0 : -16 -------------------------------------------------- -Shashi
On Wed, 2012-03-21 at 22:51 +0100, Björn Döbel wrote:
Hi,
I am trying to use e1000e driver in Ankh to bring-up intel's 82574L ethernet controller. But its unable to allocate interrupt and I cant figure out the source of the problem.
this may be related to the problem reported by Timur on this list a week ago or so. I'll try to come up with a fix.
Bjoern
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers