Adam Lackorzynski wrote:
. . . l4lx | =====> L4Linux 2.6 starting... <===== l4lx | Linux version 2.6.21-l4 (cw@Braxis) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 Thu Jul 12 13:57:59 CEST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb root=/dev/sda5 l4lx | Image: 00400000 - 00681000 [2564 KiB] l4lx | Areas: Text: 00400000 - 005e8000 [1952 kB] (a bit longer) l4lx | Data: 005e8000 - 005fd2cc [84 kB] l4lx | Initdata: 00600000 - 006240a0 [144 kB] l4lx | BSS: 00626000 - 0067e900 [354 kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode ROOT: Task #0c is not allowed to execute cli/sti loader| vmlinuz26, #e: Can't map I/O space, ROOT denies page (result=00004000) -- app_pager ------------------------------------------ IP : 01304207 [loader.pager] (c.03) jdb:
Ehm.. what have I to do??
I thank you need to add the following configuration to roottask: task modname "loader" allow_cli boot_priority 0xA0
The allow_cli is important here. Either add this at the command line of roottask or in a roottask configuration file.
Hi Adam, this is the entry -I've modified where sentence is in bold-
title L4Linux -Linux on L4- (DROPS - Lackorzynski) root (hd0,4) kernel /L4Linux_binary/build/l4/bin/x86_586/bootstrap -serial root=/dev/sda5 -modaddr 0x06000000 module /L4Linux_binary/build/fiasco_ia32/main -nokdb -serial_esc module /L4Linux_binary/build/l4/bin/x86_586/l4v2/sigma0 module /L4Linux_binary/build/l4/bin/x86_586/l4v2/roottask task modname "bmodfs" attached 4 modules task modname "loader" allow_cli boot_priority 0xA0 module /L4Linux_binary/build/l4/bin/x86_586/l4v2/events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/names --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/log --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/dm_phys --isa=0x00800000 -v --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/simple_ts -t 300 --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/rtc --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/l4io --events module /L4Linux_binary/build/l4/bin/x86_586/l4v2/loader --fprov=BMODFS linux26.cfg module /L4Linux_binary/build/l4/bin/x86_586/l4v2/bmodfs module /L4Linux_binary/build/l4/bin/x86_586/l4v2/linux26.cfg module /L4Linux_binary/build/linux/vmlinuz26 module /L4Linux_binary/build/l4/bin/x86_586/l4v2/libloader.s.so module /L4Linux_binary/build/l4/bin/x86_586/l4v2/libld-l4.s.so vbeset 0x117
Good, but the output said something about the ORe server:
l4lx| Creating 1 ORe device(s) l4lx| Opening device eth0 at ORe instance ORe l4lx| l4ore_open(): called l4lx| l4ore_open(): descriptor 0 l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 1.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 2.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 3.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 4.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 5.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 6.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 7.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 8.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 9.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', 10.attempt. l4lx| ore_lookup_server(): Could not find ORe server 'ORe', aborting. l4lx| panic: going to sleep forever, bye
What is this server? Who is going to creating/loading it? How to make all the things work?
Regards, Massimo.