Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@wanadoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added stage2 ldscripts
Date: Thu, 21 Nov 2013 15:47:25 +0100	[thread overview]
Message-ID: <528E1CFD.2070000@wanadoo.fr> (raw)
In-Reply-To: <20131121114731.3623f716@skate>

Le 21/11/2013 11:47, Thomas Petazzoni a ?crit :
> Dear Thierry Bultel,
>
> On Thu, 21 Nov 2013 11:04:25 +0100, Thierry Bultel wrote:
>
>> I have taken your branch and compiled it. I am testing like this:
>>
>> sudo kvm -cdrom rootfs.iso9660
>>
>> which works with upstream + the lscript patch
>>
>> However, on your branch, the grub menu does not show up, I am only
>> getting the grub minimal prompt. For the moment I cannot figure out why.
>>
>> So that would mean that stage2 is OK but there is another extra issue.
>
> I *believe* this usually means that it can't find the grub
> configuration file.

Yes that's the point. I have attempted to debug:
grub_open fails on /boot/grub/menu.lst

But when I mount my iso image, it is there:

$ ls /mnt/boot/grub/
menu.lst         stage2_eltorito

I finally found out that it is grub does not support the iso9660 filesystem.

I have added it to the list of supported ones and it works.
That is a little bit annoying to have to do it manually.

On your branch it is explicitly deselected when configured, whereas it 
was configured by default on mainstream.

I think it could be could to :
1) Set the supported FS as choices in xconfig
2) Make iso9660 automatically selected when an iso image must be built

Regards
Thierry


>
> Thomas
>

  reply	other threads:[~2013-11-21 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 22:33 [Buildroot] [PATCH 1/1] Added stage2 ldscripts Thierry Bultel
2013-11-21  8:13 ` Thomas Petazzoni
2013-11-21 10:04   ` Thierry Bultel
2013-11-21 10:47     ` Thomas Petazzoni
2013-11-21 14:47       ` Thierry Bultel [this message]
2013-11-21 15:05         ` Thomas Petazzoni
2014-04-20 10:16 ` Thomas Petazzoni

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=528E1CFD.2070000@wanadoo.fr \
    --to=thierry.bultel@wanadoo.fr \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox