On Mon Jan 05, 2009 at 12:21:38 +0800, Adam Chang wrote:
module /common/roottask -symbols -lines task modname "loader" boot_priority 0xA0 allow_cli task modname "bmodfs" attached 7 modules module /common/Lines module /common/Symbols
Those need to be in the same order as the options as the on the roottask command line, i.e. Lines and Symbols need to be the other way around.
module /common/names module /common/log module /common/dm_phys --isa=0x00800000 module /common/simple_ts -t 300 module /common/rtc module /common/l4io module /common/l4dope module /common/bmodfs module /common/cfg/l4linux26.cfg module /common/libloader.s.so module /common/libld-l4.s.so module /common/vmlinuz module /common/drops.rd module /common/proxygon module /common/run module /common/loader --fprov=BMODFS proxygon run l4linux26.cfg vbeset 0x117 =====End of menu.lst=========
And the following is the loader script for L4linux
=====Begin of l4linux26.cfg========= #l4linux cfg
verbose 0 sleep 1 task "vmlinuz" "mem=64M video=l4fb:refreshsleep:200 load_ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=drops.rd" allow_cli priority 0xA0 all_sects_writable allow_vga
=====End of l4linux26.cfg=========
It still black screen forever for using l4con. And for using Dope I can see the graphic environment and the console titled "proxygon", but when I clicked the windows and press L key, then the Vmware machine rebooted. sometimes the cursor can't be moved through my
Ok, strange.
mouse. sometimes I saw only the background without console.It confused me. So the above is my current circumstance,can someone give me some advice how to solve this problem?
You need to get the serial line out of the Vmware to see what's going on. Long back when I tried this this worked by switching the guest first serial to some named socket on the host. E.g. minicom can attach to this when using unix#/file/to/socket as a device name. Maybe qemu is a better choice here, since it's easy with 'qemu -serial stdio'.
Adam