- l4-hackers - example.com Site

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