Hello
Is there any good Documentation on RMGR available ? I need to know how I can load modules into specific areas of memory, because I got some overlapping module problems, almost the same as mentioned in the list before. The solution with l4ka GRUB using the feature modaddr doesn`t work for me, cause I use a different architecture (Athlon K7, Reiserfs).
RMGR: loading (hd 2,0)/sigma0 RMGR: loading kernel (hd 2,0)/main -nokdb RMGR:overlaps:00300000 - 0030239c: (hd 2,0)/main -nokdb RMGR: 00100000 - 001be980 module 02 : 00231000 - 0023256c: (hd 2,0)/rmgr.cfg.linux module 03: 0023200 - 0032eb14: (hd 2,0)/glinux.gz root=/dev/sda3 overlaps = 1, mem_high = 0x0fff0000 RMGR: overlapping modules
#!rmgr
### this is an example RMGR config file
### first, some global settings
# small address spaces have a size of 64 MB small_space_size 0x04000000
# wait for key press after initialization bootwait
### configuration for Sigma0 and RMGR follows
# NOTE: it's generally useless to specify any resource allocation # constraints for Sigma0 and RMGR here: most will be ignored because # these tasks statically allocate all of their resources. That's why # we only specify bootstrap parameters here.
task sigma0 boot_priority 100
task rmgr boot_priority 100 # enable next line if you want RMGR to run in small address space # 3 #boot_small 3
### configuration for boot modules follows
task modname "glinux" # make sure this entry # corresponds to a Linux server boot_small 2 # small address space # 2 boot_priority 100 boot_mcp 0x90 # maximum controlled priority log_mcp 0x90 # logical maximum controlled priority # -- useful if "boot_mcp 0" child max 512 in [10, 1023] # at most 512 child tasks in that range memory in [0, 0x02000000] # use only lower 32 MB RAM high_memory in [0xc0000000, 0xffffffff] # use only hi memory in that range small in [1,3] # allow these small address # spaces to be allocated # enable next line if you want to disallow allocation if IRQs 3 and 4 # (IRQs for serial lines COM2 and COM1) # irq mask 0xffffffe7
end
menu.1st:
gfxmenu (hd2,0)/message color white/blue black/light-gray default 0 timeout 8
title linux kernel (hd2,0)/vmlinuz root=/dev/sda3 vga=791 initrd (hd2,0)/initrd title Linux other root (hd1,0) makeactive chainloader +1 title floppy root chainloader +1 title failsafe kernel (hd2,0)/vmlinuz.shipped root=/dev/sda3 ide=nodma apm=off acpi=off vga=normal nosmp maxcpus=0 disableapic 3 initrd (hd2,0)/initrd.shipped title Fiasco + "hello world" root (hd2,0) kernel (hd2,0)/rmgr-fiasco -sigma0 module (hd2,0)/main-fiasco -nokdb module (hd2,0)/sigma0-fiasco #module (hd2,0)/glinux root=/dev/sda3 module (hd2,0)/hello-fiasco title L4-Linux #root (hd2,0) kernel (hd2,0)/rmgr -configfile -sigma0 module (hd2,0)/main -nokdb #modaddr=0x03000000 module (hd2,0)/sigma0 module (hd2,0)/rmgr.cfg.linux module (hd2,0)/glinux root=/dev/sda3 no-scroll module (hd2,0)/hello
On Sun, Feb 23, 2003 at 05:47:18PM +0100, Daniel Koch wrote:
Hello
Is there any good Documentation on RMGR available ? I need to know how I can load modules into specific areas of memory, because I got some overlapping module problems, almost the same as mentioned in the list before. The solution with l4ka GRUB using the feature modaddr doesn`t work for me, cause I use a different architecture (Athlon K7, Reiserfs).
I had the same problems once. What I did was relink the offending modules to different addresses, by changing the makefiles.
Hope this helps, Jacob
Hi, Yes that's usually the first thing you do (and the first you forget for the next time).
You can locate the modules at a specific address using: modaddr=0x12345678
Your menu.lst entry would then look something like:
title=Pistachio kernel=(nd)/tftpboot/rmgr.l4ka -sigma0 -roottask modaddr=0x03000000 module=(nd)/tftpboot/ia32-kernel module=(nd)/tftpboot/sigma0 module=(nd)/tftpboot/what_ever_you_want_to_have_here
Anyhow: Frank Mehnert's homepage at Dresden seems to be the current source for the up to date Grub and related documentation. Try: os.inf.tu-dresden/~fm3/grub.html
Ciao Marcus
-----Original Message----- From: l4-hackers-admin@os.inf.tu-dresden.de [mailto:l4-hackers- admin@os.inf.tu-dresden.de] On Behalf Of Jacob Gorm Hansen Sent: Sunday, February 23, 2003 6:09 PM To: Daniel Koch Cc: l4-hackers@os.inf.tu-dresden.de Subject: Re: RMGR Documentation needed
On Sun, Feb 23, 2003 at 05:47:18PM +0100, Daniel Koch wrote:
Hello
Is there any good Documentation on RMGR available ? I need to know
how I
can
load modules into specific areas of memory, because I got some
overlapping
module problems, almost the same as mentioned in the list before.
The
solution with l4ka GRUB using the feature modaddr doesn`t work for
me,
cause
I use a different architecture (Athlon K7, Reiserfs).
I had the same problems once. What I did was relink the offending modules to different addresses, by changing the makefiles.
Hope this helps, Jacob
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
My problem is that I don`t want to use this specially designed GRUB for my purpose. I don`t have a network to boot (only floppy or Reiserfs) from, so it seems to me that adjusting the makefiles would be the solution for me. Unfortunately I don`t know how exactly to adjust these files so that they`re correctly linked. Perhaps anyone can help me there ?
Daniel
Am Montag, 24. Februar 2003 07:59 schrieben Sie:
Hi, Yes that's usually the first thing you do (and the first you forget for the next time).
You can locate the modules at a specific address using: modaddr=0x12345678
Your menu.lst entry would then look something like:
title=Pistachio kernel=(nd)/tftpboot/rmgr.l4ka -sigma0 -roottask modaddr=0x03000000 module=(nd)/tftpboot/ia32-kernel module=(nd)/tftpboot/sigma0 module=(nd)/tftpboot/what_ever_you_want_to_have_here
Anyhow: Frank Mehnert's homepage at Dresden seems to be the current source for the up to date Grub and related documentation. Try:
os.inf.tu-dresden/~fm3/grub.html
Ciao Marcus
-----Original Message----- From: l4-hackers-admin@os.inf.tu-dresden.de [mailto:l4-hackers- admin@os.inf.tu-dresden.de] On Behalf Of Jacob Gorm Hansen Sent: Sunday, February 23, 2003 6:09 PM To: Daniel Koch Cc: l4-hackers@os.inf.tu-dresden.de Subject: Re: RMGR Documentation needed
On Sun, Feb 23, 2003 at 05:47:18PM +0100, Daniel Koch wrote:
Hello
Is there any good Documentation on RMGR available ? I need to know
how I
can
load modules into specific areas of memory, because I got some
overlapping
module problems, almost the same as mentioned in the list before.
The
solution with l4ka GRUB using the feature modaddr doesn`t work for
me,
cause
I use a different architecture (Athlon K7, Reiserfs).
I had the same problems once. What I did was relink the offending modules to different addresses, by changing the makefiles.
Hope this helps, Jacob
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Mon, 2003-02-24 at 11:44, Daniel Koch wrote:
My problem is that I don`t want to use this specially designed GRUB for my purpose. I don`t have a network to boot (only floppy or Reiserfs) from, so it seems to me that adjusting the makefiles would be the solution for me. Unfortunately I don`t know how exactly to adjust these files so that they`re correctly linked. Perhaps anyone can help me there ?
I had the same problem/attitude/attitude problem once.
In the Makefile, look for something like this:
$(PROGS): %: %.o $(LINK_MESSAGE) $(VERBOSE)$(LD) -N -Ttext 0x400000 -o $@ $(CRT0) $^ $(LIBS) $(CRTN)
Then change the number after -Ttext to the appropriate address.
Jacob
On Monday 24 February 2003 11:44, Daniel Koch wrote:
My problem is that I don`t want to use this specially designed GRUB for my purpose. I don`t have a network to boot (only floppy or Reiserfs) from, so it seems to me that adjusting the makefiles would be the solution for me. Unfortunately I don`t know how exactly to adjust these files so that they`re correctly linked. Perhaps anyone can help me there ?
You only have to make sure that the binaries you want to load don't overlap mutual and that they don't overlap rmgr, sigma0 or the kernel. So the best is to link the binaries to addresses above 8MB (0x00800000). Modules must not overlap because rmgr sees any memory one-by-one mapped.
Frank
l4-hackers@os.inf.tu-dresden.de