- l4-hackers - example.com Site

bug report
by chenggh 29 Aug '07

29 Aug '07

ranlib libfe.a make[5]: Leaving directory `/home/L4/tudos/dice/src/fe' Making all in parser make[5]: Entering directory `/home/L4/tudos/dice/src/parser' Making all in idl make[6]: Entering directory `/home/L4/tudos/dice/src/parser/idl' bison --report=all -d idl-parser.yy idl-parser.yy:2.1-8: invalid directive: `%require' idl-parser.yy:2.10-15: syntax error, unexpected string make[6]: *** [idl-parser.tab.cc] Error 1 make[6]: Leaving directory `/home/L4/tudos/dice/src/parser/idl' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/L4/tudos/dice/src/parser' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/L4/tudos/dice/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/L4/tudos/dice' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/L4/tudos/dice' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/L4/tudos/dice' make: *** [../dice] Error 2 make: Leaving directory `/home/L4/tudos/l4' OS: Ubuntu6.06 bison (GNU Bison) 2.1 This l4 is downloaded on 2007-08-27. Thanks. Cheng Guanghui

2 1

Re: The ultimate HOW-TO
by Bjoern Doebel 27 Aug '07

27 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 skitmax81(a)yahoo.it wrote: > Bjoern Doebel wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >>> PS. For a test, could you please post the entry to add at the menu.lst >>> file >>> to try booting L4Linux? >>> Maybe everything is still working.. &-( >> Did you have a look at >> http://os.inf.tu-dresden.de/L4/LinuxOnL4/use-2.6.shtml >> ? >> .... >> > Quoted from: > http://www.nabble.com/The-ultimate-HOW-TO-tf4192072.html#a12351172 > > ------------------------------------------------------------------------------------------------------ > > Yes, I've read the page, but, because I'm newbie, I don't understand how to have a standalone > setup without DOpE.. I would like to have a simple console where compile/build and run <i>lmbench</i> As Adam already pointed out, you shouldn't even use DOpE when doing a benchmark. So let's sum it up: * Build Fiasco and the hello server. Then run it and make sure that the red (performance-critical) warnings at Fiasco bootup are gone. * Build the L4Env packages needed for L4Linux, namely those that appear in the menu.lst which can be found on the "Using L4Linux" page you already know. * Build L4Linux. Disable DOpE support, disable networking and sound stuff, enable VGA text console and hard disk support. * Put all the binaries obtained so far into the boot directory where GRUB gets its modules from, e.g., where your (SUSe?) Linux kernel is. * Create a loader config file for L4Linux, just like the one on the L4Linux page and put it in the same location. You don't have to use a ramdisk, but can just put a "root=/dev/hda1" or something similar there. Basically, you should be able to use your native Linux environment from HD with L4Linux, too. * Add a menu.lst entry such as the one on the L4Linux page to your GRUB menu.lst. Which of the above points is unclear to you? > I'm not intereste to have networking or sound or other stuffs, only a simple console Linux-like.. it's > for a course and I'm a bit frustrated.. two months and no results.. sigh! :-(( Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG0v6tP5ijxgQLUNkRApeUAJ9jKk/U6xdywJ4Ih1FH4XeWiMT+cgCfXelx LCnf2fk5w8zcNoyxIwOnJm0= =11yE -----END PGP SIGNATURE-----

1 0

Re: The ultimate HOW-TO
by chenggh 25 Aug '07

25 Aug '07

> > API Version: (87) experimental > > Sigma0 config ip:001048a8 sp:002c9760 > > Roottask config ip:00110000 sp:00000000 > > Starting kernel /DROPS/kernel/fiasco/build/fiasco at 0030082c > > > > Comport 0x0001 is not accepted by the uart driver! > > > > Welcome to Fisco (ia32)! > > DD-L4(v2)/ia32 microkernel (C) 1998-2007 TU Dresden > > Rev: rUNKNOWN compiled with gcc 4.1.0 for Intel Pentium [ ] > > Performance-critical config option(s) detected: > > CONFIG_NDEBUG is off > > > > Enabling special fully nested mode for PIC > > > > Assertion failed: '0' > > in /DROPS/kernel/fiasco/src/abi/kip.cpp:126 > > at f00175d1 > > > > Press any key to reboot. > > Founded the option and set it on, I see that the output is something like > #06.. but it reboots and I can't read so fast! > The result is that I can't be more exahustive in the explaination so I > answer: How to have a log file to read the outputs? In the grub/menu.lst you could do like this: module /boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 Then you could receive the boot message in another machine with connection to the l4 machine by ttyS0 (com1) with comspeed 115200 like this: minicom -m -s -C logfile Good luck to you. Cheng Guanghui

1 0

Re: The ultimate HOW-TO
by chenggh 25 Aug '07

25 Aug '07

> Founded the option and set it on, I see that the output is something like > #06.. but it reboots and I can't read so fast! > The result is that I can't be more exahustive in the explaination so I > answer: How to have a log file to read the outputs? In the grub/menu.lst you could do like this: module /boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 Then you could receive the boot message by the ttyS0 (com1) with comspeed 115200. Good luck. Cheng Guanghui

2 1

Re: about compile environment
by chenggh 15 Aug '07

15 Aug '07

On Wednesday 15 August 2007 02:19, sunshine007 wrote: > Thanks adam, > > but now i have problem with booting the L4linux by remote serial console. > i follow the pdf kickstart. > but, i still got error like this (after i reboot the machine): > Using IPI shortcut mode > List of all partitions > No file system could not mount root, tried : > kernel panic - not syncing > VFS : unable to mount root fs on unknown block (0,0) These information shows that your Fiasco has no problem and it could drag the booting of L4Linux. But the L4Linux can't find or mount the root file system. If VFS can't mount root fs with unknown blocks. First you should check your l4linux configuration with the filesystem type as ext2, ext3, etc. Basically you should compile the ext2 or ext3 into the linux kernel not compile as modules. > my menu.lst : > #L4linux > title L4Linux-2.6/Fiasco+dope > root (hd0,2) > kernel /boot/L4linux/bootstrap > modaddr 0x02000000 > module /boot/L4linux/fiasco -nowait -nokdb -serial_esc -comspeed 115200 > -comport 1 > module /boot/L4linux/sigma0 > module /boot/L4linux/roottask task modname "bmodfs" attached 4 modules > module /boot/L4linux/events > module /boot/L4linux/names --events > module /boot/L4linux/log --events > module /boot/L4linux/dm_phys --isa=0x00800000 -v --events > module /boot/L4linux/simple_ts -t 300 --events > module /boot/L4linux/rtc --events > module /boot/L4linux/l4io --noirq --events module > module /boot/L4linux/loader --fprov=BMODFS linux26.cfg > module /boot/L4linux/bmodfs > module /boot/L4linux/vmlinuz > module /boot/L4linux/linux26.cfg > module /boot/L4linux/libloader.s.so > module /boot/L4linux/libld-l4.s.so > #end l4linux Here, your root partition is located in /dev/hda3 > #linux26.cfg > modpath "(hd0,2)/boot/L4linux" > task "vmlinuz" "earlyprintk=yes console=ttyS1,115200 init=1 mem=256M > root=/dev/sda3" > all_sects_writable > Here, your l4linux kernel image is located in /dev/hda3 but root partitition is located in /dev/sda3. > # fdisk -l > > Disk /dev/sda: 250.0 GB, 250000000000 bytes > 255 heads, 63 sectors/track, 30394 cylinders Units = cylinders of 16065 * > 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 1 5 40131 de Dell Utility > /dev/sda2 * 6 2616 20972857+ 7 HPFS/NTFS > /dev/sda3 2617 26931 195310237+ 83 Linux > /dev/sda4 26932 30394 27816547+ 82 Linux swap > > It is i wrongly typed the root partition? > But there is no devive named /dev/hda3. So may you should replace /dev/sda3 with /dev/hda3. You can try. Best regards. Cheng Guanghui

1 0

about compile environment
by huang 15 Aug '07

15 Aug '07

hi,dear Adam: Could you give me some advices about the operating system on which we can build fiasco and l4env? I have used some different linux such as suse 9 and fedora core 3, fedora core 6 and so on, there always some problem ocurred while building or booting the l4 components. What operating system are you using now? And what operating systems are fully tested for the l4 system? Best regards! huang

6 9

about input in hello
by huang 11 Aug '07

11 Aug '07

hi,dear all: if I want to get some input in the "hello" example, what should I do? I simply use "scanf()", but it does not work! my main.c is as below: #include <l4/sys/types.h> #include <l4/sys/syscalls.h> #include <l4/sys/ipc.h> #include <stdio.h> int main(int argc, char **argv) { l4_threadid_t th; l4_msgdope_t result; l4_umword_t d1, d2; int choice; printf("Hello World\n"); th = l4_myself(); for (;;) { printf("hello: My thread-id is %x.%x\n", th.id.task, th.id.lthread); scanf("%d",&choice); if(choice==0) return 0; } }

2 1

Re: I have a problem, when run Fiasco-UX
by chenggh 10 Aug '07

10 Aug '07

On Friday 10 August 2007 09:27, xiaosan Huang wrote: > Hi, > > I am a new learner of Fiasco-UX. I followed the steps on > http://os.inf.tu-dresden.de/Studium/MkK/uebung/. Everything was ok before > I typed the command : > > ./fiasco -l name -l log -l dm_phys -l hello > > The error information is as follows: > > Fiasco-UX on Linux 2.6.19(i686) > > Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 > > > > Failed to open file : sigma0 Do you have the sigma0 application in the current directory? cheng

1 0

Re: I have a problem, when run Fiasco-UX
by Udo A. Steinberg 10 Aug '07

10 Aug '07

On Fri, 10 Aug 2007 17:27:34 +0800 xiaosan Huang (XH) wrote: XH> The error information is as follows: XH> XH> Fiasco-UX on Linux 2.6.19(i686) XH> Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 XH> Failed to open file : sigma0 XH> XH> What is the problem? Please help me. The Problem is that Fiasco-UX cannot find the sigma0 binary file. You can either: * copy sigma0 into the directory where you start Fiasco-UX * create a symlink named "sigma0" in that directory, pointing to the file * specify -S parameter with the full path of sigma0 For some more details, have a look at: http://os.inf.tu-dresden.de/fiasco/ux/using.shtml Cheers, - Udo

1 0

I have a problem, when run Fiasco-UX
by xiaosan Huang 10 Aug '07

10 Aug '07

Hi, I am a new learner of Fiasco-UX. I followed the steps on http://os.inf.tu-dresden.de/Studium/MkK/uebung/. Everything was ok before I typed the command : ./fiasco -l name -l log -l dm_phys -l hello The error information is as follows: Fiasco-UX on Linux 2.6.19(i686) Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 Failed to open file : sigma0 What is the problem? Please help me. Xiaosan Huang

1 0