- l4-hackers - example.com Site

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there are > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) 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 loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB 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 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng

1 0

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Tuesday 22 May 2007 10:40, chenggh wrote: > Hi: > When I boot the L4Linux there are some errors. In this mail there are 2 > attachments of linux26.cfg, grub configuration and boot log. Please help me > to check the boot log. The new boot log is as following: names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:09:29:11 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPED DMphys | 0x00106000-0x00107000 -- -- DENIED DMphys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x009d6000-0x00b80000 ( 1704KB, 2MB) free DS: DMphys | 0x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Mon Ma l4lx : y 21 13:54:26 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b73a0 [428kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread will be 0e.04 l4lx | l4env_register_pointer_section: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB 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 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thank you. cheng

1 0

RE: The boot error of L4Linux
by Clermont, Nicolas 23 May '07

23 May '07

Hi maybe adding the 'allow_cli' option in your l4linux.cfg ? -----Message d'origine----- De : l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] De la part de chenggh Envoyé : mercredi 23 mai 2007 19:39 À : l4-hackers(a)os.inf.tu-dresden.de Objet : Re: The boot error of L4Linux On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there > > > are > > > 2 attachments of linux26.cfg, grub configuration and boot log. > > > Please help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) 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 loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB 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 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 1

Re: The boot error of L4Linux
by Adam Lackorzynski 23 May '07

23 May '07

On Wed May 23, 2007 at 17:39:09 +0000, chenggh wrote: > On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > > Hi: > > > > When I boot the L4Linux there are some errors. In this mail there are > > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > > help me to check the boot log. > > > > > > The new boot log is as following: > > > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > > 0x000 > > > l4lx : 04000) > > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > > l4lx | unhandled page fault > > > > You probably need 'allow_vga' in your l4linux loader configuration file. > The error is same when I add the "allow_vga" in linux26.cfg like this: > > modpath "(hd0,1)/boot/L4Linux" > task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M > root=/dev/hda2" > all_sects_writable allow_vga Please give each option its own line: all_sects_writable allow_vga Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Tuesday 22 May 2007 10:40, chenggh wrote: > Hi: > When I boot the L4Linux there are some errors. In this mail there are 2 > attachments of linux26.cfg, grub configuration and boot log. Please help me > to check the boot log. The new boot log is as following: names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:09:29:11 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPED DMphys | 0x00106000-0x00107000 -- -- DENIED DMphys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x009d6000-0x00b80000 ( 1704KB, 2MB) free DS: DMphys | 0x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Mon Ma l4lx : y 21 13:54:26 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b73a0 [428kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread will be 0e.04 l4lx | l4env_register_pointer_section: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB 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 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thank you. cheng

1 0

Re: The boot error of L4Linux
by Adam Lackorzynski 23 May '07

23 May '07

On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > On Tuesday 22 May 2007 10:40, chenggh wrote: > > Hi: > > When I boot the L4Linux there are some errors. In this mail there are 2 > > attachments of linux26.cfg, grub configuration and boot log. Please help me > > to check the boot log. > The new boot log is as following: > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > 0x000 > l4lx : 04000) > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault You probably need 'allow_vga' in your l4linux loader configuration file. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

RE: [NITPICKER] Porting X.org 1.1.1 to use NitPicker
by Clermont, Nicolas 22 May '07

22 May '07

Hi Norman, > Hi Nicolas, > > I managed to reproduce your issue with the non-working refresh of the > X11 windows with Xorg of the latest Debian unstable. The problem was > an API change of the shadowfb Module of Xorg from version 7.0 to the current version. I updated the drivers ovlscreen_drv.so and lxevent_drv.so in: > > overlay_wm/examples/xf86screen/ and > overlay_wm/examples/xf86input/ Wondeful ! Thanks a lot Norman, I was going to test your proposed solutions (just coming back from holiday). I'll update from Dresden svn and have a try of your updates to see if all work for me. > Frank Mehnert's up-to-date PSLIM driver in 'l4con/examples/xf86_stub' > was a very good reference for finding the problem. The updated drivers > should be available at our public SVN repository soon. Thanks for the tip, I will have a look. > > So we have started with a Linux installation (Gentoo Linux), after > > what we have installed Fiasco, L4Env and L4Linux (2.6.20, next > > 2.6.21, on top on our recently installed Gentoo, reusing its > > filesystem). To test our installation, we first use L4Con, but the > > mouse moves were extremely slow; so next we use DOpE, and it was > > cool, all worked (network and hard disk via L4Linux, not Ore... Oh > > is there exist a multiplexer, as Ore, for hard disk ?). But of > > course, the desktop-in-window aproach does > > To my knowledge, there is no hard-disk multiplexer available. Maybe my next step ... ;) > > not fully satisfied us, we want a fullscreen aproach so we start > > investigating on NitPicker. > > > > The problem is that all tutorials related to NitPicker + X.org are > > based on a quite-old version of X.org, before the X.org team adopted > > the modular approach. So we decide to port the last X.org (1.1.1) to > > use NitPicker, following instructions found at > > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html > > > > First we compiled the nitpicker-client ovlwm server, nitovlwm. Then > > we install into the L4Linux the lxevent program, started after Linux > > kernel boot, with creation of /dev/lxevent, and the ovltrack > > program, started via .xinitrc. We had to change a little the > > Makefile of ovltrack by adding the -Bdynamic option in LIBS. We > > compiled and generated lxevent_drv.o (X.org mouse driver in > > xorg.conf). The last step was generating the X.org screen driver, > > ovlscreen_drv.o. The changes toward previous versions occurs at this > > step, as now X.org is modular and consists in several small > > packages. But after resolving a lot of include path problems, > > importing the needed X.org package to compile the driver, we got the > > driver ovlscreen_drv.o compiled and copy it into the L4Linux filesystem, modifying xorg.conf to use this driver. > > Also we use NitDope, so L4fb driver in L4Linux that creates /dev/fb0. > > I am amazed of how far you went on your own without even asking one > question. Respect! :-) Good luck with the updated drivers. > > Best regards > Norman Thanks Norman, it makes me great pleasure to read this from you (respect for your job, be it NitPicker, DOpE, Bastei, ... That's amazing ! ;)). Also thanks for your help and your time. I have no doubt that the updated drivers will work for me (I'll confirme you as soon as I have all the stuff working). Best regards, Nicolas

1 0

The boot error of L4Linux
by chenggh 22 May '07

22 May '07

Hi: When I boot the L4Linux there are some errors. In this mail there are 2 attachments of linux26.cfg, grub configuration and boot log. Please help me to check the boot log. Thank you. cheng

2 1

What is the modifications of latest L4 packages?
by chenggh 21 May '07

21 May '07

Hi: Several months ago I downloaded the l4 packages which are much more packages than them now. This was the snapshot of l4 pkg directory several months ago. In total there are 100 directories. COPYING dm_generic/ input/ linux-24-headers/ oskit_support_l4env/ slab/ CVS/ dm_mem/ ipreg/ linux-26-headers/ overlay_wm/ socket_linux/ Makefile dm_phys/ l4con/ loader/ pci/ stepper_motor/ arm_drivers/ dmon/ l4env/ local_socks/ petze/ tftp/ bootstrap/ dope/ l4ide/ lock/ pingpong/ thread/ c++-examples/ dsi/ l4io/ log/ presenter/ thread_linux/ cpu_reserve/ dsi_example/ l4rm/ log_net/ proxygon/ uclibc/ crtx/ dsi_staticfs/ l4sys/ lxfuxlibc/ qt3/ uclibc++/ cxx/ events/ l4util/ names/ rmgr/ uclibc_r/ cxx_linux_io/ exec/ l4vfs/ nethub/ roottask/ verner/ cxx_log_io/ flips/ ldso/ nitpicker/ rt_mon/ x86emu/ dde_linux/ generic_blk/ libc_backends_l4env/ omega0/ rtc/ zlib/ dde_linux26/ generic_fprov/ libc_support/ ore/ semaphore/ demangle/ generic_io/ libpng/ oskit10_support/ serial/ dice_hello/ generic_ts/ libsigma0/ oskit10_support_l4env/ sigma0/ dietlibc/ hello/ libstdc++/ oskit10_support_l4env_full/ signal/ dietlibc_r/ hello_cxx/ libvfb/ oskit_support/ simple_ts/ But now there are only 47 directories as following: COPYING dm_generic/ generic_fprov/ l4io/ libc_backends_l4env/ log/ roottask/ slab/ zlib/ Makefile dm_mem/ generic_io/ l4rm/ libc_support/ lxfuxlibc/ rtc/ tftp/ bootstrap/ dm_phys/ generic_ts/ l4sys/ libsigma0/ names/ semaphore/ thread/ crtx/ dope/ input/ l4util/ linux-24-headers/ omega0/ serial/ uclibc/ cxx/ events/ l4con/ ldso/ loader/ pci/ sigma0/ uclibc_r/ demangle/ generic_blk/ l4env/ libc_backends/ lock/ proxygon/ simple_ts/ x86emu/ What is the modifications of L4 architectures and what is the aim ? But there is no new version of Fiasco to be published. Thanks. cheng

