Problem of running L4Linux
Adam Chang
windbread at gmail.com
Mon Jan 5 05:21:38 CET 2009
Dear all:
Thanks for Adam's advice. but there still has some problem.
the following is my new menu.lst
=====Begin of menu.lst=========
default=0
timeout=0
splashimage=/boot/grub/splash.xpm.gz
hiddenmenu
title L4Linux-2.6
kernel /common/bootstrap
modaddr 0x02000000
module /common/fiasco -nokdb -serial_esc
module /common/sigma0
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
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
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?
Thanks!!
Best Regards.
Adam Chang
On Wed, Dec 31, 2008 at 7:23 PM, Adam Lackorzynski
<adam at os.inf.tu-dresden.de> wrote:
>
> On Wed Dec 31, 2008 at 02:02:32 +0800, Adam Chang wrote:
>>
>> ==============
>> l4lx | memory_setup done
>> l4lx | l4env_rd_path: drops.rd
>> l4lx | Loading: drops.rd
>> l4lx | INITRD: Size of RAMdisk is 16384KiB
>> l4lx | RAMdisk from 04c0000 to 05c00000 [16384KiB]
>> l4lx | l4lx_thread_create: Created thread 0d.05 (timer.i0)
>> l4lx | Jumping over 4x 'hit' at 0x70970f
>> l4lx | idler0: utcb=0xbff00400 0d.04
>> l4lx | l4lx_thread_create: Created thread 0d.06 (idler0)
>> l4lx | Starting L4FB via DOpE
>> l4lx | DOpE is not registerd at names!
>> l4lx | DOpE no available!
>> l4lx | Starting L4FB via CON
>> l4lx | CON not availble!
>> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14
>> l4lx | l4lx_thread_create: Created thread 0d.07(IRQ14)
>> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15
>> l4lx | l4lx_thread_create: Created thread 0d.08(IRQ15)
>> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 16
>> l4lx | l4lx_thread_create: Created thread 0d.09(IRQ16)
>> ==============
>> And that it just stop here and didn't run any more.
>> I saw the message knowing that L4FB needs CON and DOpE
>> So I modified menu.lst and l4linux26.cfg for using l4con and DOpE
>>
>> =====Begin of menu.lst=========
>> default=0
>> timeout=0
>> splashimage=/boot/grub/splash.xpm.gz
>> hiddenmenu
>> title L4Linux-2.6
>> kernel /common/bootstrap
>> modaddr 0x02000000
>> module /common/fiasco -nokdb -serial_esc
>> module /common/sigma0
>> 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
>> 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/con
>> 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 new loader script for L4linux
>>
>> =====Begin of l4linux26.cfg=========
>> #l4linux cfg
>>
>> verbose 0
>> sleep 1
>> task "vmlinuz" "mem=64M video=l4fb:refreshsleep:200 l4fb.nograb=1
>> 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=========
>>
>> When I boot VMware, I just saw full black screen after loading modules.
>> And it didn't show anything, just full black screen.
>> So the above is my current circumstanceļ¼can someone give me some
>> advice how to solve this problem?
>
> Just need l4con or Dope, not both (xor!). So the screen goes black
> because GRUB is doing the vbeset and thus switching the video mode,
> which initially is black. And probably because dope and l4con step on
> each others feet while trying to get access to the video memory it will
> stop on boot-up. Just use one, either dope or con. BTW, it is good to
> have a (virtual) serial console to see the debug messages when using
> graphics because otherwise you don't really see anything if things go
> wrong.
>
>
>
> Adam
> --
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
>
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
--
Adam Hung-Hsiang Chang
windbread at gmail.com
+886-987-335398
Wireless Networking and Embedded Systems Lab
Graduate Institute of Networking and Multimedia
National Taiwan University
More information about the l4-hackers
mailing list