Hi,
I am still trying to run l4linux on top of fiasco. I am running it on top of a console system and configured L4Linux2.6 without any input drivers. Thanks to your suggestion I am loading vmlinuz with a start script.
I can't tell you much, but once booted both serial and console are spammed with
... l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94140 l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94150 l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94160 ...
messages.
Did I forget to configure some kind of memory translation unit?
Here is my grub config:
kernel /bin/svn453/bootstrap -serial modaddr 0x03000000 module /bin/svn453/fiasco -nokdb -nowait -serial -comspeed 115200 -pcsampling -debug -sp 1000000 module /bin/svn453/sigma0 module /bin/svn453/roottask task modname "bmodfs" attached 7 modules module /bin/svn453/dm_phys module /bin/svn453/names --verbose 0 --logsrv logcon module /bin/svn453/events module /bin/svn453/simple_ts --events -t 300 module /bin/svn453/l4io module /bin/svn453/bmodfs module /bin/svn453/l4linux26.cfg module /bin/svn453/libloader.s.so module /bin/svn453/libld-l4.s.so module /bin/svn453/logcon module /bin/svn453/run module /bin/svn453/vmlinuz module /bin/svn453/drops-rd.rd module /bin/svn453/loader --events --fprov=BMODFS run l4linux26.cfg logcon module /bin/svn453/con --nolog vbeset 0x117
Thanks for your help.
Kind Regards, Stefan
Hi,
On Tue Aug 04, 2009 at 11:11:15 +0200, Stefan Kögel wrote:
I am still trying to run l4linux on top of fiasco. I am running it on top of a console system and configured L4Linux2.6 without any input drivers. Thanks to your suggestion I am loading vmlinuz with a start script.
I can't tell you much, but once booted both serial and console are spammed with
... l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94140 l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94150 l4lx | l4env_phys_to_virt: Could not translate phys. address 0x94160 ...
messages.
Did I forget to configure some kind of memory translation unit?
No but I'd guess that there's some driver in the Linux that causes this. Maybe you could start from the x86-ux or x86-native defconfigs and see if the same happens?
Adam
l4-hackers@os.inf.tu-dresden.de