Problem beim starten von l4linux auf fiasco

Volkmar Uhlig volkmar at
Sat Mar 15 20:45:33 CET 2003

If you have overlapping modules you have no chance whatsoever. So you better fix that ;)

I'm not too familiar with the FIASCO kernel boot process, but usually the problem is GRUB, not the kernel. GRUB loads the modules after all loaded elf sections of the initial kernel (which is RMGR in your case). RMGR then tries to load the modules as ELF files and figures out that some elf sections collide with the module locations and barks. This was the reason to add the modaddr feature to GRUB allowing to relocate the load address in main mem. Simply try sticking a modaddr=0x<whatevermemoryyouhave-16MB> after the kernel=rmgr line. Note, that this is only available in the Dresden version of GRUB, not the GNU GRUB (at least AFAIK). So bake yourself a boot floppy from

The Linux error message is due to the kernel-debugger console in L4Linux. At the end Linux tries to open the console but since it does not support all required features Lx simply falls back to VGA. So this error can be ignored even if it sounds scary.

- Volkmar

PS: Please post in English -- most subscribers of this list don't understand a word of German (except maybe "Bier" ;)

> -----Original Message-----
> From: Rudolf Weber [mailto:rfweber at] 
> Sent: Saturday, March 15, 2003 8:21 PM
> To: l4-hackers at
> Subject: Problem beim starten von l4linux auf fiasco
> Hallo,
> Vorbemerkung:
>   Das starten von glinux bringt einen Fehler überlappender Module,
>   Der Fiasco beginnt da, wo glinux liegt,
>   folgende Änderung habe ich gemacht:
> --- ./l4/kernel/fiasco/src/Makerules.BOOT.vorrudi       2003-02-25
> 11:34:43.000000000 +0100
> +++ ./l4/kernel/fiasco/src/Makerules.BOOT       2003-03-15
> 16:13:58.000000000 +0100
> @@ -7,7 +7,7 @@
>  $(BOOT):       kernel.o $(OBJ_BOOT) $(LIBKERN) $(MINILIBC) 
>                 @echo "  ... Building boot image"
>                 $(LINK_MESSAGE)
> -               $(VERBOSE)$(LD) -Ttext 0x300000 -o $@ $^ $(LIBGCC) \
> +               $(VERBOSE)$(LD) -Ttext 0x400000 -o $@ $^ $(LIBGCC) \
>                 -defsym checksum_ro=0x`cut -f1 -d' ' $(CHECKSUM)` \
>                 -defsym checksum_rw=0x`cut -f2 -d' ' $(CHECKSUM)`
>                 chmod 755 $@
> Das starten von grub aus:
> title L4 fiasco x586 l4v2 L4Linux
>         kernel /l4-20030315-x586/rmgr -sigma0
>         module /l4-20030315-x586/fiasco.400000
>         module /l4-20030315-x586/sigma0
>         module /l4-20030315-x586/glinux root=/dev/hda2
> Der glinux startet dann auch, und ganz zum Schluß :
> Warning: unable to open an initial console
> Root: ptc is NULL for 00080030 (virt 00080030)
>       and pdir 00400000 at eip: 0050c11b
> Die Warnung kommt aus dem l4linux als ein open("/dev/console/") schief
> geht. (offenbar ging wohl das mounten von / nicht :-()
> Was will mir der rest sagen ? pdir sieht ganz so aus wie die
> Start-Adresse von Fiasco ?
> Was habe ich nur falsch gemacht ?
> Gruß
> 	Rudolf Weber 

More information about the l4-hackers mailing list