About build of L4Linux

Lin bugeaterk at gmail.com
Wed Jul 11 01:05:18 CEST 2007


> > But the "Section mismatch" errors in "MODPOST vmlinux" remain yet.
>
> Most of those are from Linux, don't take them too serious.

Ok, I see.
I wrote "error" instead of "WARNING", but it was a mistake. Sorry...



> > After make, the vmlinux(about 101.7MB) and the vmlinuz26(about 32.8M)
> > are created.
>
> Over 100MB is too much. Can you please post your .config from the
> L4Linux build directory?!

My ".config" file may be too strange for you because I am a beginner
in configuring or building kernels.
I probably added many vain components to the kenel unconsciously.



> > And I'm trying to boot the made L4Linux and Fiasco with GRUB.
> > My GRUB doesn't have "modaddr" command, so I want to use
>
> I recommend using the -modaddr switch to bootstrap which does the same
> as the modaddr GRUB command.

Thanks, but I'd already gained the GRUB which has the "modaddr"
command by using the patch (grub-0.97-os.1.diff.gz) you made.
And I tried to boot L4Linux/Fiasco(+l4dope) with it, however it failed.
The kernel configuration is equal to the posted file.
The "menu.lst" in the "/boot/grub" directory and the loader
configuration file "linux26.cfg" are as follows.

[/boot/grub/menu.lst] ------------------------------
title L4Linux2.6/Fiasco
        root (hd0,0)
        kernel /boot/L4Linux/bootstrap
        modaddr 0x06000000
        module /boot/L4Linux/fiasco -nowait -nokdbi -serial_esc
-comspeed 115200 -comport 1
        module /boot/L4Linux/sigma0
        module /boot/L4Linux/roottask task modname "bmodfs" attached 4 modules
        module /boot/L4Linux/events
        module /boot/L4Linux/names --events
        module /boot/L4Linux/log --events
        module /boot/L4Linux/dm_phys --events
        module /boot/L4Linux/simple_ts -t 300 --events
        module /boot/L4Linux/rtc --events
        module /boot/L4Linux/l4io --noirq --events
        module /boot/L4Linux/bmodfs
                module /boot/L4Linux/vmlinuz26
                module /boot/L4Linux/libloader.s.so
                module /boot/L4Linux/linux26.cfg
                module /boot/L4Linux/libld-l4.s.so
        module /boot/L4Linux/l4dope --l4io
        module /boot/L4Linux/loader --fprov=BMODFS linux26.cfg
        vbeset 0x117
-----------------------------------------------------

[linux26.cfg] ---------------------------------------
verbose 0
task "vmlinuz26" "mem=256M video=l4fb root=/dev/hda1"
all_sects_writable
allow_vga
-----------------------------------------------------

After GRUB loads modules, a black mouse cursor and a "Linux console"
window are displayed (the window often aren't).
But I cannot use my keyboard and mouse (the cusor won't move and keys
produce nothing).
Besides, the console message stops on the way (stop points are
different every time like following).

------------------------------------------------------------------
...
l4fb: DOpE framebuffer at 0x12005000, size 600k
l4fb: mode is 640x480x16, linelength=1280, pages=0
l4fb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 80x30 <--- [stop]
l4fb0: l4fb L4 frame buffer device (refresh: 100ms)
vga16fb: mapped to 0x000a0000
vga16fb: mapped to 0x000a0000
fb1: VGA16 VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
RocketPort device driver module, version 2.09, 12-June-2003
No rocketport ports found; unloading driver.
Cyclades driver 2.4                                    <--- [stop]
        built Jul 11 2007 05:10:13                     <--- [stop]
------------------------------------------------------------------

I cannot understand the cause of this behavior...
I'm reading the ML logs, but I don't solve it yet.
May I request your advice ?



Regards,
Lin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 73687 bytes
Desc: not available
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20070711/dad09f63/attachment.wsdl>


More information about the l4-hackers mailing list