When asking questions, it is o.k. to CC me but please ask the list. Perhaps I should put this in my sig?
Nicolas Clapies <[EMAIL PROTECTED]> writes: > hello, > > Is there another way ( something else than elfimage ) to load a kernel > and an initrd with LinuxBIOS ? No. Although it probaly is not needed. Most people just have root on the DOC if they are using that solution. > It seems to be code in the source of linuxBIOS dealing with initrd but I > don't know if it is usable. There may be. It isn't especially hard to do other things... The ELF image is the most flexible though. > I meet problems with elfimage I can't solve > > > > safe_range start 0x10000 end 0x148e0 > > > safe_range Conflicts with range 4 > > > which starts at 0x5048 ends at 0x45048 > > > Bad memory range: [0x0000000000010000, 0x00000000000048e0) > > > > Bad ELF Image > > > > 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > > > 02 00 03 00 01 00 00 00 40 07 01 00 34 00 00 00 > > > a0 50 12 00 00 00 00 00 34 00 20 00 04 00 28 00 > > > 0d 00 0a 00 > > > > I don't really know what it means, any idea ? > > > It is a little terse but it basically means that the ELF Image wants > > to load where linuxBIOS code or data is located. And the ELF loader > > detects this and so refuses to load (instead of getting corruption) > > and weird behavior. > > > The easy trick is to change rambase in linuxBIOS, but other ways > > to keep one image from stomping on the other can work as well. > > > Eric > > Eric, can you explain me how to change the rambase, I've tried to modify > the file ldoption, but I still have the problem. I don't really know how > to solve it. put a rambase directive in your config file (the one passed to NLBConfig.py) Eric
