grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
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 17:15:30 +0100	[thread overview]
Message-ID: <4EC53322.2070805@gmail.com> (raw)
In-Reply-To: <CAAJw_ZvyjKhrwecUHyPb2y=q9P2se_D7Y2PypZJ-wUozT9B6jA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

On 17.11.2011 16:38, Jeff Chua wrote:
> 2011/11/17 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>
>> Is it "GRUB" or "GRUB Loading"?
>
> Vladimir,
>
> It's "GRUB Loading".
>
>
>> Your lzma_decompress.image is fine (as in: I added it into my build
>> system and then resulting grub-mkrescue image still works fine. I will
>> need your diskboot.img, boot.img lzma_decompress.img, core.img and
>> kernel.img.
> Can't find the "core.img" file. The rest of the files are attached.
core.img is in /boot/grub. I still was unable to reproduce. All of the
files you sent are fine. Are you sure that your grub-mkimage and
grub-setup were updated?
Do you have an x86-64 or i386 system?
> Thanks,
> 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 --]

  reply	other threads:[~2011-11-17 16:15 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
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 [this message]
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=4EC53322.2070805@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).