- l4-hackers - example.com Site

Building Fiasco-UX
by Shakthi Kannan 11 Dec '06

11 Dec '06

Hi, I am trying to build Fiasco-UX as per the documentation: http://os.inf.tu-dresden.de/fiasco/ux/building.shtml on Ubuntu Dapper (Intel, x86). gcc is 4.0.3. g++ is 4.0.3. I have obtained the code from CVS. Did menuconfig: cd l4/kernel/fiasco make menuconfig Have enabled: * Target platform (choose UX) * Generate inline code I don't see the "Assembler IPC shortcut" option. Saved the config. On running: make I get the following errors: make[1]: Circular l4/kernel/fiasco/src/Modules.ux.o <- Modules.ux dependency dropped. make[1]: Circular .Modules.deps <- Modules.ux dependency dropped. make[1]: Circular l4/kernel/fiasco/src/rules.cml.o <- Modules.ux dependency dropped. make[1]: Circular l4/kernel/fiasco/src/rules.cml.o <- .Modules.deps dependency dropped. make[1]: Circular create-sources <- Modules.ux dependency dropped. make[1]: Circular create-sources <- globalconfig.out dependency dropped. make[1]: Circular create-sources <- .Modules.deps dependency dropped. l4/kernel/fiasco/src/Makefile.sub1:17: .Modules.deps: No such file or directory make[2]: *** No rule to make target `.Modules.deps'. Stop. make[1]: *** [create-sources] Error 2 make: *** [build] Error 2 Appreciate any help in building fiasco-ux. Thanks, SK -- Shakthi Kannan http://www.shakthimaan.com ____________________________________________________________________________________ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com

3 5

segment fault for fiasco-ux
by halo.duan 11 Dec '06

11 Dec '06

Hi all I am newbie for L4 and just downloaded the fiasco last week. as i compiled as ux and run fiasco hello stuff. loading of sigma0 and roottask and irq0 is ok. but nothing displayed. as i use strace attach the fiasco process, it shown full screen segment fault. only think i can do is "kill -9 PID". any sugestion? best regards

2 1

Re: l4-hackers Digest, Vol 44, Issue 4
by cb huang 09 Dec '06

09 Dec '06

> > Hi, > > On Mon Dec 04, 2006 at 22:33:48 +0800, cb huang wrote: > > These days I'm studying the fiasco especially the IPC mechanism, so I > > want to get the paper The Fiasco Kernel: System Architecture, but it > seems > > that the paper is not yet published.Who can tell me where I can get it. > > I think this will never be published. It's also quite old and the IPC > path has changed significantly since then so it's probably not very > useful either. Yes, I know it's quite old, whereas I don't know whether there is another more useful one. Thanks for your reply!

2 1

Where can I get the paper The Fiasco Kernel: System Architecture
by cb huang 06 Dec '06

06 Dec '06

Hi These days I'm studying the fiasco especially the IPC mechanism, so I want to get the paper The Fiasco Kernel: System Architecture, but it seems that the paper is not yet published.Who can tell me where I can get it. Thanks a lot! -- cbhuang

2 1

Re: L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 06 Dec '06

06 Dec '06

I added the UHCI HCD support to my config (thanks to lspci -v command ...), and now my keyboard is ok. Under DOpE, my mouse doesn't move from (0,0), but that's an old problem ... Pascal

1 0

L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 05 Dec '06

05 Dec '06

On a PC with keyboard/mouse on USB, I booted L4Linux 2.6.17, but I only had keyboard running. That was not a problem when using only l4con. Now, with L4Linux 2.6.18, neither keyboard and mouse are running ... Everything is ok on a PC with keyboard/mouse on PS/2.

2 1

vbemode option in l4dope?
by "Gábor Bérczi (Gabucino)" 05 Dec '06

05 Dec '06

Greetings. I'd like to ask if it's planned to implement l4con's --vbemode command line option in l4dope too? I couldn't get grub's vbeset option to work in QEMU (always ends up in black screen), but l4con-s vbemode option does work. -- Gábor Bérczi

3 9

Can't start L4Linux-2.6.18
by FERANDELLE Pascal 04 Dec '06

04 Dec '06

