All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]
Date: Wed, 22 Jul 2009 19:57:49 +0200	[thread overview]
Message-ID: <20090722175749.GO8706@thorin> (raw)
In-Reply-To: <1248277541.3517.25.camel@fz.local>

On Wed, Jul 22, 2009 at 05:45:41PM +0200, Felix Zielcke wrote:
> Hi David,
> 
> could you please have a look at this?
> It's a sparc problem.
> 
> -------- Weitergeleitete Nachricht --------
> > Von: Alexander Vlasov <Alexander.Vlasov@Sun.COM>
> > Reply-to: Alexander Vlasov <Alexander.Vlasov@Sun.COM>,
> > 538030@bugs.debian.org
> > An: submit@bugs.debian.org
> > Betreff: Bug#538030: grub-ieee1275 fails to install bootblock
> > Datum: Wed, 22 Jul 2009 17:26:05 +0200
> > 
> > Package: grub-ieee1275
> > Version: 1.96+20090709-1
> > Severity: normal
> > 
> > I got a problem trying to setup grub as a bootloader on Ultra45 machine with 
> > LSI SAS controller.
> > 
> > Namely, after installing a package I tried to run grub-install, but it failed 
> > with following diagnostic message:
> > 
> > ---
> > grub-mkdevicemap: error: Cannot open SAS PHY ID 
> > '/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/phy_identifier'
> > ---

I think we should make GRUB tollerant to broken device.map on sparc, like
we did for i386-pc.  But I'm not sure if this is possible.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  parent reply	other threads:[~2009-07-22 17:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 15:45 sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock] Felix Zielcke
2009-07-22 15:49 ` David Miller
2009-08-27  9:40   ` Felix Zielcke
2009-07-22 17:57 ` Robert Millan [this message]
2009-07-22 18:05   ` David Miller
2009-07-22 18:11     ` Felix Zielcke
2009-07-22 18:20       ` David Miller
2009-07-23 17:26     ` Alexander Vlasov

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=20090722175749.GO8706@thorin \
    --to=rmh@aybabtu.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.