The ultimate HOW-TO
Adam Lackorzynski
adam at os.inf.tu-dresden.de
Thu Sep 6 09:55:00 CEST 2007
On Wed Sep 05, 2007 at 08:12:43 -0700, ComputerScienceStudent wrote:
> title L4Linux -Linux on L4-
> root (hd0,4)
> kernel /L4Linux_binary/build/l4/bin/x86_586/bootstrap -serial root=/dev/sda5
> -modaddr 0x06000000
> module /L4Linux_binary/build/fiasco_ia32/main -nokdb -serial_esc
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/sigma0
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/roottask task modname
> "bmodfs" attached 4 modules
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/names --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/log --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/dm_phys --isa=0x00800000 -v
> --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/simple_ts -t 300 --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/rtc --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/l4io --events
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/l4dope --menubar
> --transparency
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/loader --fprov=BMODFS
> linux26.cfg
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/bmodfs
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/linux26.cfg
> module /L4Linux_binary/build/linux/vmlinuz26
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/libloader.s.so
> module /L4Linux_binary/build/l4/bin/x86_586/l4v2/libld-l4.s.so
> vbeset 0x117
>
> FIRST: ..because time problems I'll use the binaries from OpenTC: but how to
> have a console without Dope?
You can also use plain VGA console, without DOpE or any other graphical
thing.
> The idea of dropping the l4dope line seems stupid.. (*) can you correct the
> previous lines?
It's not stupid, it's the thing to do.
> Using the "old" l4dope (compiled by me weeks ago) the error on screen is:
>
> l4dope: Did not find the VBE info block in multiboot info. GRUB has to set
> the
> l4dope: video mode with the vbeset command.
The only thing I can say is that there might be some incompatibilities
in the different binaries you use.
> Note that I use this command.. so:
> a. If I use Dope, how to repair the error?
> b. If I don't use it.. (*)
>
> SECOND: To do the image I'd use the command that you send me:
>
> cd /tmp/fs mkisofs "$@" -R -b boot/grub/stage2_eltorito \
> -no-emul-boot -boot-load-size 4 -boot-info-table \
> -hide-rr-moved \
> -J -joliet-long \
> -o /tmp/iso.iso
>
> ..but there are errors because I don't have the stage2_eltorito file:
Yes, this one is in my GRUB version, because it also has the
"boot-from-CD" patch.
> - The first time I've typed:
>
> linux-Dell:/L4Linux_binary # mkisofs "$@" -R -b /boot/grub/stage2_eltorito
> \
> -no-emul-boot -boot-load-size 4 -boot-info-table \
> -hide-rr-moved \
> -J -joliet-long \
> -o /tmp/immagine_L4Linux.iso
>
> ..and the output was:
>
> INFO: UTF-8 character encoding detected by locale settings.
> Assuming UTF-8 encoded filenames on source filesystem, use -input-charset
> to override.
> mkisofs: Missing pathspec.
> Usage: mkisofs [options] file...
> Use mkisofs -help to get a list of valid options.
Yep, I think a had the final '.' at the end of the command.
> - The second time:
>
> linux-Dell:/ # mkisofs "$@" -R -b /boot/grub/stage2_eltorito \
> -no-emul-boot -boot-load-size 4 -boot-info-table \
> -hide-rr-moved \
> -J -joliet-long \
> -o /tmp/immagine_L4Linux.iso L4Linux_binary
>
> ..and, then:
>
> INFO: UTF-8 character encoding detected by locale settings.
> Assuming UTF-8 encoded filenames on source filesystem, use -input-charset
> to override.
> Using EVENT000.;1 for L4Linux_binary/build/l4/bin/x86_586/l4v2/events_demo3
> (events_demo2)
> Using EVENT001.;1 for L4Linux_binary/build/l4/bin/x86_586/l4v2/events_demo2
> (events_demo1)
> Using SNDDR000.;1 for
> L4Linux_binary/build/l4/bin/x86_586/l4v2/snddrv-es1371 (snddrv-es1370)
> Using L4RM_000.;1 for L4Linux_binary/build/l4/bin/x86_586/l4v2/l4rm_testcow
> (l4rm_test)
> .
> .
> .
> Using LIBC_00E.A;1 for
> L4Linux_binary/build/l4/lib/x86_586/l4v2/libc_be_self_mem.a (libc_be_mmap.a)
> Using LOADE000.CON;1 for
> L4Linux_binary/L4Linux_demo_binary/config/loader_lx_drv.conf
> (loader_lx.conf)
> Using LOADE001.CON;1 for
> L4Linux_binary/L4Linux_demo_binary/config/loader_lx.conf
> (loader_lx_ore.conf)
> call to search_tree_file with an absolute path, stripping initial path
> separator.
> Hope this was intended...
> mkisofs: Uh oh, I cant find the boot image '/boot/grub/stage2_eltorito' !
>
> For now it's important that L4Linux starts, then we'll make the iso-creation
For your convenience I put a stage2_eltorito to
http://os.inf.tu-dresden.de/~adam/grub/0.97/stage2_eltorito
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