From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unable to install the bootloader
Date: Wed, 14 Jun 2017 15:54:36 +0100 [thread overview]
Message-ID: <1497452076.2416.2.camel@ipfire.org> (raw)
In-Reply-To: <a7219ec34b4177e449cba1e2b4a36ef2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Hi,
this is actually not a bug in GRUB.
It is that the kernel denied to declare some memory as writable and
executable at the same time.
It is fixed in this commit:
http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=5e00841da0f8a9350827a73719ca04295dbb719f
So rebuilding next will fix it without updating GRUB.
Best,
-Michael
On Wed, 2017-06-14 at 15:05 +0200, Marcel Lorenz wrote:
> Hi,
>
> have the same Problem, but with Grub 2.02 (without beta), the
> installer
> works.
> A patch is on Patchwork.
>
> Best,
> Marcel
>
>
> Am 2017-06-14 07:17, schrieb Wolfgang Apolinarski:
> > Hi!
> >
> > Since Sunday I'm trying to provide you with an updated version of
> > the
> > apache 2.4 patch. Usually, the build takes ~ 3h on my machine, so I
> > can perform one compilation per day, after work.
> >
> > In recent days, I had trouble to create a running image, even from
> > the
> > current next. Even if the build is executed successfully, the image
> > will not install on my virtual box machine with the error message
> > "Unable to install the bootloader" (after it successfully
> > partitioned
> > the virtual hdd and copied the files).
> >
> > Is this a known problem? Am I doing something wrong?
> >
> > Best regards,
> > Wolfgang
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-06-14 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 5:17 Wolfgang Apolinarski
2017-06-14 13:05 ` Marcel Lorenz
2017-06-14 14:54 ` Michael Tremer [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=1497452076.2416.2.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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