On Thu Aug 10, 2006 at 01:53:56 +0200, Daniel Vandersee wrote:
Andreas Niederl wrote:
You could try the option all_sects_writable in your loader script for L4Linux. This works for me with Qemu.
Thank you, this works so far. Now L4Linux begins to start, but something different is still going wrong:
ttyLv0 at MMIO 0x1 (irq = 0) is a L4 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Trap: 13: 0000 [#1] Modules linked in: CPU: 0 EIP: 0000:[<00514c7a>] Not tainted VLI EFLAGS: 00210206 (2.6.17-l4 #5) EIP is at i8042_flush+0x1a/0xa0 eax: 00808000 ebx: 03dc4408 ecx: 00080000 edx: 00000064 esi: 00000000 edi: 00000001 ebp: 00809e68 esp: 00809e5c ds: 1000 es: 4000 ss: 0000 Process swapper (pid: 1, threadinfo=00808000 task=00805bb0) Stack: 03dc4408 00000000 005dc9d4 00809e74 00515539 03dc4408 00809e88 0061bd41 03dc4408 00000000 005dc9d4 00809e94 005115c3 03dc4400 00809eac 0050fa14 03dc4408 00000000 00809ecc 0050fa60 00809ebc 0050fa70 005dc9d4 03dc4408 Call Trace: <0040a3ec> show_stack_log_lvl+0x7c/0xa0 <0040a556> show_registers+0xf6/0x160 <0040a753> die+0xe3/0x1d0 <00000000> _start+0xffc00000/0x50 <00515539> i8042_controller_init+0x9/0x100 <0061bd41> i8042_probe+0x21/0x100 <005115c3> platform_drv_probe+0x13/0x20 <0050fa14> driver_probe_device+0x54/0xa0 <0050fa70> __device_attach+0x10/0x20 <0050f178> bus_for_each_drv+0x58/0x70 <0050fad4> device_attach+0x54/0x60 <0050f295> bus_add_device+0x25/0x90 <0050e3ba> device_add+0xda/0x130 <0050e423> device_register+0x13/0x20 <005113f5> platform_device_add+0xa5/0x160 <0061be87> i8042_init+0x67/0x90 <0060a7d1> do_initcalls+0x31/0x100 <0060a8bc> do_basic_setup+0x1c/0x20 <00400220> init+0x30/0x140 <004073f9> kernel_thread_start+0x29/0x30 <004073ce> ret_kernel_thread_start+0x6/0x8 Code: fc c9 c3 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 57 56 31 f6 53 e8 f3 e8 ee ff 89 c7 e8 3c e6 ee ff 8b 15 20 c9 5d 00 <ec> a8 01 88 c3 74 60 68 de 46 03 00 e8 a5 36 fd ff 8b 15 24 c9 EIP: [<00514c7a>] i8042_flush+0x1a/0xa0 SS:ESP 007b:00809e54 <0>Kernel panic - not syncing: Attempted to kill init! panic: going to sleep forever, bye
This is the keyboard driver which probably tries to do some in/outs which will not work on Fiasco-UX. You have to disable it (Device Drivers -> Input Device suppor -> Hardware I/O prots -> ...).
Adam