Problem of running L4Linux
Alexander Valitov
valitov79 at mail.ru
Fri Feb 6 09:17:06 CET 2009
Hi Adam,
Adam Chang wrote:
>
> Dear all:
> Now I add the serial port to VMware machine and connected the serial
> port to output file
> The following is the serial output while booting L4Linux
> ======Beginning of Serial Output=====
> Welcome to Fiasco(ia32)!
> DD-L4(v2)/ia32 microkernel (C) 1998-2008 TU Dresden
> Rev: r422 compiled with gcc 4.3.2 for Intel Pentium Pro []
>
> ... ... ...
>
> run | contxt_init(): 640x480, cols:80, lines:40, sb_lines:1040
> loader | vmlinuz: Starting application using libld-l4.s.so
> loader | vmlinuz,#10: Loading binary
> loader | vmlinuz,#10: Loading ldso
> loader | vmlinuz,#10: Starting libld-l4.s.so at 000138e0 via 0000cc24
>
> DOUBLE FAULT!
>
>
I'm not L4 hacker, but recently I've built and ran L4Linux on raw hardware
(586) with dope.
When I saw your message I tried to run the same binaries on VMWare and It
works!
Try to use my GRUB config (don't forget to fix the paths) and L4linux config
file. They are given below.
Here is some of my info:
VMware version: 6.5
Host OS: other 2.6.x Linux
GCC version: 4.1.2
L4Env config: default
build command: make oldconfig O=/path-to-buildu-dir && make
O=/path-to-buildu-dir
Fiasco config: default + 'Handle and preserve segments' option was enabled
CPU type: Intel Pentium / AMD k5
build command:
cd kernel/fiasco && make BUILDDIR=/path-to-buildk-dir
cd /path-to-buildk-dir && make menuconfig
make
L4Linux config: x86-native_defconfig + L4 build directory was set to
'/path-to-buildu-dir'
build command:
cd l4linux-2.6 && make x86-native_defconfig && make menuconfig
make
GRUB: I used my 0.97 GRUB, the only thing that i did - I overwrote
/boot/stage2 file with the patched one
GRUB config:
title L4Linux-2.6
kernel /boot/L4Linux/bootstrap
modaddr 0x02000000
module /boot/L4Linux/main -nokdb -serial_esc -comspeed 115200 -comport 1
module /boot/L4Linux/sigma0
module /boot/L4Linux/roottask task modname "loader" allow_cli task modname
"bmodfs" attached 5 modules
module /boot/L4Linux/names
module /boot/L4Linux/log
module /boot/L4Linux/dm_phys --isa=0x00800000
module /boot/L4Linux/simple_ts -t 300
module /boot/L4Linux/rtc
module /boot/L4Linux/l4io
module /boot/L4Linux/l4dope
module /boot/L4Linux/bmodfs
module /boot/L4Linux/l4linux26.cfg
module /boot/L4Linux/libloader.s.so
module /boot/L4Linux/libld-l4.s.so
module /boot/L4Linux/vmlinuz
module /boot/L4Linux/drops.rd
module /boot/L4Linux/loader --fprov=BMODFS l4linux26.cfg
vbeset 0x117
l4 config:
task "vmlinuz" "mem=64M load_ramdisk=1 ramdisk_size=16384 root=/dev/ram
l4env_rd=drops.rd"
all_sects_writable
allow_vga
allow_cli
Hope it will help.
Best regards, Alexander Valitov
--
View this message in context: http://www.nabble.com/Problem-of-running-L4Linux-tp20961567p21868311.html
Sent from the L4 mailing list archive at Nabble.com.
More information about the l4-hackers
mailing list