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 19:17:08 +0100	[thread overview]
Message-ID: <4EC54FA4.4070303@gmail.com> (raw)
In-Reply-To: <CAAJw_Zu-qa9zyFTkNKH8fTuHpTVHbkM5-gtPooF7L_brWwoyeg@mail.gmail.com>

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

On 17.11.2011 19:07, Jeff Chua wrote:
> 2011/11/18 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>
>> I suppose make, sudo make install and sudo grub-install /dev/sdX as well.
>>> Tried "grub-emu" and it runs fine, but on "real" pc, it doesn't run.
> Done all that, in fact, using "root" and not sudo.
>
>> Does it work in qemu? (sudo qemu /dev/sda, be sure not to launch the OS
>> though)
> "qemu /dev/sda" ... same issue, stuck in ... (at least this is better
> than reboot the real PC).
>
> Booting from Hard Disk...
> GRUB loading.
> _
>
>
> Again, installing from Nov 14 src and "qemu /dev/sda" works.
Which exact revision does it refer to? Did you try r3607? The only
serious commit in that time is 3609
>
> 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 18:17 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
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 [this message]
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=4EC54FA4.4070303@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).