From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
Subject: Re: Testing on PowerMac G4
Date: Tue, 1 Jan 2008 00:34:51 +0100 [thread overview]
Message-ID: <20071231233451.GA6782@thorin> (raw)
In-Reply-To: <1199140655.7332.15.camel@dv>
On Mon, Dec 31, 2007 at 05:37:35PM -0500, Pavel Roskin wrote:
>
> On Mon, 2007-12-31 at 09:45 +0100, Jan Nieuwenhuizen wrote:
> > Pavel Roskin writes:
> >
> > > However, GRUB starts in the rescue mode,
> > > and I cannot do anything in that mode.
> >
> > In rescue mode, type
> >
> > insmod normal
> > normal
> >
> > That will print the error why the menu is not started, because
> > this should have been automatic, or else it will starts the menu.
>
> Oh well, that PowerMac G4 won't work at all anymore (looks like a
> hardware failure, there is no video output), so I'm trying it on
> PowerMAC G3 (Blue&White).
>
> I copied grub.cfg and kernel.elf to the root of the HFS boot partition
> hd:2. I entered openfirmware on startup by holding Alt-Mac-O-F. I used
> "dir hd:2,\" to check that kernel.elf is there. Then I loaded it with
> "boot hd:2,\kernel.elf". That's what I got:
>
> grub rescue> insmod normal
> error: unknown device
> grub rescue> normal
> unknown command `normal'
> Try `help' for usage
> grub rescue> lsmod
> Name Ref Count Dependencies
> grub rescue> set
> prefix=(ultra0,2)
> root=ultra0,2
> grub rescue> ls
> (ide0/disk) DISK-LABEL: read of block0 failed
> (cd) DISK-LABEL: read of block0 failed
> (zip) (ide1/disk) (hd) (utltra0)
>
> My guess is kernel.elf doesn't include the necessary code. It's about
> 60k long.
Sounds like "DISK-LABEL: read of block0 failed" is printed by the firmware
and not by GRUB.
Also, device enumeration is the same for all devices, so the fact that it
only appears for some of them hints at a firmware bug.
What happens if you set debug=disk ?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-12-31 23:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 8:12 Testing on PowerMac G4 Pavel Roskin
2007-12-31 8:45 ` Jan Nieuwenhuizen
2007-12-31 22:37 ` Pavel Roskin
2007-12-31 23:34 ` Robert Millan [this message]
2008-01-02 6:46 ` Pavel Roskin
2008-01-02 10:32 ` Robert Millan
2008-01-03 8:09 ` Pavel Roskin
2008-01-03 12:11 ` Robert Millan
2008-01-03 15:28 ` Pavel Roskin
2008-01-03 15:57 ` Robert Millan
2008-01-03 16:23 ` Pavel Roskin
2008-01-04 12:32 ` Robert Millan
2008-01-04 12:54 ` Robert Millan
2008-01-04 18:26 ` Pavel Roskin
2008-01-04 20:37 ` Robert Millan
2008-01-05 1:45 ` Yoshinori K. Okuji
2008-01-05 11:43 ` Robert Millan
2008-01-05 2:10 ` Pavel Roskin
2008-01-05 11:45 ` Robert Millan
2008-01-05 1:27 ` Yoshinori K. Okuji
2008-01-05 2:02 ` Pavel Roskin
2008-01-05 10:31 ` Yoshinori K. Okuji
2008-01-05 11:46 ` Robert Millan
2007-12-31 14:04 ` Robert Millan
2007-12-31 22:58 ` Pavel Roskin
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=20071231233451.GA6782@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=janneke-list@xs4all.nl \
/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.