In august, I tested L4Linux on PC, and everything was working fine with L4Linux-2.6.17. Now, I get the snapshots of 20061116, and rebuild everything. The L4Linux kernel is now 2.6.18. The build is ok, but I can't start it under Fiasco. Here is the log : Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sat Nov 11 18:26:23 2006 compiled with gcc 3.4.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:4:9:0) Model: Pentium 4E (Prescott/Nocona) at 2793 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 16 KB L1 D Cache (8-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! ... ... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled! Of course, I have the exception_ipc feature enabled in Fiasco !!! If I rebuild L4Linux-2.6.17, with the L4Env from 20061116, and try to start it under Fiasco, there is no problem ...

2 3

L4Env for X.2 (L4Ka::Pistachio)?
by Christian, Martin, OPEE45 01 Dec '06

01 Dec '06

Hi! On "http://l4hq.org/projects/env/l4env/" I read about L4Env: "Support for X.2 (L4Ka::Pistachio) will follow shortly." Is someone working on it? How is the status? When could I expect a release? Will it be architecture/platform independent? Thanks, Martin.

2 1

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

24 Nov '06

Hi, I prevented the timing problem to occur by simply unset the l4linux-2.6 option "Show timing information on printks" before. When the option is set, then in the function 'vprintk()' of "l4linux-2.6/kernel/printk.c", the system get current jiffies and then converted it to the string and add it to log buffer. The system works well right before the following codes in the function. When I remove the following code, the system works well without adding timing information on log buffer. ------------------------------------------------ tlen = sprintf(tbuf, 590 "<%c>[%5lu.%06lu] ", 591 loglev_char, 592 (unsigned long)t, 593 nanosec_rem/1000); 594 595 for (tp = tbuf; tp < tbuf + tlen; tp++) 596 emit_log_char(*tp); 597 printed_len += tlen; ------------------------------------------------ However, when I add one of the above three statements - (1) tlen = sprintf(), (2) for(), (3) printed_len += tlen - then the timing error occur during the "Freeing INITRD". even one statement of them.. This is so strange to me and also to you. I'm just beginner in this kind of works, so there might something that I overlooked. Is there somebody who can give me an advice for this kind of ERRORs..?? Thank you.

2 1

fiasco compilation problems
by Hendrik Tews 24 Nov '06

24 Nov '06

