Re: Boot Fiasco <at> ARM on QEMU

Dear Adam,

On Fri, Sep 26, 2008 at 1:56 AM, Adam Lackorzynski
<adam <at> os.inf.tu-dresden.de> wrote:
> Hi,
>
> On Wed Sep 24, 2008 at 22:13:10 +0800, Tsai, Tung-Chieh wrote:
>>   Thanks for your help. I found that my problem is that I thought I
>> could boot kernel image 'fiasco' independently without other things.
>> Now I make the package under '.../l4/' and use `.../l4/pkg/bootstrap`
>> to pack kernel image, run it on qemu, it has the following assertion
>> failed message :
>>
>> Hello from Startup::stage2
>>
>> Assertion failed: 'prev_next'
>>   in
>>   /path/to/tuods/source/snapshot/kernel/fiasco/src/kern/buddy_alloc.cpp:34
>>   at f0004da8
>>
>> Could you please tell me what does this means ?
>
> That likely means that the system memory size is not configured
> properly. The l4-config system contains a parameter to configure the
> platform memory size. It's called RAM_SIZE_MB. Is that set properly?
>

Thanks your help, I found I use default QEMU setting of integratorcp,
which is not the same to what l4 set.

Re: Boot Fiasco <at> ARM on QEMU

Hi,

On Thu Oct 09, 2008 at 01:47:42 +0800, Tsai, Tung-Chieh wrote:
> On Fri, Sep 26, 2008 at 1:56 AM, Adam Lackorzynski
> <adam <at> os.inf.tu-dresden.de> wrote:
> > Hi,
> >
> > On Wed Sep 24, 2008 at 22:13:10 +0800, Tsai, Tung-Chieh wrote:
> >>   Thanks for your help. I found that my problem is that I thought I
> >> could boot kernel image 'fiasco' independently without other things.
> >> Now I make the package under '.../l4/' and use `.../l4/pkg/bootstrap`
> >> to pack kernel image, run it on qemu, it has the following assertion
> >> failed message :
> >>
> >> Hello from Startup::stage2
> >>
> >> Assertion failed: 'prev_next'
> >>   in
> >>   /path/to/tuods/source/snapshot/kernel/fiasco/src/kern/buddy_alloc.cpp:34
> >>   at f0004da8
> >>
> >> Could you please tell me what does this means ?
> >
> > That likely means that the system memory size is not configured
> > properly. The l4-config system contains a parameter to configure the
> > platform memory size. It's called RAM_SIZE_MB. Is that set properly?
> >
> 
> Thanks your help, I found I use default QEMU setting of integratorcp,
> which is not the same to what l4 set.

Re: Boot Fiasco <at> ARM on QEMU

Dear Adam,

On Fri, Oct 10, 2008 at 5:34 AM, Adam Lackorzynski
<adam <at> os.inf.tu-dresden.de> wrote:
> The DEFAULT_RELOC of hello? Was the error an overlap?

The DEFAULT_RELOC of roottask, an overlap error as follow :

  #05: loading "hello"
       from [0206e000-0207b268] to [00140000-00144474]
  Roottask: cannot load binary because address at 00140000 not free
    for unkown reason

> What do you mean 'log with all test'?

I build with `E=log`, the entry describe in
`.../l4/pkg/bootstrap/server/src/modules.list `

Than I run it on qemu, execute all the test on it.

It's why I feel strange, since the test on `E=log` passed, why does
logserver fail to register nameserver ?

> Does something change if you leave out programs from the end, e.g.
> loader, bmodfs include its modules, l4io?

I didn't see any other output about loader, bmodfs, etc ... , is there any
other way to observe it, e.g using jdb ?

--

-- 

Re: Boot Fiasco <at> ARM on QEMU

Dear Adam,

  Beside, the whole output on running l4linux on qemu are :

$ qemu-system-arm -kernel /path/build/l4/bin/arm_int/bootstrap.image
-M integratorcp -nographic -serial stdio -m 256

L4 Bootstrapper
  Memory size is 256MB
  mod00: 0140d000-0144bb78: fiasco
  mod01: 0144c000-0145c174: sigma0
  mod02: 0145d000-0147e6ac: roottask
  mod03: 0147f000-014911a4: names
  mod04: 01492000-014a32fc: log
  mod05: 014a4000-014c51a4: dm_phys
  mod06: 014c6000-014da2fc: simple_ts
  mod07: 014db000-015061a4: l4io
  mod08: 01507000-015301a4: bmodfs
  mod09: 01531000-0155ff40: libloader.s.so
  mod10: 01560000-01574540: libld-l4.s.so
  mod11: 01575000-01577468: shared_test
  mod12: 01578000-017af240: vmlinuz
  mod13: 017b0000-027b0000: rd
  mod14: 027b0000-027b007e: l4linux.cfg
  mod15: 027b1000-027eb1a4: loader
  move modules to 2000000 with offset bf3000
  move module 16 start 27b1000 -> 33a4000
  move module 15 start 27b0000 -> 33a3000
  move module 14 start 17b0000 -> 23a3000
  move module 13 start 1578000 -> 216b000

Re: DDEkit for Linux2.6 from svn

Hi,

I would like to know from where I can get the DDEKit (Device Driver
Environment) for Linux2.6 from svn?
http://wiki.tudos.org/DDE/DDEKit

>From the svn documentation:
http://www.inf.tu-dresden.de/index.php?node_id=1735&ln=en

./repomgr modules lists the following: dice, fiasco, hello, l4env,
l4linux-2.6-env.

Thanks!

SK

--
Shakthi Kannan
http://www.shakthimaan.com

Re: DDEkit for Linux2.6 from svn

Hi,

> I would like to know from where I can get the DDEKit (Device Driver
> Environment) for Linux2.6 from svn?
> http://wiki.tudos.org/DDE/DDEKit
> 
>>From the svn documentation:
> http://www.inf.tu-dresden.de/index.php?node_id=1735&ln=en
> 
> ./repomgr modules lists the following: dice, fiasco, hello, l4env,
> l4linux-2.6-env.

DDE is not part of any of these modules. Doing "svn up dde" in l4/pkg
will do the trick.

Regards,
Bjoern

Hardware detection in L4

Hi at all,

I am working on a project that makes it necessary to have some agent
application with hardware detection capabilities.

Therefore my question is, if there is any L4 library or kernel interface
that can be used to get information on detected and hot-plugged hardware
in the system.
Best would be a solution that provides callbacks to get informed on any
change in the hardware automatically.

Thanks in advance!

Regards,
Gianfranco

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

Problems with l4linux

Hi all,
I have Mandriva 2008.0 distribution.
I compiled l4linux and got some problems with it. Maybe anyone knows what's wrong with the configuration?
First, the problem is with X11 (X.Org), when I'm launching X11 by typing startx, there is an error 

tal server error:
xf86EnableIOPorts: failed to set IOPL for I/O (Invalid argument)

I compiled in the L4con/DOpE stubs but X11 don't work. On ordinary Linux Kernel it works well. I tried to use
a fbdev driver in X.Org.

Also, each time I access /dev/null, the message is displayed that access is denied.

Third, I got PCMCIA GPRS modem to power up and register in a GSM network (power Led is on and Network 
available Led is flashing). This modem appears to an OS like ordinary PCMCIA comm port, but minicom does 
not react to AT commands, though, PCMCIA stack detected the card, but did not enabled ttyS0 and ttyS1 
ports on the card. It seems I loaded all PCMCIA stack modules and hotplug support. Except for serial_cs
module 
which warns that "no high memory space available!". When I did configuring the linux Kernel, the build
system did not 
give me a possibility to specify high memory up to 4 Gb. What should I do with it?

Fourth, I thied a wifi MiniPCI card Intel PRO/Wireless 2200 to get working in l4linux. I tried to load all
wifi 
modules like in ordinary Linux kernel on the same machine, but when I trying to make the network interface 
up, it says that device does not exists. When I check dmesg output, there is a message that a firmware could 
not be loaded. I unchecked the checkbox "Prevent the firmware from being built" and "Do not enable drivers 
which require firmware loading" and it seems that firmware must be built. The firmware is in /lib/firmware
and is 
called ipw2200-bss.fw. What should I do to get firmware loaded?

DDEkit for Linux2.6 from svn

Hi,

I would like to know from where I can get the DDEKit (Device Driver
Environment) for Linux2.6 from svn?
http://wiki.tudos.org/DDE/DDEKit

>From the svn documentation:
http://www.inf.tu-dresden.de/index.php?node_id=1735&ln=en

./repomgr modules lists the following: dice, fiasco, hello, l4env,
l4linux-2.6-env.

Thanks!

SK

--

-- 
Shakthi Kannan
http://www.shakthimaan.com

Re: DDEkit for Linux2.6 from svn

Hi,

--- On Tue, Oct 14, 2008 at 12:48 PM, Björn Döbel
<doebel <at> os.inf.tu-dresden.de> wrote:
| DDE is not part of any of these modules. Doing "svn up dde" in l4/pkg
| will do the trick.
\--

Thanks! I got the latest dde from svn. I moved to l4/ parent directory and did:

  make O=/path/to/build config
  make O=/path/to/build

and it starts building dde components, and fails at:

=== ERROR OUTPUT ===

/home/foo/tudos/l4/pkg/dde/linux26/examples/ne2k/main.c:4:55: error:
l4/ore/ore-types.h: No such file or directory
/home/foo/tudos/l4/pkg/dde/linux26/examples/ne2k/main.c: In function
'net_rx_handle':
/home/foo/tudos/l4/pkg/dde/linux26/examples/ne2k/main.c:56: warning:
implicit declaration of function 'LOG_MAC'
make[6]: *** [main.o] Error 1
make[5]: *** [/home/foo/tudos/l4/build/pkg/dde/linux26/examples/ne2k/OBJ-x86_586-l4v2]
Error 2
make[4]: *** [ne2k] Error 2
make[3]: *** [examples] Error 2
make[2]: *** [linux26] Error 2
make[1]: *** [dde.bin] Error 2