All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vernon Mauery <vernon-grub@mauery.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 1.90 is released
Date: Wed, 10 Aug 2005 09:06:32 -0700	[thread overview]
Message-ID: <42FA2608.80600@mauery.com> (raw)
In-Reply-To: <200508071939.45278.okuji@enbug.org>

Yoshinori K. Okuji wrote:
> I'm happy to announce the release of GRUB 1.90. This is the first of
> our prereleases leading up to GRUB 2.0. We encourage you to try it, as
> we have done a significant amount of work towards GRUB 2. Note that this 
> release is mainly for developers who are willing to contribute to our 
> project. If you need a working solution immediately, you'd better to stick to 
> GRUB Legacy at the moment.

I am seeing unaligned pointer messages when I use grub2 on /dev/hda2.  If I type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I type 'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unaligned pointer 0x7ff64'.

I downloaded the source, built it and installed it on my hard drive to test it out.  I had an unused partition that contains a fork of my live system, so I figured I could put grub2 on that.  That partition was hda3 (hd0,2).  So I ran grub-install /dev/hda3 and that went okay.  The files showed up in the right spot in /boot/grub.  Then I ran grub-setup "(hd0,2)" which also went fine.  I tried booting the image in bochs and qemu using /dev/hda as the drive for the emulated machine, chainloading from grub-legacy on (hd0) to grub2 on (hd0,2).  I get the grub prompt and all looks fine until I try to do something interesting.  Then I got the above messages.  I tried running on the actual harware rather than the emulator, but that gave the same messages, so I figured I should report them.

--Vernon



  parent reply	other threads:[~2005-08-10 16:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 17:39 GRUB 1.90 is released Yoshinori K. Okuji
2005-08-09  3:21 ` Hollis Blanchard
2005-08-09  6:32   ` Yoshinori K. Okuji
2005-08-09 13:43     ` Hollis Blanchard
2005-08-09 14:21       ` Marco Gerards
2005-08-09 18:47         ` Yoshinori K. Okuji
2005-08-09 20:56           ` Marco Gerards
2005-08-09 18:42       ` Yoshinori K. Okuji
2005-08-09 21:04         ` Marco Gerards
2005-08-10  1:19         ` Hollis Blanchard
2005-08-10 16:06 ` Vernon Mauery [this message]
2005-08-10 17:21   ` Vincent Pelletier
2005-08-10 17:40     ` Vernon Mauery
2005-08-10 19:59       ` Vladimir Serbinenko
2005-08-10 20:44         ` Vincent Pelletier
2005-08-11  9:17           ` Marco Gerards
2005-08-11 10:57             ` Vincent Pelletier
2005-08-11 11:22               ` Marco Gerards
2005-08-11 13:58                 ` Yoshinori K. Okuji
2005-08-11 14:47                   ` Vladimir Serbinenko
2005-08-12 20:11                     ` Yoshinori K. Okuji
2005-08-14  7:47                       ` Vladimir Serbinenko
2005-08-14 14:31                         ` Yoshinori K. Okuji
2005-08-14 14:56                           ` Vladimir Serbinenko
2005-08-10 20:56         ` Vernon Mauery
2005-08-10 20:56   ` Yoshinori K. Okuji
2005-08-10 21:50     ` Vernon Mauery
2005-08-10 23:08       ` Yoshinori K. Okuji

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=42FA2608.80600@mauery.com \
    --to=vernon-grub@mauery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.