I just failed in trying to build fiasco-ux: First I followed the fiasco building and using page (the hello module variant) using the public cvs: - The following dependencies are not mentioned: libncurses5-dev, autoconf, automake1.9, doxygen I don't understand autoconf: the configure scripts should be generated at the distributors site? When autoconf was missing, I got a message saying I need autoconf 2.50, it didn't say I need automake1.9. Here autoconf comes by default with 1.8. Further I don't understand doxygen: Wouldn't it be better to have a separate doc goal and the main make goal independent from doxygen? I appreciate the different config tools in l4 and fiasco as sign of big freedom in this world (and in Dresden in particular). ;-) However, it would make live easier for the casual l4 configurator (like me) if keybindings would agree and fiasco config had an exit button. - the fiasco-ux site says Enable at least the following configuration options: * Target platform (choose UX) * Assembler IPC shortcut * Generate inline code I could neither find IPC shortcut nor inline code. - Then I got the following message: Flex and Byacc. (If you don't have Byacc, but Bison, try setting "bison -y" in the L4 configuration menu under "Compilers and Tools". Other Yacc implementations might do it as well.) but neither the message nor the website says where to find the L4 config menu. Wouldn't it be possible to let the config automatically choose bison if byacc is not found? - the "-C l4" in in 2.a seems to prohibit relativ path for the builddir. Why not cd l4 before? - Point 3.a says "cd l4", but there is no l4 inside l4 - Somebody told me that the preferred way to download fiasco nowadays is to use one of the opentc snapshots. If thats true if would be nice to have a link to these snapshots. - Finally fiasco-ux and all the modules were compiled: tandem l4v2 38> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096d44 [sigma0-ux] Loading Module 0x00120000-0x002bd9f4 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Nov 23 10:27:00 2006 compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/current/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 Now I tried the latest opentc snapshot. I ingored the opentc build instructions and applied the fiasco build instructions to this tree. At some stage it was complaining about gcc-4.1.2 being the wrong compiler version. I changed the compilers to gcc-3.4/g++-3.4 in the l4 config. After that make skipped a lot of dirs, because the goals were done before already. Shouldn't it recompile everything after changing the compiler? So I did make clean then and rebuild. But still I saw a lot of messages with ``g++'' (which would be 4.1.2). That's unproblematic? The compilation stoped eventually with make[3]: Entering directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' cp building.tex drops-building.tex cp: cannot stat `building.tex': No such file or directory make[3]: *** [drops-building.tex] Error 1 make[3]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc/building-howto' make[1]: *** [building-howto] Error 2 make[1]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc' make: *** [doc] Error 2 There seems a problem with the builddir, because tandem l4 29> find . -name building.tex ./doc/building-howto/building.tex However, the build/bin/x86_586/l4v2 dir looked already very full, so I decided to ignore the build instructions and tried: tandem l4v2 7> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096ce4 [sigma0-ux] Loading Module 0x00120000-0x002bda14 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Unknown compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/opentc-snap/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 which is the same problem as before. Bye, Hendrik

2 1

TC and L4
by Burak OÐUZ 23 Nov '06

23 Nov '06

Hi, I have a few questions about L4 and trusted platforms. Are there any implementation of L4 which supports TSS 1.2 stack? Are there any interfaces supplied by L4 to access TPM? Are there any trusted platform application on L4? Thanks in advance.. Best regards.. -- burak() (ps: bf) METU CENG '06

4 3

Performance counter and NMI handling
by Jugwan Eom 22 Nov '06

22 Nov '06

Hi, I'm working to implement the Linux Oprofile functionality on L4/Fiasco environment. OProfile configures the performance counter to raise a NMI whenever the counter overflows. I modified the NMI handling codes in handle_slow_trap() to collect samples but I encountered an strange system behavior, REBOOTING without any information. If there is no user application activity, the system looks fine. Otherwise, the system reboots even if a very simple application like hello runs and the required time before reboot varies. I don't know what causes this behavior. IMHO, it seems a kind of triple fault. Is there any one give me an advice? Thanks in advance. -- Jugwan Eom

2 7

(no subject)
by Christian Roepke 21 Nov '06

21 Nov '06

Hello Ryan, try this one: http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.gz More information here: http://www.ertos.nicta.com.au/software/prebuilt/binaries.pml Kind regards, Hans > On Mon Nov 20, 2006 at 10:30:59 -0700, Ryan C. Spring wrote: >> I am cross-compiling the DROPS system for ARM and get compiler errors >> about "too many initializers" when it compiles the following statement >> from syscalls_impl.h (line 249) >> >> >> l4_threadid_t preempter = L4_INVALID_ID; >> l4_threadid_t pager = L4_INVALID_ID; >> >> >> When I initialize the unions without the defines, by hand as, it compiles. >> >> l4_threadid_t preempter; >> preempter.raw = (l4_umword_t)-1; >> l4_threadid_t pager; >> pager.raw = (l4_umword_t)-1; >> >> I'm using a TI-provided GCC 3.3.2 ARM crosscompiler. Is my >> cross-compiler to blame here? If so, could someone recommend a >> cross-compiler toolchain for ARM that doesn't error on this syntax? > > I'm using a self-made one, 3.4 based, which works. 4.1 is also known to > work. I can't remember we have tried 3.3 in the past. > > > > Adam -- Hans Christian Röpke Network Administration Applied Data Security Group Ruhr-Universität Bochum, IC 4/42 Universitätsstrasse 150 44780 Bochum, Germany http://www.prosec.rub.de

1 0

Re: Re: Timing problem on mem_fpage_unmap() in the fiasco kernel
by 조완근 21 Nov '06

21 Nov '06

Hi, I solved the timing problem. I just unset the "Show timing information on printks" in "kernel hacking". I found that when the system tries to free INITRD and vprintk() function tries to access any local buffer such as "char tbuf[50]", the system hangs on. I also found all the config files in "l4linux-2.6/arch/arm/configs" unset the option. The option can't work for arm architecture??? Do you know anything about that?? Thank you.

2 1

bug in cross-compiler?
by Ryan C. Spring 20 Nov '06

20 Nov '06

I am cross-compiling the DROPS system for ARM and get compiler errors about "too many initializers" when it compiles the following statement from syscalls_impl.h (line 249) l4_threadid_t preempter = L4_INVALID_ID; l4_threadid_t pager = L4_INVALID_ID; When I initialize the unions without the defines, by hand as, it compiles. l4_threadid_t preempter; preempter.raw = (l4_umword_t)-1; l4_threadid_t pager; pager.raw = (l4_umword_t)-1; I'm using a TI-provided GCC 3.3.2 ARM crosscompiler. Is my cross-compiler to blame here? If so, could someone recommend a cross-compiler toolchain for ARM that doesn't error on this syntax? Regards, Ryan -- Ryan C. Spring Doctoral Student University of Texas at El Paso +1 915-539-7311 www.spring-west.net/ryan

2 1

Re: Does the L4/Fiasco boot from CF card?
by chenggh 18 Nov '06

18 Nov '06

On Saturday 18 November 2006 18:42, Martin Pohlack wrote: > Hi Cheng, > > chenggh wrote: > > Hi, > > Today I want to boot the L4/Fiasco/L4Linux in the CF card. I copy all > > the necessary files into the CF card and install the Grub-0.97-os.1 in > > this CF card. My test machine is a VIA development board and in this > > board the CF card is connected with this machine by the IDE plugin. > > My grub menu.lst is as following: > > > > title L4Linux26/Fiasco+dope > > kernel (hd0,0)/boot/L4Linux/bootstrap > > modaddr 0x06000000 > > module (hd0,0)/boot/L4Linux/main -nowait -nokdb -serial_esc > > -comspeed 115200 -comport 1 > > module (hd0,0)/boot/L4Linux/sigma0 > > module (hd0,0)/boot/L4Linux/roottask task modname "bmodfs" > > attached 4 modules > > module (hd0,0)/boot/L4Linux/events > > module (hd0,0)/boot/L4Linux/names --events > > module (hd0,0)/boot/L4Linux/log --events > > module (hd0,0)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events > > module (hd0,0)/boot/L4Linux/simple_ts -t 300 --events > > module (hd0,0)/boot/L4Linux/rtc --events > > module (hd0,0)/boot/L4Linux/l4io --noirq --events > > module (hd0,0)/boot/L4Linux/l4exec --events > > module (hd0,0)/boot/L4Linux/l4dope --l4io --menubar > > --transparency module (hd0,0)/boot/L4Linux/loader --fprov=BMODFS > > linux26.cfg module (hd0,0)/boot/L4Linux/bmodfs > > module (hd0,0)/boot/L4Linux/vmlinuz26 > > module (hd0,0)/boot/L4Linux/linux26.cfg > > module (hd0,0)/boot/L4Linux/libloader.s.so > > module (hd0,0)/boot/L4Linux/libld-l4.s.so > > vbeset 0x117 506070 > > > > In the PC I have tested this configuration file and it is ok. Wh en I > > boot the VIA machine I choose the only one option to have this results. > > Booting L4Linux26/Fiasco+dope > > kernel (hd0,0)/boot/L4Linux/bootstrap > > > > Error 13 Invalid or unsupported executable format > > > > pass anykey to continue... > > Maybe the CF card reader is not fully ATA compatible? Maybe it emulates > SCSI? Even if it emulates an ATA drive, are you sure it is visible as > (hd0) to grub? Maybe you have to change the paths. I think the hd0 is visible to the grub. when I modify the grub option when booting I could use Tab-Completion in the grub command interface. But I change the path again. Thank you. cheng

1 0

Does the L4/Fiasco boot from CF card?
by chenggh 18 Nov '06

18 Nov '06

Hi, Today I want to boot the L4/Fiasco/L4Linux in the CF card. I copy all the necessary files into the CF card and install the Grub-0.97-os.1 in this CF card. My test machine is a VIA development board and in this board the CF card is connected with this machine by the IDE plugin. My grub menu.lst is as following: title L4Linux26/Fiasco+dope kernel (hd0,0)/boot/L4Linux/bootstrap modaddr 0x06000000 module (hd0,0)/boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,0)/boot/L4Linux/sigma0 module (hd0,0)/boot/L4Linux/roottask task modname "bmodfs" attached 4 modules module (hd0,0)/boot/L4Linux/events module (hd0,0)/boot/L4Linux/names --events module (hd0,0)/boot/L4Linux/log --events module (hd0,0)/boot/L4Linux/dm_phys --isa=0x00800000 -v --events module (hd0,0)/boot/L4Linux/simple_ts -t 300 --events module (hd0,0)/boot/L4Linux/rtc --events module (hd0,0)/boot/L4Linux/l4io --noirq --events module (hd0,0)/boot/L4Linux/l4exec --events module (hd0,0)/boot/L4Linux/l4dope --l4io --menubar --transparency module (hd0,0)/boot/L4Linux/loader --fprov=BMODFS linux26.cfg module (hd0,0)/boot/L4Linux/bmodfs module (hd0,0)/boot/L4Linux/vmlinuz26 module (hd0,0)/boot/L4Linux/linux26.cfg module (hd0,0)/boot/L4Linux/libloader.s.so module (hd0,0)/boot/L4Linux/libld-l4.s.so vbeset 0x117 506070 In the PC I have tested this configuration file and it is ok. Wh en I boot the VIA machine I choose the only one option to have this results. Booting L4Linux26/Fiasco+dope kernel (hd0,0)/boot/L4Linux/bootstrap Error 13 Invalid or unsupported executable format pass anykey to continue... I tried it many times and I think it could recognize the file and file system (now it is ext3 and I have ever tried ext2). But I don't know why is this prolem. Best wishes. Thank you. cheng

