The ultimate HOW-TO

Adam Lackorzynski adam at os.inf.tu-dresden.de
Wed Sep 12 00:17:26 CEST 2007


On Tue Sep 11, 2007 at 00:23:11 -0700, ComputerScienceStudent wrote:
> Hi Adam, this is the entry -I've modified where sentence is in bold- 

No bold in this text mail :)

> 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? 

This L4Linux is configured with the ore driver which tries to connect to
the ore server. The ore server is a network server which switches
network traffic between clients and network cards. As the ore server is
not started the driver does not find it and thus fails to initialize the
driver. That should not really harm.
You should add earlyprintk=keep to the Linux kernel command line to get
more output (add it in linux26.cfg). Unfortunately I don't know if the
L4Linux you're using supports this, it's a compile configuration option.
Additionally it's not clear to me whether this L4Linux supports VGA
output and thus would print something itself (the earlyprintk will help
in this case too).




Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list