From: David Miller <davem@davemloft.net>
To: grub-devel@gnu.org, rmh@aybabtu.com
Subject: Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]
Date: Wed, 22 Jul 2009 11:05:23 -0700 (PDT) [thread overview]
Message-ID: <20090722.110523.193703852.davem@davemloft.net> (raw)
In-Reply-To: <20090722175749.GO8706@thorin>
From: Robert Millan <rmh@aybabtu.com>
Date: Wed, 22 Jul 2009 19:57:49 +0200
> On Wed, Jul 22, 2009 at 05:45:41PM +0200, Felix Zielcke wrote:
>> > 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.
I'll look into this when I can next month.
But for the initial bug this user has, can we find out what lives
inside of this directory:
/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/
and if that directory doesn't exit, can they go back one directory node
at a time until something appears?
next prev parent reply other threads:[~2009-07-22 18:05 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
2009-07-22 18:05 ` David Miller [this message]
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=20090722.110523.193703852.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grub-devel@gnu.org \
--cc=rmh@aybabtu.com \
/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.