From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: boot/i386/pc/startup_raw.S:115: Error: attempt to move .org backwards
Date: Thu, 17 Nov 2011 01:44:04 +0100 [thread overview]
Message-ID: <4EC458D4.2090602@gmail.com> (raw)
In-Reply-To: <CAAJw_ZsFcae4rATuK4oMNV7bJzVfAQd5_gJw1t7tXhR59S-zzQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On 17.11.2011 01:29, Jeff Chua wrote:
> 2011/11/15 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>> On 14.11.2011 15:46, Jeff Chua wrote:
>>> I'm getting this error trying to compile grub2 from bzr. The bzr pull
>>> prior to Nov 11 compiled ok.
>>>
>> Try increasing
>> #define GRUB_KERNEL_I386_PC_NO_REED_SOLOMON_PART 0x6e0
>> in include/grub/offsets.h, but keep it divisible by 8 and don't increase
>> too much.
> Vladimir,
>
> I increased from 0x6e0 to 0x7f0 (the smallest that works)
Ouch, that's vast difference
> so it
> compiled without any problem. Booted and it's stuck at the very first
> grub notification "grub ...".
Make sure that you don't try to use old grub-setup with new images or
vice-versa. Also another possible trouble is gcc adding unexpected
sections. Can you submit your lzma_decompress.image?
>
> Jeff
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-11-17 0:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 14:46 boot/i386/pc/startup_raw.S:115: Error: attempt to move .org backwards Jeff Chua
2011-11-14 14:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-14 16:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 0:29 ` Jeff Chua
2011-11-17 0:44 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-17 0:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 5:23 ` Jeff Chua
2011-11-17 10:13 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 15:38 ` Jeff Chua
2011-11-17 16:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 16:30 ` Jeff Chua
2011-11-17 16:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 17:40 ` Jeff Chua
2011-11-17 17:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 18:07 ` Jeff Chua
2011-11-17 18:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 18:36 ` Jeff Chua
2011-11-17 19:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-18 0:04 ` Jeff Chua
2011-11-21 7:32 ` Jeff Chua
2011-11-21 22:22 ` Jeff Chua
2011-11-21 22:42 ` Fwd: " Jeff Chua
2011-11-25 13:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-01 7:21 ` Jeff Chua
2011-12-01 7:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-23 9:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 9:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4EC458D4.2090602@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).