- l4-hackers - example.com Site

No mouse and keyboard with the L4Linux/DOpE
by chenggh 16 Nov '06

16 Nov '06

Hi: Now I boot the l4dope but I can't use the keyboard and mouse. In the l4linux console I could see the cursor flases and the mouse stayes in the at (0,0). But i can't input anyth character and I can't move the mouse. I have checked the former mailists. And adam said we couldn't use the usb mouse and keyboard. Now in my system I use the ps/2 mouse and ps/2 keyboard. And when I push the NumLock key and the light couldn't be on, it is off alyways. So i think the keyboard is dead and have nothing reponsing. In the L4/Fiasco booting process there are some warnings like this: bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14716kB) bmodfs | module "(hd0,1)/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "(hd0,1)/boot/L4Linux/libloader.s.so" (635kB) bmodfs | module "(hd0,1)/boot/L4Linux/libld-l4.s.so" (473kB) bmodfs | module "(hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg" (84 bmodfs : 4kB) l 4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. 4dope | L4INPUT: !!! W A R N I N G !!! loader | vmlinuz26: Starting application using libld-l4.s.so My grub configuration is as following: title L4Linux26/Fiasco+dope kernel (hd0,1)/boot/L4Linux/bootstrap modaddr 0x03000000 module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/L4Linux/sigma0 module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names -events module (hd0,1)/boot/L4Linux/log module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events module (hd0,1)/boot/L4Linux/rtc --events module (hd0,1)/boot/L4Linux/l4io -noirq --events module (hd0,1)/boot/L4Linux/l4exec --events module (hd0,1)/boot/L4Linux/l4dope -l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 506070 Thank you. cheng

3 2

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 16 Nov '06

16 Nov '06

Hello chenggh, On Thu, Nov 16, 2006 at 07:58:52AM +0800, chenggh wrote: > If I setup without L4Linux. I could see a graphical interface. But the mouse > is always at (0,0) and i can't use the mouse anyway. [...] > The minicom log is like this: [...] > l4lx | ======> L4Linux 2.6 starting... <======== No offense meant, but are you kidding? Please, send the log _without_ starting L4Linux. Thanks -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 15 Nov '06

15 Nov '06

On Thursday 16 November 2006 07:05, Adam Lackorzynski wrote: > On Wed Nov 15, 2006 at 20:55:00 +0800, chenggh wrote: > > On Wednesday 15 November 2006 20:18, chenggh wrote: > > > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > > > Hi, > > > > Here is my L4Linux booting log, Please look at it to help me. thank you. > > First, please try to do what Christian suggested: Try your setup > _without_ L4Linux, this helps to identify if L4Linux is the culprit or > not. If I setup without L4Linux. I could see a graphical interface. But the mouse is always at (0,0) and i can't use the mouse anyway. > Second thing, if you do not see any more output from Linux in the > log (via serial or in the terminal you run Fiasco-UX in) and your > output device (e.g. framebuffer) does not come up for some reason, like > in your current example, enable CONFIG_L4_SERIAL and > CONFIG_L4_SERIAL_CONSOLE. Then add console=ttyLv0 to your kernel command > line. With this Linux should print the boot up in minicom or xterm > (Fiasco-UX). The minicom log is like this: l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4d, size=800 l4dope | SharedMem(get_adr): address = 5000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4e, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4f, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=50, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=51, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=53, size=800 l4dope | SharedMem(get_adr): address = 15000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=54, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #3 Wed Nov 15 12:19:04 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 0073e000 [3320 KiB]. l4lx | Areas: Text: 00400000 - 0064e000 [2360kB] (a bit longer) l4lx | Data: 0064e000 - 0069ad8c [307kB] l4lx | Initdata: 0069e000 - 006d0000 [200kB] l4lx | BSS: 006d0000 - 0073cb30 [434kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 0069c000 size = 663552 l4lx | sec-w-init: virt: 0x0069c000 to 0x0073dfff [648 KiB] l4lx | sec-w-init: Number of physical regions: 1, 663552 Bytes l4lx | sec-w-init: 1: Phys: 0x0145b000 to 0x014fd000, Size: 663552 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x1b800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1598 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) It is end. cheng

1 0

Timing problem on mem_fpage_unmap() in the fiasco kernel
by WanKeun Jo 15 Nov '06

15 Nov '06

Hi, I've been working on porting DROPS to Bulverde board - PXA270. My senior already made DROPS work on OMAP board before. He worked with L4Linux-2.6.16, but I don't know exact version of fiasco kernel and L4Env packages because they are not specified. I got all the sources from my senior - not the latest things.. - and have tried them work on Bulverde board. My status is that I have an unsolvable error in fiasco kernel. On L4Linux-2.6.16's booting process, one step is "Freeing INITRD", and system halted on that point. By tracing codes, I got to know while the mem_fpage_unmap() function in l4/kernel/fiasco/src/kern/map_util.cpp executed, the system halted. And I put "delay codes" into that function's for() {}, and then the system continued to execute and boot succeed. I found this fact after I added printf() into that code in order to debug. On that point - "Freeing INITRD", whether the boot process goes next step or not depends on how much delay time is put on that code, mem_fpage_unmap(). If I make the delay time a little bit longer, then the system goes to next step at that point, but stops somewhere else after that. If I make the delay time too short, the system never go to next step. And the mem_fpage_unmap() is called a lot while the system works, but only in the "Freeing INITRD" part, the problem appears. I think this is a serious timing error, but I can't know what the problem is. I already tried all the combinations of kernel and L4Linux options before. when I tried to install the latest kernel and l4linux-2.6.18, the halting problem didn't appear. And I found that the latest kernel's mem_fpage_unmap() functions implementation has a lot of changes compared to the kernel I work with. Could you help me solve this problem?? Please don't say to me "use the latest one".. My senior already succeed on OMAP board with the old versions. Thank you.

3 2

Re: No mouse and keyboard with the L4Linux/DOpE
by Adam Lackorzynski 15 Nov '06

15 Nov '06

On Wed Nov 15, 2006 at 20:55:00 +0800, chenggh wrote: > On Wednesday 15 November 2006 20:18, chenggh wrote: > > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > > Hi, > > > > Here is my L4Linux booting log, Please look at it to help me. thank you. First, please try to do what Christian suggested: Try your setup _without_ L4Linux, this helps to identify if L4Linux is the culprit or not. Second thing, if you do not see any more output from Linux in the log (via serial or in the terminal you run Fiasco-UX in) and your output device (e.g. framebuffer) does not come up for some reason, like in your current example, enable CONFIG_L4_SERIAL and CONFIG_L4_SERIAL_CONSOLE. Then add console=ttyLv0 to your kernel command line. With this Linux should print the boot up in minicom or xterm (Fiasco-UX). Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 15 Nov '06

15 Nov '06

On Wednesday 15 November 2006 20:18, chenggh wrote: > On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > > Hi, > > Here is my L4Linux booting log, Please look at it to help me. thank you. l4dope | DOpE(init): using L4 IO server l4dope | (hd0,1)/boot/L4Linux/l4dope: unrecognized option `--menubar' l4dope | DOpE(init): unknown option! l4dope | DOpE(init): using transparency loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec1000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec101000-ec1017ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec102000-ec1020ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d400-d47f : VIA Technologies, Inc. IEEE 1394 Host Controller io | d800-d81f : VIA Technologies, Inc. USB io | dc00-dc1f : VIA Technologies, Inc. USB (#2) io | e000-e01f : VIA Technologies, Inc. USB (#3) io | e400-e40f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e800-e8ff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4d, size=800 l4dope | SharedMem(get_adr): address = 5000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4e, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=4f, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=50, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=51, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=53, size=800 l4dope | SharedMem(get_adr): address = 15000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=54, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | dope: addr=e0000000 size=31680KiB io | Remapping I/O memory e0000000-e1ef0000 cached io | Setting MTRR 4 to e0000000-e2000000 type WC l4dope | Mapped video memory at e0000000 to 04000000+000000 [31680kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=32440320(0x1ef0000) offset=0(0x0) l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.17-l4 (root@fiasco-desktop) (gcc version 3.4.6 (Ubu l4lx : ntu 3.4.6-1ubuntu2)) #3 Wed Nov 15 12:19:04 CST 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx : t=/dev/hda2 l4lx | Image: 00400000 - 0073e000 [3320 KiB]. l4lx | Areas: Text: 00400000 - 0064e000 [2360kB] (a bit longer) l4lx | Data: 0064e000 - 0069ad8c [307kB] l4lx | Initdata: 0069e000 - 006d0000 [200kB] l4lx | BSS: 006d0000 - 0073cb30 [434kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 0069c000 size = 663552 l4lx | sec-w-init: virt: 0x0069c000 to 0x0073dfff [648 KiB] l4lx | sec-w-init: Number of physical regions: 1, 663552 Bytes l4lx | sec-w-init: 1: Phys: 0x0145b000 to 0x014fd000, Size: 663552 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x1b800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1598 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=75, size=96000 l4dope | SharedMem(get_adr): address = 400000 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 10.0a (IRQ17) l4lx | l4lx_thread_create: Created thread 10.0b (IRQ16) l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_thread_create: Created thread 10.0d (IRQ14) l4lx | l4lx_thread_create: Created thread 10.0e (IRQ13) l4lx | l4lx_thread_create: Created thread 10.0f (IRQ11) l4lx | l4lx_thread_create: Created thread 10.10 (IRQ10) l4lx | l4lx_thread_create: Created thread 10.11 (IRQ9) l4lx | l4lx_thread_create: Created thread 10.12 (IRQ8) l4lx | l4lx_thread_create: Created thread 10.13 (IRQ7) l4lx | l4lx_thread_create: Created thread 10.14 (IRQ6) l4lx | l4lx_thread_create: Created thread 10.15 (IRQ5) l4lx | l4lx_thread_create: Created thread 10.16 (IRQ3) It is end. cheng

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 15 Nov '06

15 Nov '06

Hello, On Wed, Nov 15, 2006 at 08:18:42PM +0800, chenggh wrote: > Now It has the same prolems with unavailabe mouse and keyboard. the menu.lst > is as following: > > title L4Linux26/Fiasco+dope > kernel (hd0,1)/boot/L4Linux/bootstrap > modaddr 0x06000000 > module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed > 115200 -comport 1 > module (hd0,1)/boot/L4Linux/sigma0 > module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 > modules > module (hd0,1)/boot/L4Linux/events > module (hd0,1)/boot/L4Linux/names --events > module (hd0,1)/boot/L4Linux/log > module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events > module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events > module (hd0,1)/boot/L4Linux/rtc --events > module (hd0,1)/boot/L4Linux/l4io --noirq --events > module (hd0,1)/boot/L4Linux/l4exec --events > module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency > module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg > module (hd0,1)/boot/L4Linux/bmodfs > module (hd0,1)/boot/L4Linux/vmlinuz26 > module (hd0,1)/boot/L4Linux/linux26.cfg > module (hd0,1)/boot/L4Linux/libloader.s.so > module (hd0,1)/boot/L4Linux/libld-l4.s.so > module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg > vbeset 0x117 506070 > > And the linux26.cfg is like this: > verbose 0 > task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb root=/dev/hda2" > all_sects_writable For me it looks like you're still running L4Linux via loader. Anyway: * Be sure to limit your scenario to just l4env and dope (Remove all lines after .../l4dope.) * Try to run l4io w/o "--noirq" as this mode is seldom tested and will not work in the future. If the problem persists, please, send a complete log of your boot process. Ciao -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by chenggh 15 Nov '06

15 Nov '06

On Wednesday 15 November 2006 18:20, Christian Helmuth wrote: > Hi, > > try to boot your configuration w/o L4Linux. Do mouse and keyboard work now > in dope? > > Cheers Now It has the same prolems with unavailabe mouse and keyboard. the menu.lst is as following: title L4Linux26/Fiasco+dope kernel (hd0,1)/boot/L4Linux/bootstrap modaddr 0x06000000 module (hd0,1)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/L4Linux/sigma0 module (hd0,1)/boot/L4Linux/roottask task modname "bmodfs" attached 5 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names --events module (hd0,1)/boot/L4Linux/log module (hd0,1)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,1)/boot/L4Linux/simple_ts -t 300 --events module (hd0,1)/boot/L4Linux/rtc --events module (hd0,1)/boot/L4Linux/l4io --noirq --events module (hd0,1)/boot/L4Linux/l4exec --events module (hd0,1)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,1)/boot/L4Linux/loader --fprov BMODFS linux26.cfg module (hd0,1)/boot/L4Linux/bmodfs module (hd0,1)/boot/L4Linux/vmlinuz26 module (hd0,1)/boot/L4Linux/linux26.cfg module (hd0,1)/boot/L4Linux/libloader.s.so module (hd0,1)/boot/L4Linux/libld-l4.s.so module (hd0,1)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 506070 And the linux26.cfg is like this: verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb root=/dev/hda2" all_sects_writable Thank you. cheng

1 0

Re: No mouse and keyboard with the L4Linux/DOpE
by Christian Helmuth 15 Nov '06

15 Nov '06

Hi, try to boot your configuration w/o L4Linux. Do mouse and keyboard work now in dope? Cheers -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

L4Linux and virtualization
by Robert Gubler 14 Nov '06

14 Nov '06

Hello, I'd like to run two L4Linux 2.4 based kernels and one L4Linux 2.6 based kernel. Is this something that can be achieved relatively easily or would all running kernels need to be 2.6/2.4? How do the 'guest' kernels communicate to each other in an L4 environment? In User Mode Linux (UML) and Xen on the guest kernels there is built-in support for pseudo Ethernet devices; these devices are then bridged together on the host kernel. I understand the architecture is considerably different in L4, but is there some similar mechanism already in place that allows Ethernet/IP communication between the running Linux kernels? Thanks in advance, Rob

3 2