Dear Matthias, 

You are right about the PCI. I checked the configuration and unfortunately the PCI support was not checked. I selected it and I have seen logs for e1000 and PCI support. However, unfortunately now I get kernel panics. This is shown in the following debug outputs at the last 2 lines:

" vmlinuz | Invalid IO-Port access at pc = 006c3e7c port=0x110
vmlinuz | Page fault (non-resolved): pfa=1a8 pc=49475d "

vmlinuz | l4lx_thread_create: Created thread 418 (cpu0) (u:b3000400, v:b3000600, sp:00795ff4)
vmlinuz | main thread will be 418
vmlinuz | l4x_register_pointer_section: addr = 00793000 size = 1142784
vmlinuz | section-with-init: virt: 0x793000 to 0x8a9fff [1116 KiB]
vmlinuz | section-with-init: Phys: 0x00b04000 to 0x00c1b000, Size:  1142784
vmlinuz | l4x_linux_startup: thread 418.
vmlinuz | Main thread running, waiting...
vmlinuz | main thread: received startup message.
vmlinuz | l4x_setup_memory: Forcing superpages for main memory
vmlinuz | l4re_global_env: 0xb1007edc
vmlinuz | Main memory size: 512MB
vmlinuz |     Main memory: virt: 0xc00000 to 0x20bfffff [524288 KiB]
vmlinuz |     Main memory: Phys: 0x05800000 to 0x25800000, Size: 536870912
vmlinuz | Filling lower ptabs...
vmlinuz | Done (1645 entries).
vmlinuz | l4x_register_pointer_section: addr = 00793000 size = 1142784
vmlinuz |             end: virt: 0x793000 to 0x8a9fff [1116 KiB]
vmlinuz |             end: Phys: 0x00b04000 to 0x00c1b000, Size:  1142784
vmlinuz | l4x_rd_path: rom/drops-rd.rd
vmlinuz | Loading: rom/drops-rd.rd
vmlinuz | INITRD: Size of RAMdisk is 32768KiB
vmlinuz | RAMdisk from 28c00000 to 2ac00000 [32768KiB]
vmlinuz | l4lx_thread_create: Created thread 420 (timer.i0) (u:b3000800, v:00000000, sp:0082fff8)
vmlinuz | timer_irq_thread: Starting timer IRQ thread.
vmlinuz | WARNING: Unknown rdmsr: 00000186 at 0x7cb48a
vmlinuz | WARNING: Unknown rdmsr: 00000187 at 0x7cb48a
vmlinuz | WARNING: Unknown wrmsr: 000000c1 at 0x7cb519
vmlinuz | WARNING: Unknown rdmsr: 000000c1 at 0x7cb52d
unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org
mag     | Input: new keyboard device (src='userdata: 0x6bdc' stream='userdata: 0xccc0')
mag     |                            bus='i8042' vendor=0x1 product=0x1 version=43841
vmlinuz | Invalid IO-Port access at pc = 006c3e7c port=0x110
vmlinuz | Page fault (non-resolved): pfa=1a8 pc=49475d



From: Matthias Lange <mlange@sec.t-labs.tu-berlin.de>
To: Wajidali Whowe <whowe123@yahoo.com>
Cc: l4-hackers@os.inf.tu-dresden.de
Sent: Tuesday, August 7, 2012 8:36 AM
Subject: Re: Ethernet device

On Mon, Aug 06, 2012 at 04:47:36PM -0700, Wajidali Whowe wrote:
> I prepared another iso image including only l4linux and a small file system prepared by the buildroot (including busybox).
> the .devs file was exactly the same as the one that I sent before and similarly the .vbus file. The following is the outputs during bootup until fb-drv takes the console: (moreover I wanted to show also dmesg outputs after boot and "lspci" or "mdev -s" outputs after mounting the /proc and /sys", however I could not copy them from qemu or virtual box as I could not activate serial console, please kindly find the screenshots in the respective order for the dmesg outputs" and sorry for the high load of debug outputs...)

Have you tried the "-serial stdio" option? I cannot see anything PCI or e1000
related in the L4Linux log. Can you post the result of "grep PCI .config" and
"grep E1000 .config" from your L4Linux config?

Matthias.

--
Dipl.-Inf. Matthias Lange <mlange@sec.t-labs.tu-berlin.de>
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58 553
Mobile: +49 - 160 - 587 28 07
Web: http://www.t-labs.tu-berlin.de/sect