Hi,
On Wed Feb 14, 2007 at 17:50:37 +0000, Michael Kasper wrote:
Hello L4-Hackers,
I try to become familiar with L4Linux on top of Fiasco-UX. Therefor, I've rebuilt the sources as described online. But booting L4Linux with the example drops-rd.rd ramdisk fails with kernel panic. Shortly after the ramdisk is loaded, the boot process halts with the following message:
Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye
Has anyone a solution for this? Is the ramdisk not accessible by the L4Linux kernel, or do I need explicitly specify an init parameter?
You need to enable Framebuffer support in L4Linux and also the Framebuffer-driver in the L4Linux (L4Linux->Stub drivers). You also need to start Fiasco-UX with ux-con, the graphical console. The lx script from runux will do that for you when started with the 'con' command.
The problem you are seeing is that Linux doesn't have an active console and thus fails to start. Enabling the framebuffer will give you a console and should make your setup work.
Adam