Hello, I am trying to build the complete DROPS including fiasco, DoPE and L4Linux.
As a starting point I had the demo CD from the OS research day 2004. At first I used the binaries from the cd (including the config files) and ran them on top of vmware. Modules were loaded successfully via tftp and worked (well, when accessing the cd, L4Linux had the prob that there was no cd anymore, but at least the kernel worked well).
After that I compiled the cvs tree and replaced the binaries by the own-compiled ones. It seems that fiasco and DOpE work fine since it renders nice windows and so on. But when it comes to starting L4Linux it crashes - well, in fact it just "hangs" and does nothing anymore. The weird thing is that the bootmessages, the ones printed in the "\ m /" window do not end at a reproducable point. Sometimes it comes up to "======> L4Linux 2.6 starting <========", sometimes only up to "loader : vmlinuz26,#d: Continue at l4env_init (00014264, libloader.s.so)", sometimes it hangs in the middle of a message.
These are my config-files:
menu.lst: --------- title L4Linux 2.6 from this CD [DOpE] kernel (nd)/drops/rmgr -sigma0 task modname "bmodfs" module module module module module module module task modname "l4dope" boot_priority 0xA8 modaddr 0x02000000 module (nd)/drops/fiasco -nokdb -nowait -noserial module (nd)/drops/sigma0 module (nd)/drops/names module (nd)/drops/dmon module (nd)/drops/dm_phys module (nd)/drops/simple_ts -t 380 module (nd)/drops/rtc module (nd)/drops/l4io --noirq module (nd)/drops/bmodfs module (nd)/drops/libloader.s.so module (nd)/drops/run.bmodfs.cfg module (nd)/drops/run module (nd)/drops/vmlinuz26 module (nd)/drops/vscrtest module (nd)/drops/cfg/l4linux26.cd.k_us.cfg module (nd)/drops/drops-rd.rd module (nd)/drops/l4exec module (nd)/drops/l4dope --l4io module (nd)/drops/proxygon module (nd)/drops/backdrop -------------------------
drops/cfg/l4linux26.cd.k_us.cfg: -------------------------------- sleep 1 task "vmlinuz26" "mem=64M noreplacement root=1:0 load_ramdisk=1 ramdisk_size=4096 l4env_rd=drops-rd.rd lang=us" allow_cli priority 0xA0 --------------------------------
Does anybody know what kernel options I could try to fix this? Oder does anybody have any idea? Am I doing something wrong? I used gcc 2.95.3 to compile.
Many thanks and greetings
Björn Fischer
Hi,
On Tue Mar 29, 2005 at 14:22:19 +0200, Björn Fischer wrote:
As a starting point I had the demo CD from the OS research day 2004. At first I used the binaries from the cd (including the config files) and ran them on top of vmware. Modules were loaded successfully via tftp and worked (well, when accessing the cd, L4Linux had the prob that there was no cd anymore, but at least the kernel worked well).
After that I compiled the cvs tree and replaced the binaries by the own-compiled ones. It seems that fiasco and DOpE work fine since it renders nice windows and so on. But when it comes to starting L4Linux it crashes - well, in fact it just "hangs" and does nothing anymore. The weird thing is that the bootmessages, the ones printed in the "\ m /" window do not end at a reproducable point. Sometimes it comes up to "======> L4Linux 2.6 starting <========", sometimes only up to "loader : vmlinuz26,#d: Continue at l4env_init (00014264, libloader.s.so)", sometimes it hangs in the middle of a message.
I guess that it jumps into the kernel debugger for some reason. The graphical output gets as far as the redraws get.
For such situations it is useful to have a serial cable to see the debugging output over the serial, esp. when the graphics mode is on (remove the noserial option then).
For debugging you can also leave out the graphical mode so that you stay in text mode and see the output on the screen. A simpler setup like the following should suffice for this:
title simple kernel (nd)/drops/rmgr -sigma0 task modname "bmodfs" module module module module modaddr 0x02000000 module (nd)/drops/fiasco -nokdb -nowait -noserial module (nd)/drops/sigma0 module (nd)/drops/names module (nd)/drops/log module (nd)/drops/dm_phys module (nd)/drops/simple_ts -t 380 module (nd)/drops/rtc module (nd)/drops/l4io --noirq module (nd)/drops/bmodfs module (nd)/drops/libloader.s.so module (nd)/drops/vmlinuz26 module (nd)/drops/cfg/l4linux26.cd.k_us.cfg module (nd)/drops/drops-rd.rd module (nd)/drops/l4exec module (nd)/drops/loader --fprov=BMODFS l4linux26.cd.k_us.cfg
You will not see any Linux user output, depending on your kernel configuration.
I changed some things between last December and now, so mixing binaries from then and now might not work and maybe the cause of the trouble.
Adam
Björn,
Adam was right to suggest the serial line option, however with vmware this you won't need a "real" cable. Get the modified minicom-version that allows to listen on unix-sockets as well, and hence to communicate with the virtual serial line of vmware. The unixsocket-enabled minicom should be available from Adams OS-debian server. Adam, maybe you can give him the correct pointer.
Regards, Jork
On Thu Mar 31, 2005 at 23:22:40 +0200, Jork Löser wrote:
Adam was right to suggest the serial line option, however with vmware this you won't need a "real" cable. Get the modified minicom-version that allows to listen on unix-sockets as well, and hence to communicate with the virtual serial line of vmware. The unixsocket-enabled minicom should be available from Adams OS-debian server. Adam, maybe you can give him the correct pointer.
This feature has been in the upstream version for some time now, so getting plain version 2.1 is just fine.
Adam
l4-hackers@os.inf.tu-dresden.de