2 1

Re: What is mean of this log?
by chenggh 16 Nov '06

16 Nov '06

On Thursday 16 November 2006 21:19, Christian Stüble wrote: > Hi, > > Am Donnerstag, 16. November 2006 12:45 schrieb chenggh: > > Hi: > > When I boot the L4Linux with L4dope, There are some log statements like > > this: > > > > l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost > > synchronization, > > l4dope : throwing 3 bytes away. > > l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost > > synchronization, > > l4dope : throwing 3 bytes away. > > This looks like Linux is trying to access the input HW directly. I was able > to prevent this messages (and allow user I/O) by reconfiguring L4-Linux: 1) > Activate General/For small systems > 2) Then you can deactivate PC keyboard support etc. > 3) Also disable HW serial support > > > l4lx | Terminating L4Linux. > > l4lx | L4RM: [PF] read at 0x00000a28, ip 00000a29, src 10.02 > > l4lx | [10.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > This error happens here if I try to execute an older L4-Linux binary. Thank you very much. Now my l4dope and l4linux is ok. Nothing error could appear. The minicom log is like this: log | (hd0,1)/boot/L4Linux/log: unrecognized option `--events' log | Unrecognized option: - ? log | Usage: (hd0,1)/boot/L4Linux/log <options>. Option list: log | [ -h | --help ] - this help log | [ -v | --verbose ] - verbose mode log | [ -l | --local ] - flush to local console log | [ -L | --nolocal ] - do not flush to local console log | [ -s | --comport num ] - flush to specified serial interface (0) log | [ -e | --serial-esc ] - enter kdebug on esc on serial log | [ -b | --buffer num ] - buffered mode (0) log | [ --flushprio num ] - priority of flusher thread (0x20) log | [ -p | --prio num ] - priority of main thread (0x20) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:16.11.2006 Time:15:05:15 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00134000 7 12 MAPPED DMphys | 0x00134000-0x001cb000 -- -- DENIED DMphys | 0x001cb000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009e4000 7 12 MAPPED DMphys | 0x009e4000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bef000 -- -- DENIED DMphys | 0x00bef000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114b000 -- -- DENIED DMphys | 0x0114b000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01256000 -- -- DENIED DMphys | 0x01256000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x0134d000 -- -- DENIED DMphys | 0x0134d000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151b000 -- -- RESERVED DMphys | 0x0151b000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154d000 -- -- DENIED DMphys | 0x0154d000-0x01b00000 0 12 MAPPED DMphys | 0x01b00000-0x01b8c000 -- -- DENIED DMphys | 0x01b8c000-0x01c00000 0 12 MAPPED DMphys | 0x01c00000-0x06800000 0 22 MAPPED DMphys | 0x06800000-0x068b8000 0 12 MAPPED DMphys | 0x068b8000-0x077f9000 -- -- DENIED DMphys | 0x077f9000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b839000 0 12 MAPPED DMphys | 0x1b839000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 422900KB total, 422900KB free, 32KB reserved DMphys | 0x009e4000-0x00b80000 ( 1648KB, 2MB) DMphys | 0x00bef000-0x01080000 ( 4676KB, 5MB) DMphys | 0x0108a000-0x01100000 ( 472KB, 0MB) DMphys | 0x0114b000-0x01220000 ( 852KB, 1MB) DMphys | 0x01256000-0x01300000 ( 680KB, 1MB) DMphys | 0x0134d000-0x01400000 ( 716KB, 1MB) DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) DMphys | 0x0151b000-0x01540000 ( 148KB, 0MB) DMphys | 0x0154d000-0x01b00000 ( 5836KB, 6MB) DMphys | 0x01b8c000-0x068b8000 ( 79024KB, 77MB) DMphys | 0x077f9000-0x1b839000 (327936KB, 320MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00134000 ( 208KB, 0MB) DMphys | 0x001cb000-0x002d0000 ( 1044KB, 1MB) DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) DMphys | 0x0043a000-0x009e4000 ( 5800KB, 6MB) 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 io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-20000000 ( 512MB) type WB io | 1: 1e000000-20000000 ( 32MB) type UC io | 2: e8000000-ec000000 ( 64MB) type WC io | 3: e8000000-ec000000 ( 64MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14503kB) 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) 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 loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#10: Loading binary 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 !!! loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 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)) #5 Thu Nov 16 22:52:26 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 - 00731000 [3268 KiB]. l4lx | Areas: Text: 00400000 - 00642000 [2312kB] (a bit longer) l4lx | Data: 00642000 - 0068bd8c [295kB] l4lx | Initdata: 0068e000 - 006bf000 [196kB] l4lx | BSS: 006c0000 - 0072f6f0 [445kB] 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 = 00642000 size = 512000 l4lx | sec-w-init: virt: 0x00642000 to 0x006befff [500 KiB] l4lx | sec-w-init: Number of physical regions: 1, 512000 Bytes l4lx | sec-w-init: 1: Phys: 0x0142b000 to 0x014a8000, Size: 512000 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: 0x07800000 to 0x17800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) 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 "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 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=60, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=61, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=62, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=63, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=64, size=800 l4dope | SharedMem(get_adr): address = f000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=66, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=67, size=800 l4dope | SharedMem(get_adr): address = 17000 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 | 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) Best wishes. Thank you again. cheng

1 0

What is mean of this log?
by chenggh 16 Nov '06

16 Nov '06

Hi: When I boot the L4Linux with L4dope, There are some log statements like this: l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4lx | Terminating L4Linux. l4lx | L4RM: [PF] read at 0x00000a28, ip 00000a29, src 10.02 l4lx | [10.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault What is mean? Thank you. cheng

2 1

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

16 Nov '06

On Thursday 16 November 2006 18:17, Stefan Kalkowski wrote: > On Thursday 16 November 2006 11:03, chenggh wrote: > > Thanks for Helmuth very much. Now my l4dope and l4linux could support > > the keyboard and mouse:) I only modify the grub configuration and it is > > ok. > > what have you done ? Exactly, I also modifed the l4linux kernel configuration with disable mouse, keyboard and anything input. Former my grub menu.lst is like this: ... 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 Now it is like this: 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 vbeset 0x117 506070 Thanks for you very much. Basically I could use the L4Linux with graphical user interface. It is very surprising for me. It only use small disk space to boot a grahical application. Later I will publish the l4linux kickstart for the newbie like me to help them to install L4Linux without any mistakes. Best wishes. cheng

1 0

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

16 Nov '06

On Thursday 16 November 2006 16:55, Christian Helmuth wrote: > 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. Thanks for Helmuth very much. Now my l4dope and l4linux could support the keyboard and mouse:) I only modify the grub configuration and it is ok. Now I have the new problem. I can't move the mouse out of the l4linux console and it seems that the mouse movement has a range which is the border of l4linux console. And in the attachment there is my l4linux .config file. Please pay attention that my l4linux is 2.6.17 not the latest version 2.6.18. The grub configuration 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 4 modules module (hd0,1)/boot/L4Linux/events module (hd0,1)/boot/L4Linux/names --events module (hd0,1)/boot/L4Linux/log --events 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 vbeset 0x117 506070 The minicom log is as following: log | (hd0,1)/boot/L4Linux/log: unrecognized option `--events' log | Unrecognized option: - ? log | Usage: (hd0,1)/boot/L4Linux/log <options>. Option list: log | [ -h | --help ] - this help log | [ -v | --verbose ] - verbose mode log | [ -l | --local ] - flush to local console log | [ -L | --nolocal ] - do not flush to local console log | [ -s | --comport num ] - flush to specified serial interface (0) log | [ -e | --serial-esc ] - enter kdebug on esc on serial log | [ -b | --buffer num ] - buffered mode (0) log | [ --flushprio num ] - priority of flusher thread (0x20) log | [ -p | --prio num ] - priority of main thread (0x20) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:16.11.2006 Time:09:34:53 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00134000 7 12 MAPPED DMphys | 0x00134000-0x001cb000 -- -- DENIED DMphys | 0x001cb000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009e4000 7 12 MAPPED DMphys | 0x009e4000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bef000 -- -- DENIED DMphys | 0x00bef000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114b000 -- -- DENIED DMphys | 0x0114b000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01256000 -- -- DENIED DMphys | 0x01256000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x0134d000 -- -- DENIED DMphys | 0x0134d000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151b000 -- -- RESERVED DMphys | 0x0151b000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154d000 -- -- DENIED DMphys | 0x0154d000-0x01b00000 0 12 MAPPED DMphys | 0x01b00000-0x01b8c000 -- -- DENIED DMphys | 0x01b8c000-0x01c00000 0 12 MAPPED DMphys | 0x01c00000-0x06800000 0 22 MAPPED DMphys | 0x06800000-0x068b8000 0 12 MAPPED DMphys | 0x068b8000-0x077f2000 -- -- DENIED DMphys | 0x077f2000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b839000 0 12 MAPPED DMphys | 0x1b839000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 422928KB total, 422928KB free, 32KB reserved DMphys | 0x009e4000-0x00b80000 ( 1648KB, 2MB) DMphys | 0x00bef000-0x01080000 ( 4676KB, 5MB) DMphys | 0x0108a000-0x01100000 ( 472KB, 0MB) DMphys | 0x0114b000-0x01220000 ( 852KB, 1MB) DMphys | 0x01256000-0x01300000 ( 680KB, 1MB) DMphys | 0x0134d000-0x01400000 ( 716KB, 1MB) DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) DMphys | 0x0151b000-0x01540000 ( 148KB, 0MB) DMphys | 0x0154d000-0x01b00000 ( 5836KB, 6MB) DMphys | 0x01b8c000-0x068b8000 ( 79024KB, 77MB) DMphys | 0x077f2000-0x1b839000 (327964KB, 320MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00134000 ( 208KB, 0MB) DMphys | 0x001cb000-0x002d0000 ( 1044KB, 1MB) DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) DMphys | 0x0043a000-0x009e4000 ( 5800KB, 6MB) bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/L4Linux/vmlinuz26" (14475kB) 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) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-20000000 ( 512MB) type WB io | 1: 1e000000-20000000 ( 32MB) type UC io | 2: e8000000-ec000000 ( 64MB) type WC io | 3: e8000000-ec000000 ( 64MB) type WC 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 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 loader | vmlinuz26,#10: Loading ldso loader | vmlinuz26,#10: Starting libld-l4.s.so at 00013870 via 0000bc54 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: ImPS/2 Generic Wheel Mouse on isa0060/serio1 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)) #4 Wed Nov 15 22:47: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 - 0072e000 [3256 KiB]. l4lx | Areas: Text: 00400000 - 00642000 [2312kB] (a bit longer) l4lx | Data: 00642000 - 0068bd8c [295kB] l4lx | Initdata: 0068e000 - 006bf000 [196kB] l4lx | BSS: 006c0000 - 0072c930 [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 = 00642000 size = 512000 l4lx | sec-w-init: virt: 0x00642000 to 0x006befff [500 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 512000 Bytes l4lx | sec-w-init: 1: Phys: 0x0141c000 to 0x01488000, Size: 442368 l4lx | sec-w-init: 2: Phys: 0x0120f000 to 0x01220000, Size: 69632 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: 0x07800000 to 0x17800000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1614 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) 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 "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 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=60, size=800 l4dope | SharedMem(get_adr): address = 6000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=61, size=800 l4dope | SharedMem(get_adr): address = 7000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=62, size=800 l4dope | SharedMem(get_adr): address = d000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=63, size=800 l4dope | SharedMem(get_adr): address = e000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=64, size=800 l4dope | SharedMem(get_adr): address = f000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=66, size=800 l4dope | SharedMem(get_adr): address = 16000 l4dope | SharedMem(alloc): hl.low=100000, lh.high=80000, id=67, size=800 l4dope | SharedMem(get_adr): address = 17000 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 | 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) l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. l4dope | psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, l4dope : throwing 3 bytes away. Thank you. cheng

2 1

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 16 Nov '06

16 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