1 0

Re: What is the modifications of latest L4 packages?
by Adam Lackorzynski 21 May '07

21 May '07

On Mon May 21, 2007 at 21:17:00 +0000, chenggh wrote: > Several months ago I downloaded the l4 packages which are much more packages > than them now. > This was the snapshot of l4 pkg directory several months ago. In total there > are 100 directories. We have removed packages that are obsolete and not needed anymore, like the oskit* packages. > But now there are only 47 directories as following: There are 83 directories in l4/pkg in the svn. You can check out everything if you like. > What is the modifications of L4 architectures and what is the aim ? But We're working on the project and things evolve and change, new packages come, old packages go. > there is no new version of Fiasco to be published. Not today. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 21 May '07

21 May '07

On Sun May 20, 2007 at 10:15:13 +0000, chenggh wrote: > On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > > On Saturday 19 May 2007 12:01, chenggh wrote: > > > Hi: > > > Now I have the new problem. the make menuconfig is ok but when i make > > > the kernel there are some problems like this: > > > > > > root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ > > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > > determine L4 source directory. Configuration missing?. Stop. > > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > > determine L4 source directory. Configuration missing?. Stop. > > > > as one can read, you didn't configure your kernel correctly. You have to > > specify your L4 source tree when configuring L4Linux. Lately, that's what > > the one error message above says to you. > No, it is not my error of configuration but the system warning which is an > error itself. When I make menuconfig there also is the same error. So the > most important error is second one : > make[1]: *** No rule to make target > `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by > `archprepare'. Stop. > make: *** [_all] Error 2 I have modified a few things in this area now, hope it's better. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 20 May '07

20 May '07

On Sunday 20 May 2007 10:15, you wrote: > On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > > On Saturday 19 May 2007 12:01, chenggh wrote: > > > Hi: > > > Now I have the new problem. the make menuconfig is ok but when i make Sorry, It is my fault. Now it is ok Thank you very much. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 20 May '07

20 May '07

On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > On Saturday 19 May 2007 12:01, chenggh wrote: > > Hi: > > Now I have the new problem. the make menuconfig is ok but when i make > > the kernel there are some problems like this: > > > > root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > as one can read, you didn't configure your kernel correctly. You have to > specify your L4 source tree when configuring L4Linux. Lately, that's what > the one error message above says to you. No, it is not my error of configuration but the system warning which is an error itself. When I make menuconfig there also is the same error. So the most important error is second one : make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 Do you use the l4linux-2.6.20 or l4linux-2.6.21 ?. I have ever used l4linux-2.6.1x and they have no problems. But when I use l4linux-2.6.20 or l4linux-2.6.21 they have many problems. > > GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile > > HOSTLD scripts/kconfig/conf > > scripts/kconfig/conf -s arch/l4/Kconfig > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > make[1]: *** No rule to make target > > `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by > > `archprepare'. Stop. > > make: *** [_all] Error 2

1 0

9th Real Time Linux Workshop, Linz, Austria, Nov 2-4 2007
by Nicholas Mc Guire 20 May '07

20 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 9th Real-Time Linux Workshop November 2-4, 2007 Institute for Measurement Technology Johannes Kepler University of Linz CALL FOR PAPERS General Following the meetings of developers and users at the previous 8 successful real-time Linux workshops held in Vienna, Orlando, Milano, Boston, and Valencia, Singapur, Lille, and Lanzhou the Real-Time Linux Workshop for 2007 will come back to Europa, to be held at the Institute for Measurement Technology, Johannes Kepler University of Linz, Austria. Embedded and real-time Linux is continuously growing player in the embedded appliance market world wide. Embedded systems in automation control, measurement and multimedia have been continuously moving towards 32bit systems, opening the door for the use of full featured OS like GNU/Linux on COTS based systems. With real-time capabilities being a common demand for embedded systems the soft and hard real-time variants are an important extension to the versatile GNU/Linux GPOS. Authors are invited to submit original work dealing with general topics related to real-time Linux research, experiments and case studies, as well as issues of integration of real-time and embedded Linux. A special focus will be on industrial case studies. Topics of interest include, but are not limited to: * Modifications and variants of the GNU/Linux operating system extending it's real-time capabilities * Contributions to real-time Linux variants, drivers and extensions. * User-mode real-time concepts, implementation and experience * Real-time Linux applications, in academia, research and industry * Real-time Linux in measurement and data-aquisition systems * Signal processing with Linux/real-time Linux. * Work in progress reports, covering recent developments * Educational material on real-time Linux. * Tools for embedding Linux or real-time Linux and embedded real-time Linux applications * RTOS core concepts, RT-safe synchronization mechanisms * Analysis and Benchmarking methods and results of real-time GNU/Linux variants. * Debugging techniques and tools, both for code and temporal debugging of core RTOS components, drivers and real-time applications * Real-time realted extensions to development environments * RT-Linux in safety-critical systems Registration In order to participate to the workshop, please register on the Registration Page at: http://www.realtimelinuxfoundation.org/events/events.html Venue: Johannes Kepler University,Linz, Austria http://www.realtimelinuxfoundation.org/events/ws-2007/venue.html Accommodation: http://www.realtimelinuxfoundation.org/events/ws-2007/hotels.html Important dates: August 11, 2007 Abstract submission September 15, 2007 Notification of acceptance October 13, 2007 Final paper Nov 2-3 Workshop Organization committee: * Prof. Bernhard ZAGAR, (JKU, AUSTRIA) * Prof. Li LIAN , (LZU, CHINA) * Dr. Peter WURMSDOBLER , (RTLF, USA) * Prof. Nicholas MCGUIRE , (LZU, CHINA) Program committee: Prof. Dr. Bernhard Zagar (Johannes Kepler Universit�t Linz, AUSTRIA) Prof. Li Lian (SISE, Lanzhou University, CHINA) Prof. Dr. Paolo Mantegazza (Dipartimento di Ingegneria Aerospaziale, ITALY) Prof. Dr. Alfons Crespo (Universidad Polit�cnica de Valencia,SPAIN) Prof. Dr. Ismael Ripoll (Universidad Polit�cnica de Valencia,SPAIN) Ing. Pavel Pisa (Czech Technical University, CZECH REPUBLIC) Dr. Miguel Masmano Tello (Universidad Polit�cnica de Valencia,SPAIN) Dr. Zhang Feng, Director of Mobile OS Lab (LCR Lenovo, CHINA) Prof. Hanzalek Zdenek (Czech Technical University, CZECH REPUBLIC) Ing. Michael Rumpler (Thales Group, AUSTRIA) Ing. Philippe Gerum (ADEOS Maintainer, Xenomai, FRANCE) Prof. Xing Li (Tsinghua University, CERNET Center,CHINA) Prof. Hongan Wang (Institute of Software, Intelligence Engineering Lab, Chinese Academy of Sciences, CHINA) Dr. Chen Maoke, (Tsinghua University, CHINA) Dr. Chen Yu, (Tsinghua University, CHINA) Dr. Bin Hu, (Computing Department of Computing, Business School, University of Central England,UNITED KINGDOM) Dr. Lei Wang, (School of Computer Science,Beijing University of Aeronautics and Astronautics,CHINA) Prof. Roberto Bucher (University of Applied Sciences of Southern Switzerland Dept. Innovative Technologies, SWITZERLAND) Ing. Klaus Reichl (Thales Group, AUSTRIA) Dr. Don W. Carr (Universidad de Guadalajara, Guadalajara, MEXICO) Thomas Gleixner (Linutronix, RT-Preempt, GERMANY) Tim Bird (Sony, USA) Ing. Christoph Stueckjuergen (Siemens CT SE 2, GERMANY) Prof. Marting Terbuc (University of Maribor, SLOVENIA) Prof. Matthias Sturm (University of Leibzig, GERMANY) Prof. Ahmet Onat (Sabanci University, TURKEY) Dr. Qingguo ZHOU (DSLab, Lanzhou University, CHINA) Dr. Peter Wurmsdobler (Real Time Linux Foundation, USA) Prof. Nicholas Mc Guire (DSLAb, Lanzhou University, CHINA) Workshop organizers: * Institute for Measurement Technology ,Johannes Kepler University of Linz Austria http://www.emt.uni-linz.ac.at/ * Real-Time Linux Foundation Inc. USA http://www.realtimelinuxfoundation.org * School for Information Science and Engineering (SISE), University of Lanzhou China http://www.lzu.edu.cn * Distributed and Embedded Systems Lab, University of Lanzhou, China http://dslab.lzu.edu.cn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFGT9ASnU7rXZKfY2oRAiKDAKCcVjEgdbRzBoaBkDPaElwqHS7QggCfWdMA au/utUVnuxyHPoVX03jdK1k= =5T3L -----END PGP SIGNATURE-----

