grub-0.97 problem
Adam Lackorzynski
adam at os.inf.tu-dresden.de
Wed Jan 4 22:20:44 CET 2006
Hi,
On Tue Jan 03, 2006 at 19:29:53 +0100, Der Herr Hofrat wrote:
> Not to far into l4 yet - so this is most likely quite basic.
> trying to get L4Linux-2.6 to boot from hard disk. To get it to
> boot the docs say to use the modified grub - first shot was the
> grub cvs version - but that does not compile with gcc 3.3.6 (looks
> like it compiles up to gcc 3.2.X only - so next show was the
> patched grub-0.97 with the diff from ~adam/grub/ (patch < grub-0.97-os.diff)
> recompiled (./configure, make) and installed it(make install, grub-install
> /dev/hda) - booting gives me:
>
> GNU GRUB version 0.97-os.1 (640K lower / 228288K upper memory)
>
> followed by the menu - so I guess it worked. But if I use any of the
> features (i.e. set VAR := VAL, reference as $(VAL) ) it does not seem
> to know of these extensions ?
If it does not complain about 'set' being an unknown command then it
should know it.
> the following is a part of my menu.lst:
>
>
> <snip>
> set P := (hd0,1)/usr/src/l4/l4/bin/x86_586/l4v2/
> set C := (hd0,1)/usr/src/l4/cfg
> set L := (hd0,1)/usr/src/l4/l4linux/
>
> # For booting GNU/Linux
> title GNU/Linux
> kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 read-only
>
> title The "hello" program
> kernel $(P)/rmgr -sigma0
> module $(P)/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0
> module $(P)/sigma0
> module $(P)/hello
>
> title The "hello2" program
> kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0
> module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0
> module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0
> module /usr/src/l4/l4/bin/x86_586/l4v2/hello
> <snip>
>
>
> The target "hello" fails with
>
>
> <snip>
> kernel $(P)/rmgr -sigma0
>
> Error 1: Filename must be either an absolute pathname or blocklist
>
> Press any key to continue...
> <snip>
>
>
> The target "hello2" loads as expected (it fails for other reasons later
> though)
>
>
> <snip>
> kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0
> [Multiboot-elf, <0x100000:0x20e40:0x0>, <0x121e40:0x483c:0xa4784>, shtab=0x1
> cb2f8, entry=0x100000]
> module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comsp
> eed 115200 -comport 0
> [Multiboot-module @ 0x20f000, 0x56ea4 bytes]
> module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0
> [Multiboot-module @ 0x266000, 0x10211 bytes]
> module /usr/src/l4/l4/bin/x86_586/l4v2/hello
> [Multiboot-module @ 0x277000, 0xa884 bytes]
> <snip>
>
>
> I'm excluding hardware problems as the demo-CD version works fine - so its
> something thats wrong in this menu.lst ?
I do not see anything wrong there. I have that similarily in my
menu.lsts.
> I also tried removing the (hd0,1) from the settings as I did not have that
> in the hardcoded modules - so using:
> set P := /usr/src/l4/l4/bin/x86_586/l4v2/
> but that did not change anything.
Yes, that are pure string based substitutions.
> regarding booting of linux - with all paths absolute due to the above problem:
>
>
> <menu.lst>
> title L4Linux 2.6
> kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 task modname "bmodfs" module module module module module module boot_priority 0xA8
> modaddr 0x02000000
> module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -serial_esc -comspeed 115200 -comport 0
> module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0
> module /usr/src/l4/l4/bin/x86_586/l4v2/names
> module /usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0
> module /usr/src/l4/l4/bin/x86_586/l4v2/dm_phys
> module /usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380
> module /usr/src/l4/l4/bin/x86_586/l4v2/rtc
> module /usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq
> module /usr/src/l4/l4/bin/x86_586/l4v2/bmodfs
> module /usr/src/l4/l4/bin/x86_586/l4v2/libloader.s.so
> module /usr/src/l4/cfg/run.bmodfs.cfg
> module /usr/src/l4/l4/bin/x86_586/l4v2/run
> module /usr/src/l4/l4linux-2.6/vmlinuz26
> module /usr/src/l4/cfg/l4linux26.cfg
> module /usr/src/l4/l4/bin/x86_586/l4v2/l4exec
> module /usr/src/l4/l4/bin/x86_586/l4v2/con --l4io
> module /usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg
> <snip>
>
>
> I get the following output when booting:
>
>
> <snip>
> Booting 'L4Linux 2.6 '
>
> #13: loading "/usr/src/l4/l4/bin/x86_586/l4v2/con --l4io"
> from 033ef000-0356431e to [ 00b00000-00b4efab 00b4f000-00b61000 ]
> starting at entry 00b00000 via trampoline page code 00060170
> symbols at 0cd3b000-0cd49000 (56kB), lines at 0cd0d000-0cd3b000 (184kB)
> #14: loading "/usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg"
> from 03565000-036344e3 to [ 01300000-013265cb 01327000-01339000 ]
> starting at entry 01300000 via trampoline page code 00061198
> symbols at 0cd07000-0cd0d000 (24kB), lines at 0ccf2000-0cd07000 (84kB)
>
> simplets| Configured for 380 tasks.
> rtc | Date:04.01.2006 Time:11:00:09
>
> RMGR: task a.00 at 00b99c57 is trying to get page 00100000 allocated by task 7
>
> ---------------------------------------------------------IP: 0011c6c1 --double page fault
> (4.00) jdb: ^
> Return reboots, "k" enters L4 kernel debugger...
> Rebooting.
>
> <snip>
>
> Any hint on what I've messed up - also pointers on how to get usable debug
> infos out of such a situation would be appreciated - I did fine some short
> l4_install.notes describing setup of hello + L4Linux but they seem to be a
> bit out of date. My suspicion is that the grub is not correctly patched and
> thus these problems...
This looks like some bug we recently had and which is now fixed (see
also other post here). It has nothing to do with grub. Please update
everything and rebuild. If that does not help it's something else ;)
Adam
--
Adam adam at os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
More information about the l4-hackers
mailing list