From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: zoran.stojsavljevic@intel.com
Subject: Re: How to make/compile and link Open Source gnu-2.00 package?
Date: Tue, 23 Jul 2013 20:58:48 +0400 [thread overview]
Message-ID: <20130723205848.228fcdab@opensuse.site> (raw)
In-Reply-To: <67BFA875989E5748A862DFF55409F2A21B0D42E2@IRSMSX104.ger.corp.intel.com>
В Tue, 23 Jul 2013 14:15:49 +0000
"Stojsavljevic, Zoran" <zoran.stojsavljevic@intel.com> пишет:
> Hello to GRUB community,
>
> I continued to explore and read the documentations, and so far I was not able to boot from my GRUB made and install from original GRUB package.
>
> I had all tools installed in /usr/local/sbin (all relevant tools), and then executed the following command:
> grub-install --boot-directory=/media/rootfs/boot --directory=/usr/local/lib/grub/i386-coreboot target=x86_64
>
--directory and --target are mutually exclusive and normally none is
needed - grub-install will autodetect current platform. Only if you
want to install GRUB for platform different from current (e.g. install
GRUB for EFI while running in legacy BIOS mode).
--target means use modules from standard system-wide location and is
normally used after grub is installed. --directory overrides module
location and is usually used before installation.
> It installed for me everything on the target HDD (mounted on /media/rootfs), in the directory /media/rootfs/boot/grub/i386-coreboot (I found there file core.elf, size 105K).
>
> But I also used the following command from the same /usb/local/sbin:
> grub-mkimage --directory=/usr/local/lib/grub/i386-coreboot -o /media/rootfs/boot/grub/core.img -O i386-coreboot
>
> And this command built for me core.img in /media/rootfs/boot/grub of size 27K.
>
> It seems that these two files are identical,
grub-install detects which drivers are needed to access
--boot-directory and adds them to core.img. When using grub-mkimage
directly it is up to you to specify correct drivers.
> till the end of file, where core.img has directory in ascii: /boot/grub
>
> I try to embed both files consecutively in coreboot as payload, in sincere hope to boot to MBR and get the grub> prompt.
>
> But I did not succeed, and my IVB platform stopped at Post Code 0x00F8 (PEI_RECOVERY_PPI_NOT_FOUND) instead stopping to (0x00A3) DXE IDE Detect.
>
Can't help you here, sorry.
> Any clue what I am doing wrong?
>
> Thank you,
> Zoran
> _______
> Most of The Time you should be "intel inside" to be capable to think "out of the box".
>
> From: Stojsavljevic, Zoran
> Sent: Thursday, July 18, 2013 3:48 PM
> To: grub-devel@gnu.org
> Subject: How to make/compile and link Open Source gnu-2.00 package?
>
> Hello,
>
> I would like to set/configure Open Source gnu-2.00 package (or later) in order to be able to support the following configuration on my target HDD:
>
> Directory /boot:
> [zorans@localhost boot]$ ls -al
> total 84580
> drwxr-xr-x. 3 root root 4096 Jul 12 14:27 .
> drwxr-xr-x. 22 root root 4096 Jul 17 15:41 ..
> -rw-------. 1 root root 512 Feb 6 2012 backup_mbr
> lrwxrwxrwx. 1 root root 1 Feb 6 2012 boot -> .
> -rw-r--r--. 1 root root 1236 May 10 2010 boot.readme
> -rw-r--r--. 1 root root 107874 May 20 2010 config-2.6.32.12-0.7-default
> drwxr-xr-x. 2 root root 4096 Mar 27 15:26 grub
> lrwxrwxrwx. 1 root root 28 Feb 6 2012 initrd -> initrd-2.6.32.12-0.7-default
> -rw-r--r--. 1 root root 6514736 Feb 6 2012 initrd-2.6.32.12-0.7-default -rw-r--r--. 1 root root 6667077 Mar 25 23:14 initrd-3.0.13default2 -rw-------. 1 root root 22243322 Mar 27 14:17 initrd-3.4.37-0.27-default -rw-------. 1 root root 22539906 Mar 27 15:17 initrd-3.8.4-0.27-default
> -rw-r--r--. 1 root root 435712 Feb 6 2012 message
> -rw-r--r--. 1 root root 189729 May 20 2010 symsets-2.6.32.12-0.7-default.tar.gz
> -rw-r--r--. 1 root root 495291 May 20 2010 symtypes-2.6.32.12-0.7-default.gz
> -rw-r--r--. 1 root root 178468 May 20 2010 symvers-2.6.32.12-0.7-default.gz
> -rw-r--r--. 1 root root 1651761 May 20 2010 System.map-2.6.32.12-0.7-default -rw-r--r--. 1 root root 2332527 Mar 25 23:14 System.map-3.0.13default2 -rw-r--r--. 1 root root 2041118 Mar 27 14:17 System.map-3.4.37-0.27-default -rw-r--r--. 1 root root 2133832 Mar 27 15:17 System.map-3.8.4-0.27-default -rw-r--r--. 1 root root 3774506 May 20 2010 vmlinux-2.6.32.12-0.7-default.gz
> lrwxrwxrwx. 1 root root 29 Feb 6 2012 vmlinuz -> vmlinuz-2.6.32.12-0.7-default
> -rw-r--r--. 1 root root 3231872 May 20 2010 vmlinuz-2.6.32.12-0.7-default -rw-r--r--. 1 root root 4779280 Mar 25 23:14 vmlinuz-3.0.13default2 -rw-r--r--. 1 root root 3454320 Mar 27 14:17 vmlinuz-3.4.37-0.27-default -rw-r--r--. 1 root root 3635840 Mar 27 15:17 vmlinuz-3.8.4-0.27-default
>
> I would like to have in /boot/grub/ the following (similar) directory on my target HDD as result of the grub-install command (in /usr/local/sbin on my development system):
>
> drwxr-xr-x. 2 root root 4096 Mar 27 15:26 .
> drwxr-xr-x. 3 root root 4096 Jul 12 14:27 ..
> -rw-------. 1 root root 10 Feb 6 2012 default
> -rw-------. 1 root root 47 Feb 6 2012 device.map
> -rw-r--r--. 1 root root 46 Feb 6 2012 device.map.old
> -rw-r--r--. 1 root root 8576 May 11 2010 e2fs_stage1_5
> -rw-r--r--. 1 root root 7840 May 11 2010 fat_stage1_5
> -rw-r--r--. 1 root root 7104 May 11 2010 ffs_stage1_5
> -rw-r--r--. 1 root root 7104 May 11 2010 iso9660_stage1_5
> -rw-r--r--. 1 root root 8576 May 11 2010 jfs_stage1_5
> -rw-------. 1 root root 1701 Mar 27 15:26 menu.lst
> -rw-------. 1 root root 1694 Feb 6 2012 menu.lst.old
> -rw-r--r--. 1 root root 7264 May 11 2010 minix_stage1_5
> -rw-r--r--. 1 root root 9600 May 11 2010 reiserfs_stage1_5
> -rw-r--r--. 1 root root 512 May 11 2010 stage1
> -rw-r--r--. 1 root root 101962 Feb 6 2012 stage2
> -rw-r--r--. 1 root root 7456 May 11 2010 ufs2_stage1_5
> -rw-r--r--. 1 root root 6656 May 11 2010 vstafs_stage1_5
> -rw-r--r--. 1 root root 9288 May 11 2010 xfs_stage1_5
>
> And would be able to jump from Coreboot to start executing stage1 (MBR)?
>
> Actually, I don't mind having *.elf which will somehow jump to /boot/grub (?) from Coreboot to see in the /boot all these kernels?
>
> Any GRUB BKM web page for that?
>
> Thank you,
> Zoran
> _______
> Most of The Time you should be "intel inside" to be capable to think "out of the box".
>
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen, Deutschland
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895
> Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
prev parent reply other threads:[~2013-07-23 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:47 How to make/compile and link Open Source gnu-2.00 package? Stojsavljevic, Zoran
2013-07-23 14:15 ` Stojsavljevic, Zoran
2013-07-23 16:58 ` Andrey Borzenkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130723205848.228fcdab@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zoran.stojsavljevic@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.