1 0

[NITPICKER] Porting X.org 1.1.1 to use NitPicker
by Clermont, Nicolas 19 May '07

19 May '07

Hi everybody, We are working on L4, currently especially on the graphical aspect. As we love NitPicker (NitPicker is cool ;)), we want to use it to run L4Linux on top on it. So we have started with a Linux installation (Gentoo Linux), after what we have installed Fiasco, L4Env and L4Linux (2.6.20, next 2.6.21, on top on our recently installed Gentoo, reusing its filesystem). To test our installation, we first use L4Con, but the mouse moves were extremely slow; so next we use DOpE, and it was cool, all worked (network and hard disk via L4Linux, not Ore... Oh is there exist a multiplexer, as Ore, for hard disk ?). But of course, the desktop-in-window aproach does not fully satisfied us, we want a fullscreen aproach so we start investigating on NitPicker. The problem is that all tutorials related to NitPicker + X.org are based on a quite-old version of X.org, before the X.org team adopted the modular approach. So we decide to port the last X.org (1.1.1) to use NitPicker, following instructions found at http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html <http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html> First we compiled the nitpicker-client ovlwm server, nitovlwm. Then we install into the L4Linux the lxevent program, started after Linux kernel boot, with creation of /dev/lxevent, and the ovltrack program, started via .xinitrc. We had to change a little the Makefile of ovltrack by adding the -Bdynamic option in LIBS. We compiled and generated lxevent_drv.o (X.org mouse driver in xorg.conf). The last step was generating the X.org screen driver, ovlscreen_drv.o. The changes toward previous versions occurs at this step, as now X.org is modular and consists in several small packages. But after resolving a lot of include path problems, importing the needed X.org package to compile the driver, we got the driver ovlscreen_drv.o compiled and copy it into the L4Linux filesystem, modifying xorg.conf to use this driver. Also we use NitDope, so L4fb driver in L4Linux that creates /dev/fb0. Then we boot our L4-based system, NitPicker, NitDOpE and L4Linux, all start, all was right. The problems come when starting X.org. Indeed, X.org started, the window manager also (WindowMaker), in fact all works... excepts refresh ! Indeed when moving the mouse on a L4Linux window, the window content is not refreshed, resulting in an unusable window. But clicking outside the window forces the refresh. We know that with DOpE, the refresh is automatic, periodic and so it was working for us. But with NitPicker, we know that the refresh only occurs if a change is made in the client. What we don't know is how this refresh is done, who is responsible for it (ovlscreen, ovltrack, nitovlwm ?), and which are the impacts of using a modular X.org in this process.... Is someone can give us some tips on how to make the refresh to occur ? Or details about event forwarding ? Is there other changes to be made that we missed ? Any help will be grateful appreciated. Thanks. -- Nicolas Clermont

2 2

Re: Kernel configuration missing ?
by chenggh 19 May '07

19 May '07

Hi: Now I have the new problem. the make menuconfig is ok but when i make the kernel there are some problems like this: root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 It seems the process of making l4linux-2.6.20 is very different from the process of making linux-2.6.20. What is the problem ? strange warning. strange error. cheng

2 1

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

Hi: Now I have the new problem. the make menuconfig is ok but when i make the kernel there are some problems like this: root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 It seems the process of making l4linux-2.6.20 is very different from the process of making linux-2.6.20. What is the problem ? strange warning. strange error. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

> > I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are > > you using? Maybe I need to update the make. > > With 3.80 it breaks for me as well, 3.81 works. I need to do something > about this anyway, so let me see... Thank you , Adam. I update the make in my machine to 3.81. Now it is ok. cheng

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 18 May '07

18 May '07

On Fri May 18, 2007 at 08:06:04 +0000, chenggh wrote: > > HOSTCC scripts/kconfig/lxdialog/checklist.o > > .. > > l4linux-2.6$ make O=./build/ > > L4 source directory: /path/to/l4 > > make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf > > O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 > > OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN > > l4linux-2.6/build/Makeconf.l4conf > > GEN l4linux-2.6/build/Makefile > > HOSTLD scripts/kconfig/conf > > scripts/kconfig/conf -s arch/l4/Kconfig > > Creating asm-l4/api-l4env -> asm/api symlink > > Creating asm-l4/l4lxapi/impl symlink > > Creating asm-l4/l4x-i386 -> asm/l4x symlink > > .. > > > > As said, I'll try to fix the error message inbetween. > > > > Maybe it's the make version. Which version are you using? > > root@darkstar:~# make --version > GNU Make 3.80 > Copyright (C) 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are you > using? Maybe I need to update the make. With 3.80 it breaks for me as well, 3.81 works. I need to do something about this anyway, so let me see... Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

> HOSTCC scripts/kconfig/lxdialog/checklist.o > .. > l4linux-2.6$ make O=./build/ > L4 source directory: /path/to/l4 > make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf > O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 > OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN > l4linux-2.6/build/Makeconf.l4conf > GEN l4linux-2.6/build/Makefile > HOSTLD scripts/kconfig/conf > scripts/kconfig/conf -s arch/l4/Kconfig > Creating asm-l4/api-l4env -> asm/api symlink > Creating asm-l4/l4lxapi/impl symlink > Creating asm-l4/l4x-i386 -> asm/l4x symlink > .. > > As said, I'll try to fix the error message inbetween. > > Maybe it's the make version. Which version are you using? root@darkstar:~# make --version GNU Make 3.80 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are you using? Maybe I need to update the make. Thanks. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 17 May '07

17 May '07

On Wednesday 16 May 2007 21:57, you wrote: > Hi, > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > I download the newest source page neened for L4Linux and Fiasco. The > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > the compilations of fiasco kernel and l4 packages is ok and when i > > enter the l4linux I input make menuconfig. There are some errors like > > this: > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > configuration missing. Stop. > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > It's true that there's this irritating message but it should generally > work. Does for me like this: > > $ cd l4linux-2.6 > $ mkdir /tmp/builddir > $ make O=/tmp/builddir menuconfig > ... configure path to l4-obj-dir etc... > $ make O=/tmp/builddir There is still the problem in my machine like this: root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 make: *** [menuconfig] Error 2 I think it is possible to miss some configuration files. But I don't know which file is missing. Thank you. cheng

1 0

logging to cvs problem
by Jorge Torres 17 May '07

17 May '07

Hi l4-hackers, I have a problem once I try to log in to os.inf.tu-dresden.de CVS, as suggested on http://www.inf.tu-dresden.de/index.php?node_id=1514&ln=en I get this: $ cvs -d:pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs login Logging in to :pserver:guest@os.inf.tu-dresden.de:2401/home/remote-cvs CVS password: <guest> cvs [login aborted]: connect to os.inf.tu-dresden.de(141.76.48.99):2401 failed: Connection refused Does anyone know why this may be? Thank you very much, Jorge

2 1

Re: Kernel configuration missing ?
by Adam Lackorzynski 17 May '07

17 May '07

On Thu May 17, 2007 at 09:34:32 +0000, chenggh wrote: > On Wednesday 16 May 2007 21:57, you wrote: > > Hi, > > > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > > I download the newest source page neened for L4Linux and Fiasco. The > > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > > the compilations of fiasco kernel and l4 packages is ok and when i > > > enter the l4linux I input make menuconfig. There are some errors like > > > this: > > > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > > configuration missing. Stop. > > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > > > It's true that there's this irritating message but it should generally > > work. Does for me like this: > > > > $ cd l4linux-2.6 > > $ mkdir /tmp/builddir > > $ make O=/tmp/builddir menuconfig > > ... configure path to l4-obj-dir etc... > > $ make O=/tmp/builddir > There is still the problem in my machine like this: > > root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > configuration missing. Stop. > make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 > make: *** [menuconfig] Error 2 This works just fine for me: l4linux-2.6$ mkdir build l4linux-2.6$ make O=./build/ menuconfig .../l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc GEN /path/to/l4linux-2.6/build/Makefile HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/lxdialog/checklist.o ... l4linux-2.6$ make O=./build/ L4 source directory: /path/to/l4 make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN l4linux-2.6/build/Makeconf.l4conf GEN l4linux-2.6/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-i386 -> asm/l4x symlink ... As said, I'll try to fix the error message inbetween. Maybe it's the make version. Which version are you using? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 17 May '07

17 May '07

On Wednesday 16 May 2007 21:57, you wrote: > Hi, > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > I download the newest source page neened for L4Linux and Fiasco. The > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > the compilations of fiasco kernel and l4 packages is ok and when i > > enter the l4linux I input make menuconfig. There are some errors like > > this: > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > configuration missing. Stop. > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > It's true that there's this irritating message but it should generally > work. Does for me like this: > > $ cd l4linux-2.6 > $ mkdir /tmp/builddir > $ make O=/tmp/builddir menuconfig > ... configure path to l4-obj-dir etc... > $ make O=/tmp/builddir There is still the problem in my machine like this: root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 make: *** [menuconfig] Error 2 I think it is possible to miss some configuration files. But I don't know which file is missing. Thank you. cheng

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 16 May '07

16 May '07

Hi, On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > I download the newest source page neened for L4Linux and Fiasco. The L4Dir is > dice/ kernel/ l4/ l4linux-2.6/ > the compilations of fiasco kernel and l4 packages is ok and when i enter the > l4linux I input make menuconfig. There are some errors like this: > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > configuration missing. Stop. > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 It's true that there's this irritating message but it should generally work. Does for me like this: $ cd l4linux-2.6 $ mkdir /tmp/builddir $ make O=/tmp/builddir menuconfig ... configure path to l4-obj-dir etc... $ make O=/tmp/builddir > Former I downloaded the source page by cvs and all of them is ok. But this > time I get it by svn there are some problem. please help me. That shouldn't make a difference. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0