On Sun Jul 22, 2007 at 01:00:44 +0800, kashin Lin wrote:
2007/7/21, kashin Lin kashin08@gmail.com:
2007/7/21, Adam Lackorzynski adam@os.inf.tu-dresden.de:
On Fri Jul 20, 2007 at 15:54:06 +0800, kashin Lin wrote:
when i runed l4linux on fiasco-UX by "./lx con", it stoped after following messages:
We need to find out by adding earlyprintk=keep to the L4Linux kernel command line. Then there should be more text.
Here are the results after adding "earlyprintk=keep" :
l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (kashin08@kashin08-desktop) (gcc version 4.1. l4lx : 2 (Ubuntu 4.1.2-0ubuntu4)) #1 Fri Jul 20 12:14:47 CST 2007 l4lx | Binary name: vmlinuz26.ux l4lx | Kernel command line (8 args): mem=44M earlyprintk=keep root=1:0 load_ l4lx : ramdisk=1 ramdisk_size=16384 l4env_rd=../../../test_lx/rd1 panicblink l4lx : =0 lang=us l4lx | Image: 00400000 - 00727000 [3228 KiB]. l4lx | Areas: Text: 00400000 - 00644000 [2320kB] (a bit longer) l4lx | Data: 00644000 - 0065d2b4 [100kB] l4lx | Initdata: 00660000 - 0069a100 [232kB] l4lx | BSS: 0069c000 - 00724860 [546kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 00400000 size = 3305472 l4lx | sec-w-init: virt: 0x00400000 to 0x00726fff [3228 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 3, 3305472 Bytes l4lx | sec-w-init: 1: Phys: 0x0054e000 to 0x0073d000, Size: 2027520 l4lx | sec-w-init: 2: Phys: 0x0e843000 to 0x0e961000, Size: 1171456 l4lx | sec-w-init: 3: Phys: 0x00fe9000 to 0x01003000, Size: 106496 l4lx | l4env_linux_startup thread 4. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 44MB l4lx | Main memory: virt: 0x00800000 to 0x033fffff [45056 KiB] l4lx | Main memory: Number of physical regions: 1, 46137344 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x04400000, Size: 46137344 l4lx | Filling lower ptabs... l4lx | Done (1205 entries). l4lx | l4env_rd_path: ../../../test_lx/rd1 l4lx | Loading: ../../../test_lx/rd1 fuxfprov| open "../../../test_lx/rd1" by F.04 con | Character size is 8x14, font has 256 characters con | VESA reports 640x480@16 1280bpl (0000) [4096kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | Found Fiasco-UX con | Found VHW descriptor, provider is 7167 con | Mapped I/O UX video mem c0000000 => 00400000 [4096kB] via l4io con | Using MMXEXT for colorspace transform con | L4INPUT Fiasco-UX mode activated con | Input memory page mapped to 0x00c00000 con | Running as C.02. Video mode is 640x480@16. con | vc_loop(): vc[1] running as C.05 con | vc[1] 640x480@16, bpl:1280, gmode:0x15, evprt:E.03 save:0 run | contxt_init(): 640x462, cols:80, lines:33, sb_lines:1033 l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 03400000 to 04400000 [16384KiB] [ 0.000000] Linux version 2.6.21-l4 (kashin08@kashin08-desktop) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 Fri Jul 20 12:14:47 CST 2007 [ 0.000000] CPU: Vendor unknown, using generic init. [ 0.000000] CPU: Your system may be unstable. [ 0.000000] dm_phys: 0000000000800000 - 0000000003400000 (usable) [ 0.000000] 44MB memory available. [ 0.000000] INITRD: 03400000 - 04400000 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0 -> 512 [ 0.000000] Normal 512 -> 13312 [ 0.000000] early_node_map[1] active PFN ranges [ 0.000000] 0: 0 -> 13312 [ 0.000000] Allocating PCI resources starting at 10000000 (gap: 03400000:fcc00000) [ 0.000000] Built 1 zonelists. Total pages: 13208 [ 0.000000] Kernel command line: mem=44M earlyprintk=keep root=1:0 load_ramdisk=1 ramdisk_size=16384 l4env_rd=../../../test_lx/rd1 panicblink=0 lang=us [ 0.000000] Initializing CPU#0 [ 0.000000] PID hash table entries: 256 (order: 8, 1024 bytes) [ 0.000000] Detected 2010.311 MHz processor. [ 1236.204905] keeping early console l4lx | panic: going to sleep forever, bye
Can you please post your .config?
=================================================================
when i runed l4linux on fiasco-UX by "./lx dope", it stoped after following messages:
Check out l4/pkg/dmon from svn and compile.
when i compile dmon, it says: l4/term_server/vt100.h¡Gno such file or directory
did i loss other packages? how to get them?
why are those packages not downloaded together when i download l4-env from svn?
Because not everything is L4Env.
vt100.h is in l4vfs/term_server/include, so you should also checkout the
l4vfs package (which might again require other stuff ...)
it says "Failed to open file: ../../../build/bin/x86_586/l4v2/../../../build/bin/x86_586/l4v2/launchpad" this time.
what packages should i download? it seems there is no package named "launchpad".
That's a mistake, I fixed the lx script accordingly. Should be out soon. './lx con' should work nevertheless.
2007/7/15, Adam Lackorzynski adam@os.inf.tu-dresden.de:
On Sun Jul 15, 2007 at 19:18:19 +0800, kashin Lin wrote:
thanks for answerning.
so you means if the multimedia application (a normal user application) can run in host linux, it can also run in l4linux on fiasco-UX?
Basically yes, leaving out the practical issues really getting this
to
work.
2007/7/15, Adam Lackorzynski < adam@os.inf.tu-dresden.de>: > > >On Sun Jul 15, 2007 at 15:26:54 +0800, kashin Lin wrote: >> Hi~ >> >> according to http://os.inf.tu-dresden.de/fiasco/ux/status.shtml, >> it says one of the differences between native fiasco and
fiasco-UX is
:
>> Port I/O and I/O flexpages. >> >> so is it possible to run a multimedia application in l4linux on >fiasco-UX? >> (ex: jpeg, mp3 ... etc) >> >> this kind of application seems that it could access hardware
directly(
>ex: >> speaker or monitor )? > >Fiasco-UX and all the L4 programs that are run in Fiasco-UX are
normal
>Linux user applications and thus have not more rights than any
other
>Linux program you are running. Directly accessing hardware is not >possible with Fiasco-UX, in the same way it's not possible to
access
>hardware directly as a Linux program. I hope this clarifies the >question. >
Adam