Re: problem when booting l4linux
Hi, On Fri Jul 13, 2007 at 09:17:19 +0800, [EMAIL PROTECTED] wrote: I have built the fiasco,l4env,l4linux on my fedora core 5. But there are someting wrong with booting l4linux,it says The running kernel does not have the l4lx segments and goes to jdb. You need to enable Handle and preserve segments under Kernel Options and ABI Extensions in the Fiasco configuration menu. Enable the experimental features before. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: About build of L4Linux
On Fri Jul 13, 2007 at 14:57:57 +0900, Lin wrote: Hi, Adam. Sorry for my late answer. My .config file may be too strange for you because I am a beginner in configuring or building kernels. I probably added many vain components to the kenel unconsciously. Lots of stuff switched on (too much). Please use the attached config as a basis, this one should be much better. Thanks too much, I'm going to compare my bad configuration with the given ... By Using it, it takes about 8 minutes to make. The size of vmlinux is about 17MB, and vmlinuz32 is about 5MB. (It takes about 45 minutes to make and the created binaries are too large if I use my old configuration !) That's a lot better. Thanks, but I'd already gained the GRUB which has the modaddr command by using the patch (grub-0.97-os.1.diff.gz) you made. And I tried to boot L4Linux/Fiasco(+l4dope) with it, however it failed. The kernel configuration is equal to the posted file. The menu.lst in the /boot/grub directory and the loader configuration file linux26.cfg are as follows. [/boot/grub/menu.lst] -- title L4Linux2.6/Fiasco root (hd0,0) kernel /boot/L4Linux/bootstrap modaddr 0x0600 module /boot/L4Linux/fiasco -nowait -nokdbi -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 --events module /boot/L4Linux/simple_ts -t 300 --events module /boot/L4Linux/rtc --events module /boot/L4Linux/l4io --noirq --events module /boot/L4Linux/bmodfs module /boot/L4Linux/vmlinuz26 module /boot/L4Linux/libloader.s.so module /boot/L4Linux/linux26.cfg module /boot/L4Linux/libld-l4.s.so module /boot/L4Linux/l4dope --l4io module /boot/L4Linux/loader --fprov=BMODFS linux26.cfg vbeset 0x117 - [linux26.cfg] --- verbose 0 task vmlinuz26 mem=256M video=l4fb root=/dev/hda1 all_sects_writable allow_vga - After GRUB loads modules, a black mouse cursor and a Linux console window are displayed (the window often aren't). But I cannot use my keyboard and mouse (the cusor won't move and keys produce nothing). Besides, the console message stops on the way (stop points are different every time like following). -- ... l4fb: DOpE framebuffer at 0x12005000, size 600k l4fb: mode is 640x480x16, linelength=1280, pages=0 l4fb: directcolor: size=0:5:6:5, shift=0:11:5:0 Console: switching to colour frame buffer device 80x30 --- [stop] l4fb0: l4fb L4 frame buffer device (refresh: 100ms) vga16fb: mapped to 0x000a vga16fb: mapped to 0x000a fb1: VGA16 VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug Play device found RocketPort device driver module, version 2.09, 12-June-2003 No rocketport ports found; unloading driver. Cyclades driver 2.4--- [stop] built Jul 11 2007 05:10:13 --- [stop] -- I cannot understand the cause of this behavior... I'm reading the ML logs, but I don't solve it yet. Please try with the updated L4Linux configuration. I can't spot an obvious mistake in the configuration you posted (except it's -nokdb instead of -nokdbi) I updated L4Linux (using the attached config) and retried, but it also stopped. To see the setup sequences, I tried using the serial output way. It always stops here: --- l4lx| == L4Linux 2.6 starting... l4lx| Linux version 2.6.21-l4 ([EMAIL PROTECTED]) l4lx: (gcc version 3.4.6 20060404 (Red Hat 3.4.6-4)) #7 Fri Jul 13 06:05:2 l4lx: 5 JST 2007 l4lx| Binary name: vmlinuz26 l4lx| Kernel command line (4 args): console=ttyS1,115200 init=1 mem=256M ro l4lx: ot=/dev/hda1 l4lx| Image: 0040 - 0079d000 [3700 KiB]. l4lx| Areas: Text: 0040 - 006d1000 [2884kB] (a bit longer) l4lx|Data: 006d1000 - 006ef2cc [120kB] l4lx|Initdata: 006f2000 - 0072e0a0 [240kB] l4lx|BSS: 0073 - 0079aee0 [427kB] l4lx| l4lx_thread_create: Created thread 0d.03 (tamer) l4lx| Using tamed mode. l4lx| l4env_linux_startup thread 4. l4lx| l4lx_thread_create: Created
building l4linux
Hi~ i have some questions again. my building sequence is : == in l4_all/kernel/fiasco 1. make BUILDDIR=../../build/fiasco in l4_all/build/fiasco 2. make menuconfig in l4_all/l4 3. make config O=../build/l4env 4. make O=../build/l4env == my questions : 1. when i issue make in l4/ to build the L4 userland, does it automatic build fiasco subsequently？ 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? ( after the operations mentioned above, i find there are some new files in l4_all/kernel/fiasco/build ) but my configuration for fiasco is in l4_all/build/fiasco, is this auto build operation based on my config? or i should set BUILDDIR to l4_all/kernel/fiasco/build? when config l4linux: according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, there are some options we shouldn't enable ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, power management and similar. 1. does those options are default unable? or we should unable manually? 2. what does similar mean? thanks for answering. ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
Hi, On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: my building sequence is : == in l4_all/kernel/fiasco 1. make BUILDDIR=../../build/fiasco in l4_all/build/fiasco 2. make menuconfig in l4_all/l4 3. make config O=../build/l4env 4. make O=../build/l4env == my questions : 1. when i issue make in l4/ to build the L4 userland, does it automatic build fiasco subsequently¡H 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? Yes, a default configuration is built into kernel/fiasco/build upon make in the l4 directory if not configured otherwise (see the L4 configuration menu). ( after the operations mentioned above, i find there are some new files in l4_all/kernel/fiasco/build ) but my configuration for fiasco is in l4_all/build/fiasco, is this auto build operation based on my config? No, it's a default build. or i should set BUILDDIR to l4_all/kernel/fiasco/build? No. The way you build the kernel is fine. when config l4linux: according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, there are some options we shouldn't enable ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, power management and similar. 1. does those options are default unable? or we should unable manually? 2. what does similar mean? With this statement I'm trying to express that for L4Linux one should _not_ enable any option that is close to the hardware, such as ACPI, HPET, MTRR etc. Remember, L4Linux is a normal user program and as such has no business doing anything with timer hardware or interrupt controller or similar. On the other side, you can enable e.g. any filesystem